In the previous section, we applied settings that applied to tabs. Tab permissions settings in many cases allow us to create permissions more easily since the settings are applied to all the fields assigned to the tab. After first applying tab permissions, we can now apply field level permissions as needed.
Note that field level permissions have the same effect as tab permissions, but applied more specifically at the field level.
Applying the same rules to all fields in a tab will have the same effect as applying a rule to a tab which holds those fields.
We'll continue by now updating Field Permissions for the example Projects Tool.
Note that in the settings area, Field Permissions are labeled as Advanced Column Permissions.
Field Level Permissions Take Precedence
If permissions are applied both with tab permissions and field permissions, the field permissions are given precedence. A field level permissions that denies access will be enforced regardless of the tab permission.
The first section of our form, the Definition tab needs some adjustments. Here's a list of the changes needed:
- Proj ID is assigned by the system. It should be hidden on new and readable on edit / display.
- Manager Signature should not be shown on the add form.
- Spent should not be shown on the add form.
The rules to accomplish the requirements look like this:
In the next section, here are the rules we need for Workflow:
- Status is read only for the user for edit and view / deny for add.
- The same pattern is needed for Last Workflow Date, Last Workflow User and Last Workflow Note.
The History tab / field should be read only for edit / view:
The Manager Notes section is already handled by Tab Permissions.
Permissions are frequently Paired using one rule to specify when access should be restricted and another rule to specify when it should be granted.
Without adding a second rule to grant access, you will find that the content is inaccessible!
Always check your configuration by frequently accessing the new, edit and display forms to ensure that the settings are as expected.
9/14/2015 3:42 PM
5 comments [latest: 8/4/2017 3:07 PM]
[8/3/2017 9:44 PM]
Can you place the same column in two tabs and conditionally show the field in each tab? ie. show tab #1 with field "a" for content type 1 and then show tab #2 with field "a" for content type 2?
[8/3/2017 9:48 PM]
Chris: a column can receive only one permission level per form, so if it's visible on one tab, it's visible on both and it will cause the tab to be visible as well (although it will only contain this column).
[8/3/2017 10:33 PM]
So is there any way to have different forms for different content types in a list?
[8/4/2017 3:07 PM]
Chris: each content type will only show its own columns on the form. If you have a tab that only contains columns from one content type, it won't be visible when the other content type is selected.
Comments are not designed to replace support calls. If you have a specific issue with one of our products, please send an email to firstname.lastname@example.org
to open a support ticket.