Message-ID: <607566593.505.1432750734478.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_504_927924901.1432750734478" ------=_Part_504_927924901.1432750734478 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The way authorization is implemented in SonarQube is pretty standard.&nb= sp;It is possible to create as many users and groups of users as required i= n the system. The users can then be attached (or not) to (multiple) groups.= Groups and / or users are then given (multiple) permissions. The permissio= ns grant access to projects, services and functionalities.
A group is a set of users.
To create a new group, go to Settings > Groups > Add new g= roup:
To add/remove users to/from a group, click on the Select link in the Member column.
Two groups have a special meaning:
To set global permissions, log in as a System administrator and go to
Settings > Global Permissions.
Four different permissions can be set on project-level resources (projec= ts, views, developers):
Note that permissions are not cumulative. For instance, if you want to b= e able to administer the project, you also have to be granted the Brows= e permission to be able to access the project.
You can either manually grant permissions for each project to some users= and groups or apply permission templates to projects (since version 3= .7).
Log in as a System Administrator and go to Settings > Project= Permissions > Projects (was Settings > Roles prior to version 3.7):
Create first some permission templates via Settings &= gt; Project Permissions > Permission Templates.
Since version 4.1, it is possible to provide a Project key patte= rn. By default, every new project matching this key pattern will b= e granted permissions of this template.
Then, apply permission templates to projects (either to a specific= one through the Apply permission template link = or do some bulk changes through the Bulk Change = link).
Note that there is no relation between a project and a permission templa= te, meaning that:
It is possible to configure the system so that when a new project (proje= ct, view, developer) is created, some users/groups are automatically grante= d permissions on this project.
For versions 3.7+, this is done through permission templates. Go to Settings &g= t; Project Permissions > Permission Templates > Set default templates= :
For versions prior to 3.7, it is done through the Default roles = for new Projects table:
In the example below, once a new project has been created:
For security reasons, you can prevent SonarQube to upload the source cod=
e to the database when analyzing a project. To do so, log in as a System ad=
ministrator, go to Settings > General Settings > Security and set the Import sources property to
nbsp;Note that if you want to restrict the access to the source code, grant=
See Source Code permission accordingly.
To recreate a System administrator: