From d12c302bd0f615ea945fdf5dc866f7906c7f0a40 Mon Sep 17 00:00:00 2001
From: Siddhi Khandelwal <siddhi.200727@gmail.com>
Date: Mon, 9 Feb 2026 11:23:38 +0530
Subject: [PATCH] docs: add examples for filtering Actions Service actions

Signed-off-by: Siddhi Khandelwal <siddhi.200727@gmail.com>
---
 docs/backend-system/core-services/actions.md | 27 ++++++++++++++++++++
 1 file changed, 27 insertions(+)

diff --git a/docs/backend-system/core-services/actions.md b/docs/backend-system/core-services/actions.md
index ddb28b4da7..b7e545f038 100644
--- a/docs/backend-system/core-services/actions.md
+++ b/docs/backend-system/core-services/actions.md
@@ -38,6 +38,33 @@ backend:
     pluginSources:
       - catalog
 ```
+### Restricting action sources by plugin
+
+The `pluginSources` configuration limits which plugins are allowed to register actions.
+
+```yaml
+backend:
+  actions:
+    pluginSources:
+      - catalog
+### Filtering actions
+
+In addition to plugin-level restrictions, the Actions Service supports filtering actions using include and exclude rules. This allows fine-grained control over which actions are exposed or runnable in a Backstage instance.
+
+#### Include specific actions
+
+```yaml
+backend:
+  actions:
+    filter:
+      include:
+        - 'catalog.*'
+#### Exclude specific actions
+backend:
+  actions:
+    filter:
+      exclude:
+        - 'scaffolder.internal.*'
 
 ## Using the Service