# Create custom documentation repository

There are two main steps in setting up a new custom documentation repository:

* [Create a new custom documentation repository](#create-a-new-custom-documentation-repository)
* [Allowlist a custom documentation repository](#allowlist-a-custom-documentation-repository)

### Create a new custom documentation repository

Custom documentation can be created and published from the [Code Repositories](../../code-repositories/overview/index.md) application. First, you will need to create a repository using the **Documentation** template.

In the location where you would like to store your documentation repository, select **New** and choose **Code repository**. Then, use either the **Find and select repository type** search bar or the **Building something else?** wizard to initialize a new **Documentation** type code repository.

![Screenshot showing "What are you building?" screen with "Find and select repository type" and "Building something else?" highlighted.](../../../assets/7f4d78bdccecf1749804df18ba182c0ab97b6b0f0d77ed8ca1404561ef6b3881.webp)

You will be able to specify the name of the documentation repository as well as its location. Since documentation repositories are Compass resources, the location in which you save the repository will [determine user access to the documentation](../custom-docs-permissions/index.md).

### Allowlist a custom documentation repository

For a custom documentation repository to be publishable, the repository must be allowlisted so that the documentation service can discover and publish the docs. To allowlist a documentation repository for publication, go to **Control Panel > Documentation > Custom documentation** and toggle on the **Configure which code repositories can publish documentation** setting for your repository.

If you have just created a new documentation repository, the first commit will fail checks with a `PERMISSION_DENIED` error. This is because checks run automatically after creation and the repository must be allowlisted for checks to pass, but a repository cannot be allowlisted before it has been created. Once allowlisted, re-triggering the checks will publish the documentation successfully.