Modules

Who can see and change a field in Studio

Limit who sees or changes a field of a custom module by role or access group, make a field invisible, and learn why a Super Admin must apply a limit that keeps other Managers out.

In Studio, a field of a custom module can be limited to certain roles and access groups, and it can be made invisible. A limit is a real rule, not a screen effect. This page covers both.

Limit a field

Click a field on the form to open Field properties. Two settings decide who may use the field:

  • Who can see this field. The default is everyone who can open the record.
  • Who can change this field. The default is everyone who can edit the record.

For each, choose the Roles allowed: Managers, Developers, Employees, and Viewers. Choose the Groups allowed too, from the access groups your workspace has. Groups are made in Settings, Access Rights. A workspace with no groups says so. Super Admins always can.

A field with no limit behaves as it always did. Nothing changes until you apply the change.

What a limit does

A person who may not see a field never receives its value. The server keeps this everywhere the value goes: the record, lists, boards, totals, search, exports, the API, the Agent, and automations. A value they send for that field is ignored as if the field did not exist, so they cannot test what it holds. A person who may see a field but not change it sees the value, and a change is refused.

Hiding a value would be pointless if something else gave it away, so these follow the limit:

  • A formula that reads a limited field is hidden from the same people.
  • A field whose show condition reads a limited field is hidden from them as well.
  • A field whose read only condition reads a limited field is locked for them.

A limit that cannot be read closes the field instead of opening it.

A Super Admin applies a limit that keeps other Managers out

A Manager who builds a module in Studio can limit a field. If that limit keeps out another active Manager who could see the field before, a Super Admin must apply the change. The review shows this line: The limit on {field} keeps other Managers out of it. A Super Admin must apply this change. The change stays proposed, and a Super Admin can apply it as it is.

The same holds for every other way such a limit could come back or tighten. Below a Super Admin, an Undo or a restore of an earlier module version that brings back such a limit is refused, and so is removing a member from a group, or deleting a group, that a field limit names when that would keep an active Manager out.

The review also warns about the reach of such a limit. Everyone outside the list for the field also stops seeing other people's automation run data and shared Agent chats, across the whole workspace.

Only a Super Admin can remove a field that has a limit, or a field that a limited one depends on. Anyone who reuses the name of an earlier field is told that records still hold values from it, and is asked to choose another name or ask a Super Admin.

Make a field invisible

Turn on Invisible in a field's properties to hide it from the module's pages for everyone. The field stays in the module and its records keep their values. This is different from a limit, which hides a field only from the people outside it.

An invisible field draws nowhere on the module's pages, so nothing about it is sent to the browser from those pages: no value in a row or a record, and no search, sort, or filter on it. A field whose show condition reads an invisible field is invisible too.

Two fields are kept even when hidden, because the page needs them: the workflow's stage, and the field a board uses for its columns. A required field needs a default before it can be hidden, and some system fields always show.

If a mark on the list reads an invisible field, the review warns that the mark will not draw for anyone.

Invisible fields below a Manager

For people below a Manager, an invisible field is protected as well as hidden. They cannot change it from any route, including the API, imports, file uploads and connector runs: a value sent for it is ignored, as if the field did not exist. Nothing they do can reveal it either. A duplicate value or a lock never names it or depends on its value, and a rule that reads it is judged without it.

That has these effects to plan for:

  • A calculated field that reads an invisible field is invisible to them too.
  • A field whose lock condition reads an invisible field stays locked for them.
  • A required rule whose condition reads an invisible field always applies to them, so the field is required. A date order rule with an invisible side does not apply to them.
  • Under an approval rule on an invisible field, any change they make to an approved record sends it back for approval, whatever the value.

Managers and Super Admins see and change invisible fields as before.

Troubleshooting

The change says a Super Admin must apply it

A limit on a field would keep other Managers out of it. Ask a Super Admin to open the proposal and apply it.