A spreadsheet has one view: everything. You can hide columns, you can sort, you can filter — but the next person who opens it sees everything in the default order, and they have to re-do whatever you did to find what you were looking at.

A pipeline in Leadline has many views, and each view is a URL. The URL contains the filter, the columns, and the sort. The URL is what you paste to a colleague, what you bookmark, what you put in your CRM as a link back to “the list I was working on”.

This post is the working walkthrough for how to use saved views, what they actually save, and the small rules of the road for keeping them readable.

What a saved view is

Open any list in the workspace. Filter it — say, “stage is Qualified, owner is Avery, source is Harvest.” Sort it by “last call, newest first.” Hide a column you don’t care about. You now have a filtered, sorted, custom-shaped view of the same list.

Click Save view in the toolbar. Name it (“Avery’s qualified leads”). The view is saved.

What was saved:

The filter — every condition, in order.
The columns — what’s visible, what’s hidden, the order.
The sort — primary and secondary keys, ascending vs descending.
The density — compact or comfortable.

What was not saved:

The rows. A saved view is a window into the same data, not a snapshot. When a new lead matches the filter, it shows up in the view. When a stage changes, the lead moves out of the view. A saved view is always current.
The owner. The view is yours, but anyone you share it with sees the same current data.

What the URL contains

Click the saved view. Look at the URL. It looks like this:

https://scraper.com/workspace/leads?v=q4f-a82b&t=qualified

v=q4f-a82b is the view ID. A short hash, not the filter itself.
t=qualified is the tab or section anchor, if any.

The view ID resolves to the saved filter / columns / sort. The filter itself is not in the URL — that is deliberate. If you change the filter (say, you rename “Qualified” to “MQL”), the view updates. The URL stays the same. Views are resilient to small changes in your data shape.

This is the opposite of a spreadsheet that has =COUNTIF(A:A, "Qualified") formulas that break the moment you rename a column. Saved views are references, not formulas.

Open the view. Click Copy link. Paste it to a colleague in Slack, an email, or a CRM record.

When the colleague opens the link:

If they have access to the workspace, they see the same filtered, sorted, custom-shaped view.
If they don’t have access, they see a “request access” page.

You don’t need to send a screenshot. You don’t need to explain “filter on stage Qualified, owner Avery, source Harvest”. You send a URL and they see what you see.

If you want to give the colleague a different view of the same data — say, they manage the SDR team and want to see leads by stage, you as an SDR want to see leads by last-call date — they save their own view from yours. The two views live side by side, neither one replaces the other.

Editing a saved view

Open the view. Change the filter. The URL doesn’t change. The view name still says “Avery’s qualified leads” but the filter is now different.

This is the moment to ask: did you mean to update the view for everyone you shared it with, or did you mean to make a new view just for yourself?

Two buttons:

Save changes. Updates the view. Everyone who has the URL sees the new filter.
Save as new view. Creates a new view (e.g. “Avery’s qualified leads — May”) and the original URL stays the same.

The second option is the right one in most cases. Saved views are durable references; treat them like branches in version control, not scratch files. If you want to experiment, save as new. If you want to update what the team sees, save changes deliberately.

What saved views are not

Not a dashboard. Saved views are tabular, not visual. If you want charts, that’s a dashboard widget (a different feature). Saved views show you rows in a filtered table.
Not a saved query for later. A saved view is current, not deferred. If you want a query to run every Monday morning and email you the results, that’s a different feature (and one we may or may not build).
Not a permission. The view is the same window into the data; it doesn’t grant or revoke access. Permissions live on the workspace, not the view.

A small workflow that uses this well

The pattern that comes up most often:

Build a view for the morning ritual. Filter to “stage is New, owner is me”. Sort by “last touched, oldest first” so the cold leads rise. Save it as “Morning queue”. Open it in a browser tab every morning.
Build a view for the weekly review. Filter to “stage is anything, owner is me, last call within 7 days”. Sort by “stage”. Save it as “My week”. This is the list you look at on Friday afternoon to see what got done.
Build a view per partner or per segment. One per account you prospect for, if you’re an agency. The view name is the company name. The URL goes in the CRM record for that account.

Three views. Each one is a URL. Each one updates itself. The total time spent managing views in a week is roughly zero.

Where to go next

If you have a list and a workflow in mind, open the list and try saving a view. The toolbar button is right there.

If you want to read more first:

The dialer — once you have a view, click Dial queue to start calling through it.
Harvest a neighbourhood — if the list is empty, this is how to fill it.
Solo vs Team — saved views work in Solo (locally) and in Team (shared). The Team version is what makes the URL-shareable bit possible.

That’s saved views: filter, columns, sort, density, all baked into a URL that updates itself.