# 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:** 4

<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 5, 2025, 5:36pm UTC](https://community.fibery.io/t/fibery-product-report-january-2025/8216/4 "2025-02-05T17:36:00Z")

</div>

> [@mdubakov](#):
>
> - Automatically share entities with linked Groups (in progress)

> [@mdubakov](#):
>
> 👍 Database access adoption is already above expectations: more than 800 users in 129 workspaces have received some DB access—even without Groups support! Submitter access is the most popular one, as expected, but we have a problem _Submitter access is undiscoverable (can’t figure out how to grant create capability)_ so there’s definitely a room for improvement.

Definitely looking forward to trying out share with groups, though it probably won’t solve much for us. Currently, we are creating 2 spaces for each use case.

e.g.

- Projects Admin
- Projects

Projects Admin has no access to all at Space Level and only Database level access for each user as “Submitter”.

In Projects, users have Access. Then, we create views to display items from Projects Admin.

```auto
Projects Admin/ (no access)
├── Database_1/ (only Submitter)
| └── Fields/
| ├── Person (share access by person)
| └── Relation (share access by group through Person lookup field in Team space)
├── Database_2/ (only Submitter)
| └── Fields/
| ├── Person (share access by person)
| └── Relation (share access by group through Person lookup field in Team space)
└── Database_3/ (only Submitter) 
     └── Fields/
         ├── Person (share access by person)
         └── Relation (share access by group through Person lookup field in Team space)

Projects/ (full access)
├── View 1/
| └── Projects Admin/ (only submitter access)
| └── Database_1.table (now can see entities if shared via person, related group's person lookup or submitted)
├── View 2/
| └── Projects Admin/ (only submitter access)
| └── Database_2.table (now can see entities if shared via person, related group's person lookup or submitted)
└── View 3/
    └── Projects Admin/ (only submitter access)
        └── Database_3.table (now can see entities if shared via person, related group's person lookup or submitted)

```

The biggest issues with this setup:

- Requires two spaces to manage permissions effectively
- Tedious and complex
- Notification issues (had to create rules to notify in some cases since user does not have access to Admin space.

Just sharing our setup in case it is helpful for anyone else. There are more details here: [Feature Request: Share Space but restrict entity views](https://community.fibery.io/t/feature-request-share-space-but-restrict-entity-views/7755)

> [@mdubakov](#):
>
> - 😿 Guests are a flop now with barely any usage. Why? We don’t know: there’s not much negative feedback, or any feedback, for that matter. This question requires some user research.

I think Fibery is too complicated for many guests. The idea of allowing access to our workspace and then a user having to create an account and navigate the UI is a whole obstacle in and of itself.

One thought is to create unique links to Fibery entities, views or docs and can be shared. Password restriction would be great as well. Then if Fibery Sharer wants to remove the link, they can do so. [Pitch.com](http://Pitch.com) does an AMAZING job with this:

> **[Share an external link to your presentation | Pitch | Help Center](https://help.pitch.com/en/articles/3748926-share-an-external-link-to-your-presentation)**
>
> Share links, embed your deck into your website, and collect analytics from whom you share it with.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/0/056ec3dcbbc0f8b4f96e4ab1fa0106519a626665.jpeg)

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/5/5974891129613c711056a3bc7761da19a31ba5aa.jpeg)

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/3/34624ef699b5d6cb1a2632cef06efc171b4dee35.jpeg)

They even have an embed feature.

Lastly, if the entity has a Comment field, Fibery can prompt non-signed in users to create an account and comment. This would likely increase Fibery guest share usage, site backlinks, create new sign ups.

> [@mdubakov](#):
>
> We also released find duplicates, but it is not popular now, like 170 actions on duplicates and 8 merges happened in the last 2 weeks 😕.

One issue we found with this is since we use Formulas, many entity names are similar.

e.g.

- Ticket / Product 1 / Repair Needed
- Ticket / Product 2 / Repair Needed
- Ticket / Product 3 / Repair Needed

The idea is cool but not really helpful (for us), since these are not “true” duplicates. I think the AI tab where duplicates are found should have multiple AI workflows/tools.

Ideas:

- Find Duplicates or Similar with actions thereafter (like create a view with similar items, merge, convert or Move All to Final State and Update Relations)
- Summarize Ticket (summarizing rich text fields, comments, states and other related/referenced entities)
- Realtime Analytics (there are 27 entities that are similar)
- Custom Rule creation based on prompt and current entity’s details

> [@mdubakov](#):
>
> - ? Remove Hidden Spaces
> - Home Page in Fibery

I use Hidden Spaces as an Archive mostly.

Home Page would be great. I think there should be another View called “Dashboard” and we can add different cards that link to different views, charts/reports and maybe embeded views (e.g. Assigned Tasks). Similar to Airtable Interfaces.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/f/f383abf0be5d0e4b1e16fbd1983797be224082f8.jpeg)

> **[Interface Designer: Build Custom Visuals for Any Team - Airtable](https://www.airtable.com/platform/interface-designer)**
>
> Build visual and interactive interfaces that give each and every teammate the information they need, and a simple way to take action.

Though we can create a “make shift” dashboard in Fibery with embeds and rich text columns in a Document, it’s not intuitive or convenient. A dedicated view for creating template-style dashboards would be great. If not, I guess the Fibery team can come up with a dedicated home page that I imagine would have useful data and shortcuts.

> [@mdubakov](#):
>
> We’ll restart AI theme in February and explore new approaches to make AI Assistant great (for the first time). We did not settle with any exact plan so far. First, we will experiment with approaches for 2-4 weeks and then decide.

Looking forward to this.

---

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