Skip to main content
Restricted fields hide specific fields from a role, for one flow or data type at a time. People with that role don’t see those fields in task and data screens or in the API (dashboards are the exception, see below). Use it to:
  • keep sensitive information private, for example hiding customer phone numbers from field workers;
  • simplify screens by hiding fields that don’t matter to a role;
  • meet compliance rules that limit who may see certain data.
Required permission:
  • View permission
  • Edit permission

Set restricted fields

  1. Open Settings › Permission and select the role.
  2. For tasks: in the Activities card, under Task › View task, click Configure next to No restricted fields configured. For data sources: do the same under View data source in the Workflow card.
  3. In Applies to, choose the flows (or data types) these restrictions apply to.
Task restricted fields
  1. For each one, choose the fields to hide. The editor shows how many fields are hidden, for example 3 fields hidden. A flow with no fields to restrict says so.
  2. Click Save in the editor, then Save on the Permission page.
Repeat for every flow or data type that needs restrictions.

What people with the role see

  • Hidden fields don’t appear as columns in the task list or the data source list, and they can’t add them back from Columns.
  • Hidden fields don’t appear in the task detail or the record detail.
  • The same fields are removed from what the API returns to these users. Asking for a hidden field directly through the API is refused.
  • Dashboards do not follow restricted fields. A hidden field of a flow or data type still appears in custom widgets (Group by, Filters and Sample rows), and its values show in widgets to everyone who can open the dashboard.