ByteRover implements a hierarchical role-based access control (RBAC) system with two primary levels: Teams and Spaces. This system ensures secure, granular access management across your ByteRover deployment.
Team├── Owner (Level 3)├── Admin (Level 2) ├── Member (Level 1)└── Spaces ├── Space A │ ├── Space Owner/Admin/Member │ └── Inherited from Team Role └── Space B ├── Space Owner/Admin/Member └── Inherited from Team Role
[Image Placeholder - Screenshot showing navigation to teams and spaces]Navigate to your team settings to manage team members and access individual spaces within your team.
Users by default inherit the role of the team they are part of. For more fine-grained control, you can assign a user a role on the space level. This is useful when you want to differentiate permissions for different spaces within the same team.Key behaviors:
If a space-level role is assigned, it will override the team-level role for that specific space
If you want to give a user access to only certain spaces within a team, you can set their team role to Member and then assign them specific roles on individual spaces
Space-level roles only apply to that particular space and do not affect team-level permissions
Team Role → Space Role (if not specified)Team Member → Space Member (default)Team Admin → Space Admin (default) Team Owner → Space Owner (default)Override Example:Team Member + Space Owner Role = Space Owner permissions for that space
This flexible system allows for precise access control while maintaining simple default behaviors for most use cases.