Who is this article for?

Administrators, compliance and governance teams, and system owners who need to manage and review configurable reference data.

Administrator permissions are required.

Lists sit at the foundation of the platform's data quality. Because they define the selectable values that appear across every module, changes to lists can affect how records are categorised and reported across the entire instance.

This article explains how you can utilise lists in your day-to-day management process.

Navigating to lists

To navigate to a specific list:

1. Locate the module containing the list you want to configure from the left navigation panel:
   • Action - For action-related lists
   • Audit - For audit-related lists
   • Control - For control-related lists
   • Incident - For incident-related lists
   • Risk - For risk-related lists
   • Test - For test-related lists
   • Universe - For universe-related lists
2. Click the dropdown arrow next to the module name to expand.
3. Select the specific list type you want to configure (e.g., Action Categories).

Using lists effectively

Configuration accountability

Every change to a list is attributed to a named user, so there is always a clear record of who made each configuration decision.

Change control evidence

Organisations with formal change-control requirements can use the trail to demonstrate that configuration changes were made deliberately and traceably.

Troubleshooting

If a list value goes missing or an option changes unexpectedly, the audit trail shows exactly what happened and when.

Historical context

Understanding how lists have changed over time helps explain why older records are categorised the way they are.

Using the audit trail

The audit trail for lists ensures that any change, making it straightforward to investigate unexpected changes to configuration, demonstrate compliance with change-control processes, and understand how the platform's reference data has evolved.

The audit trail for lists captures:

• Date and time - When the change occurred.
• User - Who made the change.
• Action type - For example, Create, Update, Delete, or Archive.
• Details - What specifically changed, such as an item's title, description, or colour code.

The trail can be filtered by date range and by additional criteria such as action type and user, so administrators can quickly find specific changes within a large history.