> 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/devicelink/administration/permissions-by-account-type.md). # Permissions ### Overview Access to a Site is granted by specific permission tiers. For information on access levels for repositories in Git-Based Source Control, see [this section](/docs/git-based-source-control/administration/teams/permissions-by-account-type.md). The permission levels for Sites are summarized in the following table:
ActionOwnerAdminWriteRead-only
Creating Sites✓✕✕✕
Deleting Sites✓✕✕✕
Managing permissions✓✓✕✕
Editing Site settings✓✓✕✕
Creating, editing, & deleting Site assets✓✓✓✕
Running a backup✓✓✓✕
Creating a PR✓✓✓✕
Watching Projects✓✓✓✕
Viewing assets in a Site✓✓✓✓
Viewing backup results✓✓✓✕
{% hint style="info" %} Owners have the highest level of administrative authority within your Site. When you create a new Site, it 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.copia.io/docs/devicelink/administration/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 optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.