Skip to content
SAVE4545% off every plan.See the offer

Getting StartedUser Roles & Permissions

User Roles & Permissions

Complete guide to AutomateNexus CRM user roles and permissions including full permission matrix, RBAC business scenarios, organization hierarchy…

VideoHow to Set User Roles and Permissions in Your CRM
On this page· 19
User Roles & Permissions
User Roles & Permissions

User Roles and Permissions#

AutomateNexus CRM uses role-based access to govern what each user can see and do within the platform. This system ensures that administrative functions are only accessible to authorized personnel while giving everyday users the tools they need to be productive. This guide covers the roles, what each role can see and change, custom roles, what only administrators can do, workspaces, user management workflows, client organizations, approvals, the audit log and troubleshooting access issues.

Understanding Roles in AutomateNexus CRM#

Role-based access is a security model where permissions are assigned to roles rather than individual users. Each member of an organization has one role, set per member under Administration → Access → Members, and that role determines their level of access across the platform.

AutomateNexus CRM has five member roles:

  • Owner - Everything, including billing and other owners. Whoever starts a workspace owns it. Only an Owner can make someone an Owner, change an Owner's role or remove another Owner.
  • Admin - Everything in the CRM and its settings. Admins invite and remove members, change roles, create and manage workspaces and workspace membership, and open the administrative screens: the organization sections of Settings (Modules, Custom fields, Tags, Security, Approvals, Agent limits, Notetaker seats, API keys, Audit log, White-label), Custom Objects, Employees and Plans.
  • Manager - Works the records and runs a team. By default a Manager can see, add, change and delete every person, company and deal, and can export, import, bulk edit, merge duplicates, manage tags and build automations.
  • Member - Works the records. By default a Member can see, add, change and delete every person, company and deal, and can export, import, bulk edit and manage tags, but cannot merge records or build automations.
  • Viewer - Looks, never changes anything. A Viewer sees every person, company and deal but cannot add, change or delete them, and has none of the actions above.

Owners and Admins can always do everything. What Managers, Members and Viewers can do with people, companies and deals is set under Administration → Access → Roles and permissions, where you can change each role's defaults and create custom roles (see below). Managing members, workspaces and organization settings requires Admin or Owner whatever the role's permissions.

Separately, Administration → Access → Employee roles holds custom roles with their own permission sets. These roles apply to the employee portal only; what someone can do in the CRM comes from their role under Members, set in Roles and permissions.

What Requires Admin or Owner#

The following table lists the capabilities that are reserved for Admins and Owners. Everything else - the Dashboard, People, Companies, Deals, Activities, Quotes, Projects, Tasks, Mail, Chat, Calendar, Documents, Reports and your own account settings - is available to every member, within the workspaces they belong to and what their role lets them see and change.

Capability Where Admin / Owner Manager / Member / Viewer
Invite members, change roles, remove members Administration → Access → Members / Invitations Yes No
Change role permissions and create custom roles Administration → Access → Roles and permissions Yes No (they can view them)
Create, edit, delete workspaces and manage workspace members Workspace switcher → Create New Workspace; Workspaces page Yes No
Switch on or off product modules Settings → Modules Yes No
Manage custom fields and tags Settings → Custom fields, Settings → Tags Yes Only with the Manage fields or Manage tags permission
Create custom objects Administration → Custom Objects Yes No
Manage employee records Team → Employees Yes No
Organization security settings, single sign-on and audit log Settings → Security, Settings → Audit log Yes No
Review approval requests Settings → Approvals Yes No
Agent limits, API keys and notetaker seats Settings → Agent limits, Settings → API keys, Settings → Notetaker seats Yes No
White-label branding Settings → White-label Yes No
Karrie daily brief, lead scoring and channel alert settings Settings → Notifications Yes No
Invite a person to the client portal People record menu Yes No
Plans, billing and AppSumo code redemption Administration → Plans Yes No

Managers can also open Administration → Data Warehouse; adding a connection there takes an Admin.

Roles and Permissions#

