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.

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 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 for more details.

The figure below shows SonarQube Cloud projects that were created by importing the repositories from a DevOps platform’s organization.

Default project analysis configurations can be defined at the organization level: new code definition, quality gate, and quality profiles.

Related pages

• Retrieving projects

• Managing your project as a developer

• Introduction to Administering your project