Merge pull request #2763 from port-labs/PORTN-3612-contextual-search-open-beta

contextual-search close beta -> GA

Author: hadar-co

docs/build-your-software-catalog/set-catalog-rbac/set-catalog-rbac.md

@@ -141,11 +141,6 @@ To give `read` permissions to members of the owning team of an entity, change th
 
 <TabItem value="policy" label="Policy">
 
-:::info Closed beta feature
-This capability is currently in closed beta, and is not yet generally available.  
-If you would like to join the beta, please reach out to us.
-:::
-
 The `policy` key allows you to give **dynamic** `read` permissions to users, by using [search queries](/search-and-query/#rules).
 
 You can also use [contextual query rules](/search-and-query/#contextual-query-rules) to get the context of the user executing the query.

docs/search-and-query/search-and-query.md

@@ -567,11 +567,7 @@ Since we don't have context of the logged-in user when using the API, these func
 
 ### Contextual query rules
 
-:::info Closed beta feature
-This capability is currently in closed beta, and is not yet generally available.  
-If you would like to join the beta, please reach out to us.
-:::
-To implement specific and/or complex queries, you can add the context of the triggering user to a query rule, allowing you to access that user's entity and/or owning teams.  
+To implement specific and/or complex queries, you can add the context of the triggering user to a query rule, allowing you to access that user's properties and/or owning teams.  
 You can mix contextual query rules freely with other rules as part of your queries.
 This can be used in either the `property` or `value` key in a query rule:
 
@@ -610,37 +606,53 @@ This can be used in either the `property` or `value` key in a query rule:
 | `userTeams` | The entities of the owning teams of the user triggering the query                                                                     |
 
 #### Usage examples
-
+The following rule will result in the entities owned by any one of the user's teams:
 ```json showLineNumbers
 [ 
   ...other rules
-  { // filter entities with the same department as the user
-    "property": "department",
+  { 
+    "property": "$team",
     "operator": "containsAny",
+    "value": {
+      "context": "userTeams",
+      "property": "$identifier"
+    }
+  }
+]
+```
+The following rule will result in entities with the same department as the user's:
+```json showLineNumbers
+[ 
+  ...other rules
+  { 
+    "property": "department",
+    "operator": "=",
     "value": {
       "context": "user",
       "property": "department"
     }
   }
 ]
 ```
+The following rule asserts that only users with `manager` role will get the resulting entities:
 ```json showLineNumbers
 [ 
   ...other rules
-  { // only users with `manager` role will get the entities
+  { 
     "property": {
       "context": "user",
-      "property": "role"
+      "property": "port_role"
     },
     "operator": "=",
     "value": "manager"
   }
 ]
 ```
+The following rule asserts that only users in the user's team/s will get the resulting entities:
 ```json showLineNumbers
 [
   ...other rules
-  { // only users in these team will get the entities
+  { 
     "property": {
       "context": "userTeams",
       "property": "$identifier"