To share an internal app with roles, you add each role and choose its access level: interaction, which allows viewing and filling, or full control, which allows editing the app itself. Why access decisions get postponed Sharing is often the last step of building an app, and by then nobody
App versioning lets you edit an internal app while the people using it stay on a stable published version. Changes accumulate in a new version and go live only when you decide. Why editing a live app is risky In most no-code tools, every edit is immediately visible to
There are three ways to create an app: from scratch, from something you already have, or with AI guidance. Which one is fastest depends entirely on whether a similar structure already exists in your account. Why one creation method is not enough Building from scratch is tedious when a template
To build a Kanban from connected fields, you choose a field type other than single-select as the column driver. Connected records, radio fields, and user fields can all define the phases of a board. Why single-select is not always the right column The classic board uses a status
Conditionals on the Kanban card cover control which fields appear on the outside of a card. Instead of every card showing the same information, each one shows what is relevant to its current state. Why uniform cards hide the important signal A board where every card looks identical forces you
The Mosaic Kanban information density option trades visual spacing for content. On a board with hundreds of cards, seeing two at a time is not a design choice — it is an obstacle. The problem with spacious boards Generous card layouts look good in a screenshot and slow you down in
To build a Kanban board from a table, you create the view on top of records that already exist. The table stays the source of truth; the board becomes a way of moving those records through phases. Why the board and the data should be separate Tools that store data
To replace generic forms, you stop treating a form as a way to collect answers and start treating it as the entry point to a process. The submission becomes a record with a phase, an owner, and automations attached. What a standalone form tool leaves you with A response file
A good approval request form captures everything the approver needs to decide, and nothing else. That means conditional fields, connected data shown in place, the supporting document visible, and the action buttons separated from the inputs. Why most approval forms get sent back Approvals stall for one reason more than
To work on several records at once, you minimize an open card instead of closing it. The record follows you around the platform, so you can switch context and come back without losing what you were doing. Why context switching costs so much Operations work is interrupt-driven. The cost
Read-only fields and form permissions decide what each person can see and change on a record. The same form can be fully editable for one role and reference-only for another. Why field-level control matters Access control at the file or app level is too coarse for most
To customize the record data sidebar, you choose which fields appear beside an open card and in what order. Instead of every field on the record, the panel shows only what that process actually needs. Why showing everything shows nothing A sidebar listing every field is technically complete and practically