playbook access permissions

[Singularity]

Hi,

I am trying to configure playbooks in a workspace. I have multiple playbooks for a single record (my use case is that requesters would see a simplified playbook, and fulfillers would see a more complex playbook with lots of options).

I have two questions:

1. The UI Builder "Playbook" components by default show every playbook on the record. I want to restrict this so that users see different playbooks on the record based on their role. Can you configure this? I have not found a way to do it as this UI Builder component does not have such a setting and ACLs do not work.

2. I have also tried having one universal playbook for the record and instead restricting playbook activites and stages so different users see different things in the playbook. This seems possible as per documentation, however I have no idea what the documentation means. What do you restrict exactly and with what type of ACL? I have tried restricting sys_pd_* records, and tried creating ACLs with type "pd_action" in various ways but nothing works. Can someone provide an example ACL for this to hide a playbook activity? (https://docs.servicenow.com/bundle/vancouver-customer-service-management/page/product/customer-servi...😞 "Inaccessible Data Visibility: Accessibility is determined by user permissions. When enabled, the user cannot see an activity if they do not have permissions to view the data associated with the activity. If all activities in a stage are inaccessible to the user, the stage is also hidden."

[benjamin shiao]

Here is a method to control role based visibility on playbook activities:

see the sys_playbook_activity_renderer_list table, create a record, define roles required, filter a tagline on the activity.

all activities where you add the tagline, this record will control visibility

example where activity 1.2 would be only visible to admin:

the PAD activity config

the sys_playbook_activity_renderer record: