Manage reusable app templates

Find, rename, remove, and version reusable starters without silently changing existing apps.

The New App gallery combines platform starters with templates saved by your tenant. Use All, Platform, and My templates to narrow the gallery, and search by name when the collection grows.

Select a card to load the template's full details and parameter form. A gallery card is a summary; wait for the selected template's details before deciding what setup it needs.

Rename or remove a team template

On a tenant-owned template card, choose Rename, enter a meaningful name, and choose Save. Choose Cancel to abandon the rename.

Choose Delete only when the reusable starter is no longer needed. The confirmation explains that this removes the template and its version history; apps already created from it are untouched. Removing a template is a different operation from moving an app to Trash: the template is a reusable source, while an app is a provisioned instance. Read the confirmation and resolve any displayed permission refusal.

Platform cards carry a Platform badge and cannot be renamed or deleted by an ordinary tenant user. To customize a platform starter, create an app from it, edit the resulting app, and save a new tenant template.

Template versions and app versions

Template content is versioned separately from an app's definition history. An app records the template version used during creation. Its parameter defaults, read-only settings, connector contract, and validation remain based on that saved version; a later template edit does not silently revalidate an existing app against today's schema.

Definition history tracks edits to the particular app. Publishing a release freezes a particular app's execution configuration. Neither operation means the reusable template was updated.

When distributing a revised starter, provide a clear name and description and verify a fresh app can be created from it. Do not assume an existing instance automatically acquires newly added workflows, schema fields, or components. Engine upgrades likewise update the runtime pin rather than creating a new instance from a revised template.

Download

Select a template and choose Download template when portable export is enabled. The resulting .strive.html file carries reusable configuration and requirements. It does not carry credentials or the live data of an app previously created from that template.

See Definition versions, Releases, and Import.