Skip to content

Commit bdaaab5

Browse files
authored
Update permission levels to adhere to what we actually named them
1 parent 23ef487 commit bdaaab5

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

umbraco-cloud/begin-your-cloud-journey/the-cloud-portal/organizations/organization-login-providers.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -257,14 +257,14 @@ Select the level of access you want users to get for this project.
257257

258258
The dropdown has two possible permissions:
259259

260-
- Read Only
261-
- Read and Write
260+
- Read
261+
- Write
262262

263263
#### Read
264264

265265
A team member with Read permissions can only view the project in the portal and the backoffice. They are not able to deploy or change anything on the project itself.
266266

267-
#### Read And Write
267+
#### Write
268268

269269
A team member with Write permissions can do everything on a project except delete it and edit the team. A user with Write permissions can deploy changes between environments through the portal.
270270

@@ -296,7 +296,7 @@ Use this to map the Provider Role Value (a role coming from your external login
296296

297297
If your external login provider is configured to assign roles to users, those role values are included in the ID token. You can then use these values to automatically assign the appropriate access level when the user signs in to the portal.
298298

299-
For example, a role like `Happy.Write` from your identity provider could be mapped to the `Read and Write` permission level for your Cloud project.
299+
For example, a role like `Happy.Write` from your identity provider could be mapped to the `Write` permission level for your Cloud project.
300300

301301
## Audit
302302

0 commit comments

Comments
 (0)