---
seo:
  title: "Creating Issuers"
  description: "Create and delete Issuers and Repositories, and manage Issuer-level editor permissions, from the Admin page."
llm_context: "Admin guide to creating Issuers and Repositories in the UI, including the irreversible consequences of deletion and how Issuer-level editor rights are granted."
category: "guide"
related:
  - "/platform/concepts/doc_library"
  - "/platform/guides/specifications/start_cloning_spec"
  - "/platform/guides/user_access"
---

## Creating Issuers & Repositories

:::tip Background
If you are unsure what **Issuers** and **Repositories** are or how they relate, check out the [Documentation Library](/platform/concepts/doc_library.md) page for a full explanation.
:::

### Creating An Issuer

Since Issuers are a top-level, "set-and-forget" concept, the ability to create and delete Issuers is restricted to **Admin Users**, and can be found on the _Admin_ page under the _Issuers_ tab.

Creating an Issuer is straightforward: use the :color:ADD ISSUER:white:#4caf50: button. To delete an existing Issuer, click the three vertical dots next to it.

:::warning Proceed With Caution!
Deleting an Issuer will also delete all associated Repositories, Documents and Specifications and is pretty much irreversible. Please be careful!
:::

### Managing Issuer Editors

Once an Issuer has been created, it is possible to define the set of users who are allowed to edit documentation associated with it.

![Figure: Managing Issuer Editors](https://docs.fixspec.com/api/docs/image/issuer_editors.png)

Setting this to **_All Editors_** allows anybody with a documentation editor role to edit any documentation associated with the Issuer. Alternatively, you may explicitly list which users are permitted to edit.

:::tip New joiner can't edit a spec?
This is the first place to check. Editor role alone isn't enough — they also need to be on the allowed list for the relevant Issuer (unless it's set to **_All Editors_**).
:::

### Creating A Repository

Within the platform, a **Repository** is a grouping of API documents by **Issuer** and **Protocol**. It follows that each **Issuer** has a set of known Protocols associated with it, which are added and removed on the _Issuers_ tab within the _Admin_ page.

Repositories do a lot of work under the hood, but creating one is deceptively simple: just add the new Protocol to the Issuer, and the platform builds the Repository for you in the background.
