Skip to content

Commit 5981c4a

Browse files
committed
Add sync to tabs + fix screenshot
1 parent 312f9ac commit 5981c4a

File tree

1 file changed

+8
-7
lines changed

1 file changed

+8
-7
lines changed

deploy-manage/users-roles/cluster-or-deployment-auth/controlling-access-at-document-field-level.md

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -62,8 +62,9 @@ Omitting the `query` parameter entirely disables document level security for the
6262
### Basic examples
6363

6464
:::::{tab-set}
65-
65+
:group: field-document
6666
::::{tab-item} {{stack}}
67+
:sync: stack
6768
The following role definition grants read access only to documents that belong to the `click` category within all the `events-*` data streams and indices:
6869

6970
```console
@@ -117,6 +118,7 @@ POST /_security/role/dept_role
117118
::::
118119

119120
::::{tab-item} {{serverless-short}}
121+
:sync: serverless
120122
To configure document-level security (DLS), you create a custom role where you define the documents that this role grants access to, using the [QueryDSL](/explore-analyze/query-filter/languages/querydsl.md) syntax:
121123

122124
1. Go to the **Custom Roles** page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
@@ -245,8 +247,9 @@ For more information, see [Ingest pipelines](/manage-data/ingest/transform-enric
245247
To enable field level security, specify the fields that each role can access as part of the indices permissions in a role definition. Field level security is thus bound to a well-defined set of data streams or indices (and potentially a set of [documents](../../../deploy-manage/users-roles/cluster-or-deployment-auth/controlling-access-at-document-field-level.md)).
246248

247249
:::::{tab-set}
248-
250+
:group: field-document
249251
::::{tab-item} {{stack}}
252+
:sync: stack
250253
The following role definition grants read access only to the `category`, `@timestamp`, and `message` fields in all the `events-*` data streams and indices.
251254

252255
```console
@@ -434,7 +437,7 @@ The resulting permission is equal to:
434437
::::
435438

436439
::::{tab-item} {{serverless-short}}
437-
440+
:sync: serverless
438441
To configure field-level security (FLS), you create a custom role where you define the specific fields that this role grants or denies access to:
439442

440443
1. Go to the **Custom Roles** page using the navigation menu or the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
@@ -450,10 +453,8 @@ To configure field-level security (FLS), you create a custom role where you defi
450453

451454
* To deny access to specific fields within each document, add the fields to the **Denied fields** list. For example, you can add the `customer.handle` field.
452455

453-
:::{image} /deploy-manage/images/serverless-custom-role-deny-field-level-privileges.png
454-
:title: Configuring field-level security by denying access to fields
455-
:::
456-
456+
![Configuring field-level security by denying access to fields](/deploy-manage/images/serverless-custom-role-deny-field-level-privileges.png)
457+
457458
1. Optional: To grant this role access to {{kib}} spaces for feature access and visibility, click **Assign to this space**. Specify the level of access required and click **Assign role**.
458459
1. Select **Create role** to save your custom role.
459460

0 commit comments

Comments
 (0)