I can’t recall seeing any comments on view sharing. Is that in progress or something that has been pushed out in the meantime? Sharing views and/or read-only users is the thing we are planning to leverage.
One thing I noticed for the current implementation is that we might mention an entity in an entity rich text field. So, if you share that view, the person can open that mentioned entity as you show in the demo. However, I noticed that when you expand that entity that was mentioned, that entity might have related entities or backlinks available within it. Right now even the name of those entities are redacted, which can limit the ability to understand it in some cases. I do think it would be useful to control that a bit more so that at the very least you could expose the name of those entities with or without providing access to them.
In other words, we share a document/entity as the first level. Anything mentioned can be seen and opened by the people viewing the shared doc/entity, which is the second level. So, once you are at the second level, i think a key decision is how you handle the 3rd level of references/relations. Currently you can’t view the name and can’t access them. I think it might be common that people are ok with sharing the name of the entities at that 3rd level, but don’t want to allow access to them. I get that the current approach is more conservative as a good starting point, but wanted to share the feedback.
Sharing and Navigation
One additional thing I have kind of expected as sharing has been more of an active topic, is that the more you utilize sharing, the more you need to try to provide navigation within the doc or entity instead of relying on the left nav, smart folders, etc. This is something we are going to just have to keep in mind.