Elbuz hides other people's customers and documents from an employee: a department's “Data scope” mode keeps in lists, boards and cards only records the person is responsible for, or also those of their subordinates.
When you need this:
- Each manager runs their own customer base — “Own only” shows just their customers and orders.
- A team lead oversees their team — “Own and subordinates” adds the records of everyone below them in the org structure.
- Someone opens another manager's customer from a link — they get a “No access” screen instead of the card.
Where to start: rights window → department → the “Data scope” block on the “Role” tab.
What “Data scope” does
- Three modes — “Own only”, “Own and subordinates”, “All” — set separately for each department.
- The restriction applies wherever contacts and documents open: in lists, on boards, in cards and in the call log.
- “Own and subordinates” takes subordinates from the org structure and warns you who is missing from it.
Whose records an employee sees in each mode
Module levels answer the question “which windows and buttons”. “Data scope” answers a different one: which records the person sees in lists, even when the window itself is open to them.
1
Hint: where it applies2
Own only3
Own and subordinates4
All- Hint: the mode applies to the contact and document lists.
- “Own only” — only records where the employee is the responsible person; unassigned records are hidden.
- “Own and subordinates” — the employee's own records plus those of subordinates in the org structure.
- “All” — no restriction; this is the default.
| Mode | Contacts | Documents | Records with no responsible person |
|---|---|---|---|
| Own only | where the employee is the main responsible person | where they are responsible | hidden |
| Own and subordinates | their own, plus those whose main responsible person is someone below them in the org structure | the same | visible |
| All | all | all | visible |
Only a department head has subordinates — the person marked as head in the org structure. They see the records of every employee in their department and its sub-departments. A regular employee in this mode sees only their own records.
By default, every department is set to “All”. What to know before you switch:
- Where it applies. Lists (grids) of contacts and of all documents: orders, deals, finance, inventory. Boards — the deal pipeline, the document kanban and the contact kanban — show the same set as the list. The call log hides calls from customers outside the scope; calls with no customer are visible to everyone. It also covers contact and document cards, the contact preview panel and its AI summary: a record outside the scope won't open even from a link in another window — a “No access” screen appears instead of the card.
- Where it doesn't apply. Chats, email, “My Day”, reports and analytics, and all other lists. An operator with “Own only” still sees every customer in chat.
- “Own only” hides unassigned records. A new order from the website or a new customer with no responsible person stays invisible to such an employee until someone is assigned. If your people should pick up incoming requests themselves, use “Own and subordinates” or set up automatic assignment of the responsible person.
- “Own and subordinates” works only with the org structure. Subordinates are the people below the person in the org structure. If an employee isn't in the org structure, the restriction doesn't apply to them at all — they see everything. The screen warns you: “Department employees outside the org structure: N. “Own and subordinates” does not limit them — add them to the org structure.”
- Several departments — the widest mode wins. If any of the person's departments is set to “All”, they see everything; otherwise, if any is set to “Own and subordinates”, they see their branch. “Own only” applies only when every one of their departments uses it.
The visibility toggle in the org structure panel has only two states — own department and below, and all. Turning it off there doesn't overwrite “Own only” set on the “Role” tab: only “Own and subordinates” is reset.
Scenarios
A manager sees only their own customers
Task. Three sales managers each run their own customer base, and none of them should see other managers' customers or orders.
What to click. “Sales and claims department” → “Data scope” → “Own only”.
What the employee sees. In “Contacts”, only customers where they are the main responsible person; in documents, only documents where they are responsible. Another manager's customer won't open either in the card or in the preview panel.
They won't see new requests with no responsible person until someone is assigned, so a team lead has to distribute incoming requests. The mode narrows the deal pipeline and kanban boards the same way, but not chats or email.
A sales lead sees their team's deals
Task. A senior manager oversees the deals of their three subordinates, while regular managers see only their own.
What to click. Place people in the org structure: the team goes into the department, and the lead gets the head mark (crown) in that department. Then “Sales and claims department” → “Data scope” → “Own and subordinates”.
What the employee sees. In the deal, document and contact grids, the lead sees their own records and those of everyone below them in the structure; a regular manager with nobody below sees only their own. Records with no responsible person are visible to everyone.
If the screen shows the “Department employees outside the org structure” warning, those people see everything — add them to the structure. The deal pipeline board shows the same set as the deals grid.
What to do when an employee sees the wrong customers
| What you see | Why | What to do |
|---|---|---|
| A manager doesn't see new orders from the website | The department is set to “Own only”, and new orders don't have a responsible person yet | Assign a responsible person or switch to “Own and subordinates” (Data scope) |
| You turned on “Own and subordinates”, but the employee sees all customers | The person isn't in the org structure, so the restriction doesn't apply. Or they have a second department set to “All” | Add the person to the org structure; check all departments in their card |
FAQ
How do I see exactly which records a particular manager sees?
Open the app through their eyes: in the rights window, “Actions” → “Check as employee” (how). You'll see their lists, boards and cards, taking all their departments into account.
How do I show a manager only wholesale customers instead of filtering by responsible person?
Use “Row filter” on the “Advanced” tab: a condition on the contacts grid. It works on top of “Data scope” rather than replacing it (row filter).
Can I split data between our legal entities?
No. Rights have no “company” dimension: every legal entity is visible to anyone with access to the window. You can narrow the list only with a “Row filter” on the “Advanced” tab.
Is “Data scope” carried over when you copy rights from another department?
No. Copying transfers windows, buttons, grids, columns and menu items. Set “Data scope” on the new department's “Role” tab separately.
Does the “Reset to the standard set” button reset “Data scope”?
No, the reset changes only the department's windows. The mode stays as it was (what the reset does).
Where to find it and who has access
- Desktop
- the “Users” shortcut → the “Manage groups” button
- Tab
- “Role” → the “Data scope” block
- Access right
- the “Manage user groups” window — only for “Management”
- Prepare
- responsible persons in contacts and documents; for “Own and subordinates”, the org structure
All the ways into the rights window, and why it has no menu item, are in Employee access rights.
Related topics
- For the big picture — employee access rights.
- If “Own and subordinates” restricts no one — place people in the org structure.
- If you need to close a whole module rather than records — module levels.
- If you're choosing a CRM for your store — what it gives your store.
- If you're choosing order management software — what it gives your store.
