---
sourceDocument: Xanadu Strategic Portfolio Management
sourceDocumentLink: https://www.servicenow.com/docs/r/xanadu/it-business-management

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Strategic Portfolio Management

ft:clusterId :

    - itbm

bundleId :

    - itbm

workflow :

    - Technology


---

# Associate existing RIDAC (Risks, Issues, Actions, Decisions, and Request Changes) records for a project

# Associate existing RIDAC (Risks, Issues, Actions, Decisions, and Request Changes) records
for a project {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Link existing RIDAC records (risks, issues, actions, decisions, and request changes)
to one another for your project. Associating RIDAC records with each other enables you to
keep a record of risks or issues and their outcome for analysis at project closure and
planning. It also helps to track the risks and issues throughout the project life cycle.

## Before you begin

Role required: it_project_manager

## About this task

You can associate one record with multiple different records. For example, you can
link one issue record to multiple risk, decision, action, or request change
records.

## Procedure

1. Navigate to ProjectProjectsAll.
2. Select the project for which you want to associate one RIDAC entry to another.
3. In the Project form related list, select the RIDAC record.
4. On the form, click the Associate RIDAC related link.
5. In the Associate dialog box, from the Select type list, select the RIDAC record to which you want to associate the selected record.  
   For example, if you wanted to associate a risk to an issue, you would select Issue.
6. Select the record number to which you want to associate the selected record from the Associate to list.  
   For example, if you wanted to associate the selected risk to issue (ISU0010003), you would select ISU0010003.
7. Click OK.
{#reassociate-ridac-project__steps_xll_gbc_yjb}

*[\>]: and then