---
title: "Associated Persons: Administration & Configuration"
description: Associated person, person of interest
---

[Skip to content](https://support.ravencontrols.com/raven-academy/associated-persons-administration-configuration#main-content)

![word mark primary - dark](https://support.ravencontrols.com/hubfs/word%20mark%20primary%20-%20dark.svg)

Open main navigation

Close main navigation

- [Support](https://support.ravencontrols.com/form)

[Support](https://support.ravencontrols.com/form?hsLang=en-gb)

 How can we help you?

- There are no suggestions because the search field is empty.

1. [Raven Academy](https://support.ravencontrols.com/raven-academy?hsLang=en-gb)
2. [Associated Persons](https://support.ravencontrols.com/raven-academy/associated-persons?hsLang=en-gb)

# Associated Persons: Administration & Configuration

## Associated Persons includes a range of administrative settings that allow your organization to control how records are created, how sensitive information is accessed, and how Person data is managed.

Users with the appropriate permissions can configure Person Status Types, Source Types, field sensitivity, account settings, and access permissions.

This article explains how to manage and configure Associated Persons within Raven.

 Accessing Associated Persons Settings

To manage the feature, go to **Manage \> Associated Persons**.

From here, administrators can access the following configuration areas:

- Person Status Types
- Source Types
- Field Sensitivity
- Settings
- Access Requests
- Audit Trail

You must have the **Configure Associated Persons** permission to manage most configuration options.

 Managing Person Status Types

Person Status Types define the statuses that can be assigned to a Person, such as Banned or Under review.

### How to Create a Person Status Type

1. Go to **Manage \> Associated Persons**.
2. Open the **Person Status Types** tab.
3. Select **New Person Status Type**.
4. Enter a Name for the status.
5. Enable **Restricts entry** if a Person holding this status must not enter the venue.
6. Select Save.

### Managing Existing Status Types

From the Manage menu on a status type, you can:

- Rename the status.
- Set it as restricting entry.
- Stop it from restricting entry.
- Move it up or down the list.
- Archive the status.

Archived status types cannot be applied to new Persons, but existing Persons who hold that status will retain it.

You can restore an archived status type at any time.

**Note:** Changing whether a status restricts entry does not remove existing statuses from Person records.

 Managing Source Types

Source Types define where information about a Person originated, such as a Police tip or Local Authority.

### How to Create a Source Type

1. Go to **Manage \> Associated Persons**.
2. Open the **Source Types** tab.
3. Select **New Source Type**.
4. Enter a Name for the Source Type.
5. Enable **Ask for free-text detail** if users should be able to provide additional information when selecting this source.
6. Select Save.

### Managing Existing Source Types

From the Manage menu, you can rename, reorder, archive or restore Source Types, as well as enable or disable free-text details.

**Note:** Renaming a Source Type updates its name on all Person records that already use it. Archived Source Types are no longer available when creating new records, but existing records retain their assigned source.

 Configuring Field Sensitivity

Field Sensitivity controls which users can view information stored against Associated Persons.

Each field is classified as either General or Restricted.

- **General:** Visible to anyone with permission to open a Person's record.
- **Restricted:** Only visible to users with Restricted clearance.

### How to Manage Field Sensitivity

1. Go to **Manage \> Associated Persons**.
2. Open the **Field Sensitivity** tab.
3. Review the available fields, grouped by category.
4. Choose whether each field should be General or Restricted.

The available field groups include Identity, Status, Assessment, Media, Provenance, Contact and Activity.

Each field also shows how many Person records contain information in that field and which users can currently access it.

### Raising Field Sensitivity

To make a field Restricted, select **Restricted** against the relevant field.

The change takes effect immediately.

### Lowering Field Sensitivity

Changing a field from Restricted to General requires an additional review.

1. Select **General** against each field you want to change.
2. Select **Review the impact**.
3. Review how many Person records contain information in those fields and which permission groups and users will gain access.
4. Enter a Reason for lowering the sensitivity.
5. Select **Lower sensitivity now** to confirm, or **Discard** to cancel.

The reason and change are recorded in the account-wide audit trail.

**Important:** The Person's name, photo, Person Reference and statuses that restrict entry are always visible to users who can open a Person record. These fields cannot be made Restricted.

 Configuring Associated Persons Settings

The **Settings** tab under Manage \> Associated Persons allows administrators to control account-wide behavior.

Every settings change is recorded in the account-wide audit trail.

### Governance Preset

When Associated Persons is enabled, your account starts with a governance preset, such as Standard venue or Governed.

These presets provide a starting point, but all settings can be changed to suit your organization's requirements.

### How Records Are Created

The following settings control how Person records are created:

- **Show Risk Level:** Displays the Person's Risk Level on their record, the creation form and PDF exports. The Risk Level is retained whether or not it is displayed.
- **Require a source for a Person created without an Issue:** Requires a source when creating a Person directly rather than from an Issue.
- **Require a name or description:** Prevents records from being created with only a photo.
- **Create a Person only from an Issue:** Requires users to create Persons from an Issue rather than directly from the Associated Persons list. CSV imports are not affected.

### Access to Restricted Fields

**Allow access requests** determines whether users without Restricted clearance can request temporary access to a Person's Restricted fields.

If disabled, previously approved access remains valid until it expires, and pending requests can still be approved or denied.

### Export Settings

**Allow CSV export** controls whether users can export the Associated Persons list.

When disabled, CSV exports are unavailable regardless of the user's export permission.

### Notifications

Administrators can choose which Teams receive notifications for:

- **Person Statuses that restrict entry ending:** Notifies selected Teams when a status that restricts entry lapses or is lifted. If no Team is selected, only the person who created the record is notified.
- **Every export:** Notifies selected Teams whenever an export takes place. If no Team is selected, everyone with permission to configure Associated Persons is notified.

### Audit Trail Retention

Administrators can configure how long audit trail records are retained.

- **Person audit trail:** Between 12 months and 3 years.
- **Account-wide audit trail:** Between 3 and 7 years.

Enter the required period and select **Set period**.

Changes apply to audit entries recorded from that point onwards. They do not change the retention period of entries already held.

 Managing Access Requests

Users with the **Approve Access for Associated Person** permission can review and manage requests for Restricted access.

### How to Approve or Deny an Access Request

1. Go to **Manage \> Associated Persons**.
2. Open the **Access Requests** tab.
3. Review the request details, including the requester, Person, reason and date requested.
4. Select **Approve** or **Deny**.

The requester will be notified of the decision.

Every request, approval and denial is recorded in the Person's audit trail.

### Managing Access Reasons

The Access Requests tab also contains an **Access reasons** card.

To manage the available reasons:

1. Find the Access reasons card.
2. Select **Add reason** to create a new option.
3. Manage the available reasons as required.

At least one active access reason must remain available.

 Importing Associated Persons from CSV

Users with permission to view Restricted fields can bulk import Persons using a CSV file.

Each row in the file creates a new Person record.

### How to Import Persons

1. Go to **Associated Persons \> CSV Import**.
2. Select **Download example CSV**.
3. Use the example file and CSV column reference to prepare your data.
4. Select **Upload CSV**.

Raven validates each row before importing and identifies any errors that need attention.

Examples of validation errors include duplicate records and Source Types that do not exist in your account.

### CSV Import Requirements

- **Date of Birth:** Use YYYY-MM-DD format or enter a year on its own. A date of 1 January is not accepted because it is often used as a placeholder.
- **Person Status:** Use an existing Person Status Type. Imported Persons receive this status from the date of import, with no end date.
- **Source:** Use an existing Source Type configured in your account.

**Note:** Photos cannot be imported through CSV. You can edit each Person's record after importing to add photos.

 Exporting Associated Persons to CSV

Users with the **Export CSV of Associated Persons** permission can export the Persons currently displayed in the filtered list, provided CSV exports are enabled for the account.

### How to Export the Persons List

1. Go to **Associated Persons**.
2. Apply any filters required to identify the Persons you want to export.
3. Select **Export CSV**.
4. Review the export summary, including the number of rows, fields included and who will be notified.
5. Confirm that you understand the file will leave Raven's control and that your organization is responsible for it.
6. Select **Export CSV** to proceed.

Exports can contain up to 5,000 records and include only the fields you have permission to read. Photos and media are never included.

### Exporting Restricted Fields

Exports containing General fields only are generated immediately.

Exports containing Restricted fields require authorization from another user. The person requesting the export cannot authorize their own request.

The request must be authorized within 24 hours or it will lapse.

Pending export requests can be reviewed from the **Export requests** card under **Manage \> Associated Persons \> Access Requests**.

Users with the appropriate permission can select **Authorise** or **Deny**. When denying an export, a reason can be provided and will be sent to the requester.

**Important:** Every export is recorded in the account-wide audit trail and the audit trail of each Person included. All Teams selected to receive export notifications are notified.

 Understanding the Account-Wide Audit Trail

In addition to individual Person audit trails, Raven maintains an account-wide audit trail for Associated Persons.

This is available from the **Audit Trail** tab under **Manage \> Associated Persons**.

It records account-level activity, including:

- CSV exports.
- Changes to Field Sensitivity.
- Changes to Person Status Types.
- Changes to Source Types.
- Changes to Associated Persons Settings.
- Deleted Person records.

Use the available filter to find specific types of activity.

The retention period for the account-wide audit trail can be configured from the Settings tab.

 Managing Associated Persons Permissions

Access to Associated Persons is controlled through permission groups.

Go to **Manage \> Permission Groups** to assign the relevant permissions to users.

The available permissions are:

| Permission | Access provided |
| --- | --- |
| View Associated Person | View the Persons list, open records and read General fields. |
| View Associated Person Restricted Fields | Read Restricted fields and import Persons from CSV. |
| Create Associated Person | Create new Person records. |
| Edit Associated Person | Edit existing Person records. |
| Delete Associated Person | Delete Person records. |
| Approve Access for Associated Person | Approve or deny Restricted access requests. |
| Export PDF of Associated Person | Export individual Person records as PDFs. |
| Export CSV of Associated Persons | Export the filtered Persons list, where enabled by the account. |
| Configure Associated Persons | Manage Person Status Types, Source Types, Field Sensitivity and Settings. Also provides Restricted clearance. |
| Administrate Associated Persons | Full access to all Associated Persons functionality. |

**Recommendation:** Give most staff the View Associated Person permission only. This allows them to identify Persons and see whether they are restricted from entry, while requesting additional access when needed.

Assign additional permissions based on each user's responsibilities and operational requirements.

- [Dashboard](https://support.ravencontrols.com/raven-academy/dashboard?hsLang=en-gb)
- [Log Page](https://support.ravencontrols.com/raven-academy/log-page?hsLang=en-gb)
- [Issues](https://support.ravencontrols.com/raven-academy/issues?hsLang=en-gb)
- [Checklists](https://support.ravencontrols.com/raven-academy/checklists?hsLang=en-gb)
- [Notes](https://support.ravencontrols.com/raven-academy/notes?hsLang=en-gb)
- [Logs](https://support.ravencontrols.com/raven-academy/logs?hsLang=en-gb)
- [Categories](https://support.ravencontrols.com/raven-academy/categories?hsLang=en-gb)
- [Sites](https://support.ravencontrols.com/raven-academy/sites?hsLang=en-gb)
- [Maps](https://support.ravencontrols.com/raven-academy/maps?hsLang=en-gb)
- [Notifications](https://support.ravencontrols.com/raven-academy/notifications?hsLang=en-gb)
- [Processes](https://support.ravencontrols.com/raven-academy/processes?hsLang=en-gb)
- [Reports](https://support.ravencontrols.com/raven-academy/reports?hsLang=en-gb)
- [Raven Eye](https://support.ravencontrols.com/raven-academy/raven-eye?hsLang=en-gb)
- [Service Level Objectives (SLOs)](https://support.ravencontrols.com/raven-academy/service-level-objectives-slos?hsLang=en-gb)
- [Mass Notifications](https://support.ravencontrols.com/raven-academy/mass-notifications?hsLang=en-gb)
- [Meetings](https://support.ravencontrols.com/raven-academy/meetings?hsLang=en-gb)
- [Users](https://support.ravencontrols.com/raven-academy/users?hsLang=en-gb)
- [Account Settings](https://support.ravencontrols.com/raven-academy/account-settings?hsLang=en-gb)
- [Raven Mobile App](https://support.ravencontrols.com/raven-academy/raven-mobile-app?hsLang=en-gb)
- [Integrations](https://support.ravencontrols.com/raven-academy/integrations?hsLang=en-gb)
- [Teams](https://support.ravencontrols.com/raven-academy/teams?hsLang=en-gb#main-content)

    - [Teams](https://support.ravencontrols.com/raven-academy/teams?hsLang=en-gb#teams)
- [Resolutions](https://support.ravencontrols.com/raven-academy/resolutions?hsLang=en-gb)
- [Event Markers](https://support.ravencontrols.com/raven-academy/event-markers?hsLang=en-gb#main-content)

    - [Event Markers](https://support.ravencontrols.com/raven-academy/event-markers?hsLang=en-gb#event-markers)
- [Webhooks](https://support.ravencontrols.com/raven-academy/webhooks?hsLang=en-gb)
- [Contacts](https://support.ravencontrols.com/raven-academy/contacts?hsLang=en-gb)
- [Forms](https://support.ravencontrols.com/raven-academy/forms?hsLang=en-gb)
- [Associated Persons](https://support.ravencontrols.com/raven-academy/associated-persons?hsLang=en-gb)

[![brand mark - primary](https://support.ravencontrols.com/hubfs/brand%20mark%20-%20primary.svg "brand mark - primary")](http://ravencontrols.co.uk)

<https://www.linkedin.com/company/raven-controls/> [mailto:support@ravencontrols.com](mailto:support@ravencontrols.com)

Copyright © 2025, Raven Controls