Problem: Some fields within an entity may need different permissions than others. E.g., if a Task has a “Due Date” field, this ideally would not be editable by the Assignee - only by a “manager”. But the Assignee will have Editor permission for most everything else in the Task. A hack might be to …

I don’t know when (if ever) field-level permissions might be implemented, but in the meantime, you might consider having an automation that notifies the manager when the Due Date field is updated, so at least he/she can be warned that someone is making changes. (and the change can be reverted if ne…

Hi, We have several databases where we would like to limit visibility to some of our users (in this case our interns and externals who have access to our documentation)… Currently the only solution I see is to create a separate database, however I wondered if there is any option to provide access o…

Field level permissions are not on the radar any time soon

[image] Matt_Blais: A hack might be to use a lookup to a Due Date field that exists elsewhere, but that complicates changing the Due Date for someone who does have permission. You alread know this but just for people who may read this… When you update a field in Fibery it runs in a system mod…

[image] Yuri_BC: When you update a field in Fibery it runs in a system mode that doesn’t record who made the change What do you mean by this? The activity log (for the workspace and for each entity) records whoever updates a field.

[image] Chr1sG: The activity log (for the workspace and for each entity) records whoever updates a field. yes, but Fibery does not currently expose this user context directly in field-change automations, right?

[image] Yuri_BC: yes, but Fibery does not currently expose this user context directly in field-change automations, right? true, but how does that relate to the text you quoted: [image] Matt_Blais: A hack might be to use a lookup to a Due Date field that exists elsewhere, but that complic…

It applies to both your and his messages. Matt says a lookup field to field elsewhere complicates changing the Due Date for someone who does have permission. You suggested a notification when the field is updated. The complication is that without user context any corrections or restrictions need …

Then I don’t understand what the problem is. If you have an automation that notifies someone when a field is changed, it is possible to get the identity of the person who made the change using a formula: User who triggered rule [image] (and similar is available in buttons: User who clicked butto…

Wow thats amazing, thank you for pointing that out. I will test it now…

Field-level permissions

Ideas & Features

mdubakov January 22, 2026, 3:33pm 12

Now you can try to use Validation Rules to solve many of such cases

Topic		Replies	Views
Why can't I control access to certain views, and/or specific fields Get Help	4	77	June 17, 2025
[DONE] Entity-level permissions Ideas & Features permissions , sharing	113	6294	October 18, 2024
Hide Fields for Viewers? Ideas & Features	5	75	March 26, 2026
Setting field/UI properties based on conditions Ideas & Features	6	448	May 28, 2025
Exploring private data management in Fibery	10	594	May 8, 2024

Field-level permissions

Related topics