Skip to main content
For Admins · Help Guide

Users & Roles

Manage who can access your workspace and control what they're allowed to do.

Real-World Use Case

Professional services firm with project-based teams

A consulting firm has 40 employees across three departments: Strategy, Technology, and Operations. Each department has a Director, Managers, and Consultants. The firm needs consultants to see only their own client engagements, managers to see their team's work, and directors to see everything in their department.

  1. 1Create a role hierarchy: CEO → Department Directors → Managers → Consultants
  2. 2Clone the base "Consultant" role for each department (Strategy Consultant, Tech Consultant, Ops Consultant)
  3. 3Disable peer visibility on the Engagements module so consultants only see their own clients
  4. 4Enable peer visibility on the Knowledge Base module so everyone can share resources
  5. 5Use field-level security to hide billing rates from Consultant roles (read-only for Managers, full access for Directors)
  6. 6Restrict the Import and Export features to Director roles only

Adapt this for your team: This same structure works for any organization: sales teams with territory-based reps, support teams with tiered agents, HR departments with regional managers, or educational institutions with faculty hierarchies. Create roles that mirror your org chart and let the hierarchy handle data visibility automatically.

Key Concepts

Here's what each term means in plain English.

User

A person who can log into your workspace. They have a name, email, and a role that controls what they can do.

Role

A reusable bundle of permissions. Instead of configuring access for each person, you create roles and assign people to them.

Role Hierarchy

Roles are arranged like an org chart. A role higher up can see all data owned by roles below it.

Module Permissions

Controls whether a role can Create, Read, Update, or Delete records in each module (Contacts, Deals, etc.).

Field-Level Security

Fine-grained control over individual fields. Make a field editable, read-only, or completely hidden for a role.

Feature Permissions

Controls access to platform features like Dashboards, Reports, and Import/Export. These are not tied to a specific record.

Peer Visibility

Determines whether users in the same role can see each other's records.

Notification Preferences

Default notification settings for a role. Controls which events trigger in-app or email alerts.

Settings Navigation

The Settings page has a left sidebar organized into categories. Users and Roles live under the Account section.

CategoryPages
AccountProfile, Workspace, Users, Roles
IntegrationEmail
CustomizationModules, Lock Rules, Form Rules, Notification Rules, Action Buttons
AutomationAction Flows
DataImport
AdminAudit Trail, Notification History

Users Page

SettingsUsers

This page shows everyone who has access to your workspace. A simple table where you can see at a glance who's on your team, what role they have, and whether their account is active.

Users list page showing a table with Name, Role, and Status columns
Two users listed. Click any name to open their detail page.

What Each Column Means

ColumnDescription
NameThe user's full name. Click it to view their profile and edit details.
RoleThe role assigned to this user (determines their permissions).
StatusActive = can log in. Inactive = access revoked.

Available Actions

ActionHow
Add a new userClick the "Create User" button (top right)
View/edit a userClick on their name in the table
Sort the listClick any column header
Change page sizeUse the "Items per page" dropdown at the bottom

Creating a User

Click "Create User" to open a dialog where you enter the new person's details. They'll receive an email invitation to set up their account.

Create User dialog with fields for First Name, Last Name, Email, and Role
All four fields are required. The button stays disabled until they're valid.

Form Fields

FieldRequiredDescription
First Name<span class="help-badge help-badge-required">Required</span>The person's first name
Last Name<span class="help-badge help-badge-required">Required</span>The person's last name
Email Address<span class="help-badge help-badge-required">Required</span>Where the invitation will be sent. Becomes their login email.
Role<span class="help-badge help-badge-required">Required</span>Which role to assign. This determines what they can access.

How It Works

  1. 1Fill in the person's first and last name
  2. 2Enter their email address
  3. 3Select a role from the dropdown
  4. 4Click "Create User"
  5. 5They receive an email invitation to set up their password
  6. 6Once they accept, they appear as "Active" in the users list

Tip: Submit with missing fields and validation errors appear below each one. "Create User" stays disabled until all fields are valid.

User Detail Page

SettingsUsers[User Name]

Click any user's name to see their full profile. This page shows all their information and gives you options to edit or remove them.

User detail page showing profile information, role, status, and action buttons
Profile card with Edit User and Delete User actions in the header

Information Displayed

FieldDescription
AvatarInitials-based avatar (e.g., "SE" for Samson Eductional)
Full NameDisplayed prominently as a heading
EmailTheir login email address
StatusGreen "Active" badge or "Inactive" indicator
Phone NumberContact phone number
RoleAssigned role name with a brief description
User SinceThe date they joined the workspace

