@ -43,7 +43,7 @@ Your new workspace is now ready, and you can start building your base within it.
### Build a Base
### Build a Base
Building a base in NocoDB is where you define the structure of your database, create tables to store your data, add fields to those tables, and establish relationships between tables using Links. This relational approach helps you organize and manage your data effectively, making it easier to work with complex datasets and build powerful applications. Add a [new Base](/bases/create-base). Alternatively, you can also [import existing base from Airtable](/bases/import-base-from-airtable) as a NocoDB project in minutes.
Building a base in NocoDB is where you define the structure of your database, create tables to store your data, add fields to those tables, and establish relationships between tables using Links. This relational approach helps you organize and manage your data effectively, making it easier to work with complex datasets and build powerful applications. Add a [new Base](/bases/create-base). Alternatively, you can also [import existing base from Airtable](/bases/import-base-from-airtable) as a NocoDB base in minutes.
@ -24,8 +24,8 @@ In the following section, lets look at the process of creating your NocoDB works
When you start a new workspace, you automatically become the owner.
When you start a new workspace, you automatically become the owner.
Once your workspace is set up, you can [create tables](/tables/create-table) and [invite others](/workspaces/workspace-collaboration) to join and work together.
Once your workspace is set up, you can [create tables](/tables/create-table) and [invite others](/workspaces/workspace-collaboration) to join and work together.
You can invite as many people as you want, and you can create as many tables as you need in your workspace.
You can invite as many people as you want, and you can create as many tables as you need in your workspace. Workspace ownership is transferable, but a workspace must always have at least one owner.
But remember, there can only be one owner, and only the owner can delete the workspace.
:::info
:::info
The Open Source NocoDB includes a default workspace, and it does not allow the creation of additional workspaces.
The Open Source NocoDB includes a default workspace, and it does not allow the creation of additional workspaces.
In NocoDB, bases are the foundational elements that encompass tables, views, forms, and webhooks, providing a structured framework for data organization and collaborative work. It's essential to understand that each base is inherently tied to a specific workspace and cannot be transferred between different workspaces. The creator of a base is designated as the 'base owner,' and this ownership status is non-transferable, conferring exclusive authority over the base, including the ability to delete it.
In NocoDB, bases are the foundational elements that encompass tables, views, forms, and webhooks, providing a structured framework for data organization and collaborative work. It's essential to understand that each base is inherently tied to a specific workspace and cannot be transferred between different workspaces. The creator of a base is designated as the 'base owner'. A base can have multiple owners, each with the authority to manage the base settings and access permissions. At least one owner is required for each base for it to remain operational.
Bases also come with their unique set of members and access permissions, which take precedence over any permissions set at the workspace level. This fine-grained control allows for tailored collaboration and data management within each base. Importantly, there are no restrictions on the number of members you can invite to a base, fostering open teamwork. Similarly, you have the freedom to create as many tables as needed within a single base,
Bases also come with their unique set of members and access permissions, which take precedence over any permissions set at the workspace level. This fine-grained control allows for tailored collaboration and data management within each base. Importantly, there are no restrictions on the number of members you can invite to a base, fostering open teamwork. Similarly, you have the freedom to create as many tables as needed within a single base,
offering the scalability required to accommodate diverse datasets and projects.
offering the scalability required to accommodate diverse datasets and projects.
1. Navigate to the top right corner of the top navigation bar and click on the `Share` button.
1. Navigate to the top right corner of the top navigation bar and click on the `Share` button.
2. In the `Shared base` section, toggle the switch to `Enable public access` in order to activate the shared base feature.
2. In the `Shared base` section, toggle the switch to `Enable public access` in order to activate the shared base feature.
3. The generated link for the shared base will be displayed above and can be utilized to share this project with others. To copy the URL, simply click on the `Copy Link` option.
3. The generated link for the shared base will be displayed above and can be utilized to share this base with others. To copy the URL, simply click on the `Copy Link` option.
In NocoDB, we have roles that determine what people can do in a Workspace or Base.
In NocoDB, we have roles that determine what people can do in a Workspace or Base.
You can give a member one of these roles:
You can give a member one of these roles:
* Owner
* Creator
* Creator
* Editor
* Editor
* Commenter
* Commenter
* Viewer
* Viewer
* No Access
:::info
:::info
If a role is assigned to a member at the base level, it takes precedence over a role assigned at the workspace level.
If a role is assigned to a member at the base level, it takes precedence over a role assigned at the workspace level.
@ -26,19 +28,18 @@ in workspace or base management.
## Roles
## Roles
Roles serve as the basis for user privileges in NocoDB. They are associated with members at two levels:
Roles serve as the basis for user privileges in NocoDB. They are associated with members at two levels:
Workspace and Base. When a member is invited to a Workspace with a specific role, like an "Editor," they
Workspace and Base. When a member is invited to a Workspace with a specific role, like an "Editor," they
automatically have that role in all Bases within that Workspace. However, project owners or creators can customize
automatically have that role in all Bases within that Workspace. However, base owners or creators can customize
permissions at the project level to align with specific needs. This dual-level role assignment system
permissions at the base level to align with specific needs. This dual-level role assignment system
ensures adaptable user permissions and access management in NocoDB.
ensures adaptable user permissions and access management in NocoDB.
**Owner**: When a member creates a new Workspace or Base, they automatically become the Workspace or Base "Owner."
**Owner**: When a member creates a new Workspace or Base, they automatically become the Workspace or Base "Owner."
This role grants exclusive privileges, including the authority to delete the Workspace or Base.
This role grants exclusive privileges, including the authority to delete the Workspace or Base.
The "Owner" role's privileges are non-transferable, ensuring ownership and control integrity.
**Creator**: The "Creator" role shares all privileges with an "Owner," except for deleting the workspace or base.
**Creator**: The "Creator" role shares all privileges with an "Owner," except for deleting the workspace or base.
"Creators" have full administrative rights, except for deletion authority, which remains exclusive to the "Owner."
"Creators" have full administrative rights, except for deletion authority, which remains exclusive to the "Owner."
This ensures balanced workspace or base management.
This ensures balanced workspace or base management.
**Editor**: An "Editor" can create and edit records but cannot modify the project schema,
**Editor**: An "Editor" can create and edit records but cannot modify the base schema,
like adding tables or fields. They strike a balance between data input and schema management.
like adding tables or fields. They strike a balance between data input and schema management.
**Commenter**: The "Commenter" role cannot add or edit records but can provide comments on existing records
**Commenter**: The "Commenter" role cannot add or edit records but can provide comments on existing records
@ -47,8 +48,7 @@ like adding tables or fields. They strike a balance between data input and schem
**Viewer**: "Viewers" can only access records and associated comments, without the ability to contribute
**Viewer**: "Viewers" can only access records and associated comments, without the ability to contribute
or make changes, ensuring controlled access for informational purposes.
or make changes, ensuring controlled access for informational purposes.
**No Access**: This role, applied exclusively at the base level, revokes project access for the designated user,
**No Access**: This role, applied at the base level, revokes base access for the designated user. When applied at the workspace level, it gives the user no default access to any base within the workspace.
1. Navigate to the top right corner of the top navigation bar and click on the `Share` button.
1. Navigate to the top right corner of the top navigation bar and click on the `Share` button.
2. In the `Shared base` section, toggle the switch to `Enable public access` in order to activate the shared base feature.
2. In the `Shared base` section, toggle the switch to `Enable public access` in order to activate the shared base feature.
3. The generated link for the shared base will be displayed above and can be utilized to share this project with others. To copy the URL, simply click on the `Copy Link` option.
3. The generated link for the shared base will be displayed above and can be utilized to share this base with others. To copy the URL, simply click on the `Copy Link` option.
## Copy base
## Copy base
The `Copy base` feature allows users to create a copy of the base (import base) into their own Workspace. This feature is also useful for users who wish to utilize a base as a template for future projects. To copy a base, follow the steps below:
The `Copy base` feature allows users to create a copy of the base (import base) into their own Workspace. This feature is also useful for users who wish to utilize a base as a template for future bases. To copy a base, follow the steps below:
1. Access shared base URL that you wish to copy.
1. Access shared base URL that you wish to copy.
2. Click on the `Copy base` button located in the top right corner of the toolbar.
2. Click on the `Copy base` button located in the top right corner of the toolbar.
Open source NocoDB includes a default workspace, and it does not allow the creation of additional workspaces. And hence, the user management on Open source is different from Cloud hosted solutions. This article details the specifics of User management on Open source.
Open source NocoDB includes a default workspace, and it does not allow the creation of additional workspaces. And hence, the user management on Open source is different from Cloud hosted solutions. This article details the specifics of User management on Open source.
## User Management
## User Management
Organisation is an workspace equivalent concept in Open-source NocoDB. An organisation can have multiple bases. Permissions within NocoDB are divided into two levels: `Organisation level` and `Base level`.
Organisation is a workspace equivalent concept in Open-source NocoDB. An organisation can have multiple bases. Permissions within NocoDB are divided into two levels: `Organisation level` and `Base level`.
### Organisation Level Permissions:
### Organisation Level Permissions:
- `Org Level Creator`: Allows users to create new bases and access invited bases.
- `Org Level Creator`: Allows users to create new bases and access invited bases.
@ -22,12 +22,12 @@ Organisation is an workspace equivalent concept in Open-source NocoDB. An organi
### Base Level Permissions:
### Base Level Permissions:
The permissions at base level in Open source NocoDB remain same as cloud solutions. The base level permissions are summarized below:
The permissions at base level in Open source NocoDB remain same as cloud solutions. The base level permissions are summarized below:
- `Owner`: The user who created the project. A project can have only one owner. The owner persists until the project exists and the role is non-transferable. The owner has access to carry out any operations within the project, including deleting it.
- `Owner`: The user who created the base. A base can have multiple owners, and the owner has access to carry out any operations within the base, including deleting it.
- `Creator`: Has access to carry out any operations within the project except deleting the project and removing the "Owner."
- `Creator`: Can perform any operations within the base, except for deleting the base and removing the "Owner."
- `Editor`: Can modify data but cannot modify the schema (add/remove fields, tables, users, and such).
- `Editor`: Can modify data but cannot modify the schema (add/remove fields, tables, users, and such).
- `Commenter`: Can neither modify data nor schema, can only see data and can mark record-level comments.
- `Commenter`: Can neither modify data nor schema, can only see data and can mark record-level comments.
- `Viewer`: Can only see data.
- `Viewer`: Can only see data.
Please note that the above-mentioned Base Level Permissions are additional to the already defined Organisation Level Permissions.
Please note that the above-mentioned Base Level Permissions are additional to the already defined Organisation Level Permissions.
In addition to the previously defined permissions, NocoDB also includes the role of `Super Admin`. The `Super Admin` is the first user to sign up on this NocoDB installation. An organisation can have only one `Super Admin` and this role is non-transferable. The `Super Admin` will have the equivalent permissions of an "Org Level Creator" and "Owner" for all projects within the organisation.
In addition to the previously defined permissions, NocoDB also includes the role of `Super Admin`. The `Super Admin` is the first user to sign up on this NocoDB installation. An organisation can have only one `Super Admin` and this role is non-transferable. The `Super Admin` will have the equivalent permissions of an "Org Level Creator" and "Owner" for all bases within the organisation.
Raju Udava
3 months ago
committed by
GitHub
