Permissions in default roles
A role identifies a category of users. Each role includes a specific set of permissions to accomplish certain activities.
A standard platform license comes with a set of predefined roles. Depending on your company’s license, the roles available in the Roles pane may differ. If you need a custom set of permissions in a role, contact Customer Care Team.
To assign a role to a user, see Manage user details.
Default roles
Review the default roles that are available with the standard platform license, grouped by component.
Data Preparation
Works with datasets as a consumer.
The role includes the dataprep.access permission.
For details on each permission, see All permissions. To understand what permissions are needed for shared content, see Shared content permissions.
Creates, manages, and shares datasets, data connections, and AI connections.
The role includes the following permissions:
-
dataprep.access
-
dataprep.dataset.create
-
dataprep.dataset.set-permissions
-
dataprep.data-connection.create
-
dataprep.data-connection.set-permissions
-
dataprep.ai-connection.create
-
dataprep.ai-connection.set-permissions
For details on each permission, see All permissions. To understand what permissions are needed for shared content, see Shared content permissions.
Endorses datasets, data connections, and AI connections to mark them as recommended for use.
The role includes the following permissions:
- dataprep.access
-
dataprep.dataset.certify
-
dataprep.data-connection.certify
-
dataprep.ai-connection.certify
For details on each permission, see All permissions. To understand what permissions are needed for shared content, see Shared content permissions.
Creates dataset extracts and performs the actions related to dataset extracts.
The role includes the following permissions:
-
dataprep.access
-
dataprep.dataset.create
-
dataprep.dataset.extract
For details on each permission, see All permissions. To understand what permissions are needed for shared content, see Shared content permissions.
Storyboards
Works with storyboards as a consumer to view and analyze data.
The role includes the storyboards.access permission.
For details on each permission, see All permissions. To understand what permissions are needed for shared content, see Shared content permissions.
Creates and manages storyboards; can share and set storyboard’s permissions.
The role includes the following permissions:
-
storyboards.access
-
storyboards.storyboard.create
-
storyboards.storyboard.set-permissions
-
storyboards.palette.create
-
storyboards.palette.set-permissions
For details on each permission, see All permissions. To understand what permissions are needed for shared content, see Shared content permissions.
Endorses storyboards to mark them as recommended for use and analysis.
The role includes the following permissions:
-
storyboards.access
-
storyboards.storyboard.certify
For details on each permission, see All permissions. To understand what permissions are needed for shared content, see Shared content permissions.
Publishes storyboards publicly to web (generate and manage the URLs & embed codes for storyboards to be published to web publicly).
The role includes the following permissions:
-
storyboards.access
-
storyboards.storyboard.publish-to-web
For details on each permission, see All permissions. To understand what permissions are needed for shared content, see Shared content permissions.
Administration
Manages the platform in Configuration Manager.
The role includes the config-manager.access permission.
Note: The Default Admin user is automatically created in Access Manager with the Config Admin role assigned. The default Admin role can manage Access Manager.
Composite roles
You can create a composite role. A composite role is a role that has one or more additional roles associated with it. When a composite role is mapped to the user, the user also gains the roles associated with that composite. This inheritance is recursive, so any composite of composites also gets inherited.
Groups versus roles
Groups are a collection of users to whom you can apply roles and attributes in one place. Roles define a type of users, and applications assign permissions and access control to roles.
Composite roles are similar to groups. They provide the same functionality, but the difference is conceptual. Composite roles should be used to apply the permission model to your set of services and applications. Groups should focus on collections of users and their functions in your organization. Use groups to manage users. Use composite roles to manage applications and services.
Comments
0 comments