> ## Documentation Index
> Fetch the complete documentation index at: https://archie.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Permissions

> See what Owners, Admins, Editors, and Viewers can do with branches, pull requests, publishing, and deploys, and how the Who can publish setting limits merges into protected branches.

What you can do with branches depends on your role in the project. The rules are the same for the Frontend and for Logic services. A role that can work on the Frontend's code can work on a service's code, and a role that cannot, cannot.

## Roles at a glance

| Action | Owner | Admin | Editor | Viewer |
| - | - | - | - | - |
| See branches, pull requests, diffs, and code | Yes | Yes | Yes | No |
| Create a branch, save changes to it, and switch branches | Yes | Yes | Yes | No |
| Use the chat to change the app | Yes | Yes | Yes | No |
| Open a pull request, comment, and request a review | Yes | Yes | Yes | No |
| Approve or request changes on a pull request you did not open | Yes | Yes | Yes | No |
| Create share links | Yes | Yes | Yes | No |
| Delete a branch you created | Yes | Yes | Yes | No |
| Delete a branch someone else created | Yes | Yes | No | No |
| Close a pull request you opened | Yes | Yes | Yes | No |
| Close a pull request someone else opened | Yes | Yes | No | No |
| Protect or unprotect a branch, and edit protection rules | Yes | Yes | No | No |
| Change the default branch | Yes | Yes | No | No |
| Change **Who can publish** and **Code review** | Yes | Yes | No | No |
| Merge into a protected branch | Yes | Yes | Depends on **Who can publish** | No |
| Publish the Frontend | Yes | Yes | Depends on **Who can publish** | No |
| Deploy a service | Yes | Yes | Yes | No |

A **Viewer** does not see branches or pull requests. They see "You don't have access to the code. Branches and pull requests are visible to project owners, admins and editors."

## Who can publish and merge into protected branches

Publishing the Frontend and merging into a protected branch are the actions that change what other people use. The project-wide setting **Who can publish** controls who can do them:

* **Only Owners and Admins.** This is the default. Editors cannot use **Publish site** or merge into protected branches.
* **Owners, Admins and Editors.** Editors can do both.

Find the setting in the **Settings** tab of **Manage branches** in the Frontend. In a service, it appears on the **Branches** page. Only Owners and Admins can change it. The confirmation explains the effect: with Owners and Admins only, Editors can no longer use **Publish site** or merge into protected branches of the app and its services.

The confirmation names only **Publish site** and merges into protected branches. It does not list deploying a service. Owners, Admins, and Editors can deploy a service.

If you do not have permission, you see a message such as "Merging into a protected branch requires publish permission." or "In this project only Owners and Admins publish and merge into protected branches." Ask an Owner or Admin to do it.

## Reviewing

* You cannot approve, or request changes on, your own pull request. You can still comment.
* Your approval counts while the branch has not changed. If new commits arrive, the approval is marked **Outdated: new commits since** and you review again.
* Requesting **Archie Reviewer** consumes credits. See [Archie Reviewer](https://archie.com/docs/frontend/branching/archie-reviewer.md).

## Next steps

* [Protected branches](https://archie.com/docs/frontend/branching/protected-branches.md)
* [Working with branches](https://archie.com/docs/frontend/branching/working-with-branches.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.