Workspaces

Learn about workspaces at Namespace, how ownership and isolation works and why a multi-tenant account can be helpful.

What is a workspace?

Your workspace - sometimes also referred to as a tenant - can enable collaboration on a set of resources.

When joining Namespace, a personal workspace gets created for you. You can immediately start running instances on that workspace. More on how to get started

You can also create multiple workspaces via the dashboard:

Workspace selector dropdown menu, cursor on New Workspace button
Workspace selector in the top-left of the Dashboard
New Workspace Dialog
New Workspace Dialog

Where do I find my workspace ID (tenant ID)?

In order for the Namespace team to be able to identify your workspace, it is helpful to share your unique workspace ID. You can find your Workspace ID on the Settings page.

Who can access my workspace?

From creation, each workspace is completely isolated and personal. Namespace ensures high security standards and comprehensive access control mechanisms to help you manage who can access your workspace and what actions they can perform.

An invitation from an owner or admin of the workspace is required to add additional users.

More information on Workspace access

How to handle multiple teams from the same company using Namespace?

Namespace can support different scenarios for multiple teams from the same company using Namespace. Depending on the use case, the following setup is recommended:

Multiple teams running in the same workspace

Each team has their own workspace connected as a multi-tenant account

Each team has their own independent workspace

Shared invoice

One invoice including accumulated usage.

YesYesNo
Shared usage budget

Teams share the included unit minutes, builds, etc.

YesYesNo
Shared dashboard

The dashboard is the same for all members: Usage details, instance details, etc.

YesNoNo
Shared concurrency limits

Teams use the same concurrency budget

Yes

Limits can be set globally and per-workspace

No
Sharing cache volumes possible

Share common caches between teams

YesNoNo
Can share a GitHub InstallationYesNoNo
Shared audit logs

Including workspace event audits

YesSame audit log export sink can be configuredNo