# Admin Configuration Guide

*Audience: Privacy Managers and privacy operations teams who review, maintain, and report on the ROPA.*

Open **Comply → Universal ROPA™**. The **Processing Activities** tab lists every ROPA record. The **Audit Logs** tab records every change to them (see [Audit Log and Reporting](/docs/universal-ropa/audit-log-and-reporting/)). For how records are created and kept current, read the [Overview and Implementation Guide](/docs/universal-ropa/overview-and-implementation-guide/#how-records-are-built) first.

## The processing activities list

Each row is one record: a processing activity with one controller and one processor. Select a record's **Name** to open it.

### Columns

The list shows these columns by default:

| Column | What it shows |
|---|---|
| **Name** | The processing activity. Always shown and pinned to the left |
| **Controller** / **Processor** | The entity in each role, with its logo. Select one to open its drawer. Where role prediction is enabled, hover to see the **Role Prediction** |
| **Description**, **Purpose of Processing** | What the activity is and why it happens |
| **Departments**, **Products** | Where the activity sits in your organization |
| **Status** | **Discovered**, **Draft**, **Approved**, or **Archived** |
| **Discovery Source** | One pill per source that found the activity. Hover for details, select to open the source. A struck-through pill is a source that's no longer active |
| **Subprocessors** | Subprocessors engaged for the activity |
| **Data Subject Categories**, **Data Elements** | Whose data and which personal data categories are processed |
| **Legal Bases**, **Retention Period** | The lawful basis and how long the data is kept |
| **Date Created**, **Last Updated**, **Processing Locations** | Dates and where processing happens |

More columns are available from the column selector, hidden by default: **Joint Controllers**, **Data Recipient Categories**, **Special Categories of Data**, **Security Measures**, **Transfers**, **Assessments**, the controller's and processor's **Address** and **DPO**, and further details about each entity (status, industry, description, contacts, headquarters, tags, subprocessors URL, website, and whether there's an active DPA). Every custom field you add also gets its own column.

Use the column selector to show, hide, and reorder columns. Column order is set in the selector, not by dragging headers.

### Showing values by source

The **Data Subject Categories**, **Data Elements**, and **Special Categories of Data** columns have a **Filter by Discovery Source** control in their header. Use it to show only values from certain source groups - for example, only **Operational Reality** to see what Relyance actually observed, or only **Manually Added**. It changes which values are displayed, not which records are listed. Your choice is saved with your view and applied to exports.

### Search and filters

Search by text, or filter by **Controller**, **Processor**, **Departments**, **Status**, **Discovery Source**, **Joint Controllers**, **Subprocessors**, **Products**, **Data Recipient Categories**, **Data Element**, **Legal Bases**, **Security Measures**, **Processing Locations**, and any custom field of type dropdown, multi-select, yes/no, or date.

### Grouping

Use **Group by** to group the list by **Processing Activity**, **Department**, **Processor**, **Controller**, **Status**, or any dropdown or multi-select custom field. Each group shows its name and how many records it contains. Use **Expand all** to open every group at once.

Select a group's name to open the [group page](#working-with-groups). Group pages open only when no search or filter is active. With a filter applied, the group shows **Clear filters to open this group**.

### Saved views

Filters, grouping, columns, and column order make up a view, and the browser address reflects them, so you can bookmark or share the link. To keep a view:

1. Set up the list the way you want it.
2. Open the view menu and choose **Save as New View** (or **Save Changes** to update the view you're on).
3. To share it, choose **Manage Sharing** and pick **Share with everyone in organization**, **Share with specific users**, **Share with Groups**, or **Share with Roles**.

Your views are under **My Views**, and views others shared with you are under **Shared with Me**. Use **Set as default** to open the ROPA on a view, **Reset View** to discard unsaved changes, and **Manage All Views** to rename, delete, or **Transfer Ownership** of views. Deleting a shared view removes it for everyone.

## Reviewing a processing activity

Open a record to see its detail page. The header shows the name, its status, and the **Create Assessment**, **Delete**, and **Edit** actions. The page has three tabs: **Overview**, **Articles**, and **Audit Log**.

The **Overview** tab has these cards:

| Card | Fields |
|---|---|
| **Details** | **Description**, **Purpose of processing**, **Locations of Processing**, **Product**, **Department**, **Source**, **Date Created** |
| **Controls** | **Legal Basis**, **Retention Period**, **Security Measures**, **Data Subject**, **Data Recipient Category**, **Data Elements**, **Special Categories of Personal Data**, **Transfers** |
| **Additional Fields** | Your custom fields |
| **Controller**, **Joint Controller**, **Processor** | Each entity's name, type, **Address**, and **DPO Email**. Select the name to open the entity's drawer |
| **Subprocessors** | Each subprocessor's **Name**, **Purpose**, and **Location** |

Each value in **Controls** carries a source badge. Select a value to open **Data Sources** and see where it was discovered.

The **Articles** tab lists the assessments linked to this processing activity, its processor, and its products. Start a new one with **Create New Assessment**.

## Editing a processing activity

1. Open the record and select **Edit**.
2. Update the fields you need:
    - **Locations of Processing** and **Transfers** - choose countries or regions.
    - **Product** and **Department** - choose from your existing products and departments.
    - **Legal Basis** and **Retention Period** - choose a value, or type a new one to create it.
    - **Security Measures**, **Data Subject**, **Data Recipient Category**, **Data Elements**, and **Special Categories of Personal Data** - choose from the taxonomy.
    - **Controller**, **Joint Controller**, and **Processor** - choose the type (**Business Entity** or **Vendor**, plus **Customer** or **Partner** where licensed) and the entity, and set its **Address** and **Email**.
    - **Subprocessors** - add, edit, or delete subprocessors (see [Adding a subprocessor](#adding-a-subprocessor)).
    - **Additional Fields** - fill in custom fields, or add a new one.
3. Select **Save**.

**Description** and **Purpose of processing** are required, and the name can't be empty. If any are missing when you save, Relyance lists the fields to complete.

**Source** and **Date Created** are read-only. In edit mode, hover a source pill to see its **Discovery Metadata** - the source type and the last discovery date.

> **Note.** Removing a value that discovery added hides it on this record and stops discovery adding it back. It doesn't change what Relyance discovered for the vendor itself.

A legal basis you created can be deleted from the picker, as long as no other record uses it. If one does, Relyance tells you how many.

To rename a record, edit its name in the header. To delete it, select **Delete** and confirm with **Yes, Delete**.

### Adding a subprocessor

1. In edit mode, choose to add a subprocessor in the **Subprocessors** card.
2. Search Relyance's third-party dataset by name or website and pick the vendor. Its **Description** and **Website URL** are shown.
3. Enter the subprocessor's **Purpose** and **Location**, and save.

If the vendor isn't listed, choose **Create New**, then enter its **Name**, **URL**, and **Description**. Relyance adds the new vendor to your data inventory immediately. A subprocessor or joint controller can only be added to a record once.

## Adding a processing activity

1. On the ROPA list, select **Add Processing Activity**.
2. Under **Processing Activity**, pick an existing activity, or type a new name and choose **Create**.
3. Enter the **Description** and **Purpose of processing** (both required), and optionally the **Product**, **Location of Processing**, and **Department**.
4. Under **Controls**, add the **Legal Basis of Processing**, **Data Elements**, **Retention Period**, **Special Categories of Personal Data**, **Security Measures**, **Data Subject**, **Transfers**, and **Data Recipient Category** you know.
5. Set the **Controller** and **Processor** (both required), and add any **Joint Controller**.
6. Fill in any **Additional Fields**, then save.

A new record starts as **Discovered**, ready for review.

You can also create a processing activity while creating or sharing an assessment. In the processing activity picker, choose to create a new one, fill in **Name**, **Description**, **Purpose of processing**, **Controller**, and **Processor** (plus any **Optional Fields**), and select **Create and Select**. Each controller and joint controller must be a different entity.

## Working with groups

A group page brings together every record in a group. Open one by selecting a group name in the grouped list. The header shows how many records the group contains, with **Create Assessment** and **Edit**.

The **Overview** tab shows:

- **Details** and **Controls** - the combined values of every record in the group. Select a value to see which processing activities contributed it, shown as controller → processor, with a link to each one.
- **Additional Fields** - combined custom field values.
- **Controller-Processor Pairings** - one row per controller and processor pair in the group, with the number of subprocessors. Each pairing is an individual record. Select it to edit just that record.
- **Subprocessors** - every subprocessor across the group, with the **Associated Processor**.

When the group is a processing activity, **Add New** in **Controller-Processor Pairings** adds another pairing to it, pre-filled with the activity's description and purpose. A pair that already exists can't be added twice.

### Editing a group

1. Open the group page and select **Edit**.
2. Add or remove values in **Details**, **Controls**, and **Additional Fields**.
3. Select **Save**.

Your changes apply to every record in the group. Relyance saves them as additions and removals, so values that only some records have are left alone - removing a value removes it from each record that has it, and adding a value adds it to each record that doesn't. **Description** and **Purpose of processing** can only be edited when the group is a processing activity. Pairings, subprocessors, **Discovery Source**, and **Date Created** can't be edited from the group. Open the individual record instead.

## Statuses and approval

Select records in the list and use **Approve**, **Disapprove**, or **Archive** in the bulk actions bar, or change a single record's status from the chip in its header.

| Action | Resulting status |
|---|---|
| **Approve** | **Approved** |
| **Disapprove** | **Discovered** |
| **Archive** | **Archived** |

You can also set any status through [Bulk Edit](#bulk-edit). A record in **Draft** can't be approved directly - change its status first.

## Bulk actions

Select rows (or **Select All**) to open the bulk actions bar: **Approve**, **Disapprove**, **Create Assessment**, **Archive**, **Delete**, **Excel Export**, and **Bulk Edit**. Approve, archive, delete, and create assessment act on the records in any groups you selected.

> **Note.** **Delete** in the bulk actions bar removes the selected records straight away. Check your selection first. To take a record out of use but keep it on file, use **Archive**.

### Bulk edit

1. Select the records and choose **Bulk Edit**.
2. Under **Select field to update**, pick a standard field - **Data Recipient Categories**, **Data Subject Categories**, **Department**, **Legal Basis**, **Data Elements**, **Products**, **Retention Period**, **Security Measures**, **Special Categories of Personal Data**, **Purpose of processing**, or **Status** - or a custom field.
3. For fields with several values, choose the **Edit mode**: **Add values**, **Remove values**, or **Replace values**. Then enter the values. Single-value fields replace the current value, and leaving a custom field empty clears it.
4. Select **Review changes**. The preview lists each record's **Original Value**, **New Value**, and **Outcome**, and how many records will be modified.
5. Select **Apply Changes**.

If a custom field's value was filled in by discovery, Relyance warns you that saving replaces it with your manual value. Bulk editing a custom field covers up to 10,000 records at a time. If some records can't be updated, Relyance tells you how many succeeded and how many didn't.

### Creating assessments

Select records and choose **Create Assessment** to start an assessment with those processing activities pre-filled. You can also create one from a record's or group's header. See [Creating assessments](/docs/assessments/admin-configuration-guide/#creating-assessments).

## Custom fields

Add fields your ROPA needs that Relyance doesn't provide - a data owner, a review date, or a risk rating, for example. Custom fields are defined from the ROPA itself.

1. Open any record and select **Edit**.
2. In **Additional Fields**, select **+ Add Field**.
3. Enter the **Field Name** (up to 255 characters), choose a **Field Type**, and optionally add a **Description**. The types are **Text**, **Date**, **Dropdown**, **Multi-select**, **URL**, **Number**, **Yes / No**, **Duration**, and **Location**. For dropdowns, add the **Options**. Mark the field **Required** if every record must have it.
4. Save.

The field is available on every ROPA record, as a list column, a filter (for dropdown, multi-select, yes/no, and date fields), a **Group by** option (for dropdown and multi-select fields), and in bulk edit. To change or remove a field, use **Edit Custom Field** or **Delete Custom Field**. Deleting a field tells you how many records hold data in it first.

Adding custom fields requires edit permission.

## Exporting the ROPA

Choose **Excel Export** in the bulk actions bar to download the ROPA as an Excel (.xlsx) file. The export follows your view:

- **Rows** - the selected records, or every record that matches your search and filters if none are selected. Selecting a group exports its records.
- **Columns** - the visible columns, in their current order, with the same names as the list.
- **Values** - any **Filter by Discovery Source** choice you set on the data subject, data element, and special category columns.

When the list is grouped by **Processing Activity**, the button reads **Export Groups** and exports one row per processing activity. An export can contain up to 10,000 records.

## Permissions

Anyone with access to the core platform can view the ROPA. Creating, editing, approving, deleting, and bulk editing records, and adding custom fields, require edit permission.

## Configuration checklist

- [ ] Integrations connected for source code, infrastructure, vendors, and contracts
- [ ] Vendors and services mapped to business entities and products in Business Atlas
- [ ] Custom fields added for anything your ROPA needs beyond the standard fields
- [ ] Every record has a **Description** and **Purpose of processing**
- [ ] Controller, processor, legal basis, retention period, and security measures reviewed for each activity
- [ ] Saved views created and shared for recurring reviews (for example, **Status = Discovered**)
- [ ] Reviewed records approved, and records no longer in use archived
- [ ] Assessments created for high-risk processing activities

## Related reading

- [Overview and Implementation Guide](/docs/universal-ropa/overview-and-implementation-guide/)
- [Audit Log and Reporting](/docs/universal-ropa/audit-log-and-reporting/)
- [Assessments Admin Configuration Guide](/docs/assessments/admin-configuration-guide/)
- [Business Atlas - Overview](/docs/other-settings/business-atlas-overview/)
