---
title: "Risk registers"
canonical: "https://support.appfire.com/space/RM/3459383719/Risk%20registers"
format: markdown
---
Use this page to create risk registers for Jira spaces and manage the configuration of existing risk registers.

A risk register enables Appfire LiveRisk in a Jira space. Each risk register stores your organization's risks, signals, dashboards, and space-specific configuration while sharing the site-wide configuration created during platform setup.

The **Risk registers** table (**Jira admin settings** > **Marketplace apps** > **Appfire LiveRisk admin** > **Configuration**) lists every LiveRisk risk register configured on your Jira site together with its current status. From here, you can create new risk registers, convert existing Jira spaces, and verify or update space configuration.

![Appfire LiveRisk admin panel showing the Risk registers table.](media://a4be050d-90e5-4401-9de3-bb28717a1ae3)

## Before you begin

- Before creating your first risk register, complete the steps listed in **[Shared configuration](https://appfire.atlassian.net/wiki/spaces/RM/pages/3482419360)**.
- Creating a new risk register is the recommended approach. If you convert an existing Jira space instead, LiveRisk replaces its current permission scheme. [Review the access changes](https://appfire.atlassian.net/wiki/spaces/RM/pages/3496575012/Roles+and+permissions#Access-when-converting-an-existing-space) before converting the space.

## Risk register status

The table includes the following information:

| **Column** | **Description** |
| --- | --- |
| **Key** | The Jira space key. |
| **Name** | The name of the Jira space. |
| **State** | Whether the risk register configuration is **VALID** or **INVALID**. An **INVALID** state means that the register configuration no longer matches the shared LiveRisk configuration. |
| **Work items** | The number of work items in the space. Click **Load** to retrieve the count. |
| **Signals** | The number of signals stored for the risk register. Click **Load** to retrieve the count. |
| **Actions** | Configuration actions available for the risk register. |

The **Work items** and **Signals** counts are loaded on demand. If a count cannot be retrieved, LiveRisk displays **Failed** with an option to retry.

## Create a risk register

Create a new risk register when you want LiveRisk to provision a dedicated Jira space for managing risks.

1. Click **Add register**.
2. In the *Add a risk register* pop-up, enter a **Space name** and **Space key**.
3. Search for and select a space owner.
4. Click **Create**.

LiveRisk creates the Jira space and automatically applies the shared configuration required for a risk register.

LiveRisk automatically adds the following to the **LiveRisk Manager** role:

- The space lead
- The user creating the risk register
- The LiveRisk app user

The **LiveRisk Analyst** role starts empty. Add users or groups to this role when they need to govern and work with risks without configuring the risk register.

> ℹ️ See **[Roles and permissions](https://appfire.atlassian.net/wiki/spaces/RM/pages/3496575012)** for details about LiveRisk roles and permissions.

## Convert an existing Jira space

If you already have a Jira space that you want to use with LiveRisk, you can convert it into a risk register instead of creating a new space.

> ⚠️ ### Before you begin
> ⚠️ 
> ⚠️ Converting an existing space changes its Jira permission scheme to the **LiveRisk Risk Management Permission Scheme**.
> ⚠️ 
> ⚠️ This can change who is able to open and work in the space. Users who previously had access through the old permission scheme may lose that access if they are not included in an appropriate LiveRisk role.
> ⚠️ 
> ⚠️ Before converting a space:
> ⚠️ 
> ⚠️ - Identify the people and groups that currently need access.
> ⚠️ - Check whether anyone administers the space through custom roles or groups.
> ⚠️ - Decide who should be added to **LiveRisk Manager** or **LiveRisk Analyst** after conversion.
> ⚠️ 
> ⚠️ During conversion, LiveRisk automatically adds the following to **LiveRisk Manager**:
> ⚠️ 
> ⚠️ - The space lead
> ⚠️ - The user performing the conversion
> ⚠️ - The LiveRisk app user
> ⚠️ - Users and groups assigned to Jira's **Administrators** role in the existing space
> ⚠️ 
> ⚠️ Other users and groups are not automatically assigned to a LiveRisk role.
> ⚠️ 
> ⚠️ LiveRisk preserves the existing work items in the space. However, users who are not granted access through the new permission scheme can lose access to the space and its existing work items, including non-risk work items.

1. Click **Add register **>** Convert existing**.
2. Search for and select an existing Jira space.
3. Click **Convert**.

The space is updated with the required shared configuration and becomes available as a risk register.

## Validate a risk register

Risk registers can become out of sync with the shared configuration after configuration changes or app upgrades. Use **Integrity check** to compare the configuration of a risk register with the configuration expected by LiveRisk.

1. Locate the risk register in the table.
2. Click **Integrity check**.

If the register is reported as invalid, click **Update configuration** from the same menu to reapply the required configuration.

After repairing shared configuration drift or applying schema changes, run **Integrity check** for each risk register to confirm that the space configuration is healthy.