Tabs live at #/settings/<tab>. When tabs were merged into shells — Lead Access into Roles & Access, Brand Center and Email Studio into My Business, Lead Sources into Integrations, Stage Automations into Project Stages, Custom Domain into Email — the old ids were kept as hidden registry rows that render the parent shell already switched to the right sub-tab. The visible parent chip stays lit while an alias is open.
Also called: bookmarked settings page · shared settings link · old link stopped working
- 1VALID_TABS is derived from the registry plus an explicit list of legacy aliases, so deriving the list can never quietly retire a bookmark.
- 2Shell components accept initialTab and rewrite the hash to the canonical alias when you switch sub-tabs, so refresh lands where you were.
- 3NAV_PARENT maps each alias to the parent chip that stays highlighted.
The registry comment is explicit: the hash list used to be a hand-maintained copy that had already drifted, so sub_agreement, automations and pay_structure had deep links that silently redirected to Team Members — 'a bookmark that lands on the wrong page looks like the page was deleted'. Deriving the list from the registry and naming legacy aliases out loud made reorganising the IA safe.
- Reorganising settings silently broke saved links and internal documentation.
- Merged tabs left their old URLs pointing at nothing.
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 →