> 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/administration/teams/permissions-by-account-type.md). # Permissions by Account Type ### Overview Access levels for various resources are assigned to users via their team memberships. For information on access levels for Sites in DeviceLink, see [this section](/docs/devicelink/administration/permissions-by-account-type.md). An expanded description of privileges for each account type is outlined below:
ActionOwnerAdminWriteRead-only
Creating Repositories✓✓✕✕
Renaming Repositories✓✓✕✕
Deleting Repositories✓✕✕✕
Archiving Repositories✓✕✕✕
Editing settings for Repositories✓✓✕✕
Adding users to an Org✓✕✕✕
Deleting users from an Org✓✕✕✕
Changing user permissions✓✓✕✕
Creating and deleting Teams✓✕✕✕
Adding and removing users from Teams✓✓✕✕
Opening and closing PRs✓✓✓✕
Commenting on and approving PRs✓✓✓✓
Creating Branches✓✓✓✕
Setting Branch Protections✓✓✕✕
Creating Wikis✓✓✓✕
Editing Wikis✓✓✓✓
Opening and closing Issues✓✓✓✓
Commenting on Issues✓✓✓✓
Committing changes✓✓✓✕
Viewing code and files✓✓✓✓
Downloading files✓✓✓✓
Editing Topics✓✓✓✓
Generating Reports✓✓✓✓
Editing Project File Secrets✓✓✕✕
{% hint style="info" %} Owners have the highest permission level within your organization. When you create a new organization, you will automatically be added to the Owners team. {% endhint %} --- # 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/administration/teams/permissions-by-account-type.md?ask=&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.