多维表格
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

47 lines
4.0 KiB

---
title: 'Workspace overview'
description: 'This article briefs the concept of workspaces in NocoDB.'
tags: ['Workspaces', 'Overview']
---
In NocoDB, workspaces play a pivotal role in facilitating collaborative and organized data management. A workspace serves as a container for one or more bases, allowing users to bring together interconnected tables, views, and various elements into a unified and coherent entity. Each workspace can house multiple bases, enabling users to categorize and structure their data in a way that suits their specific needs. Whether you're tracking projects, managing databases, or organizing information, NocoDB's workspaces provide the flexibility and organization required to make data-driven decisions and foster collaboration within your team. Additionally, workspaces allow for the assignment of specific access permissions to workspace members, ensuring that data security and privacy are maintained while enabling effective teamwork.
Some key points to note about workspaces are:
1. Each workspace contains its own set of bases, keeping your data separate and well-organized.
2. Workspaces have their own set of members and permissions, allowing you to control who can access and modify data within each workspace.
3. Workspaces offer unique settings and billing options, letting you customize configurations to suit specific needs.
4. Bases are tied exclusively to one workspace and can't be moved between workspaces, ensuring data integrity.
5. Members can be part of multiple workspaces. You can also fine-tune their roles within each workspace.
In summary, NocoDB workspaces streamline data management and member control, providing the flexibility and oversight necessary for various projects and teams.
To begin, you can [create a workspace](/workspaces/create-workspace) tailored to your project. Collaborate seamlessly by [inviting team members](/workspaces/workspace-collaboration) to the workspace. If roles need adjustment, simply [modify a team member's role](/workspaces/workspace-collaboration#modify-workspace-member-roles). When necessary, you can also [remove team members](/workspaces/workspace-collaboration#remove-workspace-members) from the workspace. For organizational purposes, renaming the workspace is straightforward with the [rename workspace](/workspaces/actions-on-workspace#rename-workspace) feature. Finally, if a workspace is no longer needed, you can easily [delete it](/workspaces/actions-on-workspace#delete-workspace).
:::info
The Open Source NocoDB includes a default workspace, and it does not allow the creation of additional workspaces.
:::
### Workspace context 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)
## Related articles
- [Create workspace](/workspaces/create-workspace)
- [Invite team members to workspace](/workspaces/workspace-collaboration)
- [Change team member role](/workspaces/workspace-collaboration#modify-workspace-member-roles)
- [Remove team member from workspace](/workspaces/workspace-collaboration#remove-workspace-members)
- [Rename workspace](/workspaces/actions-on-workspace#rename-workspace)
- [Delete workspace](/workspaces/actions-on-workspace#delete-workspace)
[//]: # (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)
[//]: # (- A base can be a part of only one workspace & cannot be moved between workspaces.)
[//]: # (- A member can be a member of multiple workspaces.)
[//]: # (- A member can have different access permissions in different workspaces.)