# Admin Configuration Guide

*Audience: risk owners and the GRC, privacy, security, and AI governance teams who build and run the register.*

This guide covers access, every way to add risks, scoring and treatment, controls, monitoring, and working the register view. For the concepts behind it, start with the [Overview and Implementation Guide](/docs/risk-register/overview-and-implementation-guide/).

## Access and permissions

The Risk Register is under **Risks & Issues → Risk Register**. It's on by default for every workspace; if your organization doesn't use it, your Relyance account team can turn it off, which hides the tab and the **Assess risks…** action on assessments.

Access follows the **Data Mapping Foundation** scope (the same scope as Issues, Tasks, and Inventory). See [Configuring Scope Based Permissions](/docs/other-settings/configuring-scope-based-permissions/).

| Permission on Data Mapping Foundation | What the user can do in the register |
|---|---|
| **View** | See the register, open risks, and read their issues and audit log |
| **Edit** | Add, edit, and delete risks; link controls and policies; add risks from assessments |
| Neither | The register is hidden |

**Enable & link** also turns the policy on, so it needs permission to edit policies as well.

## Adding risks

Click **Add risks** in the register toolbar to import or describe risks, or **Risk library** to start from the library. Whichever path you take, nothing is saved until you review the drafts and confirm.

### From the risk library

1. Click **Risk library**. The drawer opens on **Suggested** - risks that map to controls in frameworks you have enabled. Switch to **All** to see the whole library.
2. Narrow the list with **Framework**, **Domain** (**Privacy**, **Security**, **AI**, **Third party**), or **Search the library**.
3. Click a risk to see its description, **Default score** (likelihood × impact), **Threatens** (confidentiality, integrity, availability), **Suggested treatment**, **Controls**, **References**, and **Policies that check these controls**. Where Relyance already sees open issues for it, the drawer says how many, across how many mapped policies.
4. Tick every risk that applies to your organization. Risks already in your register are marked **In your register**.
5. Click **Add risks**. Each risk is added with its default score, suggested treatment, and controls. Rescore it and assign an owner afterwards.

### By importing a register or describing risks

1. Click **Add risks**. The composer asks **What risks should we add?**
2. Do either or both:
    - **Attach files** - a risk register export (CSV or Excel) to bring in every row, or a policy, audit report, or assessment (PDF, Word, or text) to read risks from. Up to 5 files of 10 MB each.
    - **Describe them** - for example, "Import this register and score anything without a score", or "risks of storing customer support transcripts in a third-party LLM". Keep the request under 4,000 characters.
3. Click **Draft risks**. Relyance maps spreadsheet columns, scores, and matches drafts against your register - usually in under a minute.
4. Review the drafts. For each one you can:
    - Untick it to leave it out.
    - Accept **Add to existing risk** where Relyance found the **Same scenario as** a risk already in your register - this adds the import as a source on that risk and leaves its wording and scores as they are.
    - Choose **Keep as a new risk** instead.
5. Click **Add N risks**.

How each kind of input is read:

| Input | How Relyance reads it |
|---|---|
| CSV or Excel | Treated as an existing register: each row is a risk. Relyance maps which column is the title, likelihood, impact, owner, treatment, and so on, and how values like "High" or "Mitigate" translate to the register's scale. Every row is then converted word for word by that mapping. The first 500 rows of each sheet are read. |
| PDF, Word, text, or your request | Read as prose for the risk scenarios it names, up to 25 drafts per request. |

An owner named in a spreadsheet who isn't a user in your workspace is flagged on the draft - assign an owner on the risk once it's added.

### From an assessment

On a completed assessment, open the assessment's actions menu and choose **Assess risks…**. Relyance reads the answered questions next to your register's open risks and lists the **Risks named in this assessment** - each with a suggested likelihood and impact and the questions it was read from. Add the ones that matter as new risks or to risks already in the register. Each one records the assessment as a source.

Where your workspace has the new assessment page, the assessment's **Risks** tab does the same with **Suggest risks from answers**, shows the assessment's risks on a likelihood × impact **Risk map**, and marks suggestions as **In the register**, **Already in place**, or **From answers**.

When the assessment is about an AI use case, the risks it raises apply to that use case automatically.

### From a policy

A policy's detail drawer has a **Risks** section listing the register risks the policy monitors and the library risks whose controls map to it. Click **Add to register** on a library risk to add it from there.

