I'm new on a team that shares a tmux box, and nobody can tell me which session I'm allowed to attach to. How do teams fix that?
The keybindings are the easy part — the wall is the session model: what exists, who owns it, what it's for, and whether it's safe to attach. tmux ls half-answers it with names like main, pair-1, dl, 0, 1, and the map only lives in the veterans' heads. Break "discoverability" into four sub-problems: inventory (what exists, for what), permission (which sessions may you attach to), state (active vs idle vs abandoned), and onboarding (learning all three without panicking).
The highest-leverage fix is a strict naming convention, e.g. {type}-{owner}-{purpose} where type is one of shared (anyone), pair (two-person, ask first), solo (do not attach), ops (deploys/migrations), bot (automated). Now ops-alex-deploy and solo-dan-scratch answer inventory, ownership, and permission at a glance. Add helper wrappers so the convention is the path of least resistance, and a tls listing wrapper that adds OWNER / TYPE / ATTACHED / IDLE / PURPOSE columns plus a "3 sessions attachable to you" line — backed by a purposes.txt checked into the repo.
Keep the inventory honest with a weekly "grim reaper" that kills sessions idle for 14 days (unless prefixed keep-) and a cron that auto-detaches zombie clients. Finally, adopt one rule with outsized payoff: attach read-only first (tmux a -r, aliased to tar) so you can orient — see whose session it is and what's running — before you ever send a keystroke into someone's live vim or psql.