To customize the connected tab on a card, you choose which related tables appear, which of their fields show, how they are ordered, and whether users can add records from there. Why the default panel gets ignored A connected panel showing every field of every related table is too much
Choosing between builder, member or viewer determines what someone can do structurally. Roles then determine what data they can reach. The two decisions are separate and both matter. Why seat type is decided badly Seats are usually assigned at the moment of inviting someone, when nobody is thinking about it.
To filter and audit users on an account with hundreds of people, you need two filters: what type of user someone is, and whether they are still active. Why user lists become unmanageable A flat list of every person who ever had access answers nothing useful. * No way to see
Letting users favourite apps from the menu removes a small but constant friction: shortcuts that only an administrator could arrange, or that required navigating away to set. Why shortcut management gets neglected If changing a shortcut takes more effort than living without it, nobody changes it. * Members unable to favourite
To customize the side menu, you control three things: whether app backgrounds show, how the menu behaves on hover, and how folders are nested. The title bar has its own alignment options. Why default navigation stops fitting As a workspace grows, the navigation that worked for five apps becomes the
Choosing a side menu or top menu is a trade-off between screen space and list length. A top bar keeps the interface clean and limits how much fits; a side menu holds longer lists with readable names. Why navigation choice affects daily work Navigation is used hundreds of times
To choose the right template, you compare what it already includes against what your process actually requires — and accept that adapting a close match is usually faster than building an exact one. Why template choice goes wrong Templates are installed optimistically and abandoned when they turn out to describe a
To track payables and receivables, the view should show only what is still open. Settled entries belong in history; the dashboard exists to show what still requires action. Why finance dashboards get ignored A panel showing everything ever recorded is an archive, not a working tool. * Paid invoices cluttering the
Deciding what a COO can automate starts with the parts of the day that consume attention without requiring judgement — triage, chasing, and approvals that only needed a signature. The operations leader's usual day The pattern is recognizable in almost any growing company. * Dozens of emails to triage before
To distribute project workload across weeks, you need to see projects laid out by date rather than by status. Clustering is invisible on a board and obvious on a calendar. Why capacity problems are discovered late A pipeline that looks healthy in aggregate can be impossible in a specific week.
To manage contacts and deals together, the contact is a record in its own right and each deal connects to it. Everything a client has been quoted, sold, or promised is then reachable from one place. Why contact data fragments Contacts are created wherever they first appear, which means they
To show parent record data in a card, you configure the connected field to display more than just the parent's name. A project stage can then show the project's budget without anyone navigating away. Why a name is rarely enough A connected field showing only a