---
title: "Get started as a space administrator"
canonical: "https://support.appfire.com/space/RM/3459154965/Get%20started%20as%20a%20space%20administrator"
format: markdown
---
As a space administrator, you’re responsible for configuring a LiveRisk risk register for your team. This includes defining how risks are scored, enabling compliance frameworks, setting up risk classifications, and optionally, connecting external sources.

This guide walks you through the recommended setup process and links to the detailed documentation for each task.

You perform these tasks from **Space settings** > **Apps** > **Appfire LiveRisk**.

---

## Before you begin

- The space must already be configured with a risk register by a site or organization administrator. All settings you change here apply only to the current space.
- You need Jira's **Administer Projects** permission to configure LiveRisk from **Space settings**. The **LiveRisk Manager** role has this permission by default. The **LiveRisk Analyst** role does not.

---

## 1. Configure the risk matrix

Start by defining how risks are scored and displayed in this space.

Configure the matrix axes and size, define the values on each axis, set up risk tiers, and enter the space’s risk appetite. You can also assign a tier to each cell in the matrix.

Complete this step before users begin scoring risks because the configuration determines the scores, tier badges, colors, and matrix views used throughout the space.

For more information, see **[Risk matrix](https://appfire.atlassian.net/wiki/spaces/RM/pages/3459187103)**.

---

## 2. Enable compliance frameworks

Select the compliance frameworks your team uses to classify and report on risks.

Only enabled frameworks appear in the **Controls** field on risks. They also populate the framework, domain, and control information available in **Security posture**.

For more information, see **[Controls](https://appfire.atlassian.net/wiki/spaces/RM/pages/3459121502)**.

---

## 3. Configure risk classifications

Add the classification values your team will use when documenting risks:

- **Risk categories** group risks by areas such as security, compliance, or operations.
- **Risk vulnerabilities** describe weaknesses associated with a risk.
- **Risk threats** describe events or conditions that could cause harm.

Categories, vulnerabilities, and threats are optional. You can create them manually or import them after connecting a OneTrust source.

For more information, see **[Risk categories](https://appfire.atlassian.net/wiki/spaces/RM/pages/3459776802)**, **[Risk vulnerabilities](https://appfire.atlassian.net/wiki/spaces/RM/pages/3459449304)**, and **[Risk threats](https://appfire.atlassian.net/wiki/spaces/RM/pages/3459383729)**.

---

## 4. Connect external sources (optional)

Connect the security and risk-management tools your team uses:

- **Wiz** imports cloud security findings as Signals.
- **Snyk** imports developer security findings as Signals.
- **Drata** imports compliance risk registers.
- **OneTrust** imports GRC risks through a one-way import.

After connecting Wiz and Snyk, confirm that the initial ingestion starts successfully. For OneTrust and Drata, run the first import manually from the Sources table.

Complete this task only if you want to bring external findings or risks into the space.

For more information, see **[Sources](https://appfire.atlassian.net/wiki/spaces/RM/pages/3459219866)**.

---

## Before you finish

Before handing the risk register over to your team, verify that:

- [ ] The risk matrix has been completed and saved.
- [ ] The required compliance frameworks are enabled.
- [ ] Categories, vulnerabilities, and threats have been added or imported, if your team uses them.
- [ ] External sources have been connected and the initial ingestion or import has completed, if required.