This guide shows you how to create, view, and delete workspaces that belong to an organization. You’ll learn the difference between personal and organization workspaces and how access control works for shared workspaces.
Personal vs. organization workspaces
Section titled “Personal vs. organization workspaces”Workspaces can be owned by either a user or an organization:
- Personal workspaces are owned by a single user and accessible only to that user.
- Organization workspaces are owned by the organization and accessible to all organization members.
The workspace switcher in the web groups workspaces by their owning organization, making it easy to navigate between them.
Create a workspace
Section titled “Create a workspace”Only organization admins can create new workspaces under an organization.
On the organization page, find the Workspaces section and click New Workspace. Enter a name and confirm.
tenzir-platform org create-workspace --name="Production"If you omit --name, the platform generates a name based on the current
timestamp.
View organization workspaces
Section titled “View organization workspaces”The Workspaces section on the organization page lists all workspaces owned by the organization. Click a workspace to navigate to it.
Use tenzir-platform org info to see the number of workspaces in your
organization. Individual workspace management is available through the web.
Delete a workspace
Section titled “Delete a workspace”Only organization admins can delete organization-owned workspaces.
On the organization page, click the delete button next to the workspace you want to remove. Confirm the deletion in the dialog.
Access control
Section titled “Access control”When you create a workspace through the organization page, all organization members automatically have access to it. This is different from workspaces created through static configuration files, where admins must explicitly configure access rules.
You can further restrict access to organization workspaces using auth rules that require a specific organization role. For example, you can create a workspace that only organization admins can access.
For advanced access control configuration, including manually configured workspaces, see Configure workspaces.