Understand who has what access to Entity and why
There are numerous ways how someone might receive access to a Feature, Task, or Client:
- via Space sharing;
- via direct Entity sharing;
- via extended Entity sharing using custom access templates;
- via automatic sharing to assigned users.
All of these sources combine and merge, making it hard to tell the final access for a given person. Does everyone who should have access have it? Is there someone who shouldn’t have permissions but does?
To make the access audit easier, we’ve introduced a drill-down to individual users and capabilities. Expand a particular user to see where a certain capability has come from.
Automatically share Entities with those who create them
Previously, Created By has been excluded from the automatic sharing via user relations — now it joins the party.
Author access will become truly useful with the upcoming Database access but there is one use case that already makes sense: enable the automatic access for Entity creators to ensure they won’t lose access to their creations in case their access to the parent Space is downgraded or revoked.
Unlike other relations, access via Created By doesn’t support custom access templates or extending access. On the bright side, the author access can be revoked per Entity without clearing the Field value.
Import markdown and plain text files into a database
You can import a markdown file or a zipped markdown file structure directly into an existing or new Fibery database instead of importing them into a document. Databases over documents have many advantages, so we encourage our users to use this method.
Paste markdown into Fibery’s editor
In addition to a full-scale import of markdown files, we now also support simple copy-paste of markdown from another tool.
Paste a markdown doc into Fibery’s editor — and it will automatically be formatted. If you don’t want the automatic formatting, paste using the Cmd+Shift+V keyboard shortcut or use the code block.
Hide empty Fields from Entity View
The Hide when empty Field setting is now available on the Entity View. Selectively hide Fields in Compact sections when their value is empty to streamline the UI.
As usual, this option is available under the Manage Fields & Layout menu and works for both 1-column and 2-column layouts. When some Fields are hidden, a collapsible section appears so you can access those Fields.
One-liner improvements
- Automations: we’ve replaced GPT 3.5 with GPT-4o-mini as the default model.
- Integrations: when editing integration settings, if you click away from the window, a popup will appear, asking if you want to discard changes or continue editing. This prevents accidental loss of unsaved settings.
- Integrations: we’ve added
Edit Fields to the Syncmenu item to the DB’s context menu to quickly access the integration Field mapping. With this change, you will save at least four unnecessary clicks.
Fixed Bugs
- Whiteboard: child entity doesn’t get linked to the parent if you draw relation line from parent and add child via search
- Don’t show
No valueplaceholder in edit mode for numbers - Mentions: setup units button is available for users who don’t have permissions to edit it
- Self-Relations
Unlink Alldoesn’t unlink all and Relations popup doesn’t show every relation
We have very detailed wikis per entity which explains how fields are working, when to use what etc.
