All topics
Get started8Account, team & permissions44Units & fields70Records, views & tasks39WhatsApp & Cortex Chat68Email & social27Lead ads & distribution38Automations52Documents & quotes32Dashboards40Cortex AI18Developers & API12
Help Center·448 guidesAll topicsContact support

Unit permissions: view, edit, add, delete, export and assign

Each Cortex Unit has six actions in a role. Four of them take a level (Allowed, Team-wide access, If responsible, Denied), and two are only allowed or denied: add and assign.

5 min

How it works

Action
What it controls
Notes
View
Opening the record, and seeing it in tables, kanban, search, relations, dashboards and live updates
Without it, the record never shows, and “not found” appears instead
Edit
Editing fields, and moving the record to another unit
Applies only to the records the level covers
Add
Creating a new record, and importing
Allowed or denied. “If responsible” makes no sense for a record that doesn’t exist yet
Delete
Deleting a record or a group of records
A bulk delete skips the records outside the level
Export
Exporting records to a file
Exports only the records the level covers
Assign
Changing a record’s assignee or assignees, one record at a time or in bulk
Allowed or denied. It also needs the permission to edit that record

When assigning is denied

If assigning is denied, the assignee field is read-only. If the person edits a record and changes the assignee, their other edits are saved, and the assignee change is ignored with a warning.

When not set

A role with no settings for a unit gets “If responsible” for view, edit, delete and export, and it’s allowed to add and assign.

Comments

Anyone who can see a record can comment on it. Only the comment’s author, the owner and super admins can edit or delete a comment. See Comment and mention teammates inside a record.

A real example

Shield Security Co.
The situation

Technicians update visits, but only the coordinator assigns them.

What they did
  1. A “Technician” role: on “Visits”, view and edit If responsible, and assign Denied.
  2. A “Coordinator” role: view Allowed, and assign Allowed.
The result

A technician can’t hand a visit over to a teammate, and the coordinator assigns every visit.

A made-up company, to show the idea. The numbers are rounded.

Good to know

Add and assign are only Allowed or Denied.
The assign permission doesn’t give edit, and edit doesn’t give assign.
Did this guide solve it?
If not, we’ll ask what was missing.
Open in Corteksa
Did this guide solve it?

We read every answer. To get a reply, use Contact support.