Help CenterAccount, team & permissionsLook it up
Mailbox permissions for each role
Email works like channels: a row for each type (Gmail, Outlook and IMAP), and four actions. Link employees to a shared mailbox so they see its unlinked email.
How it works
Action
What it controls
When not set
Read
Seeing messages and attachments
If responsible
Create
Connecting a new mailbox. Allowed or denied
Denied
Update
Sending and replying, labels, linking to records, and syncing the mailbox and its settings
Denied
Delete
Deleting messages and disconnecting the mailbox
Denied
Read level
What they see
Allowed
All email of this type
Team-wide access
The email of their teammates’ records, and unlinked email in the mailboxes they’re linked to
If responsible
The email of their own records, and unlinked email in the mailboxes they’re linked to
Denied
Nothing
Each mailbox has a list of members who work in it, and one linked unit. That list is what lets “If responsible” and “Team-wide access” see unlinked email. See Email in Corteksa: connect a mailbox and follow client email.
Good to know
3 types: Gmail, Outlook / Microsoft 365, and IMAP / SMTP. Connecting an Outlook / Microsoft 365 mailbox isn’t available yet, so Outlook is connected as IMAP and follows that row. Connecting an Outlook / Microsoft 365 mailbox isn’t available yet, so Outlook is connected as IMAP and follows that row.
Create is only Allowed or Denied.
When this matrix launched, the old permissions were carried over without any role losing access.
Did this guide solve it?
If not, we’ll ask what was missing.