mudbase 1.2.7 → 1.2.8

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a96d489fdf940401487d8797231921d64c6ccffdcabd1c2b857d84cb37b6bbdd
-  data.tar.gz: db95c781b6ab4d9cd009e8d0e4282bcbda8aa2ff5e00966a8763ecbd73590360
+  metadata.gz: 44bc3797563159684c03533feb5ab10678586b3b04d3ad3f5b36b05784cf578b
+  data.tar.gz: 4bf6e32cf7f3f8e27015a8f900c771de5f9de2e2543cbe5a3a595ee5db7c53b7
 SHA512:
-  metadata.gz: d3fd54f17f350a5371b8b1b9dbc01c23a47824ab041f8e454b399997916fc5e9efc2635b841d3768f122287a518922a5078797172903c3559d98b537f1a4d5be
-  data.tar.gz: da7ad1fca111b9aa7e8813928e3e385eb24e86cee2991ab09ff0c07d18e8d6a4111a72dceac8006bd1f338bfda6bf9b64b1e5c226dc608a6bf2f0621b39b1013
+  metadata.gz: 81a8bf374722bfac50cdf938d30150064f02519b07e71619f27956d6b2da6a3be53867fe8c5007cdc72c0ba690842be1ca4c4df9e61c92c1b48c93b1b12f0acd
+  data.tar.gz: 3876b96e5ba373b5c33c0c97dbbd2291942fc3e5e315dd63f2d332bdec6da5e7772ab2c5706c7396cd161bdce8c6bd55d86d7139b63b591c0eefb8fea611d77a

data/docs/MultiRoleAddRoleRequest.md

@@ -8,8 +8,8 @@
 | **name** | **String** |  |  |
 | **description** | **String** |  | [optional] |
 | **signup_endpoint** | **String** |  |  |
-| **hierarchy** | **Float** |  | [optional] |
-| **default_permissions** | [**Array<MultiRoleAddRoleRequestDefaultPermissionsInner>**](MultiRoleAddRoleRequestDefaultPermissionsInner.md) |  | [optional] |
+| **default_permissions** | [**Array<MultiRoleAddRoleRequestDefaultPermissionsInner>**](MultiRoleAddRoleRequestDefaultPermissionsInner.md) | Optional global/base permissions. For collection-level CRUD use `collectionPermissions`. | [optional] |
+| **collection_permissions** | [**Hash<String, MultiRoleUpdateRoleRequestCollectionPermissionsValue>**](MultiRoleUpdateRoleRequestCollectionPermissionsValue.md) | Per-collection CRUD map. Keys are collection slugs; values are action arrays or objects with `actions` + optional `conditions`. | [optional] |
 
 ## Example
 
