Field level permissions in entries
Log in to add to favouritesPage last updated 05 March 2026
Field-level permissions allow administrators to finely control which fields are visible and editable by different roles. This granularity improves the editing experience by tailoring the interface to the specific needs and responsibilities of various authors.
How to configure field-level permissions
- Press the Settings button in the sidebar. The Settings menu will open, revealing a number of options.
- Select Roles to open the Roles listing screen.
- Locate the role where you would like to set field-level permissions.
- Select the Field permissions from the toolbox. A new permission will be added to the list.
- The permission you’ve added will be active and the Permissions panel for the selected permission will be displayed.
- Choose the Content type from the permissions panel that you want to apply field-level permissions on.
- Turn off the fields that the role should not be able to edit.
- Save your settings. The new permissions will be immediately reflected in the user interface for users with the specified role.
How field-level permissions work with multiple roles
Field-level permissions in Contensis are subtractive. When a field is disabled for a role, that role removes the ability for its users to edit that field in the entry editor.
Users can belong to multiple roles, and field restrictions apply across all assigned roles.
If a field is disabled in one role, users assigned to that role will not be able to edit that field—even if another role grants them general editing permissions for the entry.
Overriding field restrictions
Field-level restrictions cannot be selectively overridden by another role.
The only way to override a field restriction applied in another role is to configure the second role with Enable all fields for the relevant content type. This grants editing permission for all fields in that role, including fields that may be restricted elsewhere.
For example:
| Role | Field configuration | Result |
|---|---|---|
| Editor | featureHomepage disabled | User cannot edit field |
| Super Editor | No field permissions configured | User still cannot edit field |
| Super Editor | Enable all fields | User can edit the field |
Because of this behaviour, administrators should carefully consider how field restrictions are applied across roles.
Permissioning groups of fields
If you need to restrict a large number of fields, you may find it easier to set up tab-level permissions, which can remove an entire group of fields in the entry editor.
Recommendations and limitations
- Users of a role with field-level permissions applied will not be able to move the content into a new workflow stage where required validations apply.
- Ensure you test your permission model with real user journeys to ensure team members can fulfil their role.