Managing Assignments 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.
Assignments are a core component of Attribute-Based Access Control (ABAC) and help define what users can do on specific records throughout the OneTrust Platform. An assignment is an administrator-configured permission set that determines what assigned or shared users can do on a record, including viewing, editing, deleting, sharing, or managing access. Assignments can be used across sharing, attributes, and workflow-based access scenarios to support least-privileged access and collaboration.
This article explains how to create, modify, duplicate, deactivate, and delete assignments as your organization's access-control requirements evolve.
The procedures in this article follow the same process for all supported objects, but the available configuration options are object-specific. Depending on the selected object, you may see different linked objects, supporting objects, permissions, workflow actions, and sharing settings throughout the configuration process.
To view system assignments
You can view system assignments to review the out-of-the-box permission sets provided by OneTrust for a supported object. These assignments can be used directly or duplicated to create customized versions; however, the original system assignments cannot be edited or deleted.
To create an assignment
You can create an assignment to define the permissions users receive when access is granted to a record. Assignments can be used across sharing, attributes, and workflow-based access scenarios.
To edit an assignment
You can edit an assignment to update the permissions it provides. Changes are applied anywhere the assignment is currently in use.
To duplicate an assignment
You can duplicate an assignment when you need a similar permission set without creating a new assignment from scratch. This helps standardize access models while reducing administrative effort.
To deactivate an assignment
You can deactivate an assignment to prevent it from being used in new access configurations while preserving its configuration for future reference.
To delete an assignment
You can delete an assignment when it is no longer needed and will not be reused. Before deleting an assignment, review any existing configurations that reference it to avoid unintended access changes.
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 Record Admins & Ownership 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)