Action Buttons

ButtonWhat It Does
Edit UserOpens an inline edit form to change name or role
Delete UserRemoves the user from the workspace (asks for confirmation)

Editing a User

Click "Edit User" on the detail page and the profile card transforms into an editable form.

User edit form showing editable First Name, Last Name, and Role fields
Edit mode. Change name or role, then click Save Changes.

Editable Fields

FieldEditable?Notes
First NameYesUpdate the user's first name
Last NameYesUpdate the user's last name
RoleYesReassign to a different role via dropdown
EmailNoCannot be changed from settings

Note: Changing a user's role immediately changes what they can access. Make sure the new role has appropriate permissions before reassigning.

Click "Save Changes" to apply your edits, or "Cancel" to discard them.

Roles Page

SettingsRoles

This page displays all roles as a hierarchy tree, showing parent-child relationships (who reports to whom).

Roles page showing a hierarchy tree with expand/collapse controls
Roles arranged by hierarchy. Hover any role to reveal the Add Role button.

What You See in the Tree

ElementMeaning
Crown iconSuper Admin (top-level role with full access)
People iconRegular role
Role nameThe display name of the role
"X members" badgeHow many users are assigned to this role
"Inactive" badgeRole has been deactivated
"System" badgeBuilt-in role that cannot be deleted
Expand/collapse arrowsShow or hide child roles

Tree Controls

ButtonWhat It Does
Expand AllOpens all branches to show every role
Collapse AllCloses all branches, showing only top-level roles

Adding a Role from the Tree

Hover over any role in the tree to reveal an "Add role" button. Clicking it opens the Create Role dialog with that role pre-selected as the parent.

Creating a Role

New roles are created by cloning an existing role's permissions and placing the new role in the hierarchy.

Form Fields

FieldRequiredDescription
Role Name<span class="help-badge help-badge-required">Required</span>A unique name (min 2 characters). Cannot duplicate an existing name.
Description<span class="help-badge help-badge-optional">Optional</span>Brief description of what this role is for (max 100 characters).
Clone From<span class="help-badge help-badge-required">Required</span>An existing role to copy permissions from as a starting point.
Reports To<span class="help-badge help-badge-required">Required</span>The parent role in the hierarchy. Determines data visibility.

Understanding "Reports To"

The hierarchy determines who can see whose data. A parent role can see all records owned by child roles below it.

