Changes for page Frequently Asked Questions

Summary

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

Details

Page properties

Content

...	...	@@ -30,15 +30,15 @@
30	30
31	31	(% style="color:#172b4d" %)After a few failed login attempts, your account will be locked and you have to wait for a certain period of time to be able to login again.
32	32
33		-(% style="color:#172b4d" %)Please ask the Portal Administrator to lock and then unlock your user. Usually this can solve the problem (and you don't have to wait, you can login instantly after this procedure).
	33	+(% style="color:#172b4d" %)Another reason for a locked account might be that the Portal Administrator actively locked your user account.
34	34
35		-(% style="color:#172b4d" %)Another reason for a locked account might be that the Portal Administrator locked your user account on purpose.
	35	+(% style="color:#172b4d" %)Please ask the Portal Administrator to lock and then unlock your user. Usually this can solve the problem (and you don't have to wait, you can login instantly after this procedure). You can read more about the user statuses on the [[User statuses in DevOps Portal>>doc:DevOps Portal for Admins.User statuses in DevOps Portal.WebHome]] page.
36	36
37	37	=== (% style="color:#172b4d" %)What does a specific role mean?(%%) ===
38	38
39	39	Each user who is a member of a project has to be in exactly one Project Role. Therefore it is not possible to have no or multiple roles in a project.
40	40
41		-Different roles have different sets of permissions, a role can be //Admin, Developer, Master, Viewer.// You can read more about a specific role on the [[Users and roles>>doc:Users and roles.WebHome]] page.
	41	+Different roles have different sets of permissions, a role can be //Admin, Developer, Master, Viewer.// You can read more about a specific role on the [[Users and roles>>doc:DevOps Portal for Admins.Users and roles.WebHome]] page.
42	42
43	43	=== (% style="color:#262626" %)What is the role of Organizations in the DevOps Portal?(%%) ===
44	44
...	...	@@ -138,7 +138,6 @@
138	138
139	139	This global git config will be automatically saved to the file //.gitconfig// located in the home directory of your user.
140	140	)))
141		-1. You can set the env var {{code language="none"}}XDG_CONFIG_HOME{{/code}} if you want to have the config placed in another folder. When this env var is set, git will use the file {{code language="none"}}$XDG_CONFIG_HOME/git/config{{/code}}.
142		-See [[https:~~/~~/git-scm.com/docs/git-config>>url:https://git-scm.com/docs/git-config||rel="nofollow" shape="rect" style="text-decoration: none;" class="external-link"]]
	141	+1. You can set the env var {{code language="none"}}XDG_CONFIG_HOME{{/code}} if you want to have the config placed in another folder. When this env var is set, git will use the file {{code language="none"}}$XDG_CONFIG_HOME/git/config{{/code}}. See [[https:~~/~~/git-scm.com/docs/git-config>>url:https://git-scm.com/docs/git-config||rel="nofollow" shape="rect" style="text-decoration: none;" class="external-link"]]
143	143
144	144