Departments & Approvals
Confirm which departments are in scope and how approvals should work.
#At a glance
| Detail | Value |
|---|---|
| Audience | Department leads, admins |
| Estimated time | Half a day |
| Portal areas used | Approvals (design) |
| AI used | AI never self-approves; humans decide |
#Purpose
Define the departments to roll out and the human approval points they need.
#Business outcome
Scope and approval design are agreed, matching the platform's real approval gates.
#Implementation checklist
1
Confirm in-scope departments and sequence
2
Identify required approvals (deliverables, expenses, timesheets, publish-live)
3
Assign approvers per approval type
4
Confirm no approval relies on AI deciding
#Dependencies
- Workflow discovery complete
#Risks
Watch for these
- Designing approval chains the platform doesn't support
- No named approver, so work stalls later
#Success criteria
Done looks like
- In-scope departments confirmed
- Approval types mapped to real gates
- Approvers named
#Related documentation
Approval System
What gates exist.
Human Approval & Governance
Governance.
Contact Support
Reach the DevSphere OS team.
Still need help?
Can’t find what you’re looking for? The DevSphere OS team is happy to help.
Was this page helpful?