SOPs & Knowledge

The SOP module is your living knowledge base. Procedures are organized into spaces (like departments or topics) and pages, each with version history.

How it works

• Spaces group related pages. Visibility can be scoped by department so the right teams see the right content.
• Pages are written in rich text/Markdown and are versioned — every published change is recorded.
• Suggestions work like pull requests: anyone with access can propose an edit, which a reviewer can compare (diff view) and merge or reject. This keeps procedures accurate without giving everyone direct edit rights.

How to configure

1. Create a space and set its department scope (or leave it tenant-wide).
2. Add pages and write the procedure.
3. Set page status to Published when ready; drafts stay hidden from most roles.
4. Link SOP pages to blueprint tasks so the right instructions appear exactly where work happens.

Roles

• Read: most roles, subject to department scope.
• Write / Approve: managers and above (or anyone granted sop.write / sop.approve).
• Suggest: anyone who can read can propose changes.