Documentation

Your first workspace, schema, and flow.

• Create a workspaceSet up a home for one database.
• Import a schemaBring your database structure in.
• Create a flowDiagram one important area of the database.
• Add a node to a flowThree ways to put an object on the canvas.
• What goes whereThe five kinds of knowledge, and which travels.
• You don’t have to finish itThe answer to "we don’t have time".
• Describe an objectWrite documentation worth reading.
• Connect two nodes, and add what isn’t in your databaseDraw dependencies, and bring in outside context.
• Read and share a flowThe payoff — three outputs for three readers.

Document failure, share, and keep it true over time.

• Record what to do when something failsCapture failure modes where they’ll be found.
• Share a flow with someone who has no accountHand over a read-only link.
• Understand driftWhat the red dot is telling you.
• Re-import after your schema changesMove the docs with the database.
• Flow ownershipWho owns a flow, and why drift depends on it.
• Sketch a system before the database existsFreeform is start to finish — no schema import.
• Copy a flow for AIContext to paste before you ask.
• Look up one objectThe object’s own page — everywhere it’s used.
• Duplicate a workspaceMake a private copy to work in safely.
• Move or copy a flow to another workspaceSend a flow elsewhere — safely.

Your own AI, and compliance tagging.

• Create a flow with your own AILet the AI you already use draft it.
• Compliance tagsMark sensitive columns.

People, billing, keys, and account.

• Invite a team memberAdd people to your team.
• Change billingManage your subscription.
• Create or revoke an API keyAutomate schema uploads from CI/CD.
• Revoke a share linkCut off a public link early.
• Send notifications to Teams or SlackPost drift alerts and announcements to a channel.
• Restore a deleted workspaceGet a team workspace back within 30 days.
• Delete your accountClose the team and erase its data.