What each role can do
| Role | See records | Add and change | Delete records | Change the data model |
|---|---|---|---|---|
| Owner | Yes | Yes | Yes | Yes |
| Administrator | Yes | Yes | Yes | Yes |
| Editor | Yes | Yes | No | No |
| Viewer and other roles | Yes | No | No | No |
Changing the data model means creating objects, fields and relations, and changing permissions. The workspace owner is never restricted.
Change it for one object
- Open Settings, then Data model, and choose the object.
- Open the Permissions tab.
- For each role, set See records, Add and change and Delete to the role's default, Allow or Deny.
- Choose Save.
For example, deny See records for Editors on an Invoices object, or allow Viewers to Add and change on a Support requests object. A role that cannot see records cannot change or delete them either. An object that a role cannot see is gone for that role: from the menu, the search, the API, imports, exports and agents.
An access token still needs the right ability (crm:read or crm:write), whatever a role allows.
Limit a role to certain records
Under Which records each role can reach, give a role a rule so that it reaches only the records that match. Choose Edit rules for the role and build the rule like a list filter, for example Lead is Me. The role then sees, in plain words, Can see: Lead is me.
- See limits everything. A record the rule does not match does not exist for the role: it is missing from lists, totals, groups, boards, calendars, search, exports, related records, favorites, duplicates, the trash, the timeline, notes and tasks, the API and agents, and opening it gives "not found". A filter on a field of a linked record never reaches records the role cannot see.
- Change and Delete narrow the rule further. Without a rule of their own they follow the rule for seeing records, so a role that can see a record can change and delete it, as long as the switches above allow it.
- On a member field you can pick Me (the person making the request) or My team. My team is the members who work with them: everyone in the workspace, except that a member limited to some projects works with the members who share one of those projects and with everyone who is not limited. Rules can use groups (all, any, none of) and a field of a linked record.
- Adding a record is judged by the Add and change switch alone. A role may add a record that its rule then hides from it; the new record is still returned once, in the answer that created it.
- A rule that cannot be applied, for example because it uses a field that was archived, lets no record through. The workspace owner is never limited, and an administrator is limited only when the rule is set for the Administrator role.
- Editing a record that is linked to records a role cannot see keeps those links; the role cannot link to a record it cannot see.
The count under a rule is how many records match; where the rule uses Me it is counted for you.
Hide or lock a field
Under Fields by role in the same tab, set a field for a role to:
- Full access (the default),
- Read only - the role sees the value but cannot change it, or
- Hidden - the role does not see the field at all. It is left out of records, tables, search, exports and the API, and cannot be used to filter or sort.
A hidden field also stops free-text search from looking inside the other fields for that role, so searching only finds records by their name.
Contacts, companies, deals and tasks
The permissions and record rules you set for these objects apply to the data model screens, the API and the agent tools. Their own pages (the contact list, the company and deal pages, the task list) keep the rules they have today.
