> For the complete documentation index, see [llms.txt](https://developer.mediarithmics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.mediarithmics.io/user-points/user-identifiers/networks-ids/user-based-network-ids.md).

# User-based Network IDs

### Managing compartments in the mediarithmics platform

**User-based Network IDs** refer to **Compartments** because each user network ID is assigned a compartment where its identifiers are stored.

#### **How to activate a compartment on a datamart**

Here are general steps to follow in order to activate a Compartment on a specific datamart:

* **If you have a single datamart**, the Compartment is automatically activated.
* **If you have multiple datamarts**, you must activate it on every datamart
  1. Head to **Navigator > Settings > Datamart > Compartments.**
  2. Select your Compartment.
  3. Click to the **More** button to open the menu.
  4. Choose **Edit linked datamarts.**
  5. Select the datamart where you want to activate the Compartment.

#### Activate IDs across your organisations:

For community-created user IDs, activate them across organizations by selecting Enable Compartment in the Shared User Account Compartments Enabled section.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.mediarithmics.io/user-points/user-identifiers/networks-ids/user-based-network-ids.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.