Skip to main content
A starter template is a ready-made Collection setup. Picking one at creation time seeds three things at once, so you get a working Collection with a real page instead of four empty fields. Templates appear on the creation screen (the first five, as examples) and in the full library behind Browse all, which has a search box. Choosing one creates the Collection immediately — there is no configuration step in between.

What a template seeds

  • A field schema — the custom fields that Item type needs, already typed, labeled and ordered. An inventory template arrives with SKU, supplier, quantity, reorder level and unit cost; you are not defining those by hand.
  • A page template — a real page design generated from those fields, ready to open in the Page Editor.
  • Three sample Items — filled-in examples so the grid and the page preview show something meaningful on day one. Delete them once you have real data; they are ordinary Items.
The template also sets the Collection’s scan behavior. A template built around a page turns pages on and defaults new Items to Page Mode; a pass-through template leaves pages off and defaults new Items to a single Destination.

The eight templates

The first five are the ones shown as examples on the creation screen; all eight are in the library. The platform behind the SafetyCulture template is now called Mitti — the template name still uses the older name.

Templates apply once, at creation

A template is a starting point, not a live link. Once the Collection exists, there is no way to switch it to a different template, and nothing about the template keeps applying — the fields, the page and the sample Items are now ordinary Collection content you own and can change freely. That means:
  • Editing a field the template created is safe. It is your field now.
  • Deleting the sample Items does not break the page template.
  • If you picked the wrong template, the practical fix is a new Collection from the right one rather than a conversion. Nothing is lost if the wrong one is still empty.
If you want a reusable starting point of your own rather than a system template, export a finished Collection as a backup and create new Collections from that file — see Creating a New Collection From a Backup.