Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

💾Save Views and Templates

Save, share, and reuse view setups so teams stay consistent.

Overview

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

Screenshot placeholder: view selector showing multiple saved views (private and team).

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

Screenshot placeholder: a view showing columns + filters + grouping all active.

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.

GIF placeholder: customize a view, then use Save as new view, then rename it.

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)

Avoid dates in names unless required. They go stale fast.

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.

Share a Save View

Set visibility so the right people can use it.

  • Private (single teammate)

  • Team (everyone in the project)

Screenshot placeholder: view visibility options (Private vs Team) in the share modal.

Use templates (if enabled)

Templates are starting points.

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

Screenshot placeholder: template picker or “Create from template” flow.

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:

Last updated