Access rights and restrictions

A role in a CRM is a set of rights and responsibilities assigned to a user in a customer relationship management system. Each role defines which functions and data are available to the user, depending on their position and access level.

There are 4 main role types in the CRM:

Administrators:

  • Managing users and roles
  • Creating and editing organizations, contacts, deals, and other objects
  • Configuring workflows and automation
  • Viewing and analyzing reports

Managers:

  • Creating and managing deals
  • Assigning tasks and monitoring their completion
  • Interacting with clients via messages and calls
  • Viewing reports on deals and contacts

Executors:

  • Performing tasks and assignments
  • Interacting with clients on managers' instructions
  • Maintaining documentation on deals
  • Viewing reports on tasks and contacts

Couriers:

  • Managing logistics and delivery
  • Assigning and tracking deliveries
  • Interacting with clients on delivery matters
  • Viewing reports on deliveries and contacts

By and large, this is meta information that can be used to collect statistics, make payouts, and assign rewards.

Creating a role

To create a role, go to:

Users − Profiles − in the "Roles" block click − Create role

Screenshot name: sozdat_rol

Editing a role

To edit a role, go to:

Users − Profiles − in the "Roles" block click − Edit

Screenshot name: rol_redaktirovanie_kopirovanie_udalenie

Status transitions

This setting lets you restrict movement between statuses for a specific role. In effect, this means that for each subset of statuses you can choose the destination statuses, ruling out erroneous user actions.

This setting in the CRM restricts movement between statuses for a specific role. This means you can choose destination statuses for each subset of statuses, ruling out erroneous user actions.

For example, for the "Managers" role you can configure the following destination statuses:

  1. Creating an order:

    • A manager can create new orders.
  2. Interacting with clients:

    • A manager can interact with clients via messages and calls.
  3. Viewing reports:

    • A manager can view order reports.

For other roles, such as "Executors" and "Couriers", you can configure other destination statuses that match their responsibilities.

Typical cases

  • An order that has reached completed cannot be moved to canceled.

  • An order from delivery cannot be moved to new, but it can be canceled.

Setup

To open status transitions, go to:

Users − Profiles − in the "Roles" block click edit role − Status transitions

Screenshot name: rol_perehod_statusov

Order form configuration

This setting in the CRM lets you restrict access to order and client information for specific user roles. This means you can configure which order form fields are required, which fields can be edited, and which are forbidden from editing.

For example, for the "Managers" role you can configure the order form as follows:

Required fields:

  • A manager can see and edit the "Client name", "Client phone", "Delivery address", and "Order amount" fields.

Forbidden fields:

  • A manager cannot see or edit the "Client phone" and "Client personal data" fields.

Fields allowed for editing:

  • A manager can edit the "Delivery date" and "Order comment" fields.

For other roles, such as "Executors" and "Couriers", you can configure an order form that matches their responsibilities. For example, for "Couriers" you can make the "Delivery address" and "Delivery time" fields required, and for "Executors" the "Task completion date" and "Task comment" fields.

This setting helps ensure that users have access only to the information they need to do their tasks, and cannot accidentally or deliberately access confidential data they do not need.

The form configuration is subject to your current role: you cannot set rules for fields that are not available to you.

Setup

To open order settings, go to:

Users − Profiles − in the "Roles" block click edit − order form settings

Three options are available:

  • Read (the user can only see the field but cannot edit it).

  • Write (the user can see and edit the field).

  • Required field (the user cannot save the order without filling in this field).

Screenshot name: rol_forma_zakaza

Deleting a role

You can delete a role only if it has no users; otherwise the CRM will show an error.

To delete a role, go to:

Users − Profiles − in the "Roles" block click − Delete

Screenshot name: rol_redaktirovanie_kopirovanie_udalenie

Role settings

A role's settings have 2 blocks:

  1. General settings

  2. Access rights

General settings

The settings block contains:

  • Name: the nomenclature name of the role in your workspace.

  • Role type

  • Sees only own orders: if this option is enabled, the user sees only orders where they are selected in the order field corresponding to their role type.

  • Working time tracking: the system keeps track of the time the user was online.

  • Geo tracking: requires the user to enable location detection in the browser; the CRM will then record changes in the coordinates of the device with an active session while the user is online.

  • IP whitelist access: effectively prohibits using the CRM if the user's IP address is not on the list of allowed IP addresses.

  • Dependent roles: roles that the role being edited has access to.

  • Available statuses: orders in these statuses are available to users in this role.

  • Shared statuses: lets you ignore the "Sees only own orders" rule for the selected statuses.

  • Profile activity time: the time interval within which the user can work in the CRM.

A user's role can be changed only to a role of the same type

Screenshot name: rol_nastrojki

Access rights block

In this block you can configure user access to specific features of the program.

Access rights are subject to your own role: you cannot select items that are disabled in your role.

Think of access rights as a route to a goal made up of links, where each link is a specific group of actions and pages.

When selecting rights, keep the subordination principle in mind: nested items make child items available, and vice versa.

You can configure access to any button and page; under no circumstances will a user get access beyond what is available in the role.