---
title: "Get started as a site administrator"
canonical: "https://support.appfire.com/space/RM/3459383688/Get%20started%20as%20a%20site%20administrator"
format: markdown
---
As a site administrator, you're responsible for preparing your Jira site for Appfire LiveRisk. This includes setting up the shared Jira configuration, creating risk registers, and configuring optional connections used across your organization.

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

Open the **Appfire LiveRisk admin** panel from **Jira admin settings** > **Marketplace apps** > **Appfire LiveRisk admin**.

Complete the following tasks in order.

## 1. Complete the shared configuration

Start by creating and validating the shared Jira configuration that LiveRisk uses across your Jira site.

LiveRisk manages 14 shared components, including work item types, custom fields, roles, workflows, screens, and the permission scheme. From the *Configuration* tab, you can check their status and create or update anything that is missing or has changed.

When the shared configuration is healthy, continue with creating a risk register.

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

---

## 2. Create a risk register

After the shared configuration is complete, create your first risk register.

A risk register enables LiveRisk in a Jira space. You can create a new Jira space for the risk register or convert an existing space.

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

---

## 3. Grant access

After creating a risk register, make sure the people who will work with LiveRisk have the appropriate access.

LiveRisk uses Jira permissions to control access:

- **Manage LiveRisk Risk Register** provides access to the features used to run and govern the risk register. The **LiveRisk Manager** and **LiveRisk Analyst** roles have this permission by default.
- **Administer Projects** provides access to the LiveRisk configuration under **Space settings**. The **LiveRisk Manager** role has this permission by default.

If you use your own Jira role to provide LiveRisk access, grant it **Manage LiveRisk Risk Register**. Users also need the Jira permissions required to access and work in the space, such as **Browse Projects** and **Edit Issues**.

For more information, see **[Roles and permissions](https://appfire.atlassian.net/wiki/spaces/RM/pages/3496575012)**.

---

## 4. Configure External Atlassian connections (optional)

If you want to exchange data with another Jira site running LiveRisk, configure an External Atlassian connection.

This step is optional and is required only if your organization needs to share LiveRisk data between Jira sites.

For more information, see **[External Atlassian connections](https://appfire.atlassian.net/wiki/spaces/RM/pages/3459252588)**.

---

## Before you finish

Before handing LiveRisk over to your teams, verify that:

- [ ] The shared configuration is healthy.
- [ ] At least one risk register has been created.
- [ ] Users who need to work with or govern the risk register have **Manage LiveRisk Risk Register**.
- [ ] Users who need to configure LiveRisk for the space have **Administer Projects**.
- [ ] External Atlassian Connections have been configured, if necessary.