---
title: "Shared configuration"
canonical: "https://support.appfire.com/space/RM/3482419360/Shared%20configuration"
format: markdown
---
Shared configuration creates and maintains the Jira configuration required for Appfire LiveRisk risk registers.
LiveRisk manages this configuration centrally for the Jira site. Individual risk registers then use the shared workflows, fields, screens, roles, permission scheme, and other Jira configuration created here.
Open **Jira admin settings** > **Marketplace apps** > **Appfire LiveRisk admin** > **Configuration**.
When the page opens, LiveRisk automatically checks the managed configuration and reports whether anything is missing or has changed.
## Check the configuration
LiveRisk validates 14 managed components. Each component displays its current status:
- **Green** — the configuration matches what LiveRisk expects.
- **Yellow** — LiveRisk has detected configuration drift.
- **Red** — required configuration is missing.
Expand a component to see the Jira objects associated with it. If LiveRisk detects drift, click **Show drift** to see which configuration properties differ.
To check the configuration again without making any changes, click **Reload**.
If configuration is missing or has drifted, click **Create or update** to apply the required changes.
If one or more update steps fail, LiveRisk identifies the failed steps and warns that the configuration may be only partially applied. Fix the cause of the failure, then run **Create or update** again.
## What LiveRisk manages
Shared configuration manages the following Jira components:
| **#** | **Component** | **What LiveRisk configures** |
| --- | --- | --- |
| 1 | **Issue Types** | Risk and Risk Treatment Plan |
| 2 | **Issue Link Types** | Risk Relation, Evidence, Treatment Plan, and Treatment Work |
| 3 | **Custom Fields** | Risk fields for categories, vulnerabilities, threats, controls, treatment decisions, review schedules, risk scores, source information, AI features, approval modes, and related data |
| 4 | **Project Roles** | LiveRisk Manager, LiveRisk Analyst, and LiveRisk Service |
| 5 | **Permission Scheme** | The permissions required to access and manage Risk registers.
LiveRisk creates the **LiveRisk Risk Management Permission Scheme**.
The scheme grants the permissions required by the **LiveRisk Manager** and **LiveRisk Analyst** roles, including **Manage LiveRisk Risk Register**.
The **LiveRisk Manager** role also receives Jira's **Administer Projects** permission.
The permission scheme is assigned to a risk register when the register is created or when its configuration is updated from the **Risk Registers** page. Updating Shared Configuration does not automatically reassign the permission scheme to every existing Risk register. |
| 6 | **Workflows** | Risk Management and Risk Treatment Plan workflows |
| 7 | **Workflow Scheme** | Maps the Risk and Risk Treatment Plan work item types to their workflows |
| 8 | **Field Configuration** | Required Description field and LiveRisk custom fields |
| 9 | **Field Configuration Scheme** | Associates the LiveRisk field configuration with Risk registers |
| 10 | **Screens** | Screens used to create, view, and edit Risk work items and standard Jira work items |
| 11 | **Screen Schemes** | Associates the configured screens with the relevant work item types |
| 12 | **Issue Type Scheme** | The Issue Type Scheme includes the work item types used by LiveRisk.
If **Task** or **Sub-task** is not available as a global work item type on the Jira site, LiveRisk leaves it out of the scheme. |
| 13 | **Issue Type Screen Scheme** | Routes Risk work items to the Risk screens and other work item types to the appropriate screens |
| 14 | **UI Modifications** | Renames **Assignee** to **Owner** for Risk work items |
## Force an update
Use **Force update** to reapply the complete shared configuration, even when LiveRisk reports that the configuration is healthy.
Use this option when:
- you are troubleshooting a configuration problem, or
- Appfire Support instructs you to reapply the configuration.
For normal setup and configuration drift, use **Create or update** instead.
## Purge the shared configuration
**Purge** removes the shared Jira configuration created by LiveRisk.
> ⚠️ Purge is intended for teardown, not routine maintenance. Before purging the shared configuration, remove or detach any Risk registers that still depend on it.
## Next step
Once the shared configuration is healthy, continue with [Risk registers](https://appfire.atlassian.net/wiki/spaces/RM/pages/3459383719) to create a Risk register for a Jira space.