Guides
CRM roles and permissions: what each job should see
Published November 14, 2026 · 8 min read
In a small team it is tempting to make everyone an admin. It's quick and nobody complains about not seeing something. Until someone deletes a pipeline by mistake, exports the customer list on their way out, or the intern can see every customer's invoices.
Setting permissions is not about distrusting your team: it reduces mistakes and follows the GDPR principle of data minimisation, which asks that each person only accesses what they need for their job. This guide proposes a permission matrix by job, explains the usual levels and ends with a review checklist.
Key takeaways
- Use three levels per module: no access, read and edit. That covers almost every team.
- Start from "no access" and open only what each job needs, not the other way round.
- Use sections to fine-tune inside a module: for example, see contacts without being able to export them.
- Create roles per job, not permissions per person, so it stays easy to maintain.
- AI assistants and integrations should inherit the user's permissions, never get around them.
Which permission levels does a CRM need?
Most teams get by with three levels per module:
| Level | What it allows | Example |
|---|---|---|
| No access | The module is hidden and its data can't be queried | A salesperson who doesn't need to see cash flow |
| Read | View, but not create, edit or delete | Management checking reports |
| Edit | Full access to the module | Marketing running journeys and segments |
On top of modules, a second layer helps: sections, to fine-tune inside a module. Inside the CRM, for example, you can separate contacts, companies, deals, and import and export. A healthy rule is that a section can only lower the module's access, never raise it.
And a third control, at company level: deciding whether each member sees all records or only their own. Sales teams with their own accounts often choose the latter.
Permission matrix by job
This matrix is a starting point for a small business with a sales team, marketing, customer support and someone in management. Adjust it to your case.
| Module | Sales | Marketing | Customer support | Management | Accountant |
|---|---|---|---|---|---|
| CRM (contacts, companies, deals) | Edit | Read | Edit | Read | No access |
| Contact import and export | No access | Edit | No access | Read | No access |
| Email (inbox and sending) | Edit | Read | Edit | Read | No access |
| SMS and WhatsApp conversations | Edit | No access | Edit | Read | No access |
| Journeys, segments and mass sends | Read | Edit | No access | Read | No access |
| Analytics and dashboards | Read | Edit | Read | Edit | No access |
| Web analytics | No access | Edit | No access | Read | No access |
| Identified visitor profiles | No access | Read | No access | No access | No access |
| Shop orders | Read | Read | Edit | Read | No access |
| Quotes and sales | Edit | No access | Read | Read | No access |
| Invoicing | Read | No access | Read | Edit | Read |
| Treasury | No access | No access | No access | Edit | Read |
Three decisions that often raise questions:
- Exporting contacts. It is the action with the highest risk of a data leak. Give it to few people, even if many can view contacts.
- Visitor profiles. If you use web analytics with identification, a contact's browsing history is personal data. Limit who sees it.
- Management on read. People who supervise rarely need to edit the day-to-day. Read access avoids accidental changes.
What about the accountant and employees?
These are two special profiles and they are worth handling separately:
- External accountant or bookkeeper. They need to see invoices and payments, not your contacts or deals. Ideally they get read-only access limited to invoicing and treasury, which can't be widened by mistake.
- Employees who only clock in. If you use the CRM for time tracking, someone who only clocks in, requests leave and checks their documents doesn't need any sales module. Self-service access is enough.
And AI assistants and integrations?
This is the part people forget. An AI assistant inside the CRM, an MCP connector for ChatGPT or Claude, or an API key can read and change data. If they don't respect the user's permissions, anyone with access to the chat could see what their role doesn't allow.
The rule should be simple: the assistant or the integration acts as the user and never has more permissions than they do. We cover it in detail in connecting your CRM to ChatGPT and Claude.
Checklist to review permissions
Go through this list every quarter and whenever someone joins or leaves the team:
- How many people are admins? It should be one or two.
- Does everyone have a job role rather than one-off permissions?
- Who can export contacts? Is it still needed?
- Do members with their own accounts see only their records?
- Do new invites start with no access and then get a role?
- Have people who left been deactivated?
- Which API keys and AI assistants have access? Are they still in use?
- Does the audit log show unexpected changes?
Frequently asked questions
Does GDPR require limiting permissions?
GDPR requires appropriate technical and organisational measures and processing only the data you need. Limiting who sees what is one of the most direct ways to meet that. For the rest of your obligations, see the GDPR guide for CRMs.
Roles per person or per job?
Per job. If everyone has custom permissions, in six months nobody will know why someone can see what they see.
Can a read-only user use the AI assistant?
Yes, but only with read tools. They can't create or change anything from the chat.
What happens to permissions when a new module is added?
It depends on the tool. What you want is for a role saved earlier not to suddenly gain or lose access.
How Flowgration does it
In Flowgration each user has a level per module: no access, read or edit. The modules are CRM, orders, SMS and WhatsApp conversations, workspace, journeys and sends, email, analytics, web analytics, media, AI assistant and team, plus sales, invoicing, treasury and HR when they are switched on. Inside each module you can adjust sections, such as import and export in the CRM or visitor profiles in web analytics, and a section can only lower access. You can create your own roles and assign them to the team.
New invites start with no access to any module. The company can limit members to their own records. The accountant seat reads invoicing and treasury and nothing else, and it can't be widened; the employee seat gives access to HR self-service (clocking in, own absences and own documents). The AI assistant, the MCP connector and API keys all use the user's permissions.
The limits: the owner and admins always have full edit access, and team management and company settings stay with admins. For the rest of the protection measures, see the security page and compare what each plan includes on the pricing page.
Build your WooCommerce CRM in 60 seconds
Flowgration turns your store's orders into a living CRM and runs email, SMS and WhatsApp on autopilot. Free up to 500 contacts.
Start free