Content filtering for Playbook
Specify which content a user can access based on the user's role.
Display only content that is relevant for a particular user, hiding content that is unnecessary or sensitive. Specify the Workflow Studio playbook content that you want to control access to and the role that a user must have to access it. For example, if a user with the guided_decision_builder role is creating a playbook, show only a relevant set of activities.
- Content definitions to specify types of content.
- Content filtering rules and roles to determine who can access the content.
- (Default) Playbook - Users with delegated_developer role can access all activity definitions
- (Default) Playbook - Users with playbook.activity_def_read role can access all activity definitions
Content definitions
Content definitions specify a type of Workflow Studio resource. Resources are key elements of Workflow Studio components, such as activity definitions for playbooks. Create content definitions to include an entire resource, or use a condition builder to refine your definitions. For example, the content definition for playbook activity definitions includes all activity definitions, but you could create a content definition that includes only the activity definitions that contain Guided Decision in the Name or Package.
You can further refine content definitions through tagging. Add resource tags to items in a resource list, then design your content definition to only include resources with that tag.
Content filtering rules
Content filtering rules specify the role that a user must have to access the content in a particular definition. Each rule associates user roles with a single content definition. When a user accesses Playbook in Workflow Studio, content filtering rules determine what activities the user may access based on the user's role.
Role-based activity definition access
Manage activity definition access by specifying the Required Roles to access an activity definition. This overrides any content access filtering. To learn more about roles, see Playbooks roles. To learn more about activity definitions, see Activity definitions.
Read-only playbooks
- activities they do not have access to,
- process definitions [sys_pd_process_definition] they don't have write access to.
| Resource filtered | User has role | User does not have role |
|---|---|---|
| Activity Definition |
|
|
Design considerations
- Content definition roles for activity definitions
- Give users access to the subset of activity definitions in a content definition by assigning the playbook.write role, not the pd_author role.