Workspace structure
- Separate development, staging, and production workspaces with clear ownership.
- Assign bots and channels to the correct workspace boundary by lifecycle stage.
- Use naming standards for discoverability during incident response.
Admin
Roles, Permissions, and Workspaces
Set up team access, environment separation, and approval responsibility for safe collaboration.
Audience: Workspace admins and delivery managersRead Time: 8 minUpdated: May 2026
Role model
- Grant least-privilege access for builders, reviewers, and operators.
- Restrict credential management and production publish rights to approved roles.
- Use temporary elevated access with expiry for emergency fixes.
Approval responsibility
- Define who approves prompt changes, guardrail updates, and channel activation.
- Require dual review for high-risk changes touching production credentials.
- Maintain approver logs for post-incident and compliance reviews.
Operational Checklist
- OKEnvironment separation is enforced.
- OKLeast-privilege roles are configured.
- OKProduction publish rights are restricted.
- OKApproval and audit logs are reviewable.
Related Guides
Next Action
Apply this guide in your workspace and keep notes for your team in one shared SOP so onboarding and support remain consistent.