Live network
Saved views and shared answers
11 views have been assembled, named and sent on. 73 opens between them, 9 views have a reader on the record other than the person who saved it. A link resolves to the same state for the recipient, and to a refusal when their role does not reach it.
Who a view reaches
Visibility is a property of the view. Sending somebody a link does not widen it.
Every saved view
Opening one re-runs the question against live rows rather than replaying a stored answer, so a view that was true last week can show you that it no longer is.
Actions
What is waiting on a person
Adoption spreads when a colleague sends something that worked, so what matters here is whether a link resolves to the same thing for the person who receives it.
views have been opened by somebody other than the person who saved it
10 of 11 views are visible beyond their owner, and 9 of those carry a reader on the record who is not the owner. This is a seeded record of sharing, not observed behavior.
views re-run a question when opened
These resolve to the same computation the sender ran, against the estate as it stands now. The number can legitimately differ from the one the sender saw, and the view says when it was saved so the difference can be read.
views point at a page rather than a question
These record a filter and a page. The page they open does not read the filter back, so the recipient sees the surface and the filter written out beside it, not the surface already filtered. That is a real limit and it is stated on the view.
saved views nobody has opened
A view saved and never opened is a view that was not worth sending. They stay on the board rather than being quietly removed.
view carries a role floor
A recipient below the floor sees the view exists, who saved it and why it is restricted - and does not see the figure. Hiding the existence of a view would make the restriction impossible to question.
Operations
What this desk is allowed to start
A surface that only reports is not operable. This is the work this page can set in motion, and the bound it runs into.
Trigger and bound
What a view stores. A name, a question or a page and filter, who saved it, what it covers, and who may open it. Never a copy of the answer. What opening one does. For a question, the query runs again now. For a page and filter, the filter is written out and the page is linked. How permission works. Private views open only for their owner; a role floor is checked against the role on the account at the moment of opening, not at the moment of saving. What is recorded. The number of opens and the accounts that opened it, shown on the view.
Live observability
What the record shows right now
The 3 visibilities below partition all 11 saved views. Visibility is who may open it at all; the role floor is a second, stricter test applied on top for 1 of them.
Current distribution
11 views
Is policy and strategy coming to fruition
Whether the written intent is holding here
Partly
Not holding on the record
The written intent is that a view can be named, saved and sent, and resolves to the same state for the recipient with permission respected. What is now true for the 8 question views: the recipient gets the same computation, re-run, with the query and row count shown, and the floor enforced. What is not true for the 3 page views: the target page does not accept a filter from a link, so the recipient sees the page and the filter described beside it rather than the page already filtered. 8 of the 11 work properly and 3 are a promise the rest of the product cannot yet keep.
What this page is, and what it is not
A saved view stores a question or a filter, never a copy of the answer. Opening one runs the query again, so a link shared on Monday can legitimately show a different number on Friday. That is the intent.
2 views are withheld from you and shown by name without their contents. Knowing that a colleague saved something is not the same as being able to open it.