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

Permissions: Allowed, Team-wide access, If responsible, Denied

Corteksa has two kinds of permissions: switches that turn features on, and levels that decide which records, chats and emails a person sees. If someone has several roles, the highest level among them applies.

10 min

Two kinds of permissions

1) Feature switches: allowed or denied, such as managing members, roles, templates, dashboards and business hours. The full list is in Every feature switch in a role.

2) Access levels: set for each Cortex Unit, each chat channel and each type of mailbox.

The four levels

Level
What the person sees in records
Allowed (A)
All records
Team-wide access (G)
Records assigned to them, or to anyone in their team
If responsible (M)
Records assigned to them, even as one of several assignees
Denied (D)
Nothing

From highest to lowest: Allowed, then Team-wide access, then If responsible, then Denied. Team-wide access always includes the person’s own records, even if they’re in no team.

The units matrix (for each Cortex Unit)

Action
What it controls
Levels
When not set
View
Opening records and seeing them in tables, search and dashboards
A / G / M / D
If responsible
Edit
Editing fields and moving a record to another unit
A / G / M / D
If responsible
Add
Creating new records
Allowed or denied
Allowed
Delete
Deleting records
A / G / M / D
If responsible
Export
Exporting records
A / G / M / D
If responsible
Assign
Changing who a record is assigned to
Allowed or denied
Allowed

More in Unit permissions: view, edit, add, delete, export and assign.

The channels matrix (for each channel)

Rows: WhatsApp Web (Cortex Chat), WhatsApp Cloud, Facebook, Instagram, TikTok and WhatsApp Groups.

Action
What it controls
Levels
When not set
Read
Seeing chats
A / G / M / D
If responsible
Create
Connecting a new session, starting a chat, and syncing old history
Allowed or denied
Denied
Update
Sending messages, replying, and session settings
A / G / M / D
Denied
Delete
Deleting chats, messages and sessions
A / G / M / D
Denied
Level
What they see in channels
Allowed
Every chat in the sessions they’re a member of, plus the chats of records they own
Team-wide access
The chats of records owned by anyone in their team
If responsible
Only the chats of records they own. A chat not linked to a record shows only at Allowed
Denied
Nothing

WhatsApp Groups have their own rule, because a group has no record. More in Chat channel permissions for each role.

The email matrix (for each mailbox type)

Rows: Gmail, Outlook / Microsoft 365, and IMAP / SMTP. The same actions: read, create, update and delete. (Outlook is connected as IMAP for now.) (Outlook is connected as IMAP for now.)

Level
What they see in email
Allowed
All email of this type
Team-wide access
Email of records owned by anyone in their team, and unlinked email in the mailboxes they work in
If responsible
Email of records they own, and unlinked email in the mailboxes they work in
Denied
Nothing

More in Mailbox permissions for each role.

Who goes past the matrix

The owner and super admins see everything. See Member ranks: owner, super admin and member.

A new unit

When a unit is created, its creator’s roles get Allowed and every other role gets If responsible, without any role going above its usual level. So a read-only role stays read-only.

If you see nothing

A record or chat you can’t see shows as “not found”. An empty list means your level covers nothing there, not that you’re blocked from the page.

At a glance

Default role
Permissions
Admin
Everything, on every unit, channel and mailbox
Viewer
Sees and exports every record, reads every chat and email, and can’t add, edit, delete or assign

A real example

Namaa Academy
The situation

The director wants each salesperson to see only their own clients, and each team lead to see all of their team’s clients.

What they did
  1. A “Sales” role: view and edit If responsible, delete Denied, and assign Denied.
  2. A “Team lead” role: view, edit and export Team-wide access, and assign Allowed.
  3. She put each team lead and their salespeople in one team.
The result

Everyone sees exactly what’s theirs, in tables, chats, dashboard numbers and live updates.

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

Good to know

Changing a role updates the permissions of open sessions straight away.
Dashboard numbers, live updates and notifications follow each person’s level.
Comments follow the permission to view the record.
API keys work with the permissions of the person who created them. See Key scopes, and how they combine with permissions.
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.