Skip to main content

Roles and permissions

Roles determine which workspace features and actions a member can use. Permissions can be configured for individual areas, so two workspaces can give the same role different access.

Who can do this​

Owners and Admins can access workspace user settings. Members can ask a workspace administrator to explain or adjust their access.

Default roles​

RoleWorkspace description
OwnerFull access to workspace features.
AdminManages most workspace features; billing access may be restricted.
MemberStandard user whose access depends on the permissions enabled for the role.

Workspaces can also create custom roles for their own teams. Their names and permissions depend on the workspace.

Create and assign a custom role​

  1. In the workspace where the role will be used, open Settings → Team Members → Roles & Permissions. Use an Owner or Admin account with permission to manage roles.
  2. Select Create Custom Role. Enter a Role Name, such as Inbox triage, and use Description to record what the role is for.
  3. Enable the permissions the role needs. Check both the action and the record scope. For an inbox triage role, review the Unified Inbox viewing and assignment permissions. Enable Send only if these members also reply to conversations.
  4. Select Create Role. To apply it to an existing user, open Team Members → Members and change the member's role. For a new user, choose the custom role when sending the invitation.
  5. Ask the member to refresh and check the relevant page, record visibility, and available actions. Confirm that access matches the responsibilities you intended for the role.

Changing a role's permission set affects everyone assigned to it. Create a separate custom role when only part of a team needs additional access. Check module availability and record sharing alongside role permissions when an action or record is missing.

Review permissions​

  1. Open Settings → Team Members → Roles & Permissions.
  2. Select the correct workspace and review its roles and members.
  3. Open a role's edit control to review its permissions. Permission groups contain separate actions, such as View, Create, Edit, Delete or Send where applicable.
  4. To change access, select the permissions needed for the role and save the change. Changing a role affects the members assigned to it.
  5. Ask affected members to refresh the workspace and check the features they need.

For example, Contacts distinguishes View (Own) from View (All) and has separate Import and Export permissions. Smart Flows separates View, Create, Edit, Delete and Execute. Unified Inbox includes separate View (All), Assign and Send permissions.

Reports Center has a Reporting permission group with View (Own) and View (All) scopes. The Sales: Reports group separately provides View (All) and Export. Owners have full access; for Admins, Members, and custom roles, review the flags in the selected workspace. Check the relevant Export permission when a report offers an export action.

Workforce also has a dedicated permission group. It includes Attendance, Leaves, Approvals, KPIs, View (Own), View (Team), View (Group), View (Department), View (All), Edit, Requests, Reporting, and Settings. These are independent controls: a member may have access to a personal page without team-wide visibility, or may see a page without permission to edit or approve its records. The Owner role has full access. For every other role, verify the permission flags and data scope in the selected workspace; the role name alone does not determine Workforce access.

Verify your work​

  • The member has the intended role in the correct workspace.
  • The role has the permissions needed for the member's work.
  • After refreshing, the member can access the expected features and records.
  • For Workforce, check the specific page/action permission and the matching own, team, group, department, or all-data view scope.

Tips​

Give members the access they need for their work, and review role permissions when responsibilities change. A feature can also depend on workspace settings, enabled modules, record access or a connected service.

Troubleshooting​

If a menu or action is missing, check the member's role, the relevant permission and whether the module is enabled. For a particular record, check that the member has access to that record or shared board as well.

See also​