Understanding roles and permissions
Roles determine what each person can see and do in DevSphere OS. Permissions are tied to roles, and AI agents act within the same permissions as the user they assist.
#When to use this
Read this when deciding what role to give someone or when planning who should have access to sensitive areas.
#Step by step
1
Review the available roles
Look at the roles your workspace offers and what each can access.
2
Match roles to responsibilities
Assign each person the role that fits their job.
3
Restrict sensitive areas
Keep finance, HR, and admin access limited to those who need it.
#Expected result
What you should see
Each person has access appropriate to their role, and sensitive data stays protected.
#Common mistakes
- Giving everyone broad access for convenience.
- Forgetting that AI assistance inherits the user's permissions.
#Troubleshooting
| If this happens | Try this |
|---|---|
| Someone cannot access what they need | Confirm their role includes that area, or assign a role that does. |
| Someone can see too much | Move them to a narrower role. |
#Best practices
- Apply least-privilege across the team.
- Review access after role changes and departures.
Still need help?
Can’t find what you’re looking for? The DevSphere OS team is happy to help.
Was this page helpful?