Platform and control

Role-based access control for dealer networks

Who sees which record in a dealer network is decided by role, reporting line and geography. How to set role-based access so each person sees what the job needs.

A fine-line chart of Uranus on its side, its thin rings beside nested boundaries around one lit point.

The short answer

  • Three questions decide who sees a record: role, reporting hierarchy and geography.
  • Role alone is not enough. Two regional managers share a role but not a region.
  • Seeing a record and changing it are separate permissions, and should be set separately.
  • Some fields, such as margins, can be hidden from roles that see the rest of the record.
  • Access needs a review whenever people move, leave or change territory.

Role-based access control for dealer networks decides who sees and changes each record by asking three questions: what is this person's role, where do they sit in the reporting hierarchy, and which geography do they cover? A dealer's salesperson sees their own leads, the dealer principal sees the dealership's, and a regional manager sees every dealer in the region. Answer the three well and each person sees what the job needs, and nothing more.

The three questions that decide who sees a record

A dealer network has many people who should see some customers and not others. A salesperson at one dealership should not see the leads of the dealership across town. A regional manager needs every lead in the region, and none outside it. A single rule cannot express this. Three questions, asked together, can.

  • RoleWhat is this person's job? A dealer salesperson, a dealer principal, an area manager, a head-office analyst.
  • Reporting hierarchyWho reports to them? A manager sees the records of the people below them.
  • GeographyWhich zones, states, cities or areas do they cover? Records outside them stay out of sight.
The three questions that together decide who sees a record. Any one of them alone gives access that is too wide or too narrow.

Role says what kind of access a person gets. Hierarchy says whose records it applies to. Geography draws the boundary.

Role-based access in a typical dealer network

Here is how the three combine for common roles. Your titles will differ; the shape usually does not.

RoleSeesCan changeDoes not see
Dealer salespersonTheir own leads and customersTheir own leads: calls, dispositions, quotationsColleagues' leads unless shared; other dealers
Dealer principalEvery record at their dealershipAssignments within the dealershipOther dealerships' records
Area sales managerEvery dealer in their areaReassignment between their dealersOther areas
Regional managerEvery area in the region, through the managers belowTargets and reassignment in the regionOther regions
Head-office analystReports across the networkNothing on customer recordsPersonal details, where hidden from the role
National sales headThe whole networkRules for the networkNothing within sales

Notice that the regional manager sees most records through hierarchy, not through role. If the area manager below them leaves, the region does not lose sight of those dealers.

Why role alone is not enough

A system that gives access by role only has two bad options. Give every regional manager access to every region, and the North sees the South's pipeline. Or create a separate role per region, and the list of roles grows until nobody can maintain it.

Follow one lead and the three questions doing their work.

  1. The enquiryA lead arrives for a city in the western region.
  2. GeographyIt belongs to the dealer whose territory covers that city.
  3. RoleThe dealer's salesperson is assigned it and can work it.
  4. Hierarchy, one upThe dealer principal sees it because the salesperson reports to them.
  5. Hierarchy, further upThe area and regional managers see it through the reporting line.
  6. Everyone elseA dealer in the next city, and the eastern region, never see it.
How role, hierarchy and geography decide who sees one lead. Each person's view follows from the three answers, not from a list kept by hand.

How territories themselves should be drawn is a separate design job, covered in sales territory design.

Seeing a record versus changing it

Access is not one switch. For each role, decide separately whether it may create, see, change or remove a kind of record. A head-office analyst may need to see every lead to build a report, but should never change a disposition a dealer recorded.

Who may see it

  • Everyone in the reporting line above the owner
  • Analysts, for reports, without personal details
  • The dealer principal, for every lead at the dealership
  • Service staff, for customers they serve

Who may change it

  • The owner, and whoever reassigns their work
  • Nobody outside the line, however senior
  • The dealer principal, for assignment only
  • Service staff, for their own service records
Seeing and changing set apart for the same records. Set as one permission, either analysts can edit dealer records or managers cannot see them.

Within a record, some fields deserve their own rule. Dealers may see a customer's quotation but not head office's margin on it. Analysts may see every row of a lead report but not the mobile number column. Rules by row and by column handle this without creating extra roles.

How to set up role-based access, step by step

  1. List the rolesWrite every job that touches a customer, at head office, dealers and in the field.
  2. Draw the hierarchyRecord who reports to whom, including dealer staff to their principal.
  3. Map the geographyAssign each role its zones, states, cities or areas.
  4. Decide see and changeFor each role and each kind of record, set see, change, create and remove.
  5. Hide sensitive fieldsMark the columns, such as margins or phone numbers, that some roles should not see.
  6. Test as real peopleSign in as a dealer salesperson and a regional manager, and check what each sees.
Six steps to role-based access for a dealer network. The last one catches errors before a dealer does.

Then keep it current. Access goes wrong slowly, as people move.

0 of 4 ticked

Your ticks are kept in this browser only.

A monthly access review for a dealer network. Four checks that keep access in step with the people who actually hold each job.

Each new dealer is also an access decision, which is why access belongs in the dealer onboarding checklist. Why one shared record makes these rules matter more, not less, is in why a single customer record matters.

How Intellsys OS handles role-based access for dealer networks

In Intellsys OS a business defines its own roles and territories, and permissions reach down to a single record, by role, by reporting hierarchy and by geography. On data and reports, access rules work by row and by column, so an analyst can see a report without the fields their role should not. Work can be reassigned one at a time or in bulk, round-robin, with an audit log, which is what a leaver or a territory change needs. People sign in with one-time codes, passwords, Google or Microsoft.

Dulux runs BlueStore on Intellsys OS: each store online with its own page and its own lead owner. A business switches on the modules it needs, and its own team sets the roles and access without code. More is on the Intellsys OS platform page, and the wider idea in what a business operating system is.

Questions people ask

What is role-based access control in a dealer network?

It is a way of deciding who sees and changes each record by the person's role, combined with their place in the reporting hierarchy and the geography they cover. A dealer salesperson sees their own leads; a regional manager sees every dealer in the region.

Why is role alone not enough for dealer access?

Many people share a role but cover different places. Two regional managers have the same job and different regions. Without geography and hierarchy, you must either show every region to both, or create a separate role for each region, which becomes impossible to maintain.

Should dealers see each other's leads?

Usually not. Each dealer sees the leads in their own territory, and their staff see their own leads or the dealership's. Head office and regional managers see across dealers through the reporting line. Sharing between dealers should be a deliberate reassignment, with a log.

What should happen to access when a salesperson leaves a dealer?

Their access should close the same day, and their open leads and customers should be reassigned to a named person, with a record of who moved them and when. A monthly review catches anyone missed.

Read next

See it on a live workspace.

A demo shows the parts of Intellsys OS that are in use today, with the people who run it.

Request a demo
Request a demo