Workplace & IT module
SOPs & Policies
Approved, versioned procedures people can find and ask about in Slack.
Why you need it
Procedures sit in shared drives of unknown age. People follow old versions or ask around in Slack, and nobody can show what was in force on a given date.
What you get
- One approved source for how work is done, not a folder of old files.
- Nothing changes under a reader: amendments are reviewed and published as a new version.
- New joiners and Slack questions get the current procedure they are allowed to see.
See it in action
What you can do with SOPs & Policies
SOPs, runbooks, technical standards and governance guidelines live in one searchable place, filterable by department, client, project or group. Each has a scope and minimum access level, so a client-specific procedure never reaches someone off that account.
Company-wideDepartmentClient / projectMin access level
raven / knowledge — Atlas · overview.md
RequirementsFeaturesBackground
# Client · Atlas Financial
- SLA: 99.9% · Lead: R. Shah
- SLA: 99.9% · Lead: R. Shah
Connects to
Slack
Access levelsViewer — reads reports and recordsMember — does the day-to-day workAdmin — sets up the moduleHow roles work
FAQ
Common questions
- Who can read an SOP?
- Whoever its scope allows. An SOP can be company-wide or limited to a department, client, project or group, with a minimum access level. Raven Assistant follows the same rule in Slack: if you can't see it in the app, the bot won't reveal it.
- How does a change get published?
- Anyone with access proposes a draft or amendment. Scoped SOPs get a Level 1 review by the project or scope lead, then every SOP gets Level 2 admin sign-off. Approval publishes a new immutable version; the live document doesn't change until then.
- Is this a wiki?
- No. It is a governed document store: markdown authoring from starter templates, side-by-side diffs, inline line comments, version history and a formatted PDF per version. Client and project background lives in the Knowledge Base.