Support role definitions and their assignments in non-root space
Currently the roles must be defined in the administrative stack(s) of the root space. It should be possible to do so in any space.
- Workaround
- Problem
Currently the roles must be defined in the administrative stack(s) of the root space. It should be possible to do so in any space.
Log in to comment and vote
Comments7
Krzysztof Niepokojczycki
Sep 9, 2025
We’ve accepted this to be implemented (https://app.clickup.com/t/869adybfw) with the limitation that we will only allow it via programmatic approach first (administrative stacks will be enabled to manage role bindings for their space and subspaces)
Gold Orbit
Sep 22, 2025
Sounds great. Thanks!
Black Breeze
Sep 9, 2025
Once created, you can assign roles to any space. But correct, you cannot create per-space role definitions, these are global.
Some context… while designing the feature we considered space-local roles but found them too cumbersome to use, creating naming conflicts, inheritance conflicts and resulting in overall confusion. With global role definitions, we tried to strike the right balance between power and simplicity.
We verified with our design partners that it was the right decision for where we are, and we will not be revisiting that in the foreseeable future.