> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-cloud/administering-sonarcloud/about-sonarqube-cloud-solution/resources-structure/projects.md).
# Organization's projects
SonarQube Cloud projects represent DevOps platform repos and can be public or private, with binding to the repository determining visibility. Project permissions are managed through user groups.
A project in SonarQube Cloud represents a repository of a DevOps platform organization.
The project’s visibility may be:
* Public: anyone, including anonymous users, can view the code and analysis results of public projects.\
However:
* Non-members are not able to see the list of members in the organization.
* Anonymous and unauthorized users are prevented from easily downloading source code via API and web views.
* Or private: only authorized users, who are organization members, 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, and in private organizations. When your organization is set to private, all projects are automatically private, and you cannot change their visibility to public. See [Changing organization settings](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/changing-organization-settings.md#making-an-organization-private) for more information.
A project is created by importing and binding to a repository from the DevOps platform. It’s also possible to create projects manually, but they won’t benefit from the same features. A bound project inherits its visibility from its corresponding repository. However, you can change it if the organization is not on a free subscription plan. See [Changing project binding](/sonarqube-cloud/managing-your-projects/administering-your-projects/changing-binding.md) for more information.
You can grant SonarQube Cloud users analysis-related permissions on the projects of the organizations they are members of. You can manage permissions through the user group function. See [User group concept](/sonarqube-cloud/administering-sonarcloud/about-sonarqube-cloud-solution/user-management/user-group-concept.md) for more details.
The figure below shows SonarQube Cloud projects that were created by importing the repositories from a DevOps platform’s organization.
{% hint style="info" %}
Default project analysis configurations can be defined at the organization level: new code definition, quality gate, and quality profiles.
{% endhint %}
## Related pages
* [Retrieving projects](/sonarqube-cloud/managing-your-projects/retrieving-projects.md)
* [Configuring end-user settings for your project](/sonarqube-cloud/managing-your-projects/managing-your-project-as-developer.md)
* [Project administration overview](/sonarqube-cloud/managing-your-projects/administering-your-projects/introduction.md) to Administering your project
---
# 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.sonarsource.com/sonarqube-cloud/administering-sonarcloud/about-sonarqube-cloud-solution/resources-structure/projects.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.