Access control overview
Access control for ۶Ƶ Experience Platform is provided through the Permissions in . This functionality leverages roles and policies, which link users with permissions and sandboxes.
Access control hierarchy and workflow
In order to configure access control for Experience Platform, you must have system or product administrator privileges for an organization that has an Experience Platform product. The minimum role that can grant or withdraw permissions is a product administrator. Other administrator roles that can manage permissions are system administrators (no restrictions). See the ۶Ƶ Help Center article on for more information.
A high-level workflow for gaining and assigning access permissions can be summarized as follows:
- After licensing ۶Ƶ Experience Platform, or an Application/App Service that uses Experience Platform, an email is sent to the administrator specified during licensing.
- The administrator logs in to ۶Ƶ Admin Console and selects ۶Ƶ Experience Platform from the list of products on the overview page.
- To grant access to Experience Platform, it is recommended that the administrator add users to the default product profile:
AEP-Default-All-Users. - In Experience Platform Permissions, the administrator can create new roles or edit the permissions and users for any existing roles.
- When creating or editing a role, the administrator adds users to the role using the users tab, and grants permissions to these users (such as “Read Datasets” or “Manage Schemas”) by editing the role’s permissions. Similarly, the administrator can assign access to sandboxes using the same editing option.
- When users log in to the Experience Platform user interface, their access to Experience Platform capabilities is driven by the permissions that have been granted to them from the previous step. For example, if a user does not have the View Datasets permission, the Datasets tab in the side menu will not be visible to that user.
For more detailed steps on how to manage access control in Experience Platform, see the access control user guide.
All calls to Experience Platform APIs are validated for permissions, and will return errors if the appropriate permission(s) are not found in the current user context. Within the UI, elements will be hidden or altered depending on permissions granted to the current user.
Permissions platform-permissions
Permissions provides a central location for managing Experience Platform access for your organization. Through Permissions, you can grant groups of users access permissions for various Experience Platform capabilities, such as Manage Datasets, View Datasets, or Manage Profiles.
Roles
In the Roles section, permissions are assigned to users through the use of roles. Roles allow you to grant permissions to one or multiple users, and also contain their access to the scope of the sandboxes that are assigned to them through roles. Users can be assigned to one or multiple roles belonging to your organization.
Default roles
Experience Platform comes with two pre-configured default roles. The following table outlines what is provided in each default profile, including the sandbox they grant access to as well as the permissions they grant within the scope of that sandbox.
Sandboxes and permissions
Non-Production sandboxes are a form of data virtualization that allow you to isolate data from other sandboxes and are typically used for development experiments, testing, or trials. A role’s permissions give the role’s users access to Experience Platform features within the sandbox environments to which they’ve been granted access to. A default Experience Platform license grants you five sandboxes (one production and four non-production). You can add packs of ten non-production sandboxes up to a maximum of 75 sandboxes in total. Please contact your organization’s administrator or your ۶Ƶ sales representative for more details.
For more information about sandboxes in Experience Platform, please refer to the sandboxes overview.
Access to sandboxes
Access to sandboxes is managed through roles. For detailed steps on how to enable access to a sandbox for a role, see the attribute based access control roles guide.
Users can be granted access to one or more sandboxes within a role. If one user is included in two or more roles, that user will have access to all sandboxes included in those roles.
The “Sandbox Management” permission allows users to manage, view, or reset sandboxes.
Resource permissions permissions
The resource Permissions tab within a role displays the sandboxes and permissions that are active for that role:
Permissions that are granted through the resource permissions are sorted by category, with some permissions granting access to several low-level functionalities.
The following table outlines the available permissions for Experience Platform in the role, with descriptions of the specific Experience Platform capabilities they grant access to. For detailed steps on how to add permissions to a role, see the attribute based access control roles guide.
Next steps
By reading this guide, you have been introduced to the main principles of access control in Experience Platform. You can now continue to the attribute based access control user guide for detailed steps on how use Experience Cloud to create roles and assign permissions for Experience Platform.