# Setting your project's permissions

As a project admin, you can update your project’s permissions manually or, with a [Team or Enterprise plan](https://www.sonarsource.com/plans-and-pricing/sonarcloud/) organization, reset the default permissions and apply a permission template defined by the organization administrator.

{% hint style="info" %}
If you are an organization admin, you can:

* Apply a permission template to several projects of your Enterprise plan organization at a time. See [Using Projects Management page](/sonarqube-cloud/administering-sonarcloud/managing-organization/manage-org-projects/projects-management-page.md) for more information.
* Recover administration access to an organization’s project. See [Recovering project admin access](/sonarqube-cloud/administering-sonarcloud/managing-organization/manage-org-projects/manage-project-permissions/recovering-admin-access.md) for more information.
  {% endhint %}

## Permissions related to a project <a href="#project-level-permissions" id="project-level-permissions"></a>

The following permissions are available for a project:

<table><thead><tr><th width="192">Permission Type</th><th>Description</th></tr></thead><tbody><tr><td><strong>Administer</strong></td><td><p>On private projects, the Browse project permission must also be granted. The project administrator can access project settings and perform administration functions, including the following permission-related functions:</p><ul><li>Management of the project’s user and group permissions.</li><li>Project's visibility (public, private).</li></ul></td></tr><tr><td><strong>Execute analysis</strong></td><td><p>Grants the ability to:</p><ul><li>Retrieve all settings required to run the analysis, including secured credentials like passwords</li><li>Push analysis results to SonarQube Cloud</li></ul><p><strong>Note</strong>: Users with the Execute Analysis permission at the organization-level are able to scan projects, even if they don’t have any explicit project permissions.</p></td></tr><tr><td><strong>Administer security hotspots</strong></td><td>Can change the status of a security hotspot. For private projects, the Browse project permission must also be granted.</td></tr><tr><td><strong>Administer issues</strong></td><td><p>Can perform the following actions:</p><ul><li>Accept an issue</li><li>Mark an issue as False positive</li></ul></td></tr><tr><td><strong>See source code</strong> (private projects)</td><td><p>Grants the ability to view the source code (via API and web view) provided the Browse project permission is also granted.</p><p><strong>Note</strong>: Anonymous and unauthorized users are prevented from easily downloading public projects’ source code via API and web views.</p></td></tr><tr><td><strong>Browse</strong><br>(private projects)</td><td>Can view a project.</td></tr></tbody></table>

## Updating the permissions of your project <a href="#updating-resetting-permissions" id="updating-resetting-permissions"></a>

To update the permissions of your project:

1. Retrieve your project. See [Retrieving projects](/sonarqube-cloud/managing-your-projects/retrieving-projects.md) for more details.
2. Go to **Administration** > **Permissions**. The **Permissions** page opens.
3. Filter the page by **Users** or **Groups**, or search for a specific user or group.
4. Select the check boxes to change the permissions.
5. Click **Apply Permission Template** to apply a predefined set of permissions to your project. See [Using permission templates](/sonarqube-cloud/administering-sonarcloud/managing-organization/manage-org-projects/manage-project-permissions/templates.md#apply-template-to-several-projects) for more information.

<figure><img src="/files/YaJkPM9SeqRX8W9iJ5r3" alt=""><figcaption></figcaption></figure>

## Changing the project’s visibility <a href="#changing-visibility" id="changing-visibility"></a>

The project’s visibility may be:

* Public: Anyone, including anonymous users, can view public projects. A public project may be part of any organization.
* Or private: Only authorized users, who are members of the organization, can view a private project. By default, the visibility of newly created projects is set to private on [Free, Team and Enterprise](https://www.sonarsource.com/plans-and-pricing/#sonarqube-cloud-features) plans.

If you’re a project admin, you can change your project’s visibility.

To change the visibility of your project:

1. Retrieve your project. See [Retrieving projects](/sonarqube-cloud/managing-your-projects/retrieving-projects.md) for more details.
2. Go to **Administration** > **Permissions**. The **Permissions** page opens.
3. In the **Project visibility** section, select the **Public** or **Private** checkbox. (You can also upgrade your organization from this section.) The **Turn to Private / Public** dialog opens.
4. Confirm the change.

## Related pages <a href="#related-pages" id="related-pages"></a>

* [Creating your project](/sonarqube-cloud/managing-your-projects/administering-your-projects/setting-up-project.md)
* [Configuring project binding features](/sonarqube-cloud/managing-your-projects/administering-your-projects/devops-platform-integration.md)
* [Changing project binding](/sonarqube-cloud/managing-your-projects/administering-your-projects/changing-binding.md)
* [Customizing Information page](/sonarqube-cloud/managing-your-projects/administering-your-projects/customizing-info-page.md)
* [Deleting project](/sonarqube-cloud/managing-your-projects/administering-your-projects/deleting-project.md)
* [Permissions](/sonarqube-cloud/administering-sonarcloud/permissions.md)


---

# 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.sonarsource.com/sonarqube-cloud/managing-your-projects/administering-your-projects/setting-permissions.md?ask=<question>
```

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.