Skip to content

Atlas

Answers from this help and cites its sources. 20 questions a day.

Permission profiles

A permission profile decides, object by object, which records a member sees, creates, edits and deletes, and which actions they can take. You create it once, then assign it to several members.

Depending on your plan Settings › Team and access › Permission profiles The Owner and Admins
12
  1. 1New profile
  2. 2Edit a profile
Hover a number to locate the area. Click the screenshot to enlarge it.
The Permission profiles page: each profile with the number of members who have it, its last change date and the Edit button, and the New profile button.
A profile's editor: the name, the object table with View, Create, Edit and Delete, the All other objects rule and own rules, then the actions and visible revenue.
  1. Click New profile and give it a name (unique in the organization).
  2. Set the All other objects row: it is the default rule for every object.
  3. For an object that should be an exception, turn on its switch (Own rule) and set its row.
  4. Choose the allowed actions and the visible revenue.
  5. Click Create profile.

For each object, View, Edit and Delete take a scope, and Create is a checkbox:

Scope Records it covers
None No record of this object.
Own records Those the member owns, plus those of the members of the teams they lead.
Their team Those of the members of their teams.
All Every record of the object.

Edit and Delete never go beyond View, and without View there is no Create. Unowned records imported from a shared mailbox the member reads also count for reading and editing. On an object without an owner field, only None and Create matter.

Actions:

  • Import a CSV, on the objects where they can create;
  • Bulk edit: edit, transfer, archive or delete several records at once;
  • Workflows: create, publish and run their own workflows (replaces the Automator option);
  • Data model: manage the organization’s own fields and objects;
  • Integrations: connect and manage the organization’s integrations.

Visible revenue sets the Stripe amounts in dashboards and on records: None, Their companies or All.

In Members, open a member’s menu and choose Permission profile. The profile then replaces their member settings (scope, Automator, data model, revenue). It does not apply to Admins or the Owner, who have every right.

The same rules apply everywhere: lists and records, CSV import, record transfer, Atlas and MCP clients.

Edit opens the same editor; changes apply to every member who has the profile. Deleting a profile puts its members back on their member settings.