> For the complete documentation index, see [llms.txt](https://docs.copia.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.copia.io/docs/git-based-source-control/basic/create-a-new-repository.md).

# Configuration

### Overview

A repository (or "repo") is a folder structure stored in Git. The root of a repository is the base folder you want to store. A repository acts like a typical directory, but is technically different as it stores hidden context about the changes to the root folder and all of the subfolders under the root. Copia enables you to have limitless repositories, and each repository can be of any size.

Only account holders with Administrator or Owner level access can create repositories. When you create a repository, you are essentially creating a folder that you can add files and subfolders to. There are a few options when creating a repository:

* Creating a new repository (Copia Web App or Desktop App)
* Creating a new repository from an existing, local folder (Copia Desktop App)
* Creating a new repository from a template (Copia Web App)

{% hint style="info" %}
If you create a repository using the Copia Web App, you will need to clone that repository to your local machine. If you create a repository using the Copia Desktop App, you will typically publish that repository to the remote Copia server.
{% endhint %}

In the controls world, you may use one repository to represent a project for a client, a manufacturing site, or a zone within a manufacturing site. However, as you grow more comfortable with Git, it will make sense to define your own best practices that cater to your organizational needs.


---

# 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://docs.copia.io/docs/git-based-source-control/basic/create-a-new-repository.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.