Overview
As a workspace accumulates template components, it helps to know where they live, how changes reach the apps that use them, and which actions you can take on each one. This guide covers what you can do with a template component after it is created: finding it in the library, publishing changes, and managing it from its card.
For creating a new template component from scratch, see Creating a Template Component.
Accessing the Template Component Library
Template components are listed in two places:
Applications → Template components — the library page, which shows your team's templates as cards under Custom templates. Use Search template (or press ⌘K, Ctrl+K on Windows) to find a template by name, and Create template to start a new one.
The component picker in the Application Builder — inside any app, open the component picker and go to its Template components tab. Add a template like any other component, then set its inputs and fill its slots.
How Changes Reach Your Apps
Every instance of a template component is a live view of the source component, not a copy. When you place a template on a page, the instance renders the source's content directly. On the canvas, its inner content is a preview — you can't click into it and edit the blocks inside from the page.
Because of this, there is one version of the template that every instance follows:
When you publish a change to the template, every instance in every app shows the change.
There is no per-instance version, and you can't pin one instance to an older look while the source moves on.
To make an instance differ from others, use what the author exposed: its Inputs, its Slots, and its Child components overrides. See Inputs, Slots & Overrides.
Warning: A breaking change to the source — for example, renaming an input or removing a slot — affects every instance at once. Treat a widely used template like shared code: test changes before you publish them, and let the teams that use it know.
Publishing a Template
Template components are published from their builder, with the Publish button in the header. Like apps, each template also has a details page with Overview, Versions and Localization tabs — open the template from the library to reach it. Versions lists the template's versions. Instances always follow the latest published version; you can't pin an instance to an older one. See App Versions.
Edit the template: Open the template in its builder. Make your structural changes — add, remove, or modify blocks, inputs, slots, and overrides.
Preview the changes: Use the builder preview to verify the template renders correctly. Check it with different sample input values if the template accepts inputs.
Publish: Publish the template from its builder. The change then reaches every instance of the template.
Managing a Template from Its Card
On the Template components page, open a template card's menu to manage it:
Action | What it does |
|---|---|
Open in Builder | Opens the template in its builder so you can change it. |
Edit Details | Changes the template's details, such as its name and description. |
Clone | Creates a copy of the template that you can change independently. |
Share | Gives other users or teams access to the template. |
Delete | Removes the template. |
Permissions
Template components follow the same permissions as applications. To see Create template and create new templates, you need permission to create applications. Users with view access can browse templates but don't see Create template.
Related Pages
Template Components Overview — what template components are and how they differ from modules.
Creating a Template Component — step-by-step guide to building a new template from scratch.
Inputs, Slots & Overrides — making templates configurable so they work in multiple contexts.
Permissions — configuring who can create and manage applications and templates.