Skip to content
PURE

org chart · access matrix · vocabulary — make every version speak the same languagePURE Hierarchy & Access

Mind Map

Who belongs where. Every organization, the people and roles inside it, and what each is for. This is the structure 4.8 expressed as module-access and 5 expresses as hats — shown one way so they line up.

Role × surface access — who can see and edit what, read live from pure_nav_grants (the Nav Governance store). This is the same data that builds each hat's menu in 5; 4.8 called it module permissions.

editviewnonenot set

The same concept, named differently in each build. Highlighted rows differ across versions — those are where to standardize. The right column is the canonical term to use everywhere.

What is a "hat" in 5? In 4.8 a user had a fixed role tied to which modules they could open. In 5, one login can wear several hats — Agent, Broker, TC — and switches context without logging out; access is computed per hat from the same grants. 5B calls the person an identity. Canonical going forward: a person has one account and one or more ROLES; the act of switching is "changing hats."

Volume through the pipeline — how many records sit at each stage, read live. The band width shows where business concentrates and where it falls off (the drop between stages is your conversion gap).

One deal across the people who touch it — each lane is a role, each step lands in the lane that owns it, left to right from first contact to closed. This is the same deal 4.8 ran as a “file” and 5 runs as a Deal Spine.