From a862dc169178b7838f77fc4bf702484cfef24d44 Mon Sep 17 00:00:00 2001 From: Irena Rindos Date: Mon, 21 Oct 2024 16:50:47 -0400 Subject: [PATCH] chore(docs): clarify that storage policies must be attached in order to take effect (#5191) --- website/content/docs/concepts/domain-model/storage-policy.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/website/content/docs/concepts/domain-model/storage-policy.mdx b/website/content/docs/concepts/domain-model/storage-policy.mdx index 5729d8848b..b2a7665203 100644 --- a/website/content/docs/concepts/domain-model/storage-policy.mdx +++ b/website/content/docs/concepts/domain-model/storage-policy.mdx @@ -12,6 +12,7 @@ description: |- A resource known as a storage policy is used to codify how long [session recordings][] must be kept and when they should be deleted. A storage policy's name is optional, but it must be unique if you define one. Storage policies can only be assigned to the global [scope][] or an org scope. +You must [attach][] storage policies to a scope (global or a specific org) to take effect. A storage policy exists in either the global scope or an org scope. Storage policies that are created in the global scope can be associated with any org scope. @@ -55,5 +56,6 @@ The following services are relevant to this resource: - [Scope Service](/boundary/api-docs/scope-service) - [Policy Service](/boundary/api-docs/policy-service) +[attach]: /boundary/docs/configuration/session-recording/configure-storage-policy#attach-storage-policies-to-a-scope [session recordings]: /boundary/docs/concepts/domain-model/session-recordings -[scope]: /boundary/docs/concepts/domain-model/scopes \ No newline at end of file +[scope]: /boundary/docs/concepts/domain-model/scopes