diff --git a/topics/groups/default-groups.adoc b/topics/groups/default-groups.adoc index d17b063986..4719c23a7a 100644 --- a/topics/groups/default-groups.adoc +++ b/topics/groups/default-groups.adoc @@ -3,9 +3,9 @@ Default groups allow you to automatically assign group membership whenever any new user is created or imported through <> or <>. -To specify _default groups go to the `Groups` left menu item, and click the `Default Groups` tab. +To specify default groups go to the `Groups` left menu item, and click the `Default Groups` tab. -.Default Roles +.Default Groups image:../../{{book.images}}/default-groups.png[] diff --git a/topics/groups/groups-vs-roles.adoc b/topics/groups/groups-vs-roles.adoc index 8b64323a13..85edc2d8cd 100644 --- a/topics/groups/groups-vs-roles.adoc +++ b/topics/groups/groups-vs-roles.adoc @@ -7,7 +7,7 @@ In {{book.project.name}}, Groups are just a collection of users that you can app Roles define a type of user and applications assign permission and access control to roles Aren't <> also similar to Groups? -Logically they provide the same exact functionality, but the difference is conceptual +Logically they provide the same exact functionality, but the difference is conceptual. Composite roles should be used to apply the permission model to your set of services and applications. Groups should focus on collections of users and their roles in your organization. -Use groups to manage users, composite roles to manage applications and services. +Use groups to manage users. Use composite roles to manage applications and services.