In CodeScene, you can use groups to manage permissions for related projects. If someone has access to a group, they get access to all the projects in the group. At the group level you fill also find settings common to all the projects in the group.
Admins will be able to view groups by selecting Groups from the top menu. From this page, global admins will also be able to create and delete groups. Group admins will be able to modify settings for their existing groups, but not create new ones.
Control Access to a Group¶
Access to the projects in a group is controlled by defining roles for users at the group level. Note that globally defined roles apply across all groups. Role permissions are additive and any roles defined at the group level will add to what is globally defined. This means that if you want to limit a user to have access only to a certain group, you should not give that user a global role mapping. For more details on the different roles available, see Users and Roles.
Specify SSH Key for a Group¶
When editing a group it is possible to generate an SSH key that will be used for cloning and updating repositories by all projects in the group. If such a key is not specified, the default SSH key configured in the environment where CodeScene runs will be used. This will also be the case for projects that are not in a group. After generating an SSH key for the group, log in to your repository provider with the user account you want CodeScene to use and add the public key you see in the UI.
Specify settings for a Group¶
Some settings, such as plugin settings, that are available on the global level are replicated on the group configuration pages. For projects in a group, the values for these settings will be taken from the groups settings. For projects not within a group, the global settings will apply.