Templates
Two kinds, and the difference is what lands in your workspace.
App templates and Form templates
| App template | Form template | |
|---|---|---|
| Brings | Tables, pages, boards, Forms and Flows, wired together | One Form, its Flow, and the record table it owns |
| Lands in | A new App | An app you already build in, opened in the designer |
| Example | Purchasing, Admissions, Employee Requests, Asset Register, CRM | Public Form, Client Enquiry, Vendor Onboarding |
| Who can | Workspace admins — an app is an access boundary and consumes plan quota | Any member |
What happens when you add one
One transaction: it either all lands or none of it does. Nothing is half-created for somebody to find later.
- Every reference inside a template is symbolic, so a new page's bindings resolve without a single substitution.
- Reviewers arrive as placeholders — "Finance", "Department Heads" — which you swap for real teams before publishing. A template never carries somebody else's team ids.
- Templates ship structure, never rows. The app arrives empty and correct.
What a template can ask for
A template can declare that it depends on a table your workspace already shares — an Employees table, say — rather than creating a second copy of it. If you have one with the columns it needs, it is used; if you do not, it is created for you.
It can also declare connectors it would like. Those are a checklist rather than a blocker: an app whose Slack step is not wired yet is still an app worth looking at. Credentials are never templated.
Exporting your own
Export an app you have built and add it to another workspace. It is the same format the shipped templates use — one bundle, one validator, one path in.