Field permissions hide or lock one field for chosen members or Teams. They sit on top of solution and table permissions: a member must already reach the table before a field permission means anything.

Here is the test: is there one value in a table that some people must not see, or must not change? If yes, set that field's permissions. If a whole table is the issue, use Table Permissions. If whole records are, use Dynamic Record Permissions.

Example: a Vendor Management solution. On the Vendors table, only the Security Team sees the Security Risk Notes field. On the Contracts table, only the Procurement Team edits Annual Contract Value, while the Finance Team reads it.

The column menu of the Security Risk Notes field in Grid View, with Edit Field Permissions and its lock icon highlighted.

Plan Availability	Professional, Enterprise and Signature. Signature provides the same capabilities as Enterprise, but this is where our GRC and IT Service Delivery products can be licensed. These products can not be licensed for Team, Pro or Enterprise plans.
Permissions	Account Administrators and the solution's Solution Managers.
Platform	Web
Related Reading	Table Permissions Solution Permissions: who can see and edit Field Management: add, edit, duplicate or delete Conditional Record Fields.

Opening Field Permissions

In Grid View, select the chevron on the field's column header. The column menu opens.
Select Edit Field Permissions, the item with the lock icon.

The Field Permissions dialog opens under the line "Allows you to further limit view and edit access to this field". It asks two questions, Who can View this Field? and Who can View and Edit this Field?, each with a dropdown of the same four answers. A footer under a crown icon reminds you that Solution Managers have access to view and edit all fields, next to Cancel and Save. The rest of this article takes the two questions in that order, then Save.

Note: Five fields cannot carry permissions: Record Title, Auto Number, First Created, Last Updated and Open Comments. Their dialog opens with both dropdowns grayed, and a line under each says the field type doesn't allow custom View or Edit permissions.

Who can View this Field?

Who sees the field at all. The dropdown reads Everyone (default) until you change it. The four answers, with the product's own line under each:

Everyone: any member of the table can see the field.
Everyone except: any member of the table can see the field, except selected members or Teams.
Selected Members or Teams: the field is visible to selected members or Teams only.
Nobody: nobody can see the field, except Solution Managers.

For Security Risk Notes: Selected Members or Teams, the Security Team. Everyone else never sees the field, on forms included.

The Field Permissions dialog for Security Risk Notes: Who can View this Field? set to Selected Members or Teams with the Security Team in the Add Teams or Members box, the edit question the same, and the Save button.

Who can View and Edit this Field?

Who can change the value. The dropdown reads Everyone (default) until you change it. The same four answers:

Everyone: any member of the table can view and edit the field.
Everyone except: any member of the table can view and edit the field, except selected members or Teams.
Selected Members or Teams: the field is editable for selected members or Teams only. They can also see the field, even when Who can View this Field? leaves them out.
Nobody: nobody can edit the field, except Solution Managers. Read-only for everyone else.

For Annual Contract Value: view Everyone, edit Selected Members or Teams with the Procurement Team. Finance reads the value and cannot change it.

Picking the members or Teams

Choosing Everyone except or Selected Members or Teams adds a box under the question, Add Teams or Members, with a + at its right. The + opens a picker grouped Members and Teams, the Everyone Team among them. Pick as many as you need. The picker offers members and Teams only, never a role or a level.

Saving

Select Save. The change applies at once for every member. If you close the dialog with a change pending, a prompt asks "Are you sure?" with two buttons: Exit without Saving drops the change and Save Changes keeps it. Cancel with nothing pending closes the dialog at once.

What members without access see

A member who cannot view the field does not see it anywhere. The field's name is absent from records, reports and view controls. It is left out of the record window, Linked Record tiles, Grid View and Card View. If a Files and Images field is a card's cover image, the card shows without a cover. In Map, Calendar and Timeline views the field is left out of the View By controls.

A member who can view but not edit sees a lock icon on the field. Its tooltip reads "Edits to this field are restricted".

A Contracts record as a Finance member sees it, with the lock icon on Annual Contract Value and its tooltip.

Note: A field permission applies on forms too. A member who cannot view a field does not see it on a form. To hide a field on the record page only, use Conditional Record Fields (Enterprise and Signature).

What each role can do

Account Administrator and Solution Manager: set field permissions, and always see and edit every field.
Solution Creator: as a Solution Manager of the solutions they create.
General Access: subject to the setting.
Guest: A Guest sees and comments on the records assigned to them, cannot be granted any other permission, even through a Team, and does not use a paid seat.

Using field permissions day to day

Hide the few, lock the sensitive, leave the rest at Everyone. In Vendor Management two fields carry permissions and the rest do not. Security Risk Notes is hidden from everyone but Security. Annual Contract Value is visible to all and editable by Procurement alone.

Tip: Name Teams, not people, in Selected Members or Teams. When Security changes, the field follows the Team.

Changing field permissions later

Reopen the column menu and select Edit Field Permissions again. Change either answer and Save.

Frequently asked questions

Does a field permission hide the field on forms?

Yes. A member who cannot view the field does not see it on a form either.

Can I hide a field for one role, for example Guests?

No. The picker names members or Teams, not roles. Put the members in a Team and name the Team under Everyone except. A Guest already sees only the records assigned to them.

Can I lock a field for everyone except me?

Yes. Set Who can View and Edit this Field? to Selected Members or Teams and name yourself. Solution Managers and Account Administrators can still edit it.

Which fields cannot have permissions?

Record Title, Auto Number, First Created, Last Updated and Open Comments. Their dropdowns are grayed and the dialog says the field type does not allow custom permissions.

Need more help? Ask the SmartSuite Community, where builders, administrators and the SmartSuite team answer questions about building on SmartSuite. For your account, billing or data, select the chat button in the lower-right corner of SmartSuite to reach support.

Last verified 1 Nov 2026.