Solution Overview for Business Users / Version 2512.0
Table Of ContentsKIO resolves playbooks through a priority chain from least to most specific. When two playbooks share the same id, the more specific one always overrides the less specific one. The full chain, in ascending order of priority, is:
System playbooks
└── Global CMS path (/Settings/Options/Settings/Playbooks)
└── Site layer
├── Master site (<master-root>/Options/Settings/Playbooks) [only if present]
└── Preferred site (<site-root>/Options/Settings/Playbooks)
└── User home (<user-home>/Playbooks)| Layer | Description |
|---|---|
| System | Playbooks loaded from filesystem and/or GitHub connectors. Lowest priority. |
| Global CMS | Playbooks stored at the global CMS path (default: /Settings/Options/Settings/Playbooks). |
| Site | Playbooks from the preferred site's content tree. If the preferred site is derived from a master site, the master site's playbooks are loaded first and the preferred site's playbooks override them. If the preferred site is not derived from a master site, only the preferred site's playbooks are considered. |
| User | Personal playbooks stored in the user's CMS home folder. Highest priority. |
Table 12.1. Playbook layers
Note
Only one playbook per id is active at a time. A user-level playbook completely replaces any site, master-site, or global playbook that shares the same id.
