Roles and permissions
Access has two layers: the role in the workspace, of which there are four, and the job title, the named set of permissions that decides what a Member reaches. Owner, Administrator and Integrator do not use job titles — their access is set by the role.
Prerequisites: only Owner and Administrator invite people, change roles and build job titles. Every permission below depends on the person holding an active seat in the workspace.
Workspace roles
Descriptions as shown in the Manage role screen.
The Owner role is not assignable: it exists only for whoever created the account. Administrator and Member can be picked when inviting and changed later in Settings → Members. So can Integrator, but only for emails Clickmax has registered on an active partner.
Promoting to Administrator removes the job titles, because an administrator is broad by definition and the job title would stop meaning anything. Demoting back to Member hands back the Atendente job title, the starting point. Switching roles between members does not touch access — role and job title are separate axes.
Default job titles
A job title is a named set of permissions, built once and given to whoever needs it. In an account with none, Settings → Permissions offers Create default job titles, which creates the five below at once. They are a starting point: every permission can be adjusted afterwards.
The five are created with the names below, which you can rename at any time.
One person can hold several job titles, and access is the sum of all of them. A job title never subtracts: giving one more never removes what the person already had.
What a permission can be set to
On Settings → Permissions, job titles are the columns and each row is one action of a resource. Each cell shows one of these values; clicking it opens the options, each with what it means:
The middle option only exists on resources that have an owner — opportunities, scheduling, conversations and meetings and recordings, tagged By owner next to the name. The others are tagged Yes or no.
The actions are View, Create, Edit, Delete and Manage — each resource shows only the ones it uses. Manage is the resource's configuration: changing the temperature scale, connecting a channel, setting up a team.
Some resources also have Import and Export. They are separate on purpose: editing a contact should not, by itself, let someone download the whole base as a spreadsheet or upload thousands of contacts at once. Export is granted resource by resource — a job title can export contacts and not form answers, for example.
Marks on the screen
Find and compare
- The area tabs above the table show one area at a time (or all of them); the number is how many resources it has. The areas are the same modules as the sidebar menu.
- Search resource looks at the name and the description.
- Only what differs between job titles, in the arrow menu next to New job title, hides the actions where every job title is the same. While it is on, the Only differences pill shows in the filter row; click it to see everything again.
- Each area collapses with the arrow next to its name.
Save
Changes stay as a draft until Save changes, in the bar that appears at the bottom with how many cells changed and in which job titles. Discard reverts to what is saved. Saving signs out whoever has the changed job titles, so they come back with the new access.
Name and order don't go through the draft: renaming (clicking the name or from the job title's ⋯ menu) and moving (dragging the column, or Move left/right in the menu) save right away. The same menu has Duplicate job title (the copy shows up right after, with the same permissions and no members), Give this job title to someone, See everyone with this job title and Delete job title.
Admins have full access and don't appear as a column.
Resources in the matrix
Each row on Settings → Permissions is one of these resources (names as shown on screen), grouped by the sidebar modules. By owner marks the ones with the Only their own option.
Marketing
Messaging and support
Contacts and sales
Products and delivery
Sales and recovery
Affiliation
AI
Max Design
Studio de vídeo
Drive
Integrations
Account
An exception for one person
No permission is ever handed to a person directly — all access comes from a job title. When someone needs something none of their job titles grants, create a job title holding what is missing (it can be a single permission) and add it to the ones they already have, through Manage job titles. Access is the union.
It is one step more than ticking the box on the person, and that is deliberate: this way every permission anyone holds carries a name that shows up on the Permissions screen, and "why can they do that?" always has an answer.
Changing job titles ends the person's session, so they come back with the new access.
Withdrawing and advancing does not come with the Finance job title. Handling billing is not moving money: the wallet is granted separately, person by person, by whoever is the Owner.
CRM attendants
The attendant record comes from the seat: inviting someone makes them exist in the CRM and able to receive opportunities. The list under CRM settings → Attendants does not register anyone — it shows who already holds a seat.
For the same reason, deleting an attendant who still holds a seat is refused. Were it allowed, the person would vanish from the CRM and keep workspace access, taking up a paid seat. To actually remove access, remove the person in Settings → Members.
What used to be the Coordinator sub-role is now a permission: tick Everyone's on a sales resource and the person starts seeing the whole team there. And now you can choose where — Everyone's on Opportunities without Everyone's on Calendar leaves someone who follows the team's board without access to their colleagues' calendars, which the sub-role could not do: it opened opportunities, calendar and conversations at once. Whoever already was a coordinator kept their access; it only became visible, and adjustable, on the Permissions screen. The attendant type still exists and is a different thing — it organizes roles inside a pipeline (see attendant assignment).
Sidebar menu
The menu shows every area of the product, including the ones the person does not reach. An item without permission appears dimmed with a lock: it does not open, and hovering shows No permission. That way the person knows the feature exists and can ask a workspace admin for access.
If they land on a screen without permission — through a direct link or a bookmark — the page shows You don't have access to followed by the resource name instead of the content. Nothing is loaded or changed.
An action inside a screen the person reaches, but that the job title does not allow (delete, configure, export), is hidden or disabled. If it is attempted anyway, the platform refuses it with the no permission notice.
Features the account doesn't have do not show in the menu — the lock is only for a missing job-title permission. This applies to everyone in the account, Owner and Admin included: their broad access is about the job title, not about what the account has. Whoever lands on one of those screens through a link sees Your account doesn't have followed by the feature name. To turn it on, contact Clickmax support.
View as a job title
To check what someone with a job title finds in Clickmax, open Settings → Permissions, click the ⋯ on the job title's column and choose View Clickmax as this job title. You land on the home page already as that job title: the menu, screens and actions follow its saved permissions — unsaved changes on the board are not included.
Meanwhile, a bar stays pinned at the bottom of every screen showing Viewing as: and the job title's name. Click Exit preview to go back to your own access and to the Permissions screen. Switching workspaces also ends the preview.
It is visual only: you keep your own access, and whatever Clickmax saves or returns is done as you. It is for checking the menu, screens and buttons, not for acting on someone's behalf. Available to the Owner and Administrators.
Debugger mode
Turn on Debugger mode at the top of the Permissions screen, or on the Viewing as bar, to see where Clickmax asks for a permission. While it is on, the top bar shows Permission debug with a Turn off button. Every place that depends on the job title gets a badge in its corner, and the color tells who reaches that place:
A hollow, dashed badge means the current access (yours, or the job title in Viewing as) does not reach the place. An action that would be hidden shows up in its place as a dashed Hidden action chip. The badge follows the element: it disappears when the element scrolls out of view and when a modal opens on top.
Hover or click the badge to open the place's summary:
- Summary: how many job titles reach it (for example, "6 of 7 job titles") and how many people have access.
- Needs: the required permission, in the same wording as the board — such as "Conversations › View, their own or more" —, with an Open in the board shortcut. Below the text comes the permission's technical ID (for example,
conversations:read), with a button to copy it. When the current access lacks the permission, the line shows Missing. - Job titles: each job title with the board's symbol (full sees everything, half sees only their own, empty has no access) and how many people it has.
- People: who has access, with the job title that grants it, and search by name. The Owner and Administrators are listed by name with their role: they pass any permission.
When the place depends on a rule that does not fit a list (for example, "any one of these"), the badge is gray with a shield and the summary says the requirement was not provided.
The mode stays on until you turn it off or close the tab, and only shows for the Owner and Administrators.
Related
- Workspaces and invites
- Workspace settings
- When "no permission" shows up
- Attendant assignment in the CRM
- Error codes
If it did not work
- An action was blocked despite the right job title: check whether the permission is set to Only their own when it should be All, and whether the resource's View is not on No (the cell shows an orange !), and see when "no permission" shows up.
- The person does not see colleagues' records: that is expected with Only their own. Adjust the job title, or add one that has All on that resource.
- The person ended up with No job title: promoting to Administrator removes the job titles, and demoting hands back only Atendente. Give the right one through Manage job titles.
- An attendant cannot be deleted: they still hold a seat — remove the person in Settings → Members.