Shared Views

Share a saved view with specific people in your workspace, instead of making it public to everyone or keeping it to yourself. Recipients get a "Shared with me" inbox.

Plan: Pro and above

A saved view is private to you or public to the whole workspace — there's no middle ground. Shared Views adds one: pick the members who should see it, and choose whether they can just look, or actually work in it.

What you can do

  • Share any saved view with named workspace members.
  • Grant either Can view (read-only) or Can edit access.
  • See every view that's been shared with you, and who shared it.
  • See every view you've shared, and how many people have it.
  • Change or revoke sharing at any time.

Getting started

Share a view

  1. Open a project's Views.
  2. Click the ••• menu on the view you want to share.
  3. Choose Share.
  4. Tick the workspace members you want to share with.
  5. Choose the access level — Can view or Can edit.
  6. Save.

📷 Screenshot: The Share modal listing workspace members with checkboxes and an access-level selector.

Find views shared with you

Click Shared Views in the workspace sidebar. The page has two sections:

  • Shared with me — views other members have shared with you, each showing who shared it and whether you have view or edit access.
  • Shared by me — views you've shared, each showing how many members have them, with a Manage button.

📷 Screenshot: The Shared Views page with "Shared with me" and "Shared by me" sections.

Permissions — how view and edit actually differ

This is the part worth reading carefully, because the two access levels behave differently by design.

Can edit — the row shows an Open link that takes you to the normal view page inside the project. You get the full, native view: filters, grouping, layouts, and the ability to open and change work items (subject to your existing project permissions).

Can view — the row shows a Preview button instead. It opens a read-only preview panel: the view's work items, with their titles, IDs, priorities and states. You cannot edit the view or the items from it, and you are not taken to the project's view page.

Two things follow from that, and they matter:

  • Sharing is additive to the view, not to the project. It tells the app which views to show you and how to open them. It does not grant access to a project you aren't already in. The preview loads work items with your own session, so your existing project permissions still apply. Sharing a view from a project someone can't see won't leak that project's work items to them.
  • Read-only is a UI boundary, not a vault. "Can view" stops the recipient opening the editable view page from Shared Views. If they already have access to that project by other means, they can still navigate to the view themselves. Treat "Can view" as "here's a clean, read-only way to look at this", not as a security control over the underlying data.

Managing and revoking

  1. Go to Shared Views → Shared by me.
  2. Click Manage on the view.
  3. Untick a member to revoke their access, or tick more to add people. Change the access level if you want.
  4. Save.

Unticking someone removes the share immediately — the view disappears from their Shared with me list.

You can only share with active members of the same workspace. Anyone else is rejected.

Tips

  • The access level is set for the whole share, not per person. If you need one person on Can edit and everyone else on Can view, share twice — once per group — or accept the higher level for all.
  • Views shared without a project (workspace-level views) show as Workspace view in your inbox and can't be previewed inline. Open them from the workspace views page.
  • Sharing survives renaming the view, but the name shown in Shared with me is captured at share time — re-share, or hit Manage and save, to refresh it.

Limits & good to know

  • The read-only preview applies the view's state, priority, assignee and label filters client-side. Very complex or unusual saved filters may not be reproduced exactly in the preview — the editable view page always is authoritative.
  • The preview is a list. It doesn't reproduce the view's board, calendar, spreadsheet or Gantt layout.
  • Deleting a view doesn't tidy up its share rows — they simply stop resolving to anything useful.
  • Sharing is per-view. There's no "share this whole project's views" action.