Guide
A Database is a collection of data records (Entities) that share the same characteristics (Fields).
To add something into Fibery, you need to create a Database first. For example, if you want to add some projects with details like Name, Effort, Risk, etc., it is necessary to create a Project Database and add the relevant Fields.
For a full overview of Spaces , Databases , and Relations — check out our Getting started video. Otherwise, just keep reading.
https://youtu.be/S2ybuyCLpSo
How to add new Database?
To add a new Database into an existing Space, click + near Space name and select Database.
Name a Database
You can give your Database any name you like, but it is worth noting that when creating relations etc. Fibery will attempt to intelligently name the fields, based on the plural or singular version of the database name. This process assumes that a Database has is named using an English word, so you might get weird defaults if you name Databases with words from other languages.
Add Fields
To make the Database more useful, add additional Fields.
Expand Database in left sidebar, navigate to Fields and click + New Field button.
Delete Database
To delete a Database, click … next to the Database name, and proceed to Delete.
When you delete a Database, all data (Entities) and connections (Relations) will be deleted as well.
For example, if you delete Opportunity Database, all Opportunities will be deleted. So make sure you don’t have anything important in there.
Restore Database
If the unfortunate deletion does happen, you can restore Database from Trash or Activity Log.
Rename and set color for a Database
To rename or set color for a Database, right-click on a Database name or click … next to it.
Move Database
You can move Databases between Spaces. Just right-click on a Database name or click … next to it.
You need to have Architect or Admin permission levels for that action.
What are the consequences?
All Relations will be preserved.
Views will stay in the Space where they were created in. You can move them separately or recreate them in the new Space.
New permissions will be applied to Views.
For example, you moved Component Database from Product Space to Research Space.
To see Views where Components are chosen as a source, a User has to have at least Viewer access to Research Space.
Integration databases - those created by tools like Slack, HubSpot, or Linear - cannot be moved because they’re fundamentally tied to the space where the integration was originally configured. All integration logic (authentication, sync settings, mappings, and permissions) is stored and executed at the space level, so relocating the database would break the connection and risk data inconsistencies. If you need to reorganize your workspace, the only reliable workaround is to delete the integration from the old space and recreate it in the new one, but this requires a full reconfiguration and may lead to data loss or duplication, so it should be done carefully.
Database size limit
Fibery performance depends on the complexity of a Database.
For instance, if you have a large Database with only a few Fields, it will work fine. However, if you have 100 Fields, it may be slow.
In general, Fibery works well up to 300K Entities in a single Database.
Beyond that, we cannot guarantee optimal performance. If you have 500K records in some Fibery Database and experience performance problems, ping us in support chat or in Fibery Community.
FAQ
How can I determine if I need a new Database or a new Field?
Sometimes you may wonder when to create a Database and when a Field (for example, Single-Select Field) is enough. If you're accustomed to spreadsheets, you might be used to creating a new sheet for every new batch of data. However, Fibery separates data storage and data visualization using Views. So there is no need to add a new Database for every new batch of data.
We recommend creating a new Database when the new data has a different structure, meaning there are different Fields and Relations.
Here's a nice video that might help you think about what should be a database:
https://youtu.be/X5JfZk72ZfU
When to create a new Database and when to create a new Space?
Space represents a process, for example, Hiring. Consequently, Database represents a part of the process, for example, you can have All Candidates and New Employees Database in the Hiring Space.