Guide
What is was Contributor access?
Contributor used to be a Space access level between Viewer and Editor:
It included the abilities to see and comment all entities in the Space as well as create new ones. Additionally, it allowed Contributors to edit entities they create or are assigned to.
Is it being phased out?
Yes. But don't worry — no one will lose any access, at least until May 1, 2026, so we hope that you'll have plenty of time to migrate.
Contributor access is an echo of dark times when you couldn't Share Database or Automatically Share Entities with Assigned People. Now that you can do both, there are no good reasons for Contributor to exist.
What should we use instead?
Here is the TLDR version:
Replace Contributor with Commenter on the Space level.
For every Database you'd like the former Contributor to create entities in, grant them Submitter access.
Enable Editor automatic access via People Fields (incl. Created by and Assignees).
The new approach involves more moving parts, but those parts are straightforward and customizable.
With automatic access, everyone who creates entities or is being assigned to them is going to receive access, regardless of their Space access. Viewers and users with no access to the Space will receive access they previously didn't have.
What if we really want to stick with Contributor?
All Users and Groups that currently have Contributor access will keep it ~forever, so there's no immediate pressure to migrate.
That being said, on May 1, 2026 Contributors will lose the ability to edit entities they create or are assigned to — they will only be able to see and comment all entities in the Space as well as create new ones. We are removing this legacy conditional access to simplify Fibery, fully transitioning to Automatically Share Entities with Assigned People. The new approach is more flexible and is independent of Space access.
If you want to grant Contributor access to more Users and Groups, you can enable Contributor Space access (legacy) feature in Settings → Experimental Lab. If you do, please let us know your use case in the community or via support chat.