Determine security data pattern for users with assigned custom admin role
Problem to solve
Admin Area pages shows group, project, user metadata. Depending on your user type, you may have read all access to groups and projects or specific access to groups and projects.
User Type | Admin access | Group / Project Access |
---|---|---|
Administrator |
|
|
Auditor |
|
|
Regular user |
|
|
When a regular user is granted admin area access via a custom admin role, we need to determine the visibility of metadata
- Option 1: Show metadata only for groups/projects where the user has direct membership
- Aligned with principle of least privilege
- Maintains consistency with the user's existing access
- Potentially limits admin area functionality if users can't see the full system state
-
✅ Option 2: Show all metadata even if user has varied membership in groups and projects- Provides complete visibility
- May raise security concerns about information shown
Solution
Security pattern
UX Details
To be included in Beta:
Area | Details |
---|---|
UX pattern |
|
Navigation |
|
/runner/30#/jobs |
|
/groups or /projects |
|
Include for GA:
Area | Details |
---|---|
Admin area access - context and permission visibility |
|
Does this feature require an audit event?
No - it needs instrumentation