What it covers
Use owner, admin, member and viewer roles plus per-area permission controls where the plan permits.
Customisation and integrations
Roles and permissions
Give each person an appropriate level of access.
How it works
Give each teammate access suited to their work
Assign owner, admin, member or viewer roles and use per-area permissions where your plan allows. Server-side checks enforce the boundary across records and actions.
In practice
Module permissions shape navigation and actions; the server remains authoritative.
When to use it
Useful situations
- Give a viewer access appropriate to their work.
- Restrict a sensitive module to selected administrators.
- Confirm that navigation matches an individual's available areas.
A working path
How the work moves
Assign
Choose owner, admin, member or viewer for the teammate.
Refine
Configure per-area access where the plan provides it.
Verify
Review the person's available navigation and actions; the server enforces the final boundary.
Illustrative scenario
finance reviewer
An administrator gives a finance reviewer the appropriate role and permitted revenue area without granting broad account administration. The arrangement gives the reviewer the commercial information needed for their job while keeping unrelated administrative and account-management capabilities unavailable.
Before you start
What to check
- Per-area permissions start on Business.
- Client navigation reflects access, but server-side checks remain authoritative.
Can hidden navigation still be accessed directly?
No. Server enforcement applies to routes and actions.
Are roles the only control?
Roles provide the base level; eligible plans add per-area permissions.
Get started
See your customer work in one place.
Start with the core CRM for free, then add the tools your team needs.