@@ -17,12 +17,12 @@
 require 'mudbase'
 
 instance = Mudbase::MultiRoleAddRoleRequest.new(
-  slug: rider,
-  name: Delivery Rider,
-  description: Delivery rider role for logistics,
-  signup_endpoint: /api/auth/local/signup/rider,
-  hierarchy: 25,
-  default_permissions: null
+  slug: seller,
+  name: Seller,
+  description: Seller role with CRUD on seller-owned collections,
+  signup_endpoint: seller,
+  default_permissions: null,
+  collection_permissions: null
 )
 ```
 

data/docs/MultiRoleApi.md

@@ -30,7 +30,7 @@ require 'time'
 require 'mudbase'
 
 api_instance = Mudbase::MultiRoleApi.new
-role = 'vendor' # String | Role slug for signup (e.g. customer, vendor, seller).
+role = 'customer' # String | Path segment must match the role's `signupEndpoint` (default `customer`; use each role's configured endpoint).
 provider = 'google' # String | OAuth provider (e.g. google, github).
 project_id = '685ad30be129932fbb7a1047' # String | Project ID.
 opts = {
@@ -68,7 +68,7 @@ end
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **role** | **String** | Role slug for signup (e.g. customer, vendor, seller). |  |
+| **role** | **String** | Path segment must match the role's `signupEndpoint` (default `customer`; use each role's configured endpoint). |  |
 | **provider** | **String** | OAuth provider (e.g. google, github). |  |
 | **project_id** | **String** | Project ID. |  |
 | **redirect_url** | **String** | The URL to redirect to after authentication | [optional] |
@@ -93,7 +93,7 @@ No authorization required
 
 Register user with specific role (Local Auth)
 
-Public endpoint for user registration with a specific role. The role is specified in the URL path (e.g., /signup/customer, /signup/vendor). No authentication required - this is a public signup endpoint. 
+Public endpoint for user registration with a specific role. The path segment must match a role's `signupEndpoint` (default starter is `customer`; add more roles via multi-role API). No authentication required - this is a public signup endpoint. 
 
 ### Examples
 
@@ -102,7 +102,7 @@ require 'time'
 require 'mudbase'
 
 api_instance = Mudbase::MultiRoleApi.new
-role = 'customer' # String | Role slug for signup (e.g. customer, vendor).
+role = 'customer' # String | Must match the role's `signupEndpoint` (default `customer`; other values for roles you add).
 auth_register_with_role_request = Mudbase::AuthRegisterWithRoleRequest.new({email: 'email_example', password: 'password_example', first_name: 'first_name_example', last_name: 'last_name_example', project_id: 'project_id_example'}) # AuthRegisterWithRoleRequest | Registration payload (email, password, firstName, lastName, projectId).
 
 begin
@@ -135,7 +135,7 @@ end
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **role** | **String** | Role slug for signup (e.g. customer, vendor). |  |
+| **role** | **String** | Must match the role's `signupEndpoint` (default `customer`; other values for roles you add). |  |
 | **auth_register_with_role_request** | [**AuthRegisterWithRoleRequest**](AuthRegisterWithRoleRequest.md) | Registration payload (email, password, firstName, lastName, projectId). |  |
 
 ### Return type
@@ -154,7 +154,7 @@ No authorization required
 
 ## multi_role_add_role
 
-> <MultiRoleUpdateSettings200Response> multi_role_add_role(project_id, multi_role_add_role_request)
+> <MultiRoleToggleRole200Response> multi_role_add_role(project_id, multi_role_add_role_request)
 
 Add custom role
 
@@ -173,7 +173,7 @@ end
 
 api_instance = Mudbase::MultiRoleApi.new
 project_id = '685ad30be129932fbb7a1047' # String | Project ID.
-multi_role_add_role_request = Mudbase::MultiRoleAddRoleRequest.new({slug: 'rider', name: 'Delivery Rider', signup_endpoint: '/api/auth/local/signup/rider'}) # MultiRoleAddRoleRequest | Custom role definition (slug, name, description, signupEndpoint, hierarchy, defaultPermissions).
+multi_role_add_role_request = Mudbase::MultiRoleAddRoleRequest.new({slug: 'seller', name: 'Seller', signup_endpoint: 'seller'}) # MultiRoleAddRoleRequest | Custom role definition. Use `collectionPermissions` to apply CRUD per collection slug (e.g. users/products/orders). `defaultPermissions` is optional for global/base permissions.
 
 begin
   # Add custom role
@@ -188,7 +188,7 @@ end
 
 This returns an Array which contains the response data, status code and headers.
 
-> <Array(<MultiRoleUpdateSettings200Response>, Integer, Hash)> multi_role_add_role_with_http_info(project_id, multi_role_add_role_request)
+> <Array(<MultiRoleToggleRole200Response>, Integer, Hash)> multi_role_add_role_with_http_info(project_id, multi_role_add_role_request)
 
 ```ruby
 begin
@@ -196,7 +196,7 @@ begin
   data, status_code, headers = api_instance.multi_role_add_role_with_http_info(project_id, multi_role_add_role_request)
   p status_code # => 2xx
   p headers # => { ... }
-  p data # => <MultiRoleUpdateSettings200Response>
+  p data # => <MultiRoleToggleRole200Response>
 rescue Mudbase::ApiError => e
   puts "Error when calling MultiRoleApi->multi_role_add_role_with_http_info: #{e}"
 end
@@ -207,11 +207,11 @@ end
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
 | **project_id** | **String** | Project ID. |  |
