> ## Documentation Index
> Fetch the complete documentation index at: https://developers.fibery.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Terminology

> Core Fibery concepts and the UI/API naming differences.

| Term         | Definition                                                                                                                                                              |
| ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Space**    | A hub with data and Views relevant to a specific process. For example: Software Development, Candidates tracking, Vacations tracking, CRM, HR, etc.                     |
| **Database** | A collection of data records (Entities) that share the same characteristics (Fields).                                                                                   |
| **Entity**   | A Database record. For example, you may have an Interviews Database, and every record in this Database is an Entity.                                                    |
| **Field**    | A way to store information of a certain kind for all Database Entities, such as text, number, relation, etc. You can add as many Fields as you want for every Database. |
| **Schema**   | The metadata describing every Database and its Fields.                                                                                                                  |
| **View**     | A way to visualize and edit data records from one or several Databases in order to analyze them and make decisions.                                                     |

## API naming

To avoid confusion, please note that the terms in the API may differ from those in the Fibery User Guide and the interface.

<Callout icon="check" color="#fc551f">
  * **Type** → Database
  * **App** → Space
</Callout>

Initially, we used Type and App across all assets and interface. Based on user feedback, we decided to rename them as Database and Space.

However, the old terms still exist in the API code and are likely to remain unchanged.