---
title: "Space administration"
canonical: "https://support.appfire.com/space/RM/3459875012/Space%20administration"
format: markdown
---
Use **Space administration** to configure Appfire LiveRisk for the risk register in a specific Jira space.

The settings here control how risks are scored and classified, which external sources provide data, and which compliance frameworks are available in the space.

To open the page, go to **Space settings** > **Apps** > **Appfire LiveRisk**. 

![Space settings page showing the Appfire LiveRisk entry used to open the Space administration page.](media://0c48e2f7-c45d-42e3-9199-76082a95c7ee)

> ℹ️ For a quickstart, see [Get started as a space administrator](https://appfire.atlassian.net/wiki/spaces/RM/pages/3459154965).

## Before you begin

- The Jira space must already have a risk register. A site administrator can create a risk register for a new space or add one to an existing space from **Site administration** >** ****[Risk registers](https://appfire.atlassian.net/wiki/spaces/RM/pages/3459383719)**.  
If the current space isn't configured as a risk register, LiveRisk displays a `This project is not a risk register` warning with a link to the LiveRisk admin page.
- You need Jira's **Administer Projects** permission for the space to access LiveRisk configuration. The **LiveRisk Manager** role has this permission by default. If you use a custom Jira role, grant it **Administer Projects** to allow users to configure LiveRisk.
- The shared LiveRisk configuration, including its work item types, fields, screens, workflows, roles, and permission scheme, must be set up for the Jira site. See [Shared configuration](https://appfire.atlassian.net/wiki/spaces/RM/pages/3482419360).

> 📝 If you open the page and see `Project context unavailable`, open it from **Space settings**, not a direct link.

## Available settings

Space administration includes:

- **[Sources](https://appfire.atlassian.net/wiki/spaces/RM/pages/3459219866)**: Connect and manage Wiz, Snyk, Drata, and OneTrust integrations.
- **[Risk matrix](https://appfire.atlassian.net/wiki/spaces/RM/pages/3459187103)**: Define the matrix size, axes, scoring tiers, and risk appetite.
- **[Risk categories](https://appfire.atlassian.net/wiki/spaces/RM/pages/3459776802)**: Create the categories used to classify risks.
- **[Risk vulnerabilities](https://appfire.atlassian.net/wiki/spaces/RM/pages/3459449304)**: Manage the vulnerabilities that can be associated with risks.
- **[Risk threats](https://appfire.atlassian.net/wiki/spaces/RM/pages/3459383729/Risk+threats?atl_f=PAGETREE)**: Manage the threats that can be associated with risks.
- **[Controls](https://appfire.atlassian.net/wiki/spaces/RM/pages/3459121502)**: Enable the compliance frameworks and controls available for risks.

> ℹ️ All settings on these tabs apply only to the current space's risk register.

## Recommended setup order

Complete the initial space configuration in the following order:

1. **Confirm the space is a risk register.**  
A site administrator creates a new risk register or converts an existing Jira space.
2. **Configure the risk matrix.**  
Set the matrix size and axes, define the scoring tiers, and set the risk appetite before users begin scoring risks.
3. **Enable controls and compliance frameworks.**   
Select the frameworks your organization uses for risk reporting and governance.
4. **Configure the risk taxonomy.**    
Add the categories, vulnerabilities, and threats users can select when working with risks. These settings are optional and can also be populated from supported source data where applicable.
5. **Connect your sources.**   
Configure Wiz, Snyk, Drata, or OneTrust and complete the initial synchronization or import.

After the risk register is configured, users with the appropriate LiveRisk permissions can begin creating, assessing, treating, and monitoring risks.