Public View Sharing

Ideas & Features
,
1

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.

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 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 and here 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. Unfortunately, we seem to be back where we were in May in assessing alternatives.

References

2

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.

2 Likes
3

This is a show-stopper missing feature for us as well - what is the status?

4

What are your cases?

5

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/. 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.

6

I think your case might be solved with Share Space to the Web feature.

Here is an early example how it will look like

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.

7

^This and “Allow Viewers to comment” looks promising! Thanks Michael.

8

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.

1 Like
9

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.