馃攽 UX Work for Manage | Auth: Permissions inheritance and policies exploration
*This epic is a work in progress and will be evolving as I investigate the problem space and begin solution ideation and validation.*
## Problem
Currently there is not an efficient way to:
- View user access roles
- Create and assign custom user roles
- No granular permissions across the architecture
## Research
There has been some early research and ~"UX problem validation" issues:
- [Custom roles](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/12736)
- [Policies discovery](https://gitlab.com/gitlab-org/gitlab/-/issues/7625)
#### Interviews
馃敩 [**Research in Dovetail**](https://dovetailapp.com/projects/d2eca677-cbae-4f84-aad4-f6be6e3f6a6c/data/b/ef3dd998-9d55-409c-92d6-898c4b9f7f71)
## Long Term Vision
- Define what `Organization` level permissions and settings are.
- Permissions and settings that are not contingent on a specific group or project.
- 2fa
- compliance
- security
- user management
- etc...?
- Create a refined permissions hierarchy to allow tighter specificity of access levels.
- Provide greater visibility and management of permissions for `Groups`, `Projects`, `Users`
- Rethink the information architecture of components to better work across various sizes of organizations.
epic