-| **multi_role_add_role_request** | [**MultiRoleAddRoleRequest**](MultiRoleAddRoleRequest.md) | Custom role definition (slug, name, description, signupEndpoint, hierarchy, defaultPermissions). |  |
+| **multi_role_add_role_request** | [**MultiRoleAddRoleRequest**](MultiRoleAddRoleRequest.md) | Custom role definition. Use &#x60;collectionPermissions&#x60; to apply CRUD per collection slug (e.g. users/products/orders). &#x60;defaultPermissions&#x60; is optional for global/base permissions. |  |
 
 ### Return type
 
-[**MultiRoleUpdateSettings200Response**](MultiRoleUpdateSettings200Response.md)
+[**MultiRoleToggleRole200Response**](MultiRoleToggleRole200Response.md)
 
 ### Authorization
 
@@ -298,7 +298,7 @@ end
 
 Get multi-role feature configuration
 
-Get the ready-to-use multi-role system configuration for a project
+Returns project app roles (default one editable `customer` starter until you add more) and settings.
 
 ### Examples
 
@@ -363,7 +363,7 @@ end
 
 ## multi_role_toggle_role
 
-> <MultiRoleUpdateSettings200Response> multi_role_toggle_role(project_id, role_slug, multi_role_toggle_role_request)
+> <MultiRoleToggleRole200Response> multi_role_toggle_role(project_id, role_slug, multi_role_toggle_role_request)
 
 Toggle role on/off
 
@@ -382,7 +382,7 @@ end
 
 api_instance = Mudbase::MultiRoleApi.new
 project_id = '685ad30be129932fbb7a1047' # String | Project ID.
-role_slug = 'vendor' # String | Role slug to toggle (e.g. vendor, customer).
+role_slug = 'customer' # String | Role slug to toggle (e.g. starter `customer` or a role you added).
 multi_role_toggle_role_request = Mudbase::MultiRoleToggleRoleRequest.new({is_enabled: true}) # MultiRoleToggleRoleRequest | Whether the role is enabled (true) or disabled (false).
 
 begin
@@ -398,7 +398,7 @@ end
 
 This returns an Array which contains the response data, status code and headers.
 
-> <Array(<MultiRoleUpdateSettings200Response>, Integer, Hash)> multi_role_toggle_role_with_http_info(project_id, role_slug, multi_role_toggle_role_request)
+> <Array(<MultiRoleToggleRole200Response>, Integer, Hash)> multi_role_toggle_role_with_http_info(project_id, role_slug, multi_role_toggle_role_request)
 
 ```ruby
 begin
@@ -406,7 +406,7 @@ begin
   data, status_code, headers = api_instance.multi_role_toggle_role_with_http_info(project_id, role_slug, multi_role_toggle_role_request)
   p status_code # => 2xx
   p headers # => { ... }
-  p data # => <MultiRoleUpdateSettings200Response>
+  p data # => <MultiRoleToggleRole200Response>
 rescue Mudbase::ApiError => e
   puts "Error when calling MultiRoleApi->multi_role_toggle_role_with_http_info: #{e}"
 end
@@ -417,12 +417,12 @@ end
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
 | **project_id** | **String** | Project ID. |  |
-| **role_slug** | **String** | Role slug to toggle (e.g. vendor, customer). |  |
+| **role_slug** | **String** | Role slug to toggle (e.g. starter &#x60;customer&#x60; or a role you added). |  |
 | **multi_role_toggle_role_request** | [**MultiRoleToggleRoleRequest**](MultiRoleToggleRoleRequest.md) | Whether the role is enabled (true) or disabled (false). |  |
 
 ### Return type
 
-[**MultiRoleUpdateSettings200Response**](MultiRoleUpdateSettings200Response.md)
+[**MultiRoleToggleRole200Response**](MultiRoleToggleRole200Response.md)
 
 ### Authorization
 
@@ -436,7 +436,7 @@ end
 
 ## multi_role_update_collection_permissions
 
-> <MultiRoleUpdateSettings200Response> multi_role_update_collection_permissions(project_id, role_slug, collection_id, multi_role_update_collection_permissions_request)
+> <MultiRoleToggleRole200Response> multi_role_update_collection_permissions(project_id, role_slug, collection_id, multi_role_update_collection_permissions_request)
 
 Update collection permissions for a role
 
@@ -455,7 +455,7 @@ end
 
 api_instance = Mudbase::MultiRoleApi.new
 project_id = '685ad30be129932fbb7a1047' # String | Project ID.
-role_slug = 'vendor' # String | Role slug (e.g. vendor, customer).
+role_slug = 'customer' # String | Role slug (e.g. starter `customer` or a role you added).
 collection_id = '696ba6e4f4a9422ac4be4f74' # String | Collection ID to set permissions for.
 multi_role_update_collection_permissions_request = Mudbase::MultiRoleUpdateCollectionPermissionsRequest.new # MultiRoleUpdateCollectionPermissionsRequest | Allowed actions and optional conditions for the role on this collection.
 
@@ -472,7 +472,7 @@ end
 
 This returns an Array which contains the response data, status code and headers.
 
-> <Array(<MultiRoleUpdateSettings200Response>, Integer, Hash)> multi_role_update_collection_permissions_with_http_info(project_id, role_slug, collection_id, multi_role_update_collection_permissions_request)
+> <Array(<MultiRoleToggleRole200Response>, Integer, Hash)> multi_role_update_collection_permissions_with_http_info(project_id, role_slug, collection_id, multi_role_update_collection_permissions_request)
 
 ```ruby
 begin
