Wiki source code of Shared Projects and Repositories

Version 4.3 by Boris Folgmann on 2025/05/22 14:26

version	line-number	content
1.2	1	When a project is created on the DevOps Portal of type PRIVATE, it means that no user can access it without a role assignment.
	2
1.5	3	However, as a Project ADMIN, you can manually change the permissions on a single repository or on a complete project.
1.3	4
1.4	5	This allows you to grant read-only access to all users which have a Bitbucket license assigned, i.e. all users that can log in to Bitbucket.
	6
1.11	7	In the following example the steps for changing a complete project are shown.
	8
2.2	9	1. Go to the Project settings of the Project in Bitbucket and open the sub page SECURITY/Project Permissions.
2.3	10	[[image:1747923524767-792.png]](((
2.4	11	Since the example project has the project key SBOM, you see a user for Jenkins called sbom-git as well as SDCloud Admin which is used by the portal for managing the projects. All other users have been added by the Portal when somebody assigned a role for them to the project.
2.3	12	)))
2.4	13	1. (((
3.2	14	Press the button "Add user or group" on the top right. For the name enter //stash-users//. Stash is the former name of Bitbucket and the //stash-users// group containers all users having access to this Bitbucket. For permission select Read. It's strictly recommend to not use higher permssions. Then press "Add".
	15	[[image:1747923859647-669.png\|\|height="215" width="440"]]
2.4	16	)))
3.2	17	1. (((
	18	The permission list now contains one more entry.
4.2	19	[[image:1747923907253-711.png\|\|height="218" width="514"]]
3.2	20	)))
4.2	21	1. (((
4.3	22	Now you are done. Please note that a Project Resync in the DevOps Portal will only remove individual users that you have added here, if they
4.2	23	)))
1.11	24
	25

Wiki source code of Shared Projects and Repositories

DevOps-as-a-Service

Navigation