> ## Documentation Index
> Fetch the complete documentation index at: https://docs.augmentcode.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Cosmos Spaces

> Spaces group the experts, environments, sessions, and settings for a team or workstream so everyone works from a shared, focused set of resources.

## About spaces

A **Space** is a grouping of the experts, environments, sessions, secrets, and integrations your team uses in Cosmos. Each Space is a dedicated area of Cosmos for one team or workstream, showing resources associated with it that you have permission to access.

Most organizations create one Space per team, such as Engineering, Data Science, Marketing, DevOps, IT, or Design. Each team can organize its experts and environments, configure secrets for its work, and set sensible defaults for new sessions, without the clutter of every other team's resources.

Switching Spaces changes your working context, but **Space membership is not an access grant**. Resource access controls determine who may use a resource; secret applicability determines where a secret is selected. Resources configured for all Spaces can be available across teams, subject to their access controls.

## What belongs to a Space

A Space can group most of the resources you configure in Cosmos:

| Resource | In a Space |
| - | - |
| **Experts** | The agents your team runs, pinned to the Space so launches stay in context. |
| **Environments** | Cloud environments and daemon pools available for the Space's sessions. |
| **Sessions** | Interactive and automation sessions started while the Space is selected. |
| **Secrets** | Values whose **Used in** coverage includes the Space; the session must also have use access. |
| **MCP servers** | Configurations associated with the Space, subject to their own access grants. |
| **Webhooks** | Inbound webhooks that trigger work within the Space. |
| **Projects** | Project groupings associated with the Space. |

A Space also shows how many experts and environments belong to it, so you can see at a glance how much each team has configured.

## Access and Secret Applicability

To make an MCP server and its referenced generic secret usable by a teammate, check both resources:

* **MCP access:** use **Manage access** to grant the intended recipients **Can use**, or **Everyone → Can use** for organization-wide access.
* **Secret access:** separately grant appropriate use access on the referenced secret. Sharing the MCP configuration is not a substitute for configuring the secret's permissions.
* **Secret applicability:** check **Used in**. **Scoped access** selects target Spaces; **Organization-wide** covers every current and future Space. A personal secret's **Every Space** coverage still applies only to its owner's sessions.

Access grants do not change secret applicability, and selecting a Space does not grant access. For environment-variable injection, auto-install must also be enabled. Validate changes in a **fresh session in the target Space as the intended recipient**, without printing credential values.

See [MCP sharing](/cosmos/config-mcp#sharing-an-mcp-server) and [Managing Secrets](/cosmos/config-secrets#access-and-applicability) for the complete flow.

## The Default space

Every organization has a **Default space**. Resources with no Space assignment generally appear there; explicit all-Spaces settings and secret applicability are handled separately. It always exists, and it can't be renamed or deleted.

Until you create a named Space, every expert, environment, and session lives in the Default space. You can start there and add named Spaces to organize your work as your team grows.

## When to use spaces

Use Spaces when more than one team or workstream shares a Cosmos organization and you want to:

* **Keep surfaces focused**: organize experts, environments, and sessions by team instead of browsing a shared, crowded list.
* **Separate configuration**: select where secrets and MCP servers apply, and grant resource access independently.
* **Set team defaults**: a Space can define a default expert and default environment, so new sessions started in that Space begin with the right setup.

A single team getting started can stay in the Default space. As you add more teams, create a Space for each one.

Read more about [managing spaces](/cosmos/spaces/managing) to switch, create, assign resources, and manage access.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.