Skip to main content
A Database is a template for a kind of Entity: Bugs, Teams, Objectives, etc. It consists of metadata and Fields. 2024-01-12 12.43.42.gif
The API uses type for Database and app for Space. See Terminology.

Database and Field permissions

Imagine you’ve got a Database Task with a Field called Effort. Here’s how permissions apply depending on secured? parameter:
Task secured?
Effort secured?Everyone has access to all fieldsEveryone has access to Effort, but not to other secured? fields
Everyone has access to all fieldsEveryone has access to Task’s non-secured Fields like Id, but permissions are applied to Effort

Create Database

Every Database is a part of some Space. If the Database’s Space does not exist yet, create or install the Space. To create a fully functional Database, we’ll execute two commands:
  1. schema.type/create to create a Database with at least five mandatory primitive Fields:
  • fibery/id
  • fibery/public-id
  • fibery/creation-date
  • fibery/modification-date
  • ${space}/name
  1. fibery.app/install-mixins to be able to prioritize the Database’s Entities.
For auxiliary Databases, that are hidden from Workspace Map screen, ${space}/name Field and rank Mixin are optional. Just skip these parts when creating a Database. Auxiliary Databases might be useful as an Entity-based storage — that’s how our User’s favourite pages and recent items work, for example.
Response:

Command parameters

Rename Database

Response:

Command parameters

Delete Database

Response:

Command parameters

delete? parameter behavior

delete? parameter
falsetrue
Entities (or related Fields)don’t existDatabase is deletedDatabase is deleted
existError is thrownDatabase and Entities (or related Fields) are deleted
Related single-select enum Databases are not deleted even with delete-related-fields? enabled. Delete these Databases separately the same way you delete the original Database.