@@ -480,7 +480,7 @@ begin
   data, status_code, headers = api_instance.multi_role_update_collection_permissions_with_http_info(project_id, role_slug, collection_id, multi_role_update_collection_permissions_request)
   p status_code # => 2xx
   p headers # => { ... }
-  p data # => <MultiRoleUpdateSettings200Response>
+  p data # => <MultiRoleToggleRole200Response>
 rescue Mudbase::ApiError => e
   puts "Error when calling MultiRoleApi->multi_role_update_collection_permissions_with_http_info: #{e}"
 end
@@ -491,13 +491,13 @@ end
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
 | **project_id** | **String** | Project ID. |  |
-| **role_slug** | **String** | Role slug (e.g. vendor, customer). |  |
+| **role_slug** | **String** | Role slug (e.g. starter &#x60;customer&#x60; or a role you added). |  |
 | **collection_id** | **String** | Collection ID to set permissions for. |  |
 | **multi_role_update_collection_permissions_request** | [**MultiRoleUpdateCollectionPermissionsRequest**](MultiRoleUpdateCollectionPermissionsRequest.md) | Allowed actions and optional conditions for the role on this collection. |  |
 
 ### Return type
 
-[**MultiRoleUpdateSettings200Response**](MultiRoleUpdateSettings200Response.md)
+[**MultiRoleToggleRole200Response**](MultiRoleToggleRole200Response.md)
 
 ### Authorization
 
@@ -511,11 +511,11 @@ end
 
 ## multi_role_update_role
 
-> <MultiRoleUpdateSettings200Response> multi_role_update_role(project_id, role_slug, multi_role_update_role_request)
+> <MultiRoleToggleRole200Response> multi_role_update_role(project_id, role_slug, multi_role_update_role_request)
 
 Update role configuration
 
-Update an existing role's metadata and requirements (name, description, hierarchy, approval/payment/KYC flags).
+Update an app role — same fields as **Add custom role** (partial). `defaultPermissions` / `collectionPermissions` use the same normalization as on create.
 
 ### Examples
 
@@ -530,8 +530,8 @@ end
 
 api_instance = Mudbase::MultiRoleApi.new
 project_id = '685ad30be129932fbb7a1047' # String | Project ID.
-role_slug = 'vendor' # String | Role slug to update (e.g. vendor, customer).
-multi_role_update_role_request = Mudbase::MultiRoleUpdateRoleRequest.new # MultiRoleUpdateRoleRequest | Role fields to update (name, description, hierarchy, requiresApproval, requiresPayment, requiresKYC).
+role_slug = 'customer' # String | Role slug to update (e.g. starter `customer` or a role you added).
+multi_role_update_role_request = Mudbase::MultiRoleUpdateRoleRequest.new # MultiRoleUpdateRoleRequest | Same fields as **Add custom role** — send only fields you want to change. `defaultPermissions` / `collectionPermissions` are normalized the same way as on create.
 
 begin
   # Update role configuration
@@ -546,7 +546,7 @@ end
 
 This returns an Array which contains the response data, status code and headers.
 
-> <Array(<MultiRoleUpdateSettings200Response>, Integer, Hash)> multi_role_update_role_with_http_info(project_id, role_slug, multi_role_update_role_request)
+> <Array(<MultiRoleToggleRole200Response>, Integer, Hash)> multi_role_update_role_with_http_info(project_id, role_slug, multi_role_update_role_request)
 
 ```ruby
 begin
@@ -554,7 +554,7 @@ begin
   data, status_code, headers = api_instance.multi_role_update_role_with_http_info(project_id, role_slug, multi_role_update_role_request)
   p status_code # => 2xx
   p headers # => { ... }
-  p data # => <MultiRoleUpdateSettings200Response>
+  p data # => <MultiRoleToggleRole200Response>
 rescue Mudbase::ApiError => e
   puts "Error when calling MultiRoleApi->multi_role_update_role_with_http_info: #{e}"
 end
@@ -565,12 +565,12 @@ end
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
 | **project_id** | **String** | Project ID. |  |
-| **role_slug** | **String** | Role slug to update (e.g. vendor, customer). |  |
-| **multi_role_update_role_request** | [**MultiRoleUpdateRoleRequest**](MultiRoleUpdateRoleRequest.md) | Role fields to update (name, description, hierarchy, requiresApproval, requiresPayment, requiresKYC). |  |
+| **role_slug** | **String** | Role slug to update (e.g. starter &#x60;customer&#x60; or a role you added). |  |
+| **multi_role_update_role_request** | [**MultiRoleUpdateRoleRequest**](MultiRoleUpdateRoleRequest.md) | Same fields as **Add custom role** — send only fields you want to change. &#x60;defaultPermissions&#x60; / &#x60;collectionPermissions&#x60; are normalized the same way as on create. |  |
 
 ### Return type
 
-[**MultiRoleUpdateSettings200Response**](MultiRoleUpdateSettings200Response.md)
+[**MultiRoleToggleRole200Response**](MultiRoleToggleRole200Response.md)
 
 ### Authorization
 
@@ -588,7 +588,7 @@ end
 
 Update multi-role feature settings
 
-Update multi-role feature settings for a project, including enabling/disabling the feature and configuring default roles. Accepts BearerToken (JWT) or ApiKeyAuth (X-API-Key). 
+Update multi-role feature settings: enable/disable the feature, `defaultRole`, and `settings` (`allowMultipleRoles`, `requireRoleSelection`, `autoAssignDefault`). Does not edit role definitions — use `POST/PATCH .../multi-role/roles` (same body shape as add role). Accepts BearerToken (JWT) or ApiKeyAuth (X-API-Key). 
 
 ### Examples
 
@@ -603,7 +603,7 @@ end
 
 api_instance = Mudbase::MultiRoleApi.new
 project_id = '685ad30be129932fbb7a1047' # String | Project ID.
-multi_role_update_settings_request = Mudbase::MultiRoleUpdateSettingsRequest.new # MultiRoleUpdateSettingsRequest | Multi-role settings (e.g. isEnabled, defaultRole, allowMultipleRoles, requireApproval).
+multi_role_update_settings_request = Mudbase::MultiRoleUpdateSettingsRequest.new # MultiRoleUpdateSettingsRequest | Feature flags only — not per-role approval. Use `settings.allowMultipleRoles`, `requireRoleSelection`, `autoAssignDefault`.
 
 begin
   # Update multi-role feature settings
@@ -637,7 +637,7 @@ end
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
 | **project_id** | **String** | Project ID. |  |
-| **multi_role_update_settings_request** | [**MultiRoleUpdateSettingsRequest**](MultiRoleUpdateSettingsRequest.md) | Multi-role settings (e.g. isEnabled, defaultRole, allowMultipleRoles, requireApproval). |  |
+| **multi_role_update_settings_request** | [**MultiRoleUpdateSettingsRequest**](MultiRoleUpdateSettingsRequest.md) | Feature flags only — not per-role approval. Use &#x60;settings.allowMultipleRoles&#x60;, &#x60;requireRoleSelection&#x60;, &#x60;autoAssignDefault&#x60;. |  |
 
 ### Return type
 

data/docs/MultiRoleToggleRole200Response.md

@@ -0,0 +1,22 @@
+# Mudbase::MultiRoleToggleRole200Response
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **success** | **Boolean** |  | [optional] |
+| **message** | **String** |  | [optional] |
+| **data** | **Object** |  | [optional] |
+
+## Example
+
+```ruby
+require 'mudbase'
+
+instance = Mudbase::MultiRoleToggleRole200Response.new(
+  success: null,
+  message: null,
+  data: null
+)
+```
+

data/docs/MultiRoleUpdateRoleRequest.md

@@ -6,10 +6,13 @@
 | ---- | ---- | ----------- | ----- |
 | **name** | **String** |  | [optional] |
 | **description** | **String** |  | [optional] |
-| **hierarchy** | **Float** |  | [optional] |
+| **signup_endpoint** | **String** |  | [optional] |
 | **requires_approval** | **Boolean** |  | [optional] |
 | **requires_payment** | **Boolean** |  | [optional] |
 | **requires_kyc** | **Boolean** |  | [optional] |
+| **default_permissions** | **Array<Object>** |  | [optional] |
+| **collection_permissions** | [**Hash<String, MultiRoleUpdateRoleRequestCollectionPermissionsValue>**](MultiRoleUpdateRoleRequestCollectionPermissionsValue.md) | Per-collection CRUD map (same as POST add role). | [optional] |
+| **metadata** | **Object** |  | [optional] |
 
 ## Example
 
@@ -17,12 +20,15 @@
 require 'mudbase'
 
 instance = Mudbase::MultiRoleUpdateRoleRequest.new(
-  name: Vendor,
-  description: Vendor/seller role with enhanced permissions,
-  hierarchy: 35,
-  requires_approval: true,
-  requires_payment: true,
-  requires_kyc: false
+  name: App user,
+  description: End users of the app,
+  signup_endpoint: customer,
+  requires_approval: false,
+  requires_payment: false,
+  requires_kyc: false,
+  default_permissions: null,
+  collection_permissions: null,
+  metadata: null
 )
 ```
 

data/docs/MultiRoleUpdateRoleRequestCollectionPermissionsValue.md

@@ -0,0 +1,49 @@
+# Mudbase::MultiRoleUpdateRoleRequestCollectionPermissionsValue
+
+## Class instance methods
+
+### `openapi_one_of`
+
+Returns the list of classes defined in oneOf.
+
+#### Example
+
+```ruby
+require 'mudbase'
+
+Mudbase::MultiRoleUpdateRoleRequestCollectionPermissionsValue.openapi_one_of
+# =>
+# [
+#   :'Array<String>',
+#   :'MultiRoleUpdateRoleRequestCollectionPermissionsValueOneOf'
+# ]
+```
+
+### build
+
+Find the appropriate object from the `openapi_one_of` list and casts the data into it.
+
+#### Example
+
+```ruby
+require 'mudbase'
+
+Mudbase::MultiRoleUpdateRoleRequestCollectionPermissionsValue.build(data)
+# => #<Array<String>:0x00007fdd4aab02a0>
+
+Mudbase::MultiRoleUpdateRoleRequestCollectionPermissionsValue.build(data_that_doesnt_match)
+# => nil
+```
+
+#### Parameters
+
+| Name | Type | Description |
+| ---- | ---- | ----------- |
+| **data** | **Mixed** | data to be matched against the list of oneOf items |
+
+#### Return type
+
+- `Array<String>`
+- `MultiRoleUpdateRoleRequestCollectionPermissionsValueOneOf`
+- `nil` (if no type matches)
+

data/docs/MultiRoleUpdateRoleRequestCollectionPermissionsValueOneOf.md

@@ -0,0 +1,20 @@
+# Mudbase::MultiRoleUpdateRoleRequestCollectionPermissionsValueOneOf
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **actions** | **Array<String>** |  | [optional] |
+| **conditions** | **Object** |  | [optional] |
+
+## Example
+
+```ruby
+require 'mudbase'
+
+instance = Mudbase::MultiRoleUpdateRoleRequestCollectionPermissionsValueOneOf.new(
+  actions: null,
+  conditions: null
+)
+```
+

data/docs/MultiRoleUpdateSettings200Response.md

@@ -6,7 +6,7 @@
 | ---- | ---- | ----------- | ----- |
 | **success** | **Boolean** |  | [optional] |
 | **message** | **String** |  | [optional] |
-| **data** | **Object** |  | [optional] |
+| **data** | **Object** | Same shape as GET `/multi-role` — `isEnabled`, `defaultRole`, `settings`, and `roles` (no raw MultiRoleFeature document). | [optional] |
 
 ## Example
 

data/docs/MultiRoleUpdateSettingsRequestSettings.md

@@ -4,8 +4,9 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **allow_multiple_roles** | **Boolean** |  | [optional] |
-| **require_approval** | **Boolean** |  | [optional] |
+| **allow_multiple_roles** | **Boolean** | Whether an end user may hold multiple app roles. | [optional] |
+| **require_role_selection** | **Boolean** | If true, signup must pick a role; if false and `autoAssignDefault` is true, `defaultRole` is used when omitted. | [optional] |
+| **auto_assign_default** | **Boolean** | When true, assigns `defaultRole` when the client does not specify a role at signup. | [optional] |
 
 ## Example
 
@@ -14,7 +15,8 @@ require 'mudbase'
 
 instance = Mudbase::MultiRoleUpdateSettingsRequestSettings.new(
   allow_multiple_roles: null,
-  require_approval: null
+  require_role_selection: null,
+  auto_assign_default: null
 )
 ```
 

data/docs/RoleElevationApi.md

@@ -103,7 +103,7 @@ end
 
 api_instance = Mudbase::RoleElevationApi.new
 project_id = 'project_id_example' # String | Project ID.
-role_elevation_request_request = Mudbase::RoleElevationRequestRequest.new({role_slug: 'vendor'}) # RoleElevationRequestRequest | Role slug to request elevation to (e.g. vendor).
+role_elevation_request_request = Mudbase::RoleElevationRequestRequest.new({role_slug: 'seller'}) # RoleElevationRequestRequest | Role slug to request elevation to (e.g. a higher-privilege role you configured).
 
 begin
   # Request role elevation
@@ -137,7 +137,7 @@ end
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
 | **project_id** | **String** | Project ID. |  |
-| **role_elevation_request_request** | [**RoleElevationRequestRequest**](RoleElevationRequestRequest.md) | Role slug to request elevation to (e.g. vendor). |  |
+| **role_elevation_request_request** | [**RoleElevationRequestRequest**](RoleElevationRequestRequest.md) | Role slug to request elevation to (e.g. a higher-privilege role you configured). |  |
 
 ### Return type
 

data/docs/RoleElevationRequestRequest.md

@@ -12,7 +12,7 @@
 require 'mudbase'
 
 instance = Mudbase::RoleElevationRequestRequest.new(
-  role_slug: vendor
+  role_slug: seller
 )
 ```
 

data/lib/mudbase/api/auth_api.rb

@@ -3,7 +3,7 @@
 
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: Flutterwave only for fiat (platform subscriptions + org payment processing with 7% + $0.50 split); crypto payment processor for multi-chain checkout - 📡 Block-based multi-chain wallet monitoring (ETH/UTXO scanners, GetBlock, scanner metrics API) 
 
-The version of the OpenAPI document: 1.2.7
+The version of the OpenAPI document: 1.2.8
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0

data/lib/mudbase/api/billing_api.rb

@@ -3,7 +3,7 @@
 
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: Flutterwave only for fiat (platform subscriptions + org payment processing with 7% + $0.50 split); crypto payment processor for multi-chain checkout - 📡 Block-based multi-chain wallet monitoring (ETH/UTXO scanners, GetBlock, scanner metrics API) 
 
-The version of the OpenAPI document: 1.2.7
+The version of the OpenAPI document: 1.2.8
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0

data/lib/mudbase/api/chat_api.rb

@@ -3,7 +3,7 @@
 
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: Flutterwave only for fiat (platform subscriptions + org payment processing with 7% + $0.50 split); crypto payment processor for multi-chain checkout - 📡 Block-based multi-chain wallet monitoring (ETH/UTXO scanners, GetBlock, scanner metrics API) 
 
-The version of the OpenAPI document: 1.2.7
+The version of the OpenAPI document: 1.2.8
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0

data/lib/mudbase/api/collections_api.rb

@@ -3,7 +3,7 @@
 
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: Flutterwave only for fiat (platform subscriptions + org payment processing with 7% + $0.50 split); crypto payment processor for multi-chain checkout - 📡 Block-based multi-chain wallet monitoring (ETH/UTXO scanners, GetBlock, scanner metrics API) 
 
-The version of the OpenAPI document: 1.2.7
+The version of the OpenAPI document: 1.2.8
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0

data/lib/mudbase/api/compliance_api.rb

@@ -3,7 +3,7 @@
 
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: Flutterwave only for fiat (platform subscriptions + org payment processing with 7% + $0.50 split); crypto payment processor for multi-chain checkout - 📡 Block-based multi-chain wallet monitoring (ETH/UTXO scanners, GetBlock, scanner metrics API) 
 
-The version of the OpenAPI document: 1.2.7
+The version of the OpenAPI document: 1.2.8
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0

data/lib/mudbase/api/data_api.rb

@@ -3,7 +3,7 @@
 
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: Flutterwave only for fiat (platform subscriptions + org payment processing with 7% + $0.50 split); crypto payment processor for multi-chain checkout - 📡 Block-based multi-chain wallet monitoring (ETH/UTXO scanners, GetBlock, scanner metrics API) 
 
-The version of the OpenAPI document: 1.2.7
+The version of the OpenAPI document: 1.2.8
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0

data/lib/mudbase/api/functions_api.rb

@@ -3,7 +3,7 @@
 
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: Flutterwave only for fiat (platform subscriptions + org payment processing with 7% + $0.50 split); crypto payment processor for multi-chain checkout - 📡 Block-based multi-chain wallet monitoring (ETH/UTXO scanners, GetBlock, scanner metrics API) 
 
-The version of the OpenAPI document: 1.2.7
+The version of the OpenAPI document: 1.2.8
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0

data/lib/mudbase/api/health_api.rb

@@ -3,7 +3,7 @@
 
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: Flutterwave only for fiat (platform subscriptions + org payment processing with 7% + $0.50 split); crypto payment processor for multi-chain checkout - 📡 Block-based multi-chain wallet monitoring (ETH/UTXO scanners, GetBlock, scanner metrics API) 
 
-The version of the OpenAPI document: 1.2.7
+The version of the OpenAPI document: 1.2.8
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0

data/lib/mudbase/api/integrations_api.rb

@@ -3,7 +3,7 @@
 
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: Flutterwave only for fiat (platform subscriptions + org payment processing with 7% + $0.50 split); crypto payment processor for multi-chain checkout - 📡 Block-based multi-chain wallet monitoring (ETH/UTXO scanners, GetBlock, scanner metrics API) 
 
-The version of the OpenAPI document: 1.2.7
+The version of the OpenAPI document: 1.2.8
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0

data/lib/mudbase/api/messaging_api.rb

@@ -3,7 +3,7 @@
 
 #MUDBASE is a scalable, real-time, and secure Backend-as-a-Service (BaaS) platform  designed for modern applications. Built with custom logic, it offers fine-grained  control, extensibility, and enterprise-grade security.  ## Features - 🔐 Multi-provider authentication (30+ OAuth providers) - 📊 Real-time database with collections - 📁 File storage and management - 🔑 API key management with permissions - 🔗 Webhook system with retry logic - ⚡ Serverless functions - 💬 Multi-channel messaging (Push, Email, SMS) - 📈 Usage analytics and monitoring - 🌐 Real-time WebSocket events - 🔍 Full-text search capabilities - 💳 Billing: Flutterwave only for fiat (platform subscriptions + org payment processing with 7% + $0.50 split); crypto payment processor for multi-chain checkout - 📡 Block-based multi-chain wallet monitoring (ETH/UTXO scanners, GetBlock, scanner metrics API) 
 
-The version of the OpenAPI document: 1.2.7
+The version of the OpenAPI document: 1.2.8
 Contact: support@mudbase.dev
 Generated by: https://openapi-generator.tech
 Generator version: 7.20.0