Managing Record Admins & Ownership with Attribute-Based Access Control (ABAC)
The Attribute-Based Access Control (ABAC) Phase 1: Foundations feature is under Public Preview. Please contact OneTrust Support to request early access.
Record admins help ensure every record has a designated user responsible for managing access and responding to access requests. As records move between teams and responsibilities evolve, organizations can use access rules to automatically assign Record admin ownership to the appropriate users.
This article explains how Record admin assignments work and how to configure access rules that automatically assign Record admin responsibilities when records are created.
What is a record admin?
Record admin is a standard assignment available across all ABAC-supported objects. Users assigned as a Record admin are responsible for managing access to the specific records for which they have been granted the Record admin assignment, including reviewing, approving, and denying access requests from the Access Requests screen in Global Settings. Record admin responsibilities apply only to those records and do not grant administrative access across other records of the same object type.
By default, the user who creates a record becomes the Record admin for that record. This ensures every record has a designated user responsible for managing access requests and ongoing access management. Organizations can also configure access rules to automatically assign Record admin responsibilities to another user when ownership should be handled by someone other than the record creator. For example, a newly created vendor record may automatically assign Record admin responsibilities to the appropriate Vendor manager, or a newly created risk record may route access management responsibilities to a designated Risk manager.
To configure an access rule for Record admin assignment
You can create an access rule to automatically assign Record admin responsibilities to a user other than the record creator. For example, a user may create a vendor record, but the Vendor manager should be responsible for managing access requests and ongoing access administration for that record.
Access rules are currently supported for the following objects: AI Agents, AI Systems, Datasets, Issues, Models, Projects, Risks, Vendors. All objects supported by ABAC in Public Preview are planned to support Record Admin access rules by General Availability.
To configure a default access rule
You can create a default rule that assigns a Record admin when no other access rule conditions are met. Default rules help ensure records always have a designated Record admin, even when no configured access rule applies.
To edit an access rule
You can edit an access rule when assignment criteria, routing logic, or Record admin ownership requirements change. Changes apply to future records that meet the updated rule conditions.
To delete an access rule
You can delete an access rule when it is no longer needed or has been replaced by a different Record admin assignment strategy. Deleting an access rule prevents it from being applied to newly created records.
Additional Resources
For a complete list of ABAC resources, see the Attribute-Based Access Control (ABAC) User Guide, which includes foundational concepts, implementation guidance, and solution-specific documentation.
To continue configuring and managing ABAC, reference the following procedural configuration articles:
-
Managing Assignments with Attribute-Based Access Control (ABAC)
-
Sharing, Requesting, and Managing Access with Attribute-Based Access Control (ABAC)
-
Configuring Attribute-Based Access Control (ABAC) Assignments for User Attributes
-
Configuring Attribute-Based Access Control (ABAC) Assignments for Workflows
-
Auditing Access Changes with Attribute-Based Access Control (ABAC)