Departments and Data Scope: Who Should See Whose Records?

A CRM permissions guide: separating role from scope, department trees, own/team/company scopes and common mistakes.

Almost everyone starts permissions in the same place: who can delete records, who can run reports? Yet the question that comes up far more often in daily work is different: which customers should this person be able to see?

Two separate concepts: role and scope

Role (what they can do)

Create, edit, delete, report, change settings. A list of actions.

Scope (what they can see)

Only their own records, their team’s, their whole department, the entire company. A data boundary.

Confusing the two produces two typical problems: either everyone sees everything (no scope at all), or permissions narrow so far that people cannot work and start asking each other for records.

Four levels of scope

  1. Own records only: field reps, contact centre agents. The narrowest, and the right level for most roles.
  2. Team or department: a team lead seeing all their team’s records.
  3. Department and below: a regional manager seeing their department and everything beneath it. In hierarchical organisations this is the level most needed.
  4. Company-wide: management and audit. It should sit with very few people.

The third level matters because organisations are not flat. If three branches sit under “Aegean Region”, the regional manager should see all three but not Central Anatolia. Defining that by hand is unsustainable; it has to be derived from the department tree.

The two most common mistakes

1. Applying scope only to lists

If the list screen is filtered but the detail page can be opened directly by URL, there is no scope. Anyone who knows a record id can reach it. Scope has to hold at every access point: list, detail, search, reports and exports.

2. Forgetting exports

This is the most overlooked hole. If someone seeing 20 records on screen can download 20,000 through an Excel export, the whole scope is void. Exports must obey the same boundary and be logged.

A checklist for every new screen

  • Does the list query apply the scope?
  • Does the detail page check a record whose id was supplied directly?
  • Do search results escape the scope?
  • Are reports and charts fed with filtered data?
  • Is the export subject to the same limit?
  • Do notifications expose out-of-scope records? (“Customer X was updated” must not reach someone who should not see X.)

Handover and leave scenarios

The most forgotten side of scope design is exceptions:

  • Leave: who sees a rep’s portfolio while they are away? Temporary access should be definable and expire by itself.
  • Department moves: what happens to someone’s access to their old records when they transfer?
  • Departures: access must be revoked without the portfolio disappearing; records should transfer to a new owner.
  • Cross-team work: a project may need temporary access to another department’s records. Time-limited access is right; permanent access is not.

Auditability

As important as scope is being able to see who accessed what. When a record leaks, that log is the only evidence. It also deters: people who know access is logged do not open records out of curiosity.

Frequently asked questions

Is scope needed in a small team?

In a team of five it may not be technically necessary, but building the habit pays. Adding scope later, once the team grows, means taking away access people are used to — and that generates resistance.

Does scope hurt performance?

Built properly it usually helps: a filtered query reads less data. The problem is applying the filter after the query — that is both slow and risky.

Should managers see everyone’s data?

Only as far as needed. “Managers see everything” is a hard position to defend for personal data. Aggregate figures in reports are usually enough; access to individual records needs its own justification.

Next step: to see how department trees and scopes are configured, request a demo.