Designing access and visibility for a global commercial organization
A case about access as architecture: ownership, record visibility, hierarchy, shared commercial responsibility, global accounts and sensitive data.
The case in brief
Current reality
Access rules grew one request at a time; nobody can explain who sees what, or why.
What must become true
Visibility and edit authority follow explicit organizational and business rules rather than accumulated exceptions: ownership means accountability, visibility follows relationships, edit rights are narrower than view rights, and sensitive data has its own boundary.
Design question
What does ownership grant—and what should visibility, edit authority and sensitive-data access grant independently?
01The reality · current state
What the platform looks like today.
A global commercial organization works across subsidiaries, regions, sales teams, key-account teams and specialists. Access rules grew one request at a time: sharing exceptions, copied profiles and manual grants. Some users see everything; others cannot see accounts they work on every day.
- Ownership is used to grant visibility, so accounts are reassigned just to be seen
- Global account teams cannot see local opportunities on their own accounts
- Manual sharing exceptions pile up and nobody reviews them
- Sensitive terms are visible to anyone who can see the account
- Access changes lag behind organization changes
- Reports show different totals to different people, with no explanation
02The boundary problem
What is mixed today.
Access grew one reasonable request at a time—“give this manager access”, “this region needs these accounts”—until four different ideas had collapsed into one.
- OwnershipWho is accountable for the account—used as the only way to grant visibility.
- VisibilityWho may see it—granted by reassigning owners and by manual sharing.
- Edit authorityWho may change it—usually the same people who can see it.
- Sensitive-data accessWho may see terms and margins—anyone who could see the account.
03Key dimension · Ownership, visibility & edit authority
Who sees and edits what
Visibility is broader than edit authority, and both are separate from ownership. The matrix is the model—not a list of exceptions.
| Role | Owned accounts | Account-team accounts | Region | Global accounts | Sensitive terms |
|---|---|---|---|---|---|
| Account manager | Edit | Edit | Summary | No access | View |
| Specialist | No access | View | No access | No access | No access |
| Sales manager | Edit | Edit | View | Summary | View |
| Global account lead | Edit | Edit | Summary | Edit | View |
| Finance | No access | No access | View | View | Edit |
- Ownership is accountability, not visibility.
- View is broader than edit—by design.
- Hierarchy grants visibility, never ownership.
- Sensitive data has its own boundary.
- Manual sharing expires.
- Service and agent identities get only what their job needs.
“Everyone sees everything” and “everything is private” both avoid the design question. The matrix answers it.
05Candidate architectures
Credible options, judged against these premises.
Everyone can see everything
Small, single-entity organizations
Cost: Sensitive terms exposed; ownership loses meaningPrivate by default, manual sharing
Highly confidential sales
Cost: Sharing exceptions pile up; collaboration breaksPrivate by default; visibility from hierarchy and account teams; field-level protection
A global organization with shared accounts
Cost: Needs governed org data and periodic access reviewsDesign decision
Separate accountability (one owner), visibility (derived from organization and account-team relationships) and edit authority (narrower and role-based)—and drive all three from governed organizational data.
06Resulting architecture
Every platform, one job—and a boundary.
What each platform owns in this design, and what it deliberately does not. These are the responsibilities for this context, not universal rules.
CRMHR & org dataIdentity providerData platform
CRM
Enforces record access- Record ownership (accountability)
- Account teams and shared responsibility
- Visibility rules from hierarchy and teams
- Field-level protection of sensitive data
- Who belongs to which organization unit
- Authentication
HR & org data
The organization as it is- Organization units and reporting lines
- Role assignments and effective dates
- Account ownership decisions
Identity provider
Who the user is- Authentication and single sign-on
- Joiner, mover and leaver events
- Record-level access
Data platform
Reporting access that matches the CRM- Row-level security aligned with CRM visibility
- Access-review analytics
- Operational access decisions
07Governance & operations
Who owns the boundary over time.
An access model decays as the organization changes—unless changes to people and teams drive it.
| What | Owner | Cadence | Evidence |
|---|---|---|---|
| Joiners, movers and leavers | HR data owner, with the identity provider | On every change | Access changes lagging behind organization changes |
| Manual sharing and exceptions | CRM platform owner | Expire by default; reviewed quarterly | Open exceptions and their age |
| Non-human identities | Integration owner | Reviewed with each release | Service and agent identities, their scope and their owner |
08The second layer
Questions that change the architecture.
Ownership
- Does ownership mean accountability or visibility?
- Can one record have several commercial stakeholders?
- What happens to access when ownership changes?
Visibility
- How does a manager inherit visibility?
- How is global access separated from edit permission?
- Which reports must show the same totals to everyone?
Boundaries
- What should remain private?
- Which fields are sensitive, and for whom?
- Who reviews manual sharing—and when does it expire?
09Decisions & outputs
What the work produces.
- 01Ownership model
- 02Visibility matrix
- 03Sharing strategy
- 04Hierarchy model
- 05Permission boundaries
- 06Access review cadence