Skip to content

Commit 4434f81

Browse files
author
Tomas Pospisek
committed
easier to understand phrasing
1 parent ad95e4a commit 4434f81

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/configuration/ResourcesPermissions.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ The configuration backend allows to assign users and groups to roles. The roles
66

77
## Users, groups and roles
88

9-
All resource permissions are assigned to a role. On their part, you can assign a user and a group of users to a role.
9+
Roles can be given permissions on resources. That means that if you want to give users or groups permissions on resources, then you have to first create a role, configure the permissions that the roles has on some resources, and then assign the role the users or groups.
1010

1111
## Resources
1212

@@ -51,7 +51,7 @@ These can be queried, e.g. in a custom service, by using `PermissionClient::reso
5151
## Permissions
5252

5353
Permissions are based on roles. Roles can be assigned to groups or users, and users can be members of groups.
54-
A special role is `public`, which is always included, whether a user is signed in or not.
54+
A special role is "public". The "public" role applies always, no matter whether a user is signed in or is not signed in.
5555

5656
Each role can be assigned a permission for a resource.
5757

0 commit comments

Comments
 (0)