# Fibery Product Report: January 2025

**URL:** <https://community.fibery.io/t/fibery-product-report-january-2025/8216>\
**Category:** News & Announcements\
**Created:** [February 5, 2025, 7:24am UTC](https://community.fibery.io/t/fibery-product-report-january-2025/8216 "2025-02-05T07:24:31Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![Illusory](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/illusory/32/10403_2.png) [@Illusory](https://community.fibery.io/u/Illusory)\
**Post date:** [February 6, 2025, 1:35pm UTC](https://community.fibery.io/t/fibery-product-report-january-2025/8216/10 "2025-02-06T13:35:15Z")

</div>

> [@Michael\_Ichter](#):
>
> I would assume it includes the set filters. So yes if a view has “Assigned to me” then an external user would see a blank view. I see the views as being integral to a view, although I’m not quite sure how this would perform with pinned filters (perhaps they function just as they would for an internal user?).

I think we’re describing two different things.

My notes were in reference to Guest features. My thoughts on Guest as outlined above are that Fibery is too complex for many users, so adding an official Guest account to a workspace is not always ideal.

> [@Chr1sG](#):
>
> We have public sharing for entities. What are the drawbacks you see with the current implementation?

- There is only one public link. Multiple unique links (like specified in the example above) allow you to share an entity with multiple guests. This allows for you to remove the link later without removing others and ideally, apply access templates (e.g. allow viewer on this specific public link to view child entities or lock a specific Entity View so that you are only showing specific fields).
- No option for password protection, so once you share a link, it is public, period.
- Making a space public means everything is available in the Space and can also be viewed when someone simply visits your “Public Fibery Workspace”.

> [@Chr1sG](#):
>
> So what does it mean to ‘share a view’?

Sharing a view with an external party, outside of my Fibery instance (to me), means sharing whatever is visible in that view, via a unique link and acts as a sort of container. Obviously, nothing is assigned to the user, so there is no way to add further user based checks to determine appropriate visibility permissions. The only thing that makes sense is to control, whether the viewer can view child elements or not, via the unique viewing container.

Sharing a view with an internal user (to me), means sharing whatever is visible in that view, via the Space, but ideally allows for more granular access control (like, can only see items within the view or database that are assigned to them). Technically, you can create a filter that shows only assigned, however, is not truly secure, because the user can still find, search or view entities not assigned to them… But, we already discussed this in [Feature Request: Share Space but restrict entity views](https://community.fibery.io/t/feature-request-share-space-but-restrict-entity-views/7755)

This is similar to postgres RLS policies where users can only read records related to themself or creating postgres table views.

I get it’s complex so I’m sure Fibery permissions and sharing will continue to transform over time.

---

_[View the full topic](https://community.fibery.io/t/fibery-product-report-january-2025/8216)._