Teaser:
5 Likes
I’m often the one making them on behalf of other people, so they’re not usually for me.
Like, there might be a view that 2 people want and would only need for a single meeting each week. I create it for them, but now it lives in the left sidebar for every user to see until the end of time, even though its only relevant for 2 users (out of a total of 15 users) for 1 hour (out of a total 40-60 work hours in a week).
I’d prefer to just create the view and have the users it’s relevant either search to find it every week, or tell them to star it so it shows up in their “favorite section” when they need access to it.
If when created, all views defaulted to only being viewable by their creator and there was a setting that could be changed to make them viewable/visible to all, that would work too. That’s essentially how Google Drive, OneDrive, etc, all work which is mentally what I compare this to.
We’ve thoughtfully customized the left sidebar to be our primary, global navigation in fibery and not an exhaustive list of everything everywhere, which is why it throws things off for us when new things like views get add to the sidebar automatically. We rely heavily on relation views within an entity to navigate deeper to other where needed.
Is that because these users have difficulty using Fibery, or because they lack permissions, or something else?
1 Like
I’m sad to hear this. I’m a big believer that the most impactful case for AI integration in work management platforms is not the chat/prompt workflow, but rather in a model steeped in the context of one’s databases. Bill French writes and shares a few resources following this thought.
Previous announcements about this functionality is actually what made me bite the bullet and move my business out of Coda & ClickUp.
I hope there will be a marketable reason to change course here.
2 Likes
Some people (Sales and Account Management teams) primary work in Hubspot and they only go into Fibery when they have to, so it’s a combination of the “difficulty using a complex system” and “no desire/bandwidth to learn another system” situation.
Another reason is that we try to track and document all the time and effort we put into customizing/improving our “operating system” in Fibery so we can apply for various government grants for innovation and experimentation in our industry. Internally, I own this initiative so everyone’s feedback and feature requests funnel through me to ensure they get documented in the right way. But since I’m also our overall Fibery champion/expert and can often implement a request more quickly and efficiently than others, I do it for them.
In this specific case, I’m just trying balance the needs of the few (important, but highly specific and not often used views) against the needs of the many (simple & clean left sidebar) and the limitations of fibery (no ability to hide database views in left sidebar).
1 Like
I agree here. Being able to prompt AI about workspace data is a huge selling point and certainly needs priority.
3 Likes
Note that this would introduce security issues, as the AI is probably not going to be able to follow/enforce all access rules.
But there could be RAG applications where respecting access rules is not that important, and it could be a boon in those cases 
Or if RAG access is restricted to admins (who already have access to the data), that’s one use case.
There’s also the possibility of developing an external tool to suck in all your Fibery data, and then do RAG on it… probably not too difficult as long as the total amount of data is manageable.
2 Likes
I’m sure it’s complex but I don’t think it’s impossible.
Couple thoughts…
A. Reject requests if AI has to query from databases that the user does not have access to.
B. Workspace data branches are indexed for the user based on their permissions.
3 Likes
After further thought, I think this is pretty insignificant if we have the ability to use AI to assist with report generation. I would honestly not care to use workspace QA at all if AI assisted report generation was possible.
I dont get this, what different between User field and People field in this case, All user have to register right ?
Also how to manage these, when I’ve already have People database, If I seperate those to 2 database, I cant manage all interactions in 1 People db
This is not related to permissions, it is just a unification of Assignment field we had before. In the past only one Assignment field could be added to a database, now there are no limitations
2 Likes
My needs are similar to @interr0bangr. We have several people who don’t have all the technical acumen for setting up their own workflow in Fibery. While I’m happy to sit down with people to help them, some live in remote places and I only get the chance to see them a couple times a year.
I like this a lot. Are there any plans to add this functionality to the right click context menu of entities not in the left sidebar?
If I am looking at a view and want to see two entities side by side. I either have to:
- open a search panel
- open one entity, then expand the second, then collapse the second
1 Like
Released
1 Like
Thank you!
Any comments you could provide on the “panel management” requests @ccollins and I had?
1 Like
In this case we should add “Open in left panel” and “Open in right panel” actions to make it work
3 Likes