Settings menu, a cleaner draft
A high-level proposal for the Settings menu, to agree before building.
2026-09-26 · draft · follows the settings redesign · nothing built yet
What is wrong today
- Two menus side by side: the app menu plus the settings menu.
- Too many "You"s: a "You" group of "My…" items.
- An extra layer: pages hide under a "Settings" item.
- Two words: "Company" here, "Organization" elsewhere.
The proposal
One menu, plain indented text, no icons, no dropdowns. In Settings, the app menu turns into the settings menu, and everything is visible at once.
Today (settings menu)
- You
- Profile
- Sign-in & security
- My calendar
- My notifications
- Company · Acme
- Knowledge
- Policies
- Settings ▾
- General
- Connections
- Leasing & tours
- …6 more
- Building · The Willows
- Knowledge
- Policies
- Settings ▾
- …7 pages
- Admin
- Settings
Proposed (the only menu in Settings)
- ← Back to PropFlow
- Your account
- Profile
- Sign-in & security
- Calendar
- Notifications
- Company · Acme Property
- Knowledge
- Policies
- General
- Connections
- Leasing & tours
- Calls & messages
- Team
- …3 more
- Building · The Willows ⌄ change
- Knowledge
- Policies
- General
- Maintenance
- …5 more
- PropFlow admin · staff only
- Settings
Three calls for Gera
1. Menu shape
- Recommended: one menu. In Settings the app menu becomes the settings menu, with a back link.
- Keep the app menu, and make the settings menu the one indented list beside it.
- Tabs across the top for the four levels.
2. Name of the personal group
- Recommended: "Your account", with the "My" dropped from item names.
- "Me".
- The person's own name, e.g. "Gera".
3. Company or Organization
- Recommended: "Company" everywhere a customer reads it. Rename the leftover "Organization Settings" and "Organization admin" labels.
- "Organization" everywhere, including the settings pages.
- Leave both as they are.
Why these recommendations
One menu: two stacked menus is the confusing part; replacing the app menu while in Settings is the common pattern (Linear, Notion, GitHub) and gives the tree room to show every page with no dropdown.
No "Settings" layer: the topic pages sit directly under Company and Building, so the tree is two levels deep, never three.
"Your account": says whose settings these are once, instead of "You" plus "My" on every row.
"Company": it is the word property managers use, and 309 places in the app say it versus 67 for "Organization". The code keeps its internal name; only the words people read change. "Organization admin" as a role name would read "Company admin".
What does not change: every page, its address and its content stay as built; this is the menu and the words only.