# Public View Sharing **URL:** \ **Category:** Ideas & Features\ **Tags:** views, sharing\ **Created:** [August 5, 2021, 4:55pm UTC](https://community.fibery.io/t/public-view-sharing/1885 "2021-08-05T16:55:52Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![rothnic](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/rothnic/32/1850_2.png) [@rothnic](https://community.fibery.io/u/rothnic)\ **Post date:** [August 5, 2021, 4:55pm UTC](https://community.fibery.io/t/public-view-sharing/1885/1 "2021-08-05T16:55:52Z")
### Summary One of the fundamental features that I believe will be expected by fibery is the ability to share a view of dynamic data with external people. A product management tool should yes help with insights, but also help with stakeholder communication. For us, external communication is greatly limited at the moment by the lack of View Sharing and [Form View](https://community.fibery.io/t/form-view-and-required-fields/680). ### Workarounds? Fibery docs and entity sharing can’t provide a workaround that I’m aware of at the moment that doesn’t require manual upkeep. There is no way to share a doc that has a dynamic list of items that are kept up to date. You could potentially share an entity view externally that mimics something like a roadmap, but would require model changes to visualized effectively. For example, you could have a relationship between Project and Epic for each status. Our company often has to partner with external agencies and communicate progress and would like to share a public roadmap, so the request for [[APPROVED] Read-only guest users](https://community.fibery.io/t/approved-read-only-guest-users/1527) doesn’t address the need. ### Expected Features: - **Sharing** : Any view can be shared to non-fibery users, similar to the entity and doc sharing - **Control Settings** : The view at the very least should lock the view configuration, but it would be nice to have a setting to allow a read-only adjustment of the view settings - **Images** (optional): have an option to share the view as an image, rather than an interactive webpage ### Background This is a feature request for what I assumed would be included in sharing work that seems to be seen as complete by fibery at this point. It has been made clear [here](https://community.fibery.io/t/changelog-june-3-share-documents-and-entities-performance-improvements-bug-fixes/1686/5) and [here](https://community.fibery.io/t/community-re-start/1881/8) it isn’t in the near-term plans. When we first started using fibery and assessed other options in May, I communicated sharing a public roadmap was a key blocker for us and we were assured sharing was imminent, along with [Read-only guest users](https://community.fibery.io/t/approved-read-only-guest-users/1527). Unfortunately, we seem to be back where we were in May in assessing alternatives. ### References - [Coda Public Release Doc (with table view embedded)](https://coda.io/d/Coda-Product-Updates_dz5Ie_WzBJp/Coda-Product-Updates_suT02?utm_campaign=embed&utm_medium=web&utm_source=z5Ie_WzBJp#_luNGN) - Something like this should be possible maybe with the [eventual blocks work](https://community.fibery.io/t/embed-custom-views-into-entity-view/936), but it sounds like it is pretty far off. - [Help Doc for Roadmunk (who we were trying to migrate from for roadmapping)](https://support.roadmunk.com/hc/en-us/articles/360044355734-Publish-Roadmaps-to-URL-PNG-or-HTML) ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [August 5, 2021, 6:47pm UTC](https://community.fibery.io/t/public-view-sharing/1885/2 "2021-08-05T18:47:02Z")
This feature is number 2 by the count of requests in our internal feedback list. And with blocks we should solve it anyway since it will be possible, for example, to include a Timeline into a Project and share the Project (otherwise current entity view sharing will just stop working). However, it is technically quite challenging. We’ll think about it in depth soon. ---
**Author:** ![Remo](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/remo/32/820_2.png) [@Remo](https://community.fibery.io/u/Remo)\ **Post date:** [March 30, 2022, 5:32am UTC](https://community.fibery.io/t/public-view-sharing/1885/3 "2022-03-30T05:32:46Z")
This is a show-stopper missing feature for us as well - what is the status? ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [March 30, 2022, 9:27am UTC](https://community.fibery.io/t/public-view-sharing/1885/4 "2022-03-30T09:27:24Z")
What are your cases? ---
**Author:** ![Remo](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/remo/32/820_2.png) [@Remo](https://community.fibery.io/u/Remo)\ **Post date:** [March 30, 2022, 2:01pm UTC](https://community.fibery.io/t/public-view-sharing/1885/5 "2022-03-30T14:01:31Z")
We thought of not only hosting our team wiki in fibery, but also the customer knowledge base/help pages. But we also found out we might would want some visitor metrics and a more “polished” look, like you have with [https://help.fibery.io/](https://help.fibery.io/). What product is this? Still, there are teams that use other wiki tools, and we would still want an easy way to share some of our wiki articles, without them having to create user accounts. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [March 30, 2022, 2:21pm UTC](https://community.fibery.io/t/public-view-sharing/1885/6 "2022-03-30T14:21:51Z")
I think your case might be solved with Share Space to the Web feature. > [@\[DONE\] Share Space to the web](https://community.fibery.io/t/in-dev-share-space-to-the-web/2492): > > Spaces can be shared to the web (set as Public), it means they will be accessible by anyone and indexed (or not) by Google. How to share space Admin or Creator can Share space to the web. This space becomes available to anyone . For example, If I have [xxx.fibery.io](http://xxx.fibery.io) Workspace and make User Guide space Public, then ANY anon visitor will see this Space in left menu when open [xxx.fibery.io](http://xxx.fibery.io). Direct link to the space will be [. | Fibery](http://xxx.fibery.io/@public/user_guide) Under the hood we use read-only users mechanism, but multiplex… Here is an early example how it will look like > **[Fibery process: Start](https://the.fibery.io/@public/Fibery_Process/Start-5885?app-sharing&enable-views-service)** This is our development process that we want to share to the world, and later move User Guide, Changelog and even community into Fibery. It would be great to hear your feedback. ---
**Author:** ![Remo](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/remo/32/820_2.png) [@Remo](https://community.fibery.io/u/Remo)\ **Post date:** [March 30, 2022, 2:40pm UTC](https://community.fibery.io/t/public-view-sharing/1885/7 "2022-03-30T14:40:46Z")
^This and “Allow Viewers to comment” looks promising! Thanks Michael. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [March 31, 2022, 8:23am UTC](https://community.fibery.io/t/public-view-sharing/1885/8 "2022-03-31T08:23:55Z")
In fact to Comment a Viewer must be registered in Fibery, we are going to add users registration mechanism in the future, but not sure when exactly. ---
**Author:** ![rothnic](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/rothnic/32/1850_2.png) [@rothnic](https://community.fibery.io/u/rothnic)\ **Post date:** [May 5, 2022, 2:25pm UTC](https://community.fibery.io/t/public-view-sharing/1885/9 "2022-05-05T14:25:03Z")
Yeah, I think the core need here has been addressed. It could be refined more, but we can now at least quickly share a space with our broader unauthenticated organization.