# Managing Repositories

Repositories are used to separate and securely manage configurations, rule sets and data (data files, content or test data) for a given server. They can also be used in combination with user roles to separate responsibilities for rule writing, testing and deployment between different users.

By default, repositories are not enabled, and configurations, rule sets and data are stored directly under the root of the relevant section in the administration tree.

To create a new repository, simply click the Repositories link in the administration tree. The following will be presented:

<figure><img src="/files/37NgAh7PcanHl87ocDmj" alt=""><figcaption><p>Filter/create new repo</p></figcaption></figure>

Enter a name for the repository in the “Details” section *(such as “Test”)* and click on **Create**.

Note that you can also filter repositories from this location. Adding a filter allows you to limit the number of repositories shown in the administration tree. This speeds up the console and also makes development within a single repository much easier.

A new repository will now exist under configurations, rule sets and data, however you will not be able to see these folders until they contain some data.

To create a new configuration, rule set or data file in a repository, select that repository on the creation page as shown below:

<figure><img src="/files/ocBQ4mSdrq6PCn9y0iKj" alt=""><figcaption><p>New data file</p></figcaption></figure>

In this example, once you have uploaded a file to the Console Demo repository, it becomes visible in the administration tree as shown here:

<figure><img src="/files/VNkI9mVEAiLkCnMiex3J" alt=""><figcaption><p>Data Files folder</p></figcaption></figure>


---

# 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.tomorrowx.com/cap/product-reference/managing-repositories.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.