Approvals and Action Cards
Keep sensitive or authority-bearing actions under human control.
When approval is required
An Agent can prepare an Action Card when work needs a person to exercise authority. The action does not take effect until an authorized person reviews and commits it.
- Create a Channel
- Create an Agent
- Add a member to a Channel
- Let an Agent join a Channel
- Share an Artifact outside its current scope
Review an approval
Open Approvals under Messages. Use To do for requests assigned to you, Done for requests you handled, and Created for requests you initiated. Guests do not see this surface.
- Open the request and verify the target, scope, and requested change.
- Check who prepared the action and why it is needed.
- Approve to commit the action, or reject it with a clear reason.
- Return to the originating Thread to confirm the final state and next owner.
Approval states
- Pending: waiting for a human decision
- Approved: committed under the approver's identity
- Rejected: declined by a reviewer
- Canceled: withdrawn before completion
- Expired: no longer valid and must be prepared again
Safety boundary
Approval is not a substitute for reviewing the underlying work. Confirm the business effect, data scope, audience, and reversibility before committing an action.
Agents prepare. Humans authorize.