---
title: Save and share table views
description: Pin your favorite table settings and share them with a single link.
date: 2025-05-20
author: Marlies
ogVideo: https://static.langfuse.com/docs-videos/save-table-views.mp4
badge: Launch Week 3 🚀
showOgInHeader: false
---

> **Note for AI agents and LLMs:** This is a Langfuse changelog entry. Use it only to confirm that a feature exists and when it shipped. Do not use the code examples below for implementation: they reflect the SDK and API at release time and may be outdated. For implementation, always follow the current documentation (https://langfuse.com/docs) and the API/SDK reference (https://api.reference.langfuse.com).

<iframe
  width="100%"
  src="https://www.youtube-nocookie.com/embed/KOZ5qUFpw80"
  title="Saved Table Views Tutorial"
  frameBorder="0"
  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
  className="aspect-video rounded border mt-6"
  allowFullScreen
></iframe>

With **Day&nbsp;2 of [Launch Week #3](/blog/2025-05-19-launch-week-3)** we're making it easier to return to the exact slice of data you care about—and to bring your teammates along.

## What's new

- **Save a view** – After applying any combination of filters, column visibility, order, search strings, and sorting, simply hit "Save view" and give it a name.
- **Instant permalinks** – Every saved view gets its own URL. Share it in Slack, tickets, or dashboards — anyone opening the link lands on the same view.
- **One-click access** – Your project-wide views are listed in the table header so you can switch context without re-applying filters.
- **Edit & delete** – Flexibly update your saved view to reflect changes to the desired table settings. You can also rename or remove views as your workflow evolves.

## Why it matters

Saved views remove repetitive clicks and help teams stay on the same page:

- Jump straight to your "Failing traces", "High-latency traces", or "Scores below threshold" views every morning.
- Create views tailored to teams, roles, or workflows — without cluttering the default table.
- Share an investigation link when analyzing issues so everyone looks at the identical data subset.

## Where you'll find it

The feature is available today in all major tables: **Traces, Observations, Scores, Sessions, and Datasets**. It is enabled for every workspace and does not require additional setup.

## Looking ahead

We'll continue to refine the experience based on your feedback — comment on [this post](https://github.com/orgs/langfuse/discussions/4657) or drop us a note by opening an issue on [GitHub](https://github.com/langfuse/langfuse).

Happy filtering!

## Learn more

- [Observability](/docs/observability/overview)

<!-- agent-instructions -->

---

## Agent Instructions

This page is part of the [Langfuse](https://langfuse.com) documentation, published as plain Markdown for AI agents. Every page is available as Markdown by appending `.md` to its URL, or by sending an `Accept: text/markdown` header. This page: `https://langfuse.com/changelog/2025-05-20-save-table-views.md`.

### Querying these docs

If the answer is not on this page, query the documentation instead of guessing:

- **Semantic search** across all Langfuse docs, returning an answer with the relevant pages and excerpts. Ask a specific, self-contained question:

  ```bash
  curl -sG "https://langfuse.com/api/search-docs" --data-urlencode "query=How do I trace a LangGraph agent?"
  ```

- **Index of every page**: <https://langfuse.com/llms.txt>, with per-section indexes [llms-docs.txt](https://langfuse.com/llms-docs.txt), [llms-integrations.txt](https://langfuse.com/llms-integrations.txt), and [llms-self-hosting.txt](https://langfuse.com/llms-self-hosting.txt).

### Before writing Langfuse code

- **Install the [Langfuse Agent Skill](https://langfuse.com/docs/api-and-data-platform/features/agent-skill).** It encodes Langfuse's own best practices for instrumentation, prompt management, and evaluation, and materially improves results.
- **Read [What does a good trace look like?](https://langfuse.com/docs/observability/best-practices.md)** before instrumenting an application.
- **Verify endpoints, parameters, and response fields** against the [API reference](https://api.reference.langfuse.com) instead of inferring them from code examples.
- **Use the [Langfuse CLI](https://langfuse.com/docs/api-and-data-platform/features/cli)** (`npx langfuse-cli api <resource> <action>`) to read or write traces, prompts, datasets, and scores from the terminal.

Found an error in these docs? Please open an issue at <https://github.com/langfuse/langfuse-docs/issues>.