Changes for page Shared Projects and Repositories

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,18 +1,13 @@
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.
	1	+When a project of type PRIVATE is created on the DevOps Portal, it means that no user can access it without a role assignment. However, as a Project ADMIN, you can manually change the permissions on a single repository or on a complete project. 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.
2	2
3		-However, as a Project ADMIN, you can manually change the permissions on a single repository or on a complete project.
	3	+In the following example, the steps for changing a complete project are shown.
4	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		-
7		-In the following example the steps for changing a complete project are shown.
8		-
9		-1. Go to the Project settings of the Project in Bitbucket and open the sub page SECURITY/Project Permissions.
10		-[[image:1747923524767-792.png]](((
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.
	5	+1. Go to the Project settings of the Project in Bitbucket and open the sub-page SECURITY/Project Permissions.[[image:1747923524767-792.png||height="788" width="1019"]](((
	6	+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.
12	12	)))
13	13	1. (((
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"]]
	9	+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 contains all users having access to this Bitbucket. For permission select Read. It's strictly recommended to not use higher permissions. Then press "Add".
	10	+[[image:1747923859647-669.png||height="248" width="508"]]
16	16	)))
17	17	1. (((
18	18	The permission list now contains one more entry.
...	...	@@ -24,5 +24,11 @@
24	24	1. (((
25	25	If at any time you want to stop sharing your project with all users, simply remove the group again from the permission list. To do this click on the 3 dot menu in the actions column and then select Remove.
26	26
27		- [[image:1747924090508-197.png]]
	22	+ [[image:1747924090508-197.png||height="114" width="517"]]
	23	+
	24	+
	25	+
	26	+The same approach can be applied to a single repository. To do it open the Repository settings and go to the sub-page SECURITY
	27	+
	28	+
28	28	)))