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

# Namespaces

![Studio Namespaces page listing namespaces with document and object counts](https://mintcdn.com/mixpeek/Wd_dr3_jo8gqgFxV/assets/studio/namespaces.png?fit=max\&auto=format\&n=Wd_dr3_jo8gqgFxV\&q=85\&s=6a2ee282a02e6ea5ed691211ebdad5b3)

The Namespaces page — every namespace you can access, with its document and object counts.

[Namespaces](https://d8ts56gtwtyh1.cloudfront.net/docs/warehouse/namespace.mp4)

Namespaces are isolated warehouse environments, each with its own storage, collections, and retrieval pipelines.

### Manage namespaces in Studio

* **Create**: Click New Namespace, provide a name and optional description. You can attach feature extractors and payload indexes up-front. API parity: [Create Namespace](https://docs.mixpeek.com/docs/api-reference/namespaces/create-namespace.md).
* **Switch active namespace**: Use the top bar to scope every page. This sets the `X-Namespace` in API calls made by Studio.
* **Update**: Edit payload indexes or rename. API parity: [Update Namespace](https://docs.mixpeek.com/docs/api-reference/namespaces/update-namespace.md).
* **List and search**: Quickly find namespaces you have access to. API parity: [List Namespaces](https://docs.mixpeek.com/docs/api-reference/namespaces/list-namespaces.md).
* **Get details**: Inspect configured feature extractors and indexes. API parity: [Get Namespace](https://docs.mixpeek.com/docs/api-reference/namespaces/get-namespace.md).
* **Delete**: Remove a namespace that you no longer need. This deletes the associated MVS namespace. API parity: [Delete Namespace](https://docs.mixpeek.com/docs/api-reference/namespaces/delete-namespace.md).

### Tips

* Namespaces map 1 to 1 with [MVS](https://mixpeek.com/mvs) namespaces. Choose clear names per environment like `acme_dev`, `acme_prod`.
* Keep one or more feature extractors attached; Engine ensures the collection is bootstrapped on first ingestion.

**1. Create a namespace**

Click New Namespace, add details, and optionally attach feature extractors and payload indexes.

**2. Switch active namespace**

Use the top bar switcher; this sets the `X-Namespace` applied by Studio.

**3. Manage and clean up**

Update indexes as needs evolve; delete unused namespaces to keep your workspace tidy.

Deleting a namespace removes its backing vector store namespace for the org scope.

On an Enterprise plan the platform takes a snapshot first, including a copy of your
bucket objects, and keeps it for 30 days. You can restore from it into a new
namespace, or over the original. On every other plan the delete is not covered by
anything, so take your own copy before you delete.

A snapshot is a copy of the namespace's data, taken while writes continue. It
restores the documents, vectors and objects it captured. It does not reproduce a
single instant, so treat it as a backup rather than as a rewind. See
[Create Namespace Snapshot](https://docs.mixpeek.com/docs/api-reference/namespace-snapshots/create-namespace-snapshot.md)
and [Restore From Snapshot](https://docs.mixpeek.com/docs/api-reference/namespace-snapshots/restore-from-snapshot.md).


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