@@ -32,7 +32,8 @@ ability to manage security.
3232`manage_ccr`::
3333All {ccr} operations related to managing follower indices and auto-follow
3434patterns. It also includes the authority to grant the privileges necessary to
35- manage follower indices and auto-follow patterns.
35+ manage follower indices and auto-follow patterns. This privilege is necessary
36+ only on clusters that contain follower indices.
3637
3738`manage_index_templates`::
3839All operations on index templates.
@@ -71,6 +72,7 @@ who created or updated them.
7172All read only {ccr} operations, such as getting information about indices and
7273metadata for leader indices in the cluster. It also includes the authority to
7374check whether users have the appropriate privileges to follow leader indices.
75+ This privilege is necessary only on clusters that contain leader indices.
7476
7577`transport_client`::
7678All privileges necessary for a transport client to connect. Required by the remote
@@ -93,8 +95,9 @@ close, delete, exists, flush, mapping, open, force merge, refresh, settings,
9395search shards, templates, validate).
9496
9597`manage_follow_index`::
96- All actions that are required to manage a follower index, which includes pausing
97- and resuming {ccr}.
98+ All actions that are required to manage the lifecycle of a follower index, which
99+ includes creating a follower index, closing it, and converting it to a regular
100+ index. This privilege is necessary only on clusters that contain follower indices.
98101
99102`view_index_metadata`::
100103Read-only access to index metadata (aliases, aliases exists, get index, exists, field mappings,
0 commit comments