Guide
Ways to share
There are also a few ways to share information outside Fibery:
User roles
Global user roles limit what kind of access a user can receive:
Admins always have maximum access to everything except others' Private Spaces.
Members can receive any kind of access.
Observers cannot update anything, only view and comment.
Guests can receive any access, but only to specific entities.
Check out User Roles for the detailed breakdown.
Users visibility
By default:
Guests can't see other Guests.
Admins, Members, and Observers can see each other as well as Guests.
You can make users visibility more or less strict in Users → Access:
Check out Access to Users guide for details.
User groups
User Groups simplify access management in larger workspaces: share Spaces (and later Entities) with entire Teams, Roles, or Tribes.
Check out the guide above on how to convert any Database into Group DB.
No overriding
Access is always extended and never overridden on a lower level of hierarchy. Here are a few examples:
Space & Entity: if someone has Editor access to a Space and is invited as a Viewer to an Entity in this Space, they'll be able to edit the Entity.
Group & User: if someone gets Owner access to an Entity as a part of a Group and then receive Commenter access individually, they'll be able to edit and share the Entity.
Extended access: if someone gets Commenter access to a Project extended to its Tasks and then Viewer access to one of those Tasks, they'll be able to comment on the Task.
So if you are sensitive about access the rule of thumb is: start with minimal permissions at the highest level (e.g. Space, Group) and add more on the lower levels (Entity, User).
FAQ
Can I set permissions for specific fields of an entity?
No, Fibery does not support field-level permissions, and we don’t plan to add them in the near future.
That being said, in most cases, field-level permissions aren’t necessary thanks to Fibery’s flexible structure. You can often achieve the same result by organizing data across different databases, views, or spaces - and applying permissions there. You can also achieve a similar effect by splitting your data across two databases:
General Task DB → contains non-sensitive information (visible to all employees).
Sensitive Task DB → contains sensitive fields like labor rates, costs, or other restricted info (visible only to managers).
Each real “task” would then consist of a linked pair of entities: one in the general DB and one in the sensitive DB. Managers can see both, while employees only see the general part.
Related fields can be added to show general info inside the sensitive DB for convenience.
Automations can create the “twin” entity automatically when a new task is added, keeping the workflow smooth.
If you have a specific use case where something needs to be hidden, please reach out to us in chat. We’d be happy to understand your needs and help you find a tailored solution using existing tools.
I have a user with the Observer role but they can’t see the databases. Even when I assign them access and give them a direct link, they get an error.
In Fibery, databases themselves are part of the builder-level experience, which means only users with the Architect role can access them directly. Observer and other non-architect users can’t view raw databases.
To give your Observer access:
First, create a View (like a Table, Board, Timeline, etc.) based on the database.
Then share that View with the Observer (with viewer or commenter rights as needed).
Once that's done, the Observer will be able to see and interact with the data in that view.