Use an out-of-the-box playbook, create a new playbook, or customize an existing one based on your organization's needs.
Manage playbook content by either using a remote repository, or by saving versions of your playbook in Cortex XSIAM to maintain version history. For more details, see Manage playbook content.
Playbook editing conflict management
If multiple users simultaneously attempt to open the same playbook for editing, they could overwrite each other's changes in the playbook editor. To prevent users from accidentally losing their work, the playbook editor only allows the first user to edit and save. Subsequent users are automatically placed in View Mode Only, and a banner in the playbook editor clearly shows who is currently editing the playbook. These subsequent users can still view, debug, run, duplicate, and download the playbook.
The playbook is automatically unlocked when the user currently editing the playbook closes the editor, logs out, or when their session expires. In addition, the Administrator can click Unlock in the banner on the Playbooks page or directly in the playbook editor to force-unlock the playbook.
Important
Manually unlocking a playbook may cause version conflicts. This turns off concurrent editing protection, and if the original user is still editing, their changes might be lost or overwritten.