Saved Table Views

Saved table views

Set a table up how you want it — the right columns in the right order, sorted and filtered — then save that arrangement under a name. It joins a library you can search, share with a team or everyone, and set as the view a table opens with.

The developer guide is Saved table views — Developer Guide.

Related: Assets · Tasks · Calendar · Change Management

Requested by dschipfel in discussion #96, expanded by Ed.

---

1. It works on four tables, not one

The request was about the asset table. It is built into the table engine those four modules share, so it works the same way on all of them:

Module	Where
Assets	Asset Management → Table
Tasks	Tasks → Table
Calendar	Calendar → Table
Change Management	Changes → Table

🔑 Each table keeps its own views. A view saved on the asset table never appears on the tasks table — the two have nothing in common but the machinery.

---

2. Saving one

Get the table looking right, then Save view in the toolbar. Give it a name, a description, and choose who can see it.

What is saved: which columns are visible, what order they are in, the sort, and every per-column filter.

What is not: the search box.

⚠️ The search is deliberately left out. A filter is how you like to look at things; a search is a question you asked once. Saving it would mean opening Servers tomorrow and finding three rows because of what you typed last Tuesday.

---

3. Who can see it

	Who
Only me	Nobody else, ever
A team	Everybody in that one team
Everyone	Anybody who can open that table

Sharing asks which team, because most people are in more than one. Somebody in Service Desk and Infrastructure can share a server view with Infrastructure without the whole service desk seeing it.

🔑 A shared view is readable by the team and editable only by whoever wrote it. That keeps "who changed my view?" a question nobody has to ask. Anybody who wants their own variation can save one.

A view shared with a team or everyone survives its author leaving. A private view belongs to one person and goes with them.

---

4. Your default

The star on a view makes the table open with it every time.

🔑 It is your default, not everybody's. Two people can have different defaults pointing at the same shared view, and changing yours does not touch theirs.

If the view behind your default is later deleted — or shared with a team you have since left — the table simply opens with its own defaults. No error to chase about a view you cannot do anything about.

To go back to the plain table, click the star again to turn the default off.

---

5. The library

Views in the toolbar opens everything you can reach on that table.

• Search by name, by description, or by who made it — which is how people look for a view they did not write.
• List or cards, whichever you prefer. The choice is remembered.
• Each view shows its description, who owns it, who can see it, when it was created, when it was modified, and when it was last used.

🔑 Last used is the one that earns its place. In a library that has grown for a year it is what tells you which views anybody is actually opening, and therefore which can go.

The toolbar button shows the name of the view you are looking at, so an unusual set of columns is never a mystery.

---

6. Editing one

Editing changes the name, description and who can see it. It does not change what the view shows.

⚠️ Renaming something should not silently change what it does. To capture the table as it looks now, use Save view again.

---

7. If a table changes underneath a view

Views keep working:

• A column that no longer exists is dropped from the view when it is applied.
• A column the view has never heard of appears where it normally would, rather than vanishing — so a view saved before a column shipped still works, and still shows the new column.
• A filter naming a value that no longer exists matches nothing, which reads as an empty table rather than an error.

---

8. On an installation serving more than one company

A view is a way of looking at rows, not the rows themselves. Its filters are applied to whatever you were already allowed to load, so a shared view cannot show you another company's equipment.

A view written by somebody in a different company may filter on a value that means nothing to you. That shows up as a filter matching nothing — an empty table, not a leak.