For AI agents: the complete documentation index is available at https://docs.clickmax.io/en/llms.txt, the full documentation bundle is available at https://docs.clickmax.io/en/llms-full.txt, and this page is available as Markdown at https://docs.clickmax.io/en/reference/permissions.md.
  • English

      • Roles and permissions

      Every workspace member has a role that defines what they can see and change. On top of the roles, the CRM attendant has sub-roles that widen or narrow their reach inside the CRM.

      Prerequisites: only the Owner and the Admin manage member roles (invite, change role, deactivate/remove). All the roles below depend on the member having an active seat in the workspace.

      Workspace roles

      Descriptions as shown on the Manage role screen.

      Role (in the interface)What it does
      OwnerAccount owner, with full access — including the withdrawable balance (wallet).
      AdminManages the whole account: members, plans, channels, integrations and CRM. Does not see the withdrawable balance.
      EditorCreates and runs content and CRM. Does not manage members, plans or the wallet.
      CollaboratorDay-to-day operational access. No administration, finance or bulk creation tools.
      FinanceFinance-focused: sales, plans and billing. No access to content, CRM or the wallet.
      AttendantService and sales in the CRM, restricted to their own records.
      GuestMinimal access: the overview and only their own conversations in the CRM.

      Roles that can be invited

      The Owner role cannot be assigned: it exists only for whoever created the account. The rest can be set when inviting someone or when managing a member's role.

      RoleCan be invited
      OwnerNo
      AdminYes
      EditorYes
      CollaboratorYes
      FinanceYes
      AttendantYes
      GuestYes

      Attendant sub-roles (CRM)

      The Attendant role has a sub-role inside the CRM. The Coordinator is an attendant with a workspace-wide view; the others see only their own records. A new attendant starts out as Attendant.

      Sub-role (in the interface)Reach in the CRM
      Attendant (default)Their own records only.
      SalespersonTheir own records only.
      CoordinatorWorkspace-wide view (everyone's opportunities and calendar).

      Scope restrictions in the CRM

      Some roles can read the whole CRM but cannot perform actions whose reach goes beyond what they can see. The actions below are denied to the Guest and to the Attendant (except the Coordinator sub-role).

      ActionGuestAttendantCoordinator
      Read lists, segments and contactsAllowedAllowedAllowed
      Create/edit a listDeniedDeniedAllowed
      Create/edit a segmentDeniedDeniedAllowed
      Export contactsDeniedDeniedAllowed

      A denied action returns a permission error (403). Reading stays open so the attendant can filter and understand the lead.

      If it didn't work