You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: source/adminguide/projects.rst
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,7 +53,11 @@ added to a project without a project role, it would imply that the
53
53
user / account added will have access to all APIs that are made available
54
54
by the Account level role. If there are no specific deny rules in the
55
55
project role, it would again fallback onto the account-level role to decide
56
-
whether the user has permissions to perform a specific action.
56
+
whether the user has permissions to perform a specific action. It is also to be
57
+
noted that Project roles are restricictive in nature, i.e., to say that, one may
58
+
not allow a user to perform an operation that is NOT allowed at Account level.
59
+
Even if a rule is added at the project level, allowing such an action, it will not
60
+
have any effect as the action will be prohibitted by the Account Role.
57
61
58
62
59
63
The project administrator can promote or demote a user in the project.
@@ -310,7 +314,7 @@ not turned on, use the procedure in Adding Project Members From the UI.
310
314
311
315
You can invite only people who have an account in this cloud within the same domain as the project. However, you can send the invitation to any email address.
312
316
313
-
5. To view and manage the invitations you have sent, return to this tab.
317
+
#. To view and manage the invitations you have sent, return to this tab.
314
318
When an invitation is accepted, the new member will appear in the
0 commit comments