From 16865ba423aa75550c075d9305bd2590ec47d1d5 Mon Sep 17 00:00:00 2001
From: JP Hwang <61258750+databyjp@users.noreply.github.com>
Date: Thu, 19 Dec 2024 11:17:31 +0000
Subject: [PATCH] Add note (#2891)

---
 developers/weaviate/configuration/roles.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/developers/weaviate/configuration/roles.md b/developers/weaviate/configuration/roles.md
index 5b51592328..73768d8d4a 100644
--- a/developers/weaviate/configuration/roles.md
+++ b/developers/weaviate/configuration/roles.md
@@ -103,6 +103,12 @@ In `v1.28`, aggregate queries require the user to have the `read_config` permiss
 This is due to the implementation of the `aggregate` queries under-the-hood, which uses GraphQL rather than gRPC. This will be improved in future versions of Weaviate.
 :::
 
+#### Wildcards in permissions
+
+Many permissions require a collection name filter, to specify which collections the permission applies to.
+
+In thi case, `"*"` acts as a multi-character wildcard. As an example, setting a permission with `"Test_*"` as the collection filter would apply that permission to all collections that start with `Test_`. Or, setting a permission with `"*"` as the collection filter would apply that permission to all available collections.
+
 ## Example permission sets
 
 ### Read and write permissions