AI Approval Rules
AI prepares drafts and suggestions, but meaningful actions require human approval. Know where the approval gates are.
#Purpose
Ensure AI output is reviewed before it has real-world effect.
#When to use this
When setting expectations for how AI is used safely.
#At a glance
| Detail | Value |
|---|---|
| Required permissions | Approval permission for the relevant area |
| Administrator level | CEO / Admin (policy) |
| Portal areas used | Approvals, Content, Finance, Projects |
#Step by step
1
Understand the gates
AI-drafted emails and replies are sent by people; content and client deliverables are approved; expenses are approved; live WordPress publishing requires a publish-live approval.
2
Assign reviewers
Ensure people with approval permission exist for each area.
3
Set expectations
Make clear AI drafts; humans approve.
4
Monitor approvals
Keep approvals moving so work is not blocked.
#Approval points
Human approval required
- Content, client deliverables, expenses, and live-publishing all require a human decision; AI never self-approves.
#Security notes
Security considerations
- Never remove human approval for sensitive actions.
- Ensure a permitted reviewer exists so approvals are not stuck.
#Best practices
- Keep approvals required for sensitive actions.
- Review AI output before approving.
#Common mistakes
- Assuming AI acts without approval.
- No reviewer assigned, so items stall.
#Troubleshooting
| If this happens | Try this |
|---|---|
| An approval is stuck | Confirm a permitted reviewer exists; see Approval Issues. |
#FAQ
Can AI approve its own output?
No — a human with the right permission approves; AI never self-approves.
#Keep exploring
#Related admin guides
#Business modules & workflows
Getting Started
Initial setup.
Platform Overview
How the OS fits together.
Knowledge Base
Task-level how-tos.
Business Workflows
End-to-end processes.
#AI departments
Still need help?
Can’t find what you’re looking for? The DevSphere OS team is happy to help.
Was this page helpful?