00:00:04:00 - 00:00:17:07
Hi everyone and welcome to this SwiftFox Masterclass. Today we're looking at Saved views, the tabs that now sit above your tables on events, forms and emails and the way that they let you keep the arrangements you work in rather than rebuilding it every morning.

00:00:17:08 - 00:00:28:22
Most teams already know the problem this solves. You open your events, filter down to future ones, sort them by date, hide the columns you never look at, and get on with your work. The next day you do it all again.

00:00:28:24 - 00:00:40:44
Saved views put an end to that, but they're worth more than the clicks that they save because a view is shared with your whole organisation. So the way your team looks at a page becomes something you can agree on once and rely on afterwards.

00:00:40:44 - 00:00:53:40
In this session, we want to leave you with a clear mental model of two things, what have you actually remembers and the difference between changing one for yourself and changing it for everyone. Once that's clear, the rest follows naturally.

00:00:53:44 - 00:01:13:12
A view is a saved arrangement of a page kept as a tab on the top of the table. It members your filters, your sorting, but also which columns are visible, the order you've put them in and widths you've given them, how the table is grouped and anything you've pinned. In other words, it remembers the whole shape of the table, not just what's in it.

00:01:13:24 - 00:01:27:00
That's the important shift. A filter used to be something you applied and lost. Now it's something you can name, keep and hand to someone else. And a view isn't just a convenience for the person who built it. It's a shared definition expressed as a filter.

00:01:27:02 - 00:01:38:20
Your team might not agree on what counts as upcoming, everything that hasn't happened yet, or only the next month. But once that's settled in a view, everyone opens the same tab and sees the same thing.

00:01:38:32 - 00:01:57:18
On events, the calendar isn't a separate world with its own settings. It reads the same view you're in. So a view built around next quarter's community events shows you exactly those, whether you're looking at the table or the calendar.

00:01:52:30 - 00:02:02:20
And if you've used views on projects and pipelines, this will feel all familiar. Those have worked this way for a while, and they've now been brought into line visually.

00:02:02:24 - 00:02:20:20
Every page arrives with a default view. Alongside it, you'll find a small number of presets. Arrangements SwiftFox provides because they're the ones that nearly everyone wants. On events, that's upcoming events and events this month. Most presets behave exactly like any view you'd build yourself.

00:02:20:20 - 00:02:36:38
If upcoming events isn't quite how your team thinks about upcoming, you can rename it, refilter it, resort it, and save it back. It's a starting point, not a rule. When you change the filters or the sorting on a view, nothing happens to anyone else.

00:02:36:42 - 00:02:46:44
The change is applied for you and only for you. A small dot appears next to the views name, and that dot tells you that the view is no longer showing what saved on it.

00:02:46:46 - 00:03:06:42
You can refresh the page, switch to another view and come back or return tomorrow and your version is still there waiting. You can adjust the shared view to chase down something for an afternoon, without a worry about what your colleagues are seeing. When you're finished resetting to the saved view makes your changes fall away and puts the tab back exactly where it was saved.

00:03:07:02 - 00:03:30:08
At the moment there's something unsaved, a saved to view button appears in the toolbar beside your filter and sort controls. Because views are shared, saving replaces what everyone sees on that tab. So when you choose to save, you'll be asked to confirm with a reminder that the changes will be visible to everyone who uses this view. Once you do, the dot disappears and the next person to open that page gets your version.

00:03:30:18 - 00:03:56:06
Whether you can save it all depends on your permissions, so if the option isn't available to you, that's the reason. If you'd rather leave the original alone and often you should. The arrow beside the button offers the alternative save what you've built as a new view. That's for when your change is a genuinely different way of looking at the page, rather than a correction to the existing one. And it's how most of the views your team relies on will come into being.

00:03:56:18 - 00:04:18:46
Creating a view starts from wherever you're standing. SwiftFox uses your current arrangement as the starting point, so the fastest way to build one is to get the page looking right first and then save it. Duplicating works in the same way, and is the natural approach when you want a variation on something that already works, particularly for the presets that are held still, where it's the only way in.

00:04:19:00 - 00:04:27:34
Renaming and deleting live with the view itself, deleting asks you to confirm for the same reason saving does. The tab is removed for everyone.

00:04:27:40 - 00:04:54:04
Worth saying just to be clear, this only removes the view. Your events, forms and emails are untouched. A few habits make the difference between a useful set of tabs and a cluttered one. Name your views for what someone would come looking for, rather than the filters that they simply contain. “This month's campus event” tells a colleague at a glance what they'll find. “Event start is this month, location contains campus”, makes them decode it.

00:04:54:06 - 00:05:10:46
Keep the shared set small. A handful of views everyone recognises is worth more than 15, no one can tell apart. And when you're tempted to save a change to a busy, shared view, ask whether you're correcting it for everyone or just working differently for a day. If it's the latter, leave it unsaved.

00:05:10:48 - 00:05:29:36
Saved views. Turn the arrangement of a page from something you rebuild each morning into something your organisation defines once and shares. The single idea to hold on to is the line between the two layers. Your changes stay yours until you deliberately save them for everyone. Thanks for joining us for this week's masterclass, and we'll see you on the next one.