Who can see a view

Every saved view has a visibility tier. The tier decides who can open the view and who can change it. This page is the reference for the three tiers, who can create Workspace views, and how sharing by link works.

New to Saved Views? Start with Saved Views for what the feature does, or the Build and save a view playbook for the step-by-step.

The two tiers

You set a view's tier when you save it (the Visibility radio on the details form). The tier is permanent: it can't be changed after saving. To move a view to the other tier, duplicate it (or Save as new view), pick the new tier, and delete the original.

• Personal views are yours: only you see them in your switcher, and only you can edit or delete them. They're the default. One nuance: the tier controls whose list the view shows up in, not link access. A teammate in your organization who has the direct link can open a personal view read-only (see Sharing a view by link).
• Workspace views are shared with your whole organization, so the team looks at the same list the same way. This is how an admin curates a standard set of views everyone starts from.

Alongside your saved views, each page ships with built-in default views (like "All loads"). They belong to the product, not to anyone in your organization: duplicate one to customize it, but they can't be edited or deleted in place.

Who can create Workspace views

The Workspace option only appears on the visibility form if you're allowed to author org-shared views. If you don't see it, you can still make all the Personal views you want; you just can't publish one to the whole organization.

Admins typically curate the Workspace views so the shared set stays clean and useful.

Sharing a view by link

You don't have to make a view Workspace-wide to hand it to one teammate. Every view has a link.

1. 1

   Open the view you want to share

   Switch to it so it's the active view on the page.
2. 2

   Copy the page URL with the view on it

   The URL carries the view as a query parameter, like /loads?view=<id>. Copy it from your browser's address bar.
3. 3

   Send it

   Paste the link to your teammate. When they open it, that exact view loads for them.

A teammate who opens your link gets the view read-only. They can use it and filter within it, but they can't overwrite your saved view unless the view belongs to them. To let them save their own copy, they can shape it and use Save as new view.

How it maps to permissions

Access to saved views is governed by the Organization.SavedViews capability, with the actions read, create, update, delete, and manage. (Exporting list data is governed by the list's own subject, not by saved views.)

• Personal views are self-managed: their owner edits and deletes them.
• Workspace (org-shared) views follow a creator-or-manage rule. The person who created the view can edit it, and so can anyone who holds manage on saved views. Holding create is enough to author your own Workspace views, but not to save over someone else's. This is how admins curate the shared set.
• Offload staff cannot see or edit your views. Personal and Workspace views are reachable only inside your organization.

For the full permission picture and where this sits next to the other subjects, see the Permission Matrix and How Permissions Work.