> ## 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

<iframe width="600" height="310" src="https://d8ts56gtwtyh1.cloudfront.net/docs/warehouse/namespace.mp4" title="Namespaces" frameborder="0" allow="accelerometer; autoplay; muted" allowfullscreen autoplay muted />

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](/api-reference/namespaces/create-namespace).
* **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](/api-reference/namespaces/update-namespace).
* **List and search**: Quickly find namespaces you have access to. API parity: [List Namespaces](/api-reference/namespaces/list-namespaces).
* **Get details**: Inspect configured feature extractors and indexes. API parity: [Get Namespace](/api-reference/namespaces/get-namespace).
* **Delete**: Remove a namespace that you no longer need. This deletes the associated MVS namespace. API parity: [Delete Namespace](/api-reference/namespaces/delete-namespace).

### 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.

<Steps>
  <Step title="Create a namespace">
    Click New Namespace, add details, and optionally attach feature extractors and payload indexes.
  </Step>

  <Step title="Switch active namespace">
    Use the top bar switcher; this sets the `X-Namespace` applied by Studio.
  </Step>

  <Step title="Manage and clean up">
    Update indexes as needs evolve; delete unused namespaces to keep your workspace tidy.
  </Step>
</Steps>

<Callout type="warning">
  Deleting a namespace removes its backing MVS namespace for the org scope. Ensure backups as needed.
</Callout>