Turning your own table into a template
Once a set of tables, formulas and views is right, Export → Template gives you a file that somebody else installs in one go with Upload local template file. What to tidy up first, and the template developer mode.
Tidy three things first
- Column names and field types. Whoever uses it will read the data by your column names and type into it by your field types. Amount numeric, status single-select, dates as dates, and nothing left called "untitled".
- Formulas that only reference tables inside the template. A formula referencing a table outside it drags that table into the export too — make sure that is what you want.
- Whether to include data. Sample data makes a template instantly legible; an empty ledger for somebody else to fill should have its data cleared (menu → data → clear) before exporting.
Exporting
Open the main table, Export → Template, save the .json. Linked tables, views and dashboards are packaged with it. Send the file directly, or drop it on a shared drive.
Verifying
Install it once into a different workspace (make a new one) with Upload local template file and check: every table is there, formula columns have values, views and dashboards open. Every scenario template published on the website is accepted this way — really installed, really checked.
Template developer mode
The tools area at the top right of the home screen has a template-developer switch, for whoever maintains a library. With it on, a table's menu gains a publish action: template name, category, description, cover, languages and whether it is VIP-only, published into the library — and it can be withdrawn again. The desktop app has no central library, so this flow mostly serves the team edition; day to day, a file is enough.