@ -42,7 +42,7 @@ The layout below shows the main parts of NocoDB's user interface.
| Record | A record represents a row in a table. Alternative term `Row` |
| 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. |
| 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 |
| Workspace member | Workspace member with specific access permissions. Alternative term `Collaborator``User` |
| Workspace member | Workspace member with specific access permissions. Alternative term `Member``User` |
| Workspace Owner | Member who had created workspace. There can be only one owner for a workspace & ownership is non-transferable |
| Base member | Base member with specific access permissions. Alternative term `Collaborator``User` |
| Base member | Base member with specific access permissions. Alternative term `Member``User` |
| Base Owner | Member who had created base. There can be only one owner for a base & ownership is non-transferable |
[//]: # (Workspaces in NocoDB are collection of one or more [Bases](/bases/base-overview). You can create multiple workspaces to organize your bases and collaborators. Some of the key points to note about workspaces are:)
[//]: # (Workspaces in NocoDB are collection of one or more [Bases](/bases/base-overview). You can create multiple workspaces to organize your bases and members. Some of the key points to note about workspaces are:)
[//]: # (- Each workspace has its own set of bases.)
[//]: # (- Each workspace has its own set of members and access permissions.)
[//]: # (- Each workspace has its own set of settings & billing plans)
Next logical step after creating a workspace is to invite members to it. In this section, we will guide you through the process of inviting members to your workspace.
@ -11,9 +11,9 @@ A comprehensive guide regarding roles and permissions can be accessed [here](/ro
## Invite members
1. Navigate to the Workspace configuration page by selecting `Team & Settings` in the left sidebar.
2. Access the `Members` tab.
3. Input the email address of the intended collaborator for the invitation.
3. Input the email address of the intended member for the invitation.
4. Click on `Role` dropdown menu
5. Choose the appropriate access permission for the collaborator from the dropdown menu.
5. Choose the appropriate access permission for the member from the dropdown menu.
6. Conclude the process by selecting the `Add Member(s)` button.
In NocoDB, bases are the foundational elements that encompass tables, views, forms, reports, dashboards, and automations, 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,' and this ownership status is non-transferable, conferring exclusive authority over the base,
including the ability to delete it.
Bases also come with their unique set of collaborators 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 collaborators 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.
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.
[//]: # (Bases are the core building blocks of NocoDB. A base is a collection of tables, views, forms, reports, dashboards, and automations. You can create multiple bases to organize your data and collaborators. Some of the key points to note about bases are:)
[//]: # (Bases are the core building blocks of NocoDB. A base is a collection of tables, views, forms, reports, dashboards, and automations. You can create multiple bases to organize your data and members. Some of the key points to note about bases are:)
[//]: # (- A base can be a part of only one workspace & cannot be moved between workspaces.)
[//]: # (- Creator of a base is the `base owner`. There can be only one `base owner`(non-transferable).)
[//]: # (- Only base owner has the authority to delete a base.)
[//]: # (- Each base has its own set of collaborators and access permissions.)
[//]: # (- Collaborator permissions at base level carry higher precedence than workspace level permissions.)
[//]: # (- There is no limit to the number of collaborators you can invite to your base.)
[//]: # (- Each base has its own set of members and access permissions.)
[//]: # (- Member permissions at base level carry higher precedence than workspace level permissions.)
[//]: # (- There is no limit to the number of members you can invite to your base.)
[//]: # (- There is no limit to the number of tables you can create within a base.)
## Base Dashboard
@ -28,7 +32,7 @@ The Base Dashboard is organized into three key sections, each serving a distinct
1. **Table List**: This section provides a comprehensive list of all tables within the base, including those sourced from external data repositories. Users can conveniently access a specific table by clicking on its name. Tables originating from external sources are clearly highlighted in the list for easy identification.
2. **Base Collaborators**: In this section, users can view a roster of collaborators associated with the base, along with their respective permission levels. It's worth noting that collaborators who are part of the workspace automatically inherit access permissions at the base level. However, the base owner retains the ability to adjust these permissions, either increasing or decreasing them. Further details on collaboration management can be found in the dedicated [Base Collaborations](base-collaboration) section.
2. **Base Members**: In this section, users can view a roster of members associated with the base, along with their respective permission levels. It's worth noting that members who are part of the workspace automatically inherit access permissions at the base level. However, the base owner retains the ability to adjust these permissions, either increasing or decreasing them. Further details on collaboration management can be found in the dedicated [Base Collaborations](base-collaboration) section.
3. **Data Sources**: NocoDB offers the functionality to connect with external data sources and seamlessly integrate them as native tables. This section provides a listing of connected data sources, setting the stage for additional details on this feature, which will be covered in the forthcoming [Data Sources](/data-source/data-source-overview) section. This feature empowers users to work with external data as effortlessly as with in-house data tables, enhancing the versatility and scope of data management within the base.
@ -36,8 +40,8 @@ The Base Dashboard is organized into three key sections, each serving a distinct
[//]: # (Base dashboard has the following sections:)
[//]: # (### Table List)
[//]: # (List of tables in the base. Click on the table name to open the table. A base can consist of tables residing in external data sources as well. They are highlighted accordingly in the table list. )
[//]: # (### Base Collaborators)
[//]: # (List of collaborators in the base along with their current permission levels. Workspace collaborators inherit their access permissions to the base. Base owner can modify the permissions of collaborators at base level (either bump up or bump down). Additional details will be dealt with in section [Base Collaborations](/docs/040.bases/075.base-collaboration.md).)
[//]: # (### Base Members)
[//]: # (List of members in the base along with their current permission levels. Workspace members inherit their access permissions to the base. Base owner can modify the permissions of members at base level (either bump up or bump down). Additional details will be dealt with in section [Base Collaborations](/docs/040.bases/075.base-collaboration.md).)
[//]: # (### Data Sources)
[//]: # (NocoDB allows you to connect to external data sources & work with them as if they are native tables. List of connected data sources are listed here. Additional details will be dealt with in section [Data Sources](/docs/050.data-sources/010.data-sources-overview.md).)
A member added to a workspace will carry his assigned role specific permissions to all the base with in workspace. To override collaborator permissions to your base, please follow the clear steps outlined below:
A member added to a workspace will carry his assigned role specific permissions to all the base with in workspace. To override member permissions to your base, please follow the clear steps outlined below:
1. Go to the left sidebar and select `Base name` to access the `Base Dashboard.`
@ -24,9 +24,9 @@ We can apply permission to each View. By default, views are `Collaborative`. To
### Collaborative Views (default)
By default, views are set to "Collaborative," allowing collaborators with edit permissions or higher to modify view configurations. In this mode, all collaborators can read and write data to the view. This is the default mode for all views.
By default, views are set to "Collaborative," allowing members with edit permissions or higher to modify view configurations. In this mode, all members can read and write data to the view. This is the default mode for all views.
### Locked Views
With "Locked Views," no one can edit the view configurations until they are unlocked. In this mode, all collaborators are restricted to reading data from the view and are unable to make any changes to its settings or content. This mode is useful when you want to share a view with others but don't want them to make any changes to it.
With "Locked Views," no one can edit the view configurations until they are unlocked. In this mode, all members are restricted to reading data from the view and are unable to make any changes to its settings or content. This mode is useful when you want to share a view with others but don't want them to make any changes to it.
Naveen MR
1 year ago