| Base | A base is a collection of one or more tables, often related and linked to one another. Alternative term `Project` |
| Base Owner | Member who had created base. There can be only one owner for a base & ownership is non-transferable |
| Base member | Base member with specific access permissions. Alternative term `Member``User` |
| Cell | A cell represents the space created where a column and a row intersect within a grid-like structure. It serves as the fundamental unit for storing data |
| Field | A field or column in a table is a container for values that share the same data type. Alternative term `Column` |
| Modal | In the context of user interfaces, a modal is a type of dialog or overlay that appears on top of the main content or interface and requires user interaction before the user can proceed. Modals are often used to gather user input, display alerts, or confirm actions. They typically "block" the rest of the interface until the user dismisses them, making them a focused and attention-grabbing element |
| Record | A record represents a row in a table. Alternative term `Row` |
| Table | A base is housed in tables, where data is logically arranged into rows and columns. A base can have multiple tables. Alternative term `Model` |
| Term | Description |
| Base | A base is a collection of one or more data sources that each contain one or more tables, often related and linked to one another. Alternative term: `Project` |
| Base owner | Member who created the base. There can be only one owner for a base and ownership is non-transferable. |
| Base member | Base member with specific access permissions. Alternative terms: `Member`, `User` |
| Cell | A cell represents the space created where a column and a row intersect within a grid-like structure. It serves as the fundamental unit for storing data. |
| Field | A field or column in a table is a container for values that share the same data type. Alternative term: `Column` |
| Modal | In the context of user interfaces, a modal is a type of dialog or overlay that appears on top of the main content or interface and requires user interaction before the user can proceed. Modals are often used to gather user input, display alerts, or confirm actions. They typically "block" the rest of the interface until the user dismisses them, making them a focused and attention-grabbing element. |
| Record | A record represents a row in a table. Alternative term: `Row` |
| Table | A table is a matrix where data is logically arranged into rows and columns. A base can have multiple tables. Alternative term: `Model` |
| View | A view defines how data within a table is presented and interacted with. Default view type is the grid view; other supported view types include form, gallery, and kanban views. |
| Webhook | A webhook is a mechanism that allows one system to send real-time data to another system or application. It enables automated notifications and data synchronization between different services or platforms by triggering predefined actions or events in response to specific events or updates in the source system. |
| Workspace Owner | Member who had created workspace. There can be only one owner for a workspace & ownership is non-transferable |
| Workspace member | Workspace member with specific access permissions. Alternative term `Member``User` |
| Workspace | A workspace is a collection of one or more bases. It offers collaborative access to bases by enabling you to bring together interconnected tables, views, and various elements into a unified and organized entity |
| Workspace | A workspace is a collection of one or more bases. It offers collaborative access to bases by enabling you to bring together interconnected tables, views, and various elements into a unified and organized entity. |
| Workspace owner | Member who had created the workspace. There can be only one owner for a workspace and ownership is non-transferable. |
| Workspace member | Workspace member with specific access permissions. Alternative terms: `Member`, `User` |
@ -59,8 +59,9 @@ For production use-cases, it is **recommended** to configure
| NC_S3_REGION | For S3 storage plugin - AWS S3 region | |
| NC_S3_ACCESS_KEY | For S3 storage plugin - AWS access key credential for accessing resource | |
| NC_S3_ACCESS_SECRET | For S3 storage plugin - AWS access secret credential for accessing resource | |
| NC_ADMIN_EMAIL | For updating/creating super admin with provided email and password | |
| NC_ATTACHMENT_FIELD_SIZE | For setting the attachment field size(in Bytes) | Defaults to 20MB |
| NC_MAX_ATTACHMENTS_ALLOWED | Maximum Number of attachments per cell | |
| NC_ADMIN_EMAIL | For updating/creating super admin with provided email and password | |
| NC_ADMIN_PASSWORD | For updating/creating super admin with provided email and password. Your password should have at least 8 letters with one uppercase, one number and one special letter(Allowed special chars $&+,:;=?@#\|'.^*()%!_-" ) | |
| NODE_OPTIONS | For passing Node.js [options](https://nodejs.org/api/cli.html#node_optionsoptions) to instance | |
| NC_MINIMAL_DBS | Create a new SQLite file for each project. All the db files are stored in `nc_minimal_dbs` folder in current working directory. (This option restricts project creation on external sources) | |
Pranav C
8 months ago
committed by
GitHub