Does this apply to you? Look at your sidebar. If it has a Context entry, yes. If it still lists Performance Delivery, Project Financials and AI Return separately, your organization hasn't moved yet — read Sharing and duplicating Views instead.
A view is yours until you share it. Sharing passes along the whole thing — its teams, its tabs and its filters — so the person who opens it sees the same screen you do, not a blank one they have to rebuild.
The three access levels
From a view's menu, choose Share. Each person you add gets one of three levels:
Level | Can change filters | Can change dates | Can change tabs |
Viewer | no | no | no |
Viewer (with date range) | no | their own only | no |
Editor | yes | yes | yes |
Viewer is the honest default for a report somebody reads. They see the view exactly as you left it.
Viewer (with date range) is the one worth knowing about. The person can move the period — last 30 days, last quarter, whatever they need — and everything else stays as you set it. Their date range is theirs alone and changes nothing for you or anyone else. It's the right level for "here are our numbers, look at whichever months you like".
Editor gives away real control: an editor changes the view for everyone, because their filters are written into your copy. Use it for a view a team genuinely co-owns, not as a courtesy.
Two limits the screen enforces, both worth knowing before you go looking for the option:
Editor can only be granted to individual people — not to a team, and not to the whole organization.
Someone can't be an editor if they have no teams under them. A collaborator in that position would open the view and it would fail to load, so the level is disabled for them rather than offered and then broken.
Sharing with a public link
A view can also get a public link: anyone with it reads the view without signing in.
Treat it as publishing. The link works for whoever has it, so it suits a board pack or an update to a client — not an internal cut you'd rather keep internal.
A public view deliberately leaves some things out. The Rework Tracker never appears on one: its detail rows list tasks and status transitions, which public links haven't been reviewed to expose.
Linking to one tab
A view's URL carries the open tab, so you can point someone at the exact tab you're looking at rather than at the view's first one. Copy the address while the tab is open and the ?tab= part comes along.
It's a convenience, not a permission: the link only works for someone who can already open the view.
Duplicating instead of sharing
If what you want is your own cut of somebody else's view, Duplicate is usually the better move than asking for editor access. You get a copy with the same tabs, and you change its teams and filters without touching theirs.
One caveat when you duplicate a view that belongs to someone else: if its scope includes teams you don't manage, your copy won't be able to load its data and you'll need to adjust the scope. The screen says so before you do it.
Related articles
What is Context?
Building a view in Context
Filters in a Context view