Module 9 · Enterprise governance
Security & Governance
Governance in Ask Compass means people only follow approved guidance, every change has a history, and each organization’s data stays its own. Here is exactly where that stands today.
Example
Where things stand
The public demo has no accounts and stores data only in your browser. Customer workspaces with enforced sign-in and per-organization isolation are planned and not yet live.
- Source Only approved versions are followed
- Approval Every change is reviewed before publishing
- Step Every edit, approval and restore is logged
- Outcome Workspace isolation enforced on the serverPlanned
Trust and governance
Guidance you can check.
People should only follow guidance when they can see where it came from. This is how Ask Compass is designed to show it.
Source references, approved versions, owners, update dates, exceptions, change notices and human approval work in the Studio prototype today. Escalation guidance is written into individual steps.
Get manager approval
Send the request to your manager for approval before you submit it.
Exception: if your manager is away for more than two business days, route the approval to their delegate.
Still blocked? Escalate to the IT service desk.
- Source-linked answers Every step points to the section it came from.
- Approved versions Guidance comes from the approved version of a procedure.
- Clear ownership Each procedure has a named owner.
- Last updated See how current the guidance is.
- Visible exceptions Alternative paths appear where they apply.
- Escalation guidance Know who to contact when the standard path does not work.
- Human review Important changes are reviewed by people before they go live.
- Change awareness People who use a procedure are told when it changes.
Capabilities
What’s included
Each item is marked with its real status. “In the demo” works today in the public Studio demo, which runs in your browser with sample data. “Planned” is on the roadmap and not available yet.
Content governance
- Approved-content control: people follow published versionsIn the demo
- Approval historyIn the demo
- Version retentionIn the demo
- Audit log of changesIn the demo
- Data retention and deletion policiesPlanned
Access and isolation
- Sign-in and session managementPlanned
- Role-based access enforced on the serverPlanned
- Per-organization tenant isolationPlanned
- SSO and MFAPlanned
- Workspace administrationPlanned
- Secrets kept server-sidePlanned
In the demo works today in the public Studio demo (runs in your browser, sample data)In development being built now, not yet availablePlanned on the roadmap, not available yet
Related
Works together with
Questions about security? Ask us directly.
The Studio demo runs in your browser with sample data. No account needed.