### By hand

Click **Add risks**, then **Fill in manually**, and fill in the form. The only required field is **Risk scenario**: one sentence on what could go wrong and what it would lead to. Everything else can be added later on the risk itself.

## Working on a risk

Click any row to open the risk drawer. The header shows the risk's ID, score, and monitoring state, with its title, **Status**, **Review status**, and owners. Every edit saves as soon as you make it. The drawer has three tabs: **Overview**, **Issues**, and **Audit Logs**.

### Details

Click **Edit details** to change:

- **Description**
- **Categories** - free-text tags; type one and press **Enter**.
- **Confidentiality, integrity, availability** - which the risk threatens.
- **Applies to** - optional. The assets, identities, vendors, services, repositories, domains, AI models, AI agents, AI use cases, MCP servers, DSRs, or assessments the risk is about. Leave it empty for a risk that applies across the organization. What you pick here scopes the issues shown on the risk.

### Scoring and treatment

Set **Likelihood** and **Impact** under **Inherent risk** (before treatment) and **Residual risk** (once treatment is in place). The score and band update immediately. Click **How scores work** for the scale. A risk without both values shows **Not scored**.

Under **Treatment**, pick a type - **Mitigate**, **Accept**, **Transfer**, **Avoid**, or **Not treated** - and record **Treatment details** and a **Due date**.

### Status and review

- **Status** - **Open**, **Closed**, or **Archived**. Closed risks are hidden from the register view by default.
- **Review status** - **Draft**, **In review**, **Changes requested**, or **Approved**. Use it to run your periodic review cycle.

### Controls

Under **Controls**, click **Link a control** and search your frameworks' controls. Mark each one's **Control role**:

- **In place** - an existing control already reducing the risk.
- **Planned treatment** - a control you plan to implement as treatment.

Library risks arrive with their controls already linked.

### Monitoring a risk

The **Monitoring** card shows whether Relyance is watching the risk.

1. Under **Suggested by its controls**, Relyance lists the policies that check this risk's controls, with their open issue counts. Click **Link** on an enabled policy, or **Enable & link** on one that's **Disabled**.
2. To pick any other policy, click **+** (**Link a policy**) and search.
3. If no existing policy fits, click **Create policy** and Relyance builds a new policy from the risk's description.
Some risks can't be checked on the platform at all - for example, a purely contractual or organizational risk. Leave those without a policy and track them through their controls, treatment, and reviews.

Once at least one policy is linked, the risk shows **Monitored by Relyance**. Removing a policy from a risk leaves the policy itself as it is.

### Issues

The **Issues** tab lists the open issues raised by the risk's linked policies, limited to the subjects in **Applies to**. Issues update as your environment changes, each comes with remediation steps, and you can open a ticket in your tracker from an issue through your [workflow connectors](/docs/workflow-connectors/).

### Deleting a risk

Click **Delete risk** in the risk drawer and confirm. Deleting can't be undone - to keep the history, set the status to **Archived** instead.

## Working the register view

- **Columns** - **ID**, **Risk**, **Inherent risk**, **Residual risk**, **Treatment**, treatment due date, **Monitoring**, **Owner**, **Status**, **Review status**, **Applies to**, **Categories**, **Identified**, and **Updated**. Show, hide, and reorder them from the columns control.
- **Group by** - inherent risk, residual risk, status, treatment, monitoring, owner, source, or assessment.
- **Filters** - filter by any of the above, and toggle **Show closed risks** / **Hide closed risks**.
- **Sorting** - by default, highest inherent score first.
- **Deep links** - opening a risk adds it to the page URL, so you can share a link straight to it.

## Configuration checklist

- [ ] Confirm who needs **View** and **Edit** on the Data Mapping Foundation scope.
- [ ] Take the guided tour (**Help → Take a tour of this page**).
- [ ] Seed the register from the **Risk library** and import any existing register.
- [ ] Rescore, assign an owner, and set a treatment on every open risk.
- [ ] Link controls, marking each **In place** or **Planned treatment**.
- [ ] Link a monitoring policy to every risk that can be monitored.
- [ ] Run **Assess risks…** on completed DPIAs, vendor reviews, and AI assessments.
- [ ] Agree a review cadence and use **Review status** to track it.
