# đź‘‚ Feedback needed: Contributor access **URL:** \ **Category:** News & Announcements\ **Tags:** permissions\ **Created:** [March 12, 2025, 8:48am UTC](https://community.fibery.io/t/feedback-needed-contributor-access/8429 "2025-03-12T08:48:56Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![antoniokov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/antoniokov/32/201_2.png) [@antoniokov](https://community.fibery.io/u/antoniokov)\ **Post date:** [March 12, 2025, 8:48am UTC](https://community.fibery.io/t/feedback-needed-contributor-access/8429/1 "2025-03-12T08:48:56Z")
As we’ve [hinted before](https://community.fibery.io/t/nov-16-2023-entity-permissions-experimental/5414/25), we are looking to deprecate `Contributor` Space access. Now that we have proper [Database access](https://the.fibery.io/@public/User_Guide/Start-6568#Guide/Share-Database-342) and automatic sharing for assigned [people](https://the.fibery.io/@public/User_Guide/Guide/Automatically-Share-Entities-via-People-Field-327) and [groups](https://the.fibery.io/@public/User_Guide/Guide/Automatically-Share-Entities-with-linked-Groups-395), there’s no need for the access level that tries to imitate both. We’d like to make the transition as smooth as possible, and we need your help. If you’re currently using the `Contributor` access or have just transitioned from it, please answer a few questions about the desired access for each Database. Here is an example. `Dev` Group has `Contributor` access to `Project Management` Space with three Databases: `Objectives`, `Projects`, and `Tasks`: ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/e/e6a777dbe8a44d46bc695a9686920f0a80211974.jpeg) | What should they be able to do? | Answer | | --- | --- | | See and comment all Objectives | Yes | | Edit Objectives they are assigned to | No | | Create Objectives | No | | ——— | | | See and comment all Projects | Yes | | Edit Projects they are assigned to | Yes | | Edit Projects they are assigned to even if they lose Space access | Yes | | Create Projects | No | | ——— | | | See and comment all Tasks | Yes | | Edit Tasks they are assigned to | Yes | | Edit Tasks they are assigned to even if they lose Space access | Yes | | Create Tasks | Yes | | Edit Tasks they create | Yes | | Edit Tasks they’ve created even if they lose Space access | Yes | Please pick the most critical `Contributor` use case in your workspace, copy-paste the table into your reply, and replace the Databases with yours. Thank you! ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [March 12, 2025, 10:59am UTC](https://community.fibery.io/t/feedback-needed-contributor-access/8429/2 "2025-03-12T10:59:50Z")
---
**Author:** ![Mircea\_Braescu](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mircea_braescu/32/9729_2.png) [@Mircea\_Braescu](https://community.fibery.io/u/Mircea_Braescu)\ **Post date:** [June 12, 2025, 2:37pm UTC](https://community.fibery.io/t/feedback-needed-contributor-access/8429/3 "2025-06-12T14:37:51Z")
Hey @antoniokov I’ll dodge a bit your request but still try to address the same topic. Here’s an example of a scenario we have: A space with 20+ databases and a few user groups. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/2/2008a81ec58e7f6726d3ef350c07d7d0efaad5bb.png) I want the user groups to be able to do, for potentially all the DBs in the space, exactly what it says on the label: crete new entities or edit ones assigned to them. Let’s say I would want to do that without the Contributor access. I have an example of a custom Role we call Partner, which is meant to provide access to our business Partners per Engagement (we have multiple ongoing engagements). Here is how the role looks. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/2/2cb4d29dd72cf9a2f229f917d2a5552473ae5cd3.jpeg) If I want to implement something like “this role should be able to create entities in any of these databases”, how am I supposed to do that? The only way I can see this afaik is by pressing the “+” button. That would mean I would need to add 3 groups per 20+ databases. It’s not just horrible user experience, but it’s extremely prone to human error. The fact that I can’t tell at a glance “can they or can they not create entities” only exacerbates this problem. The “plus” button tells me nothing, it’s just a blackbox and I would need to open 20 of them to get an overview of what this role can do. So right now the Contributor role solves a real problem, at least in our case. ---
**Author:** ![antoniokov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/antoniokov/32/201_2.png) [@antoniokov](https://community.fibery.io/u/antoniokov)\ **Post date:** [June 12, 2025, 3:49pm UTC](https://community.fibery.io/t/feedback-needed-contributor-access/8429/4 "2025-06-12T15:49:26Z")
If I understand you correctly, you describe two distinct use cases: one involving internal teams and the other involving an external partner. The internal one is decomposed into three actions: 1. Change `Contributor` to `Viewer` for Teams on the Space level. 2. Grant `Submitter` access to those Databases that Teams need to create Entities of. I presume, not all of the 20+ Databases are involved here. 3. Enable automatic access for assigned [people](https://the.fibery.io/@public/User_Guide/Guide/Automatically-Share-Entities-via-People-Field-327) or even [groups](https://the.fibery.io/@public/User_Guide/Guide/Automatically-Share-Entities-with-linked-Groups-395) on relevant DBs. Less convenient than `Contributor` in your scenario, but more precise. As for the partner case, `+` should ideally be a part of the custom access template, not a button that redirects to the DB access settings. We’ll explore the feasibility of this idea later this summer.