Save Any Layout as a Template

Good layouts take effort to build. A well-designed dashboard section — a metrics row, a data table below, a filter bar at the top — represents design decisions that shouldn't need to be re-made from scratch every time a similar section is needed.

Saving layouts as templates preserves that work and makes it reusable.

Save as Template

In the builder, select any section of a page — a row, a panel, a tab, or any structural component — and use the "Save as Template" option. Give the template a name and an optional description. The template is saved to your workspace's template library.

The template captures the full structure: component types, their configuration, layout proportions, and the relationships between them. It's a complete snapshot of the section, not just its visual appearance.

Use a Template as a Starting Point

When building a new page, open the template library from the component picker. Browse saved templates by name or description. Select a template and drop it onto the canvas. The full structure lands on the page — all components, configured as they were when the template was saved.

The dropped template is immediately editable. Update the data source to point to this page's data. Adjust column selections, labels, and titles. The template provides the structure; you provide the page-specific configuration.

Template Scopes

Templates are saved at the workspace level by default — available to everyone with builder access in the workspace. Administrators can also save templates to a shared library available across all workspaces in a plan.

Platform-level templates are provided for common patterns: a standard record detail layout, a dashboard with metrics and table, a simple list page. These platform templates are a useful starting point even before your workspace has built its own library.

Templates Aren't References

A template creates a copy, not a reference. Dropping a template onto a page creates independent components. Updating the template later doesn't affect pages that used it previously. This is intentional — a template is a starting point, not an ongoing connection.

For ongoing shared components that should update everywhere when changed, use component references instead. Templates are for bootstrapping new pages; component references are for maintaining consistent sections across existing pages.

Building a Template Library

Over time, a workspace's template library becomes a significant productivity asset. Common page structures, standard dashboard patterns, approved layouts for specific functions — all available as one-click starting points. New pages take minutes instead of hours when the structural work is templated.