Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Role Permissions and Object Access Management #4362

Open
ghislaineguerin opened this issue Mar 20, 2025 · 0 comments
Open

Role Permissions and Object Access Management #4362

ghislaineguerin opened this issue Mar 20, 2025 · 0 comments
Labels
affects: ux Related to user experience needs: product approval It's not yet clear that this issue will actually improve Mathesar from a user's perspective needs: ux design type: enhancement
Milestone

Comments

@ghislaineguerin
Copy link
Contributor

Problem

We currently don't have a way to see all the objects that a role has access to. We can only do this by navigating to each owned object for our current role and find the role in the list.

Proposed solution

Implement a separate UI for detailed role permissions, clearly displaying database, schema, and table permissions for roles.

Image

Additional context

This was discussed as part of the issue for collaborator flow improvements:
#3969 (comment)

Outstanding Considerations:

Hierarchical vs. Flat Structure:

  • Keep the object list flat rather than hierarchical to prevent user misunderstanding that schema-level permissions cascade to tables within.
  • Ensure users clearly understand each object’s permissions are individually managed.

Permission Removal:

  • How users can explicitly remove an object's access from a role ("No Access").

Co-existence of Role-level and Object-level Permissions:

  • Can object-level owner permissions (individual schemas/tables) coexist alongside role-level settings?
  • Role-level permissions offer efficient bulk management; object-level settings provide granular control.
@ghislaineguerin ghislaineguerin added needs: triage This issue has not yet been reviewed by a maintainer type: enhancement affects: ux Related to user experience needs: product approval It's not yet clear that this issue will actually improve Mathesar from a user's perspective needs: ux design and removed needs: triage This issue has not yet been reviewed by a maintainer labels Mar 20, 2025
@ghislaineguerin ghislaineguerin added this to the Backlog milestone Mar 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects: ux Related to user experience needs: product approval It's not yet clear that this issue will actually improve Mathesar from a user's perspective needs: ux design type: enhancement
Projects
None yet
Development

No branches or pull requests

1 participant