# Repo Settings ### Overview You can manage the settings for a specific repository by navigating to that repository and then clicking on the *Settings* tab. ### Repository To manage your general settings for your repository, click into the *Repository* tab.
#### Managing Basic Settings The *Basic Settings* section is home to general repository settings. Most often, you will navigate here to change the name and description of your repository. You can also set the repository as a template by checking the *Template* option. To learn more about how and when to use templates, check out the [Creating Templates ](/docs/git-based-source-control/basic/create-a-new-repository/creating-templates.md)section.
#### Managing Advanced Settings Additional settings and features live in the *Advanced Settings* section. By default, the *Wiki* option will be active. Unchecking this option will disable the Wiki feature for your repository and remove it from the nav bar. {% hint style="info" %} Copia recommends that you enable Wikis for all repositories as they are powerful tools for asynchronous communication. {% endhint %} If you prefer to use an external Wiki, choose the *Use External Wiki* option and enter a valid URL into the field.
The *Issues* option will also be automatically checked. Turning this option off will disable the Issues feature for your repository and remove it from the nav bar. If you prefer to use an external issue tracker, choose the \_Use External Issue Tracke\_r option and enter a valid URL into the field.
#### Transferring, Deleting, and Archiving Repositories {% hint style="warning" %} You will need the proper [permission ](/docs/git-based-source-control/administration/teams/permissions-by-account-type.md)level to view or perform many of the following operations. {% endhint %} Within the *Danger Zone* section you can perform some high level and potentially risky operations: * **Transferring ownership** - This enables you to transfer the repository to another Organization within Copia. You would have to have Administrator or Owner access to this separate Organization. * **Deleting Wiki Data** - This allows you to delete the data from the repository's Wiki. Because deleting a Wiki is a permanent change, you would want to copy the Wiki over to another location before proceeding. * **Deleting the Repository** - This irreversibly removes the repository and its data from your Organization. * **Archiving the Repository** - This reversible feature prevents superfluous edits to a project that has reached completion. You would still have Read-Only access to the archived repository.
{% hint style="info" %} Archived repositories still appear on the repositories card on the *Dashboard*. Select the funnel symbol next to the search bar and check the *Archived* option to filter for archived repositories. {% endhint %} ### Collaborators The core of any collaborative flow starts with granting a user access to your repository. To manage the collaborators within your repository, click into the *Collaborators* tab.
#### Adding and Removing Collaborators Within the *Collaborators* section, enter the email address of each collaborator you wish to add. Press the *Add Collaborator* button to add them to the repository. ![](/files/GoT100CwWczP3IS2inux) If the invitee already has a Copia account, they will automatically be added to your repository. Otherwise, they will receive an invitation email to create a Copia account and then join your repository. The collaborator's account will be displayed once they're successfully added. You can remove the collaborator from the repository by clicking the red *Remove* button.
#### Managing Privileges for Collaborators Once a user has been added to a repository, the next step is to manage their access rights. There are three types of access rights in Copia: * **Read** - These users can read files but cannot modify them. * **Write** - These users can read and write files but cannot modify repository settings. * **Administrator** - These users can add and remove collaborators. They can also perform potentially destructive actions like deleting a repository and transferring ownership. To assign a privilege onto a collaborator, click the *Privilege Selector* and choose an option from the dropdown. Your selection will automatically be saved. ![](/files/c4b4T1MgyjN2q2SAcBKy) #### Managing Team-Level Access If you want to grant access to a group of individuals (ex., you might want to provide read access to a group of contractors), you can set a Team as a collaborator for a repository. In the *Organization Management* screen, you will need to assign Members to your Team as per the steps outlined in the [Teams](/docs/git-based-source-control/administration/teams.md) section. There, you will assign specific repositories to Teams you've created. If a Team has been given access to your repository, it will be listed in the *Teams* section. {% hint style="info" %} If you use the [Single-Role teams](/docs/git-based-source-control/administration/org-settings.md#single-role-teams) feature, the access level of the team will be displayed in this view alongside the team name. {% endhint %}
{% hint style="info" %} If you cannot remove a Team from the collaborators list, it is likely because that Team has been given universal access to all repositories. {% endhint %} You can add a new Team as a collaborator by entering the Team name in the *Search Team* field and clicking the *Add Team* button.
### Branches Branches allow each developer on your team to have a copy of the source code to work with. To manage your branching settings, click into the *Branches* tab.
#### Setting a Default Branch By default, new pull requests and code commits will use `main`. You can set a different default branch to better suit your specific workflow. To set a new default branch, select the *Branch Selector* within the *Default Branch* section and choose a new branch. Click the *Update Settings* button to save your changes.
#### Setting Branch Protections Branch protection includes rules and configurations an Owner or Administrator of a repository can set to control who can edit the specific branch. To learn more about how and when to set branch protections, review the [Branch Protections](/docs/git-based-source-control/advanced/branching/branch-protections.md) section. ### Webhooks Webhooks are automated messages sent from the Copia server when something happens in your repository. These messages are posted via HTTP to a specific URL of an App that is waiting to receive the message. To learn more about how to create webhooks and view the available integrations, see the [Integrations](/docs/git-based-source-control/integrations.md) section. --- # 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.copia.io/docs/git-based-source-control/administration/settings.md?ask= ``` 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.