Roles & Access — one tab, two views

Permission presets (what a role can do) and Lead visibility (what a rep can see) live as two sub-tabs of one Roles & Access tab.

What it is

A shell that puts the two halves of access control side by side, with the hash kept honest so refreshing or bookmarking lands where you were. The old Lead Access deep link still resolves into the second sub-tab.

Also called: permissions tab · role templates and lead access together

See it
Roles & Access — one tab, two views
Area
Platform & Admin
Group
Roles & permissions
System
Team & Access
Solves
1 named problem
01Selecting a sub-tab rewrites the hash to #/settings/permissions or #/settings/lead_access.
02Arriving via either alias switches the view without a remount.
03The parent Roles & Access chip stays lit while the alias is active.
The two sub-tab strip (Permission presets | Lead visibility) above the presets list. Sample data — no customer information appears here.
How it works
  1. 1Selecting a sub-tab rewrites the hash to #/settings/permissions or #/settings/lead_access.
  2. 2Arriving via either alias switches the view without a remount.
  3. 3The parent Roles & Access chip stays lit while the alias is active.
Why we built it

The shell comment says it plainly: these were 'two unrelated top-level tabs (Role Templates and Lead Access) though lead visibility IS a permission — one story split across two doors' (settings IA redesign, ).

The problem
  • Access control was split across two unrelated tabs.
Sound familiar?
What you get
One place answers both what someone can do and what they can see.
Old links to the lead-access tab keep working.

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →