CRM / permissions
Setting permissions amoCRM
We configure roles and data visibility so that managers do not take away the database, the manager sees the entire circuit, service employees do not get involved in unnecessary transactions, and access does not create holes in control and analytics.
Roles
Base visibility
Deletion control
Access segments
When it's critical If multiple departments work in the same account, there are branches, service roles, or the risk of losing the customer base.
What do we protect? Deals, contacts, companies, fields, funnels, data deletion and boundaries between roles.
What do you get A clear access model without chaos, random blocking and “gray areas” of responsibility.
Typical problem
Either everyone can do everything, or it’s impossible to work
Managers see other people's transactions, change data and lose control of the database.
The manager does not understand who has the right to delete, export or hide a client.
Service employees receive access wider than required for the task.
What we are setting up
Role model
Roles of the leader, ROP, manager, service, marketing, contractor and integration users.
Visibility by funnels, segments, branches, directions and responsible persons.
Restrictions on deleting, exporting, changing statuses and critical fields.
What does it give
Control without unnecessary blocking
Each employee has only the access needed for their role.
The basis and history of work depend less on the human factor.
The manager receives a transparent model of responsibility within CRM.
What's included
How the access rights system is built
Role audit First, we look at who actually works in the system and what actions they perform.
Access Matrix We record which entities, stages and fields are available to each role.
Segmentation We distribute access by branches, directions, products or management groups.
Critical Actions We specifically restrict deletion, export, mass changes, and sensitive fields.
Testing We test the roles in real scenarios so that the settings do not disrupt the team’s work.
Documentation We fix the logic so that later the accesses do not grow into chaos after each revision.
Related Pages
What is usually configured along with access
FAQ
Frequently asked questions about access rights in amoCRM
Is it possible to hide transactions between managers? Yes, but it is important to do this in a way that does not break management control, analytics and service scenarios.
Should marketing have access to CRM? Depends on the role. Most often, you need limited access to sources, reports and part of the card, but not to the entire customer base.
Why is it better to think through access rights right away? Because then the account becomes overgrown with crutches, manual exceptions and conflicts between departments. It's more expensive to fix it later.