From 9e3760df2d8d42f7402cfd8ce21dd2ee87baeb1c Mon Sep 17 00:00:00 2001 From: Max Phillips Date: Thu, 25 Jun 2026 15:43:01 -0500 Subject: [PATCH 1/2] fix typo --- content/en/logs/guide/logs-rbac-permissions.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/logs/guide/logs-rbac-permissions.md b/content/en/logs/guide/logs-rbac-permissions.md index c5d5fc50371..643267e3b2e 100644 --- a/content/en/logs/guide/logs-rbac-permissions.md +++ b/content/en/logs/guide/logs-rbac-permissions.md @@ -102,7 +102,7 @@ This permission is global and enables creating new archives, and editing and del ### `logs_read_archives` -Grants the ability to access the details of the archive configuration. In conjunction with [Logs Write Historical Views](#logs_write_historical_views), this permission also grants the ability to trigger a [Rehydration][13] from Archives. +Grants the ability to access the details of the archive configuration. In conjunction with [Logs Write Historical Views](#logs_write_historical_view), this permission also grants the ability to trigger a [Rehydration][13] from Archives. This permission can be scoped to a subset of archives. An archive with no restrictions is accessible to anyone who belongs to a role with the `logs_read_archives` permission. An archive with restrictions is only accessible to the users who belong to one of the registered roles, provided theses roles have the `logs_read_archives` permission. @@ -132,7 +132,7 @@ Use the Logs Archive API either to [assign][1] or [revoke][2] a role from a give {{% /tab %}} {{< /tabs >}} -### `logs_write_historical_views` +### `logs_write_historical_view` Grants the ability to write historical views, meaning to trigger a [Log Rehydration*][13]. From 845f868995017cb25fb944249dd359e5853e35cf Mon Sep 17 00:00:00 2001 From: Max Phillips Date: Thu, 25 Jun 2026 15:43:26 -0500 Subject: [PATCH 2/2] fix additional typo --- content/en/logs/explorer/archive_search.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/logs/explorer/archive_search.md b/content/en/logs/explorer/archive_search.md index d01dbb42172..9fc09a31023 100644 --- a/content/en/logs/explorer/archive_search.md +++ b/content/en/logs/explorer/archive_search.md @@ -59,7 +59,7 @@ Before using Archive Search: ### Permissions -Running an **Archive Search** requires the **`logs_write_historical_views`** permission. It is a **global** permission, but users can only search logs from archives for which they also have the **Logs Read Archive** permission. +Running an **Archive Search** requires the **`logs_write_historical_view`** permission. It is a **global** permission, but users can only search logs from archives for which they also have the **Logs Read Archive** permission. Archive Search results are visible to all users in your organization who have access to the Archive Search feature. However, **restriction queries**, such as log security filters and data restrictions configured in Datadog, are still enforced on the result page and apply to all users. This means each user may only see logs they are authorized to view based on organization-wide permissions and filters.