Skip to main content
A workspace is an isolated data environment inside your organization. Each workspace has its own cloud, Catalog, sources, and pipelines, along with its own members, permissions, and settings. Every organization has at least one workspace. Teams use separate workspaces to isolate environments (for example, production and staging) or business units, each with its own data and access. Because each workspace runs on its own cloud, different workspaces in the same organization can run on different clouds.
A workspace belongs to an organization, which holds your team, plan, and shared settings. See Organizations.

​
What’s in a workspace

Members

Who can open the workspace and their workspace role.

Permissions

Data-level access to layers, folders, tables, and volumes.

Groups

Assign permissions to teams instead of individuals.

Tags

Organize and filter resources across the workspace.

Cloud

Run the workspace on Nekt Express, AWS, or GCP.

Secrets

Store credentials used by sources, notebooks, and destinations.
Each workspace also has its own alerts, webhooks, activity, and audit logs.

​
Workspace roles

Within a workspace, each person is either an Admin or a Member.
  • Admin — full control of the workspace, its settings, and its members.
  • Member — access to data is scoped by permissions.
Organization Owners and Admins are Admins on every workspace automatically; only organization Members receive a per-workspace role. See Members for the full role model.

​
Creating and switching workspaces

Use the workspace picker to move between the workspaces you can open in the current organization. Organization Owners and Admins can create new workspaces from the organization home, as long as the plan’s workspace allowance has room. Each new workspace is set up with its own cloud. See Cloud management.