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.
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
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 does an AMAZING job with this:
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.
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
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.
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.
Looking forward to this.