Schema designer
Ce contenu n’est pas encore disponible dans votre langue.
The schema designer is an ERD — an entity-relationship diagram — living inside your workspace. Tables, columns, keys, and the relationships between them.
It is here for the same reason the wiki is: the diagram that explains your data model should sit next to the tasks that change it, not in a tool half the team cannot open.
What you draw
Section titled “What you draw”Tables with real columns — name, type, nullability, keys — and the relationships between them, drawn as connections rather than described in prose.
Pick the dialect your database actually speaks:
| Dialect | For |
|---|---|
| PostgreSQL | The default for most teams |
| MySQL | MySQL and MariaDB |
| SQLite | Embedded, mobile, and local-first |
| Standard | Dialect-neutral — when the diagram is conceptual |
The dialect drives the column types on offer, so the diagram stays honest about what your database can hold.
Where diagrams live
Section titled “Where diagrams live”Diagrams sit alongside your other documents. You can:
- Put one in a folder, next to the pages that describe the same subsystem
- Set its access — shared with the workspace, or private while you work
- Archive it when a design is superseded, and bring it back if you were wrong
Archiving beats deleting here. An old schema is the fastest way to understand why the current one looks the way it does.
Use it with the work
Section titled “Use it with the work”The point is proximity. A few patterns that pay off:
- Link the diagram from the page that specs the change, so a reviewer sees the shape before the SQL.
- Reference the migration task from that page with @@ — the chip stays live, so it shows the migration’s current status forever.
- Keep one diagram per bounded area rather than one enormous canvas. A diagram nobody can read is a diagram nobody updates.
Schema designer, whiteboard, or page?
Section titled “Schema designer, whiteboard, or page?”Three visual-ish surfaces, three jobs:
| You are drawing | Use |
|---|---|
| Tables, columns, and foreign keys | Schema designer |
| A flow, an architecture sketch, sticky notes | Whiteboard |
| Prose with a diagram in the middle | Page with an embedded board |
If you find yourself drawing boxes-with-columns on a whiteboard, you want this instead — it understands what a foreign key is.
Limits
Section titled “Limits”| Plan | Diagrams |
|---|---|
| Free | 1 |
| Pro | Unlimited |
The schema designer is a workspace module. If your admin has it switched off, the section is hidden for everyone — see Workspace settings.
- Whiteboards — free-form drawing.
- Pages and wiki — the prose around the diagram.
- Schema designer overview — the feature page.