---
tags: permissions, user experience, feature request, data management
---

# Request for Granular Permissions

###### Category: Feature, User Experience
###### User: steckdenis
###### Source: [GitHub Discussion](https://github.com/centerofci/mathesar/discussions/2290#discussioncomment-6163093)

## Feedback Content

>Hello,
>
>(first, thanks for the wonderful tool that Mathesar is!)
>
>My use-case for this feature is also linked to #2289 and #2288. I'm working in a decently-sized group of people (about 50 people), and we regularly use dozens of Excel sheets to administrate personnel, projects, deliverables, outcomes, lectures and other organizational stuff. Finding these Excel sheets, producing reports (so only selecting a few columns) and doing joints is very very difficult for now. We are actively looking for a tool that has the exact features of Mathesar, but its permission system is currently what prevents us from using it.
>
>Basically, we need a centralized data storage but for which certain users can only view or edit certain tables, views or specific columns (for the specific columns: we are okay with splitting tables in "sensitive information" and "non-sensitive information" versions). Our use-case is that the secretary must be able to see and edit the personal details of every member of the organization. But the business developer must only be able to list all our deliverables jointed with who worked on them, with the "who" only having a first name, last name and job title. The PR person must know who is the member responsible for a specific project, but not where they (the member) live. Ideally, members should be able to update their personal information, or current funding source, but not see or edit that information for other members.
>
>I can extend the use-case if you want, but I think that this message is already quite long :-)

## Context (Optional)

The user is part of a group of around 50 people that currently uses Excel sheets for various administrative tasks. They are looking for a more efficient tool like Mathesar, but find its permission system limiting. The user highlights the need for more granular permissions in terms of which users can view or edit certain tables, views, or specific columns. They provided specific examples to clarify their needs.

## Related GitHub Issue(s) (if applicable)

[#2289](https://github.com/centerofci/mathesar/issues/2289), [#2288](https://github.com/centerofci/mathesar/issues/2288), [Source Discussion](https://github.com/centerofci/mathesar/discussions/2290#discussioncomment-6163093)

## Actions

- [ ] No action required
- [x] Needs to be addressed (e.g., fix an issue, implement a suggestion, or improve a feature)
- [ ] Further action needed (e.g., gather more information, follow up with the user, or monitor for similar feedback)
- [ ] Roadmap suggestion (e.g., the feedback contains a valuable idea for a new feature)