Skip to content

Commit c9c35bb

Browse files
committed
Updating terminology used when describing the privileges kibana_user has (#340)
* Changing the built-in role description * Changing phrasing about minimum privileges
1 parent 2b617a6 commit c9c35bb

File tree

2 files changed

+4
-3
lines changed

2 files changed

+4
-3
lines changed

docs/en/stack/security/authorization/built-in-roles.asciidoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -68,8 +68,8 @@ NOTE: This role should not be assigned to users as the granted permissions may
6868
change between releases.
6969

7070
[[built-in-roles-kibana-user]] `kibana_user`::
71-
Grants the privileges required for users of {kib}. This role grants access to Kibana
72-
and grants monitoring privileges for the cluster.
71+
Grants access to all features in {kib}. For more information on Kibana authorization,
72+
see {kibana-ref}/xpack-security-authorization.html[Kibana Authorization].
7373

7474
[[built-in-roles-logstash-admin]] `logstash_admin` ::
7575
Grants access to the `.logstash*` indices for managing configurations.

docs/en/stack/security/get-started-security.asciidoc

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -157,7 +157,8 @@ role and save the change. For example:
157157
[role="screenshot"]
158158
image::security/images/assign-role.jpg["Assigning a role to a user in Kibana"]
159159

160-
This user now has the minimum privileges required to use {kib}.
160+
This user now has access to all features in {kib}. For more information about granting
161+
access to Kibana see {kibana-ref}/xpack-security-authorization.html[Kibana Authorization].
161162

162163
If you completed all of the steps in
163164
{stack-gs}/get-started-elastic-stack.html[Getting started with the {stack}], you should

0 commit comments

Comments
 (0)