clone/nocodb
1
0
Fork 0
mirror of https://github.com/nocodb/nocodb.git synced 2026-05-03 22:37:24 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs : workspace

Browse Source
This commit is contained in:
Naveen MR
2023-09-26 16:41:14 +05:30
parent ee46d8d5d9
commit 70c79d6b78
1 changed files with 9 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
packages/noco-docs/docs/030.workspaces/010.workspace-overview.md
View File

@@ -3,19 +3,19 @@ title: 'Workspace overview'
tags: [Workspace, List workspaces, Switch between workspaces]
---
In NocoDB, workspaces serve as collections of one or more bases, offering a structured approach to organizing your data and collaborators. Here are some key aspects to keep in mind regarding workspaces:
In NocoDB, workspaces serve as collections of one or more bases, offering a structured approach to organizing your bases and members. Here are some key aspects to keep in mind regarding workspaces:
1. **Workspace Isolation**: Each workspace maintains its distinct set of bases, ensuring separation and organization of your data.
2. **Collaborator Management**: Workspaces come with their own group of collaborators and access permissions. This allows you to precisely control who can interact with your data within each workspace.
2. **Member Management**: Workspaces come with their own group of members and access permissions. This allows you to precisely control who can interact with your data within each workspace.
3. **Customized Settings**: Each workspace offers individualized settings and billing plans, providing flexibility to tailor configurations to specific needs.
4. **Base Affiliation**: A base is exclusively associated with one workspace and cannot be transferred between workspaces, preserving data integrity.
5. **Collaborator Flexibility**: Collaborators can be members of multiple workspaces, enabling versatile collaboration across different projects. Additionally, collaborators can have varying access permissions within distinct workspaces, allowing you to fine-tune their roles as needed.
5. **Member Flexibility**: Members can be within multiple workspaces thus enabling versatile collaboration across different bases. Additionally, members can have varying access permissions within a workspace, allowing you to fine-tune their roles as needed.
In essence, workspaces in NocoDB facilitate effective data organization and collaboration management, ensuring that you have the flexibility and control required for various projects and teams.
In essence, workspaces in NocoDB facilitate effective data organization and members management, ensuring that you have the flexibility and control required for various projects and teams.
:::info
The self-hosted plan includes a default workspace, and it does not allow the creation of additional workspaces.
@@ -23,7 +23,8 @@ The self-hosted plan includes a default workspace, and it does not allow the cre
### Workspace context menu
The workspace context menu, conveniently located in the left sidebar, provides a comprehensive list of all the workspaces accessible to you. You can easily switch between different workspaces by simply clicking on the respective workspace name within this menu.
The workspace context menu, conveniently located in the left top of sidebar, provides a list of all the workspaces accessible to you.
You can easily switch between different workspaces by simply clicking on the respective workspace name within this menu.
![image](/img/v2/workspace/workspace-context-menu.png)
@@ -39,8 +40,8 @@ The workspace context menu, conveniently located in the left sidebar, provides a
[//]: # (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:)
[//]: # (- Each workspace has its own set of bases.)
[//]: # (- Each workspace has its own set of collaborators and access permissions.)
[//]: # (- Each workspace has its own set of members and access permissions.)
[//]: # (- Each workspace has its own set of settings & billing plans)
[//]: # (- A base can be a part of only one workspace & cannot be moved between workspaces.)
[//]: # (- A collaborator can be a member of multiple workspaces.)
[//]: # (- A collaborator can have different access permissions in different workspaces.)
[//]: # (- A member can be a member of multiple workspaces.)
[//]: # (- A member can have different access permissions in different workspaces.)