# Organization and Namespaces

## Organization

An organization, or org for short, corresponds to a DBNL deployment.

### Organization Resources

Some resources, such as users, are defined at the organization level. Those resources are sometimes referred to as organization resources or org resources.

## Namespaces

A namespace is a unit of isolation within a DBNL organization.

### Namespace Resources

Most resources, including projects and their related resources, are defined at the namespace level. Resources defined within a namespace are only accessible within that namespace providing isolation between namespaces.

### Default Namespace

All organizations include a namespace named **default**. This namespace cannot be modified or deleted. 

{% hint style="info" %}
By default, users are assigned the namespace reader role in the default namespace.
{% endhint %}

### Switching Namespace

To switch namespace, use the namespace switcher in the navigation bar.

<figure><img src="https://content.gitbook.com/content/RJtpFEsLhAXLBZsTPqF2/blobs/SOyuVIfXUP0RhKiSfDhK/image.png" alt=""><figcaption></figcaption></figure>

### Creating a Namespace

To create a namespace, go to **☰ > Settings > Admin > Namespaces** and click the **+ Create Namespace** button.

{% hint style="info" %}
Creating a namespace requires having the org admin role.
{% endhint %}

### Adding a User to a Namespace

See [Users and Permissions](https://docs.dbnl.com/v0.25.x/using-distributional/access-controls/users-and-permissions).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.dbnl.com/v0.25.x/using-distributional/access-controls/organization-and-namespaces.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.