From 2a418ed7fe7fd7ed6c04960c591b015c95f17ef7 Mon Sep 17 00:00:00 2001 From: kovalromank Date: Mon, 24 Jul 2023 16:00:47 -0400 Subject: [PATCH] Update daprdocs/content/en/developing-applications/building-blocks/pubsub/pubsub-scopes.md Co-authored-by: Hannah Hunter <94493363+hhunter-ms@users.noreply.github.com> Signed-off-by: kovalromank --- .../building-blocks/pubsub/pubsub-scopes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/developing-applications/building-blocks/pubsub/pubsub-scopes.md b/daprdocs/content/en/developing-applications/building-blocks/pubsub/pubsub-scopes.md index 2e3cd9fec..82bc6a28a 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/pubsub/pubsub-scopes.md +++ b/daprdocs/content/en/developing-applications/building-blocks/pubsub/pubsub-scopes.md @@ -157,7 +157,7 @@ The table below shows which application is allowed to subscribe to the topics: ## Example 4: Mark topics as protected -If your topic involves sensitive data, each new application must be explicitly listed in the `publishingScopes` and `subscriptionScopes` to ensure it cannot read from or write to that topic. Alternatively, you can designate the topic as 'protected' and grant access only to specific applications that genuinely require it. +If your topic involves sensitive data, each new application must be explicitly listed in the `publishingScopes` and `subscriptionScopes` to ensure it cannot read from or write to that topic. Alternatively, you can designate the topic as 'protected' (using `protectedTopics`) and grant access only to specific applications that genuinely require it. Here is an example of three applications and three topics, two of which are protected: ```yaml