At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Selected starter pack | Install its term set | Draft governed records | Installed content is not approved |
| Organization context | Edit meanings, scope, synonyms, and notes | Context-specific drafts | The app does not perform legal interpretation |
| Draft pack term | Submit it for review | Normal governed lifecycle | Four-eyes rules still apply |
| Later regulatory change | Review and update affected terms | New governed versions | Packs do not update legal obligations automatically |
How it works
- Open Regulation Packs.
- Review the available starter pack.
- Install it into the required space.
- Edit each relevant draft for local context.
- Remove or deprecate content that does not apply.
- Submit approved candidates through term review.
Example
A security team installs an information-security starter pack. It rewrites ownership and scope language to match its control framework, removes inapplicable terms, and submits the remaining drafts for independent review. The pack speeds setup without deciding compliance.
What this does not mean
Starter content cannot establish applicability, completeness, legal meaning, or certification. Teams must review current primary sources and qualified advice for their own context.
Related questions
Next step
Treat every installed pack term as an unapproved draft until reviewed.
View on Atlassian Marketplace