...
Playbook permissions can follow a similar model as incident permissions. When a playbook is created, a channel is created with the playbook name on a specified team. Anyone with access to that channel can edit the playbook. The channel can be a public or private as above. This encourages orderly discussion about the playbook and allows for features like linking back the channel every time the playbook is used.
This allows us to leverage the advanced permissions system with little effort. For example if a customer wanted to “only allow users in the Security LDAP group to view and access security-related workflows unless others are explicitly added” they could do this with the advanced permissions features on that channel.
In addition you can also create a “draft” playbook that only the author can access that has no channel attached. Later the draft can be published for others to use.
...