> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/getting-started/save-views-and-templates.md).

# Save Views and Templates

### Overview

Save Views capture a repeatable view setup. Templates standardize setup across Projects.

{% hint style="info" %}
Screenshot placeholder: view selector showing multiple saved views (private and team).
{% endhint %}

### Key Concepts

#### Save View

A Save View typically includes visible columns, filters, sorting, and grouping.

#### Template

A template is a starting point for creating a new view. Templates help teams use consistent patterns.

### How It’s Used

Use Save Views for daily review lists. Use templates for standard defaults across Projects.

### Benefits

* Repeatable review lists without rebuilding filters
* Standardized views across Projects for consistent governance

### Setup Steps

#### What gets saved in a Save View

Saved configuration typically includes:

* Visible columns and their order
* Filters
* Sorting
* Grouping

{% hint style="info" %}
Screenshot placeholder: a view showing columns + filters + grouping all active.
{% endhint %}

#### Create a Save View

Most changes save to the current view automatically.

When **Save as new view** appears, use it to create a clean copy.

Use a clear name.

Use names such as `Team — Weekly review` or `Tasks — This week`.

{% hint style="info" %}
GIF placeholder: customize a view, then use Save as new view, then rename it.
{% endhint %}

#### Naming conventions

Consistent names keep the view selector usable.

Use a simple pattern.

`{Audience} — {Intent} — {Optional scope}`

Recommended audiences:

* `Team` for shared views
* `Me` for personal views
* `Export` for export-only views

Use `Team` for stable defaults.

Use `Me` for personal variations.

Use `Export` when the view is designed for downloads.

For example:

* `Team — Weekly review`
* `Team — Open items`
* `Me — Open items`
* `Export — Requirements (All)`
* `Export — Tasks (Open)`

{% hint style="warning" %}
Avoid dates in names unless required. They go stale fast.
{% endhint %}

{% hint style="success" %}
**Best practices**

* Standardize names. Use a consistent prefix. For example: `Team — Weekly review`.
* Keep team views minimal. Include only columns most people need.
* Duplicate before major edits. Keep a baseline view.
* Use templates for repeatability across Projects.
* Review shared views quarterly. Archive or delete stale ones.
  {% endhint %}

#### Share a Save View

Set visibility so the right people can use it.

* **Private** (single teammate)
* **Team** (everyone in the project)

{% hint style="info" %}
Screenshot placeholder: view visibility options (Private vs Team) in the share modal.
{% endhint %}

#### Use templates (if enabled)

Templates are starting points.

They help teams use the same columns, filters, and grouping patterns.

{% hint style="info" %}
Screenshot placeholder: template picker or “Create from template” flow.
{% endhint %}

### Best Practices

* Standardize shared view names, then keep them stable.
* Duplicate a shared view before major edits.
* Review shared views quarterly and archive stale ones.

### Summary

Save Views store repeatable view configurations. Templates provide standard starting points across Projects.

Related:

* [Creating and Customizing List Views](/getting-started/creating-and-customizing-list-views.md)
* [Exporting Data from Views](/getting-started/exporting-data-from-views.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.transform.ai/getting-started/save-views-and-templates.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.