Hi, It would be great to have the ability to specify read/write permissions on the field level. That way someone can’t see all your models fields by simply looking at the schema; plus it would be really nice to have private fields that only x roles can see, it would open up the possibilities even …

For our use case we require to be able to specify CRUD permissions on field level. Some fields shouldn’t be visible for certain roles, some roles can see certain fields but not edit them, etc. So we either require to able to assign CRUD permissions based on roles, or be able to create different view…

Linked to: [image] Possibility to prevent field editing depending on permissions ✋ Feature requests It would be great to have an option to hide slug fields from editors. For most sites, my editors have no need to manually edit model slug fields, they can be generated from …

This would be great to have! For now, I’m just adding a “for developers only” fieldset and putting all the dangerous fields in there. There is also a Hidden Field plugin … maybe that can be extended to check user role/permissions before showing the field?

Yes, the “Hide field from role” plugin normally does the job: Hide field from role - Plugins - DatoCMS Let us know if the plugins are not enough!

That should be fine, thank you for the suggestion! It’s not the safest system (anybody who knows how to edit CSS can un-hide that and change the value), but on our small & trusted team it’s probably not an issue.

I completely agree, it’s just a workaround, but before adding a lot of complexity there we are trying to understand if that’s the only use case

One use case is to facilitate multi-role editor environments. For example one person might draft the initial article, another person might fill out the SEO fields, a dev might add some arbitrary JSON into a secret field, and then a reviewer would review & publish all of it. Or, another use case is …

yes, with the plugin you should be able to hide the fields from the specific roles. Regarding the ability of hiding a field after the creation you might be able to implement that with a plugin!

I’d like to be able to allow a role to edit only certain fields. For example, an SEO manager could be allowed access to just the metadata field.

Have the ability to specify read/write permissions on the field level

✋ Feature Requests

Souljuse November 25, 2019, 10:09am 3

Linked to:

Topic		Replies	Views
Best way to keep records “private” (avoid accidental publish) 🆘 Support	5	122	August 18, 2025
Fields updated by CMA leads to republishing content 🆘 Support	4	205	March 21, 2024
Ability to Lock Models/Blocks from UI Edits ✋ Feature Requests	3	95	May 12, 2025
Possibility to prevent field editing depending on permissions ✋ Feature Requests	0	729	September 18, 2019
Segmenting content in Dato ✋ Feature Requests roles-permissions	3	765	April 6, 2020

Have the ability to specify read/write permissions on the field level

Related topics