5.1.2.4. Permissions¶
There are global and project-specific permissions that can be associated with a dashboard user. The effective permissions (global and project-specific) of a user are determined by the permissions either directly associated with the user or associated with one of the groups of which the user is a direct or indirect member.
The most critical permissions are the two global permissions Log in (User)
and Administrate (Admin), as well as the project-specific permission
View. Log in determines whether a user can use the dashboard
at all, and Administrate provides the ability to configure (administrate)
the Dashboard.
Note that this permission does not automatically grant all other permissions. The
permission View is necessary to see actual project analysis results.
Caution
LDAP/ActiveDirectory users are not
automatically deleted from the
internal user database when they are
deleted from the LDAP/ActiveDirectory server.
To prevent these users from accessing the Dashboard (via internal password or
Dashboard provided API Tokens)
after deletion from your LDAP/ActiveDirectory server, ensure that the
Log in permission is only
granted to these users via an LDAP group membership.
There are several more permissions, and not all of them are necessarily visible in the example screenshots (see Figures The global permission configuration view. and The project permission configuration view.). You can find a description of individual permissions in the tooltip that appears when hovering over the respective table header in the dashboard.
Permissions are configured on two settings pages, Global Permissions and
Project Permissions.
The global permission configuration view.¶
All permissions are configured in tables where each row belongs to either a user or a
group. Internal users and groups are added to a table by name,
Add LDAP user or group searches the configured LDAP authenticators, and
Create federated group adds a group of an
OIDC identity provider.
Users and groups can thus be defined via an external authentication source.
For example, to allow users of a specific LDAP group to use the dashboard, you can grant
that LDAP group the Log in permission. To further fine-tune permissions,
you can create non-LDAP groups,
associate users with those groups, and grant them
more specific permissions for certain projects.
Note
You can grant permissions to users regardless of whether or not they are listed in user management. If a user or group with a matching name appears (either by being added later or via an external authenticator), these permissions are automatically associated with the new entry in the user table. Conversely, when deleting a user from user management, the permissions explicitly granted to them are also deleted from the permissions page.
Project-specific permissions can be configured in multiple tables, where each table has
a name and is
associated with a list of projects or project patterns; the simplest being
*, which means the permissions granted in the table apply to
all current and future projects in the dashboard. This allows you to create “groups of
projects” and grant rights on these groups to users and user groups.
The label Naming-based next to the name of a table indicates that its
permissions apply to all projects whose name matches this list.
Add new project permission table creates another table. A table whose
project list is empty shows a warning, because its permissions have no effect.
The project permission configuration view.¶
The most important project-specific permission is the ability to view project issues:
View. Other permissions include the ability to view or
create annotations,
as well as view issues of other users. The meaning of individual permissions is
explained when hovering over the table column header in the
UI.
Note
Project-specific permissions are independent of whether the project they grant rights to exists. Consequently, you can grant permissions to a project before installing it, and when deleting a project, you cannot accidentally lose complex permission configurations. However, permission configurations can become stale in this way, which is indicated by an orange background for the project or project pattern.