Open Administration → Access → Roles and permissions to see what each role can see and change in People, Companies and Deals. The first table lists Owner, Admin (everything, always) and the built-in Manager, Member and Viewer roles, each with a Can see summary and the number of members who have it. Owners and Admins can change the permissions; everyone else can view them.

  • Edit permissions (in a role's menu) changes what everyone with that role can do, unless they have a custom role. A role you changed is marked Changed, and Restore defaults puts it back.
  • Custom roles are for people who need something between the built-in roles, like sales reps who only see their own deals. Click New role, give it a Name, pick a built-in role to Start from and add a Description. From a custom role's menu you can Edit, Duplicate or Delete it; members of a deleted role go back to the defaults of their role.

What a Role Sets#

  • Records - For People, Companies and Deals: See, Change and Delete each set to All records, Their team's, Only their own or None, and whether they can Add records. "Their own" means records they own; "Their team's" adds records owned by anyone on a team they are on (teams are set up under Team → Employees → Teams). Records they cannot see do not show up for them in lists, boards or record pages.
  • Fields - Per field, including custom fields: Can edit, Read only or Hidden. A hidden field is left out of their lists, record pages and exports. Either way they can fill it in when they add a record.
  • Actions - Switches for Export, Import, Bulk edit, Merge, Manage tags, Manage fields, Build automations (create, change and run workflows) and Manage people & payroll (pay, bank details, personal details and HR documents).

To give someone a custom role, choose it in the Permissions column under Access → Members, or pick it in Access when you invite them. Owners and Admins always have full access, so a custom role applies to Managers, Members and Viewers only.

Role-Based Access Business Scenarios#

To illustrate how roles work in practice here are three common business scenarios:

Scenario 1: Sales Team Setup#

A company has a sales director and five sales representatives. The sales director needs to manage the team, configure pipeline stages, and generate reports. The sales reps need to create and manage their own deals, log activities and communicate with customers, but should not be able to change organization settings.

Configuration: Assign the sales director as an Admin. This gives them full access to invite new team members, manage workspaces and organization settings, and generate reports. Assign each sales representative as a Member. They can create people and deals, log activities, use mail, chat and the calendar, but cannot change organization settings or manage other members. If the reps should only see their own deals, create a custom role under Access → Roles and permissions (for example Sales rep, starting from Member) with Deals set to Only their own, and give it to them in the Permissions column under Access → Members.

Scenario 2: Multi-Department Enterprise#

A mid-size company has separate sales, marketing and support departments. Each department needs its own data space, but the VP of Operations needs to see everything.

Configuration: Create three workspaces (Sales, Marketing, Support) from the workspace switcher. Make the VP an Admin and add them to all three workspaces. Add department heads and team members to their own department's workspace with Workspace Members on the Workspaces page. Workspace isolation ensures each department only sees their own data, while anyone who belongs to several workspaces can switch between them from the header. People who only need to look, such as an auditor, can be given the Viewer role.

Scenario 3: Agency Managing Client Organizations#

A digital agency manages CRM operations for multiple client companies. The agency needs centralized oversight, while each client organization should be independent and unable to see other clients' data.

Configuration: On a plan that includes client organizations, the agency's Admins see an Organizations group under Administration → Access. Invite each client from Access → Invitations with the Organization invitation type so they create their own organization under yours, then give the client's own staff Admin, Manager, Member or Viewer roles inside it. The Your organizations overview shows each organization's plan, seats, who administers it and how active it is, Users in your organizations lists everyone across them, and you can invite people straight into any client organization.

Step-by-Step User Invitation Flow#

Inviting new users to your organization follows a specific workflow. Only Admins and Owners can invite users.

  1. Navigate to Administration → Access in the sidebar and open Invitations.
  2. Click Send Invitation.
  3. Keep the Invitation Type on Team Member.
  4. Enter the new user's Email address, and optionally their first and last name.
  5. Select the Role to assign: Member, Manager, Admin or Viewer.
  6. Optionally add a Message, then send the invitation.
  7. The system generates a unique invitation link and emails it to the recipient.
  8. The invited user clicks the link in the email, which takes them to the invitation page.
  9. If the user already has an AutomateNexus CRM account they sign in there. If not, they create a new account during acceptance.
  10. Once accepted the user appears in your Members list with their assigned role.

You can also send a quick invitation from Access → Members with Invite User: the email address, the role and, when your organization has custom roles, Access (the role's own access or one of your custom roles), so the person has the access they are meant to have from the moment they accept. Invitation tracking is built in: the Invitations page lists invitations under All, Pending, Accepted and Revoked, shows when each pending invitation expires (7 days after it is sent, with an Expires soon warning in the last 24 hours), and lets you Resend or Revoke a pending invitation.

If your organization uses single sign-on, people at your verified domains can also join by signing in through your identity provider. See Single Sign-On (SAML) & SCIM Provisioning.

Changing a Member's Role#

Open Administration → Access → Members. The table lists every member with their name, email, role, permissions and join date, and can be searched, filtered and sorted. Change a role directly in the Role column (Owner, Admin, Manager, Member or Viewer), or open the member to edit their details. Only Admins and Owners can change roles, and only an Owner can make someone an Owner or change an Owner's role.

The Permissions column sets what a Manager, Member or Viewer can do with people, companies and deals: Role defaults or one of your custom roles. Owners and Admins show Full access; to limit what they can do, change their role to Manager, Member or Viewer first.

Client Organizations#

Plans that include client organizations let one organization manage others. When your account has this ability, Administration → Access gains:

  • Users in your organizations - A directory of every user across the organizations you manage.
  • Your organizations - An overview of each managed organization: plan, seats used, who administers it and how active it is, with a shortcut to invite people into it.
  • Plans - The plan of each managed organization.
  • Organizations - The full list, where each organization has Details, Members, Workspaces and Hierarchy tabs.

Client organizations operate independently with their own members, workspaces, customers, deals and data. Their users cannot see data from your organization or from sibling organizations. Seats count members other than client-portal users against each organization's plan.

Accounts that sell to client organizations also get an Agency tab under Administration → Plans, with their Clients, the Plans they sell them, Snapshots to start new clients from, White label and Storage & add-ons.

Approval Workflow Configuration#

AutomateNexus CRM includes an approval workflow system that requires an admin to sign off on certain records before they are finalized. Approval workflows are switched on per record type for your organization by the AutomateNexus CRM team: contact support to have invoices, deals, orders, projects or other records wait for an admin.

Once a type is on, pending requests appear under Settings → Approvals (Admins), with a count next to the section name. The Pending tab shows each request with what is waiting, and approvers can approve or reject it, adding a note when rejecting. The History tab keeps past decisions. Drafts written by the AI assistant are a separate queue under AI → Agent Approvals.

Workspace Membership#

Workspaces segment your organization's data. Admins manage who belongs to which workspace:

  1. Open the Workspaces page at /admin/workspaces.
  2. Open Workspace Members on the workspace card.
  3. Pick a person from your organization to add them; the list only offers people who are not yet members.

Members switch between the workspaces they belong to from the workspace switcher in the header.

Removing Users#

When a team member leaves the organization or needs to have their access revoked, Admins and Owners can remove them:

  1. Navigate to Administration → Access → Members.
  2. Find the user in the Members list and click the row to open their details.
  3. Click Remove, or select several rows and use the table's delete action to remove them together.
  4. The person is removed from the organization and can no longer open its workspaces.

Only an Owner can remove another Owner.

Important: Removing a user from an organization does not delete their platform account. They can be invited again later.

Audit Log#

Changes in your organization are recorded in the audit log under Settings → Audit log (Admins). Each event shows who did it, the action (Create, Update, Delete, Export, Import or Support visit), the record type, a risk level and the details. Filter the log by user, action, risk level, record type and date range for compliance and security reviews.

Troubleshooting Access Issues#

If users report problems accessing features or data here are the most common causes and solutions:

Issue Likely Cause Solution
User cannot see certain sidebar items The module is switched off, or the item is admin-only (Employees, Custom Objects) Switch the module on under Settings → Modules, or check the role badge in Settings → Profile and promote the user to Admin if they need administrative access.
User sees no data on Dashboard Not a member of the workspace, or the wrong workspace is selected Add the user with Workspace Members on the Workspaces page, and check the workspace switcher in the header.
User cannot see some people, companies or deals Their role or custom role sees only their own or their team's records Check the user's role and Permissions column under Access → Members, and the role under Access → Roles and permissions.
User can see records but cannot add or change them Viewer role, or a role whose Change scope is narrower than its See scope Change the role to Member, or widen the role's Change and Add settings.
A field is read-only or missing for a user The role sets that field to Read only or Hidden Edit the role's Fields under Access → Roles and permissions.
User cannot invite team members Manager, Member or Viewer role Only Admins and Owners can invite users. Promote the user if appropriate.
User cannot access billing Manager, Member or Viewer role Plans and billing require the Admin or Owner role.
Organizations group not visible in Access Plan does not include client organizations Client organizations are available on plans that include them.
Approval requests stuck in pending Approver has not reviewed Check Settings → Approvals → Pending. Notify an Admin.
User cannot access organization settings Manager, Member or Viewer role The organization sections of Settings are restricted to Admins and Owners.
User is asked to sign in with single sign-on Your organization requires single sign-on They sign in through your identity provider with Sign in with SSO. Owners can still use a password.

Best Practices for Permission Management#

  • Follow the principle of least privilege - Assign the minimum role needed for each user to perform their job. Start with Member, use Viewer for people who only need to look, and promote only when necessary.
  • Use custom roles for narrower access - When a role's defaults are too wide, such as reps who should see only their own deals, create a custom role instead of promoting or demoting people.
  • Use workspaces for data isolation - Use workspaces to segment data access by team or department, and roles for what people may do within them.
  • Review member roles quarterly - Periodically audit roles in Access → Members to ensure they still match job responsibilities. Remove or demote access for users who have changed roles.
  • Use approval workflows for sensitive records - Have record types that need sign-off, such as invoices or deals, wait for an admin to add a layer of oversight.
  • Document your access policy - Maintain an internal document that defines which roles are appropriate for which job titles in your organization.
  • Monitor the audit log - Regularly review Settings → Audit log to detect unauthorized or accidental changes.

Was this page helpful?

Last updated