--- canonical: https://amplience.com/developers/docs/accounts/repositories/ title: Managing repositories description: Guide to managing your repositories within Dynamic Content, including how to create, edit and delete repositories. image: https://cdn.media.amplience.net/i/ampproduct/create-repo-1?w=1200&h=630 image_width: 1200 image_height: 630 audience: Administrator date_published: 2023-09-07 date_modified: 2024-10-08 --- # Managing repositories Repositories are part of your [account structure](https://amplience.com/developers/docs/concepts/account-structure/), and are used for organizing content within hubs. Your organization administrator can manage repositories within Dynamic Content, and grant users permission to use them. Users with permission to update repositories can create folders to organize their content further. See [Managing content folders](https://amplience.com/developers/docs/user-guides/produce-content/organize/). > **Note: users with the hub admin role** > Users assigned the hub admin role can manage repositories in the hubs for which they are a hub admin. ## Creating repositories To create a repository with Dynamic Content, click "Create new repository" from either the repository selector menu (1), the "Repositories and folders" contextual menu (2), or directly in the content navigation panel (3). ![Creating a repository](https://cdn.media.amplience.net/i/ampproduct/create-repo-1?w=1880&fmt=png 'Creating a repository') Use the "Create repository" dialog to enter a repository label and name, set the repository type, and optionally assign locales. ![The Create repository dialog](https://cdn.media.amplience.net/i/ampproduct/create-repo-3?w=1880&fmt=png 'The Create repository dialog') ### Repository label and name Enter a user-friendly label for the repository, to be displayed in the Dynamic Content navigation panel. Repository labels don't have to be unique and can contain special characters. A repository name is automatically created for you from the label, by excluding any special characters and appending a random number **to make the repository name unique**. For example, the label `&-\\"~±my repo!?`, will get a name like `myrepo1695650650942`. You can change this name before clicking the Create Repository button. A unique repository ID is also automatically created and you can view this in the [Repository settings window](https://amplience.com/developers/docs/user-guides/basics/dynamic-content/settings/#hiding-and-showing-repositories). > **Note: Developer note: Label and Name** > Special characters can be used in the label because they aren't passed to the Content Management API. > The repository name needs to be unique because it is passed to the API. ### Repository type This setting is used as an organizational guide for separating slot content from other content, and is used by the slot browser for filtering the repositories it displays. So, when users add slots to an edition using the slots browser, only slots repositories are listed. See [Adding slots to an edition](https://amplience.com/developers/docs/user-guides/schedule-content/plan/add-content-edition/#adding-a-slot-to-an-edition). Choose from: - Content - The repository can be used to contain all types of content. - Slot - The repository will only contain [slots](https://amplience.com/developers/docs/dev-tools/guides-tutorials/slots/). Slots are containers for content, and model the way that content is organized in your app or website. You can choose to [schedule](https://amplience.com/developers/docs/user-guides/schedule-content/overview) content using slots. ### Locales You can optionally assign [existing hub locales](https://amplience.com/developers/docs/user-guides/produce-content/localize/#locales) to a repository, to control the locales available to users when localizing content. See [Localizing content](https://amplience.com/developers/docs/user-guides/produce-content/localize/). To assign locales, select from the ones that have been set up for the hub. If no locales exist for the hub, then the "Locales" section isn't displayed on the dialog. > **Note: Repository usage limits** > The maximum number of repositories allowed per account is 500, and the maximum number of repositories per hub is 100. See [Usage limits](https://amplience.com/developers/docs/apis/limits/#dynamic-content-usage). ## Editing repositories To edit a repository's name and and assigned locales, select "Edit repository" from its menu in the Dynamic Content navigation pane. ![The Edit repository dialog](https://cdn.media.amplience.net/i/ampproduct/edit-repo-1?w=1880&fmt=png 'The Edit repository dialog') You can change the "user-friendly" name that identifies the repository in Dynamic Content. The repository ID remains unchanged. The repository type cannot be changed with the "Edit repository" dialog. If a user removes a locale from a hub, that locale isn't automatically removed from any repositories with which it's associated. In this case, a message tells you that locales have been removed and saving any changes to the repository will also remove these locales. ## Deleting repositories To delete a repository, from the content library, choose "Delete" from the repository's contextual menu. > **Note:** Repositories must be empty before they can be deleted. ![The Delete repository dialog](https://cdn.media.amplience.net/i/ampproduct/edit-repo-1?w=1880&fmt=png 'The Delete repository dialog') Use the "Delete repository" dialog to confirm the deletion. ## Related pages [Account structure](https://amplience.com/developers/docs/concepts/account-structure/) [Assigning repository roles](https://amplience.com/developers/docs/user-guides/manage-accounts/set-permissions/#assigning-repository-roles) [Adding content folders](https://amplience.com/developers/docs/user-guides/produce-content/organize/#adding-folders) [Usage limits for hubs and repositories](https://amplience.com/developers/docs/apis/limits/#dynamic-content-usage) [Managing repositories with the Dynamic Content Management API](https://amplience.com/developers/docs/apis/content-management-reference/content-repositories/)