`` Sales Director (sees all sales data) ├── Sales Manager (sees their team's data) │ ├── Sales Rep A (sees only their own data) │ └── Sales Rep B (sees only their own data) └── Account Manager (sees only their own data) ``

Understanding "Clone From"

Instead of building permissions from scratch, you pick an existing role to copy. After creation, you can customize the new role's permissions independently. Changes won't affect the source role.

Steps

  1. 1Hover over a role in the tree and click "Add role"
  2. 2Enter a unique role name
  3. 3Optionally add a description
  4. 4Select which existing role to clone permissions from
  5. 5Confirm the parent role (Reports To)
  6. 6Click Create
  7. 7The new role appears in the tree under its parent

Role Detail Page

SettingsRoles[Role Name]

Click any role in the hierarchy tree to open its detail page. This is where you configure everything about what users in this role can do.

Role detail page showing role info and module permissions
Vice President role. Data Access tab with editable CRUD permissions per module.

Role Details Card

FieldDescription
Role NameThe display name of this role
StatusActive or Inactive
DescriptionWhat this role is for

Tabs

TabWhat It Contains
Data AccessModule permissions (CRUD), Field-level security, Peer visibility
NotificationsDefault notification preferences for this role
Users (count)List of members assigned to this role

Note: The Super Admin role has full access to everything. Its permissions are displayed but cannot be modified.

Module Permissions

Found in the Data Access tab. A table showing each module with checkboxes for the four CRUD operations.

Permission Types

PermissionWhat It AllowsExample
CreateAdd new records to this moduleCreate a new Contact
ReadView existing recordsSee the Contacts list and open records
UpdateEdit/modify existing recordsChange a Contact's phone number
DeleteRemove records permanentlyDelete a Contact from the system

How It Works

  • Checked = permission granted
  • Unchecked = permission denied
  • Row checkbox = select/deselect all four permissions for that module at once
  • Search box = filter modules by name

In practice: If a role doesn't have "Read" for Deals, the Deals module won't appear in their sidebar. If they don't have "Create", the "New Record" button won't show.

Field-Level Security

A more granular layer below module permissions. Even if a role can access a module, you can hide or lock specific fields within it.

Access Levels

LevelWhat It MeansUse Case
Read & WriteUser can see and edit this fieldStandard fields everyone works with
Read OnlyUser can see but not change this fieldSensitive data like revenue that only managers edit
Don't ShowField is completely hiddenInternal fields certain roles shouldn't see

How It's Organized

  • Fields are grouped by module in collapsible sections
  • Each section header shows: module name, total field count, and a summary (e.g., "5 editable, 2 read-only, 1 hidden")
  • Expand a section to see a table with radio buttons for each access level
  • Use the search box to filter fields by name across all modules

Feature Permissions

Controls access to platform features not tied to specific records. Only visible to Super Admins when managing other roles.

Feature Groups

GroupFeatures It May Include
DashboardView dashboards, create/edit reports, manage widgets
SettingsAccess settings pages, manage modules, configure rules
DataImport records, export data, bulk operations
AutomationCreate workflows, manage action flows
CustomizationModule builder, form rules, action buttons

How to Edit

Click the dropdown for a feature group to see all available features. Check or uncheck individual features. Groups with unsaved changes show an amber "Modified" label.

Important: Feature permissions are saved separately from module permissions. Make sure to save changes before switching tabs.

Peer Visibility

This setting answers one question: "Can users in the same role see each other's records?"

How It Works

SettingBehavior
EnabledUsers in this role can see records owned by other users who also have this role
DisabledUsers can only see their own records (plus records from roles below them in the hierarchy)

When to Use

Enable Peer Visibility

For shared resources like Accounts where the whole team needs visibility, or support tickets any agent might handle.

Disable Peer Visibility

For personal pipelines like Deals where each rep's opportunities are private, or individual performance data.

Peer visibility is configured per module. You might enable it for Accounts (shared) but disable it for Deals (personal).

Remember: The role hierarchy always applies on top of peer visibility. A manager role above in the hierarchy can always see records from roles below, regardless of this setting.

Notification Preferences

The Notifications tab sets default notification preferences for all users in this role.

Notifications tab showing notification types with App and Email toggles
Toggle App and Email channels independently for each notification type

Notification Channels

ChannelHow It Works
App (In-App)Shows as a notification in the bell icon panel within the application
EmailSends an email to the user's registered email address

Notification Types

TypeWhen It Fires
Record CreatedA new record is created in a module the user has access to
Record UpdatedAn existing record is modified
Record SharedRecords are explicitly shared with the user

Each notification type has independent toggles for App and Email. Toggle them on or off based on what's useful for this role.

Role Members

The Users tab shows everyone currently assigned to this role.

Users tab showing assigned members with avatars and status
One member assigned. Use Refresh to update after role changes.

What You See

  • Header: "Assigned Members (count)" shows the total number of users with this role
  • Refresh button: Reload the member list
  • Member cards: Each shows an avatar (initials), full name, and status badge

Common Workflows

Add a new team member

  1. 1Go to Settings → Users
  2. 2Click "Create User"
  3. 3Enter their first name, last name, and email
  4. 4Select the appropriate role from the dropdown
  5. 5Click "Create User". They'll receive an invitation email.

Change someone's role

  1. 1Go to Settings → Users
  2. 2Click on the user's name
  3. 3Click "Edit User"
  4. 4Change the Role dropdown to the new role
  5. 5Click "Save Changes"

Create a new role for your team

  1. 1Go to Settings → Roles
  2. 2Hover over the parent role in the tree (e.g., "Sales Director")
  3. 3Click "Add role"
  4. 4Name it (e.g., "Sales Representative")
  5. 5Select an existing role to clone permissions from
  6. 6Confirm the parent role (Reports To)
  7. 7Click Create
  8. 8Open the new role and customize its permissions in the Data Access tab

Restrict what a role can see

  1. 1Go to Settings → Roles → [Role Name]
  2. 2In the Data Access tab, uncheck module permissions they shouldn't have
  3. 3Set field-level security to "Read Only" or "Don't Show" for sensitive fields
  4. 4Disable peer visibility for modules where they shouldn't see colleagues' records
  5. 5Save your changes

Control which features a role can access

  1. 1Go to Settings → Roles → [Role Name]
  2. 2In the Data Access tab, look for the Feature Permissions section
  3. 3For each feature group, open the dropdown and select/deselect features
  4. 4Save your changes