GITBOOK-730: feat: filtering customer resources

Author: Paweł Stępniak

docs/SUMMARY.md

@@ -129,6 +129,7 @@
   * [Customers](capability-guides/customer-portals/customers.md)
   * [Preview the customer portal in Console](capability-guides/customer-portals/preview-the-customer-portal-in-console.md)
   * [Integrate customer portal into your application](capability-guides/customer-portals/integrate-customer-portal-into-your-application.md)
+  * [Filtering Portal Resources by Custom Metadata](capability-guides/customer-portals/filtering-portal-resources-by-custom-metadata.md)
 * [Reservation Automations](capability-guides/reservation-automations.md)
 
 ## UI Components

docs/api/customers/create_portal.md

@@ -311,9 +311,19 @@ The locale to use for the portal.
 
 ***
 
-**`property_listing_filter`** _Object_
+**`customer_resources_filters`** _List_
 
-Filter configuration for property listings based on their custom\_metadata. Keys and values must match the custom\_metadata stored on property listings.
+Filter configuration for resources based on their `custom_metadata`. Each filter specifies a field, operation, and value to match against resource `custom_metadata`. When multiple filters are provided, a resource must match all of them (AND logic). Applies to both property listings and reservations.
+
+<details>
+
+<summary>Filter object structure</summary>
+
+* **`field`** _String_ — The `custom_metadata` field name to filter on. Must start with a letter or underscore and contain only alphanumeric characters and underscores.
+* **`operation`** _String_ — The comparison operation. Currently only `"="` is supported.
+* **`value`** _String or Boolean_ — The value to compare against.
+
+</details>
 
 ***
 

docs/capability-guides/customer-portals/customers.md

@@ -14,12 +14,6 @@ Seam gives you a way to tag each customer with your own identifier through the `
 
 `customer_key` is your unique identifier for a customer. You assign it when creating resources that belong to that customer. Seam then copies the same key to related resources, so you always have a reliable way to look them up.
 
-Key uses:
-
-* Connect Webviews: Tag a Webview with `customer_key`. When the customer connects their account, the resulting Connected Account inherits that key.
-* Customer Portals: Initialize a portal with `customer_key` so the portal shows only the devices, spaces, and accounts for that customer.
-* Lookups: Use `customer_key` to fetch all Connected Accounts, devices, or systems associated with a specific customer.
-
 ***
 
 #### Key uses: