Skip to main content

​
How access works

Access to accounts is controlled by three layers:
  1. View permission — The role must allow the Accounts page.
  2. Data scope — The role decides which creator records are in scope.
  3. Action permissions — Adding, editing a name or note, changing a proxy or sharing level, and deleting are granted separately.

​
Understanding groups

Groups represent your organizational structure — teams, shifts, departments, etc.

​
Data scopes

Owner and Admin have full agency access. Custom roles can use any combination of granular permissions and scopes, so a job title alone does not determine access.

​
Columns in the table

​
Employees (direct access) column

Shows which team members are assigned personally to this creator.
  • Displays names of assigned employees
  • Hover to see the full list
  • Shows “None” if no one is assigned

​
Groups (group access) column

Shows the organizational path for this account.
  • Displays groups from most specific to top level
  • Shows arrows indicating the hierarchy
  • Hover to see the complete structure

​
Common scenarios

​
”I can’t see an account I need”

You might not have access. Ask your manager to:
  • Assign you directly to that account, or
  • Move you to a group that has access

​
”I can see the account but can’t edit it”

You have view access but not edit permission. Contact your admin if you need to make changes.

​
”A team member can’t see an assigned account”

Check both the direct assignment and the role’s Accounts view permission. A direct assignment does not override a missing page permission.

​
Review access safely

When access is too broad, check every assigned role because permissions from multiple roles are combined and the broadest scope for the same permission wins. Change the role or assignment that grants access; moving someone between groups can also change the creator set immediately.