RubyGems - mudbase - Versions diffs - 1.2.12 → 1.3.0 - Mend

mudbase 1.2.12 → 1.3.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (2558) hide show

data/docs/MultiRoleApi.md DELETED Viewed

@@ -1,869 +0,0 @@
-# Mudbase::MultiRoleApi
-All URIs are relative to *https://cloud.mudbase.dev*
-| Method | HTTP request | Description |
-| ------ | ------------ | ----------- |
-| [**auth_oauth_signup_with_role**](MultiRoleApi.md#auth_oauth_signup_with_role) | **GET** /api/auth/oauth/signup/{role}/{provider}/{projectId} | OAuth signup with specific role |
-| [**auth_register_with_role**](MultiRoleApi.md#auth_register_with_role) | **POST** /api/auth/local/signup/{role} | Register user with specific role (Local Auth) |
-| [**multi_role_add_role**](MultiRoleApi.md#multi_role_add_role) | **POST** /api/projects/{projectId}/multi-role/roles | Add custom role |
-| [**multi_role_apply_role_feature_preset**](MultiRoleApi.md#multi_role_apply_role_feature_preset) | **POST** /api/projects/{projectId}/multi-role/roles/{roleSlug}/apply-preset | Apply Admin / User / Viewer feature permission preset |
-| [**multi_role_get_available_roles**](MultiRoleApi.md#multi_role_get_available_roles) | **GET** /api/projects/{projectId}/multi-role/roles/available | Get available roles for signup |
-| [**multi_role_get_config**](MultiRoleApi.md#multi_role_get_config) | **GET** /api/projects/{projectId}/multi-role | Get multi-role feature configuration |
-| [**multi_role_get_permissions_matrix**](MultiRoleApi.md#multi_role_get_permissions_matrix) | **GET** /api/projects/{projectId}/permissions-matrix | Get permissions matrix (collections + featurePermissions) |
-| [**multi_role_simulate_app_permissions**](MultiRoleApi.md#multi_role_simulate_app_permissions) | **POST** /api/projects/{projectId}/multi-role/simulate-permissions | Simulate app-role feature permission for a path |
-| [**multi_role_toggle_role**](MultiRoleApi.md#multi_role_toggle_role) | **PATCH** /api/projects/{projectId}/multi-role/roles/{roleSlug}/toggle | Toggle role on/off |
-| [**multi_role_update_collection_permissions**](MultiRoleApi.md#multi_role_update_collection_permissions) | **PATCH** /api/projects/{projectId}/multi-role/roles/{roleSlug}/collections/{collectionId}/permissions | Update collection permissions for a role |
-| [**multi_role_update_role**](MultiRoleApi.md#multi_role_update_role) | **PATCH** /api/projects/{projectId}/multi-role/roles/{roleSlug} | Update role configuration |
-| [**multi_role_update_settings**](MultiRoleApi.md#multi_role_update_settings) | **PATCH** /api/projects/{projectId}/multi-role/settings | Update multi-role feature settings |
-## auth_oauth_signup_with_role
-> <UsersLinkOAuthProvider200Response> auth_oauth_signup_with_role(role, provider, project_id, opts)
-OAuth signup with specific role
-Public endpoint that initiates OAuth signup flow with a specific role assigned during registration. The OAuth provider must be configured and enabled for the project first. The role must be available for signup in the project's multi-role configuration. After successful OAuth authentication, the user will be created with the specified role. No authentication required - this is a public signup endpoint.
-### Examples
-```ruby
-require 'time'
-require 'mudbase'
-api_instance = Mudbase::MultiRoleApi.new
-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 = {
-  redirect_url: 'https://client.app/auth/callback' # String | The URL to redirect to after authentication
-}
-begin
-  # OAuth signup with specific role
-  result = api_instance.auth_oauth_signup_with_role(role, provider, project_id, opts)
-  p result
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->auth_oauth_signup_with_role: #{e}"
-end
-```
-#### Using the auth_oauth_signup_with_role_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<UsersLinkOAuthProvider200Response>, Integer, Hash)> auth_oauth_signup_with_role_with_http_info(role, provider, project_id, opts)
-```ruby
-begin
-  # OAuth signup with specific role
-  data, status_code, headers = api_instance.auth_oauth_signup_with_role_with_http_info(role, provider, project_id, opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <UsersLinkOAuthProvider200Response>
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->auth_oauth_signup_with_role_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **role** | **String** | Path segment must match the role&#39;s &#x60;signupEndpoint&#x60; (default &#x60;customer&#x60;; use each role&#39;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] |
-### Return type
-[**UsersLinkOAuthProvider200Response**](UsersLinkOAuthProvider200Response.md)
-### Authorization
-No authorization required
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json
-## auth_register_with_role
-> auth_register_with_role(role, auth_register_with_role_request)
-Register user with specific role (Local Auth)
-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
-```ruby
-require 'time'
-require 'mudbase'
-api_instance = Mudbase::MultiRoleApi.new
-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
-  # Register user with specific role (Local Auth)
-  api_instance.auth_register_with_role(role, auth_register_with_role_request)
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->auth_register_with_role: #{e}"
-end
-```
-#### Using the auth_register_with_role_with_http_info variant
-This returns an Array which contains the response data (`nil` in this case), status code and headers.
-> <Array(nil, Integer, Hash)> auth_register_with_role_with_http_info(role, auth_register_with_role_request)
-```ruby
-begin
-  # Register user with specific role (Local Auth)
-  data, status_code, headers = api_instance.auth_register_with_role_with_http_info(role, auth_register_with_role_request)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => nil
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->auth_register_with_role_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **role** | **String** | Must match the role&#39;s &#x60;signupEndpoint&#x60; (default &#x60;customer&#x60;; other values for roles you add). |  |
-| **auth_register_with_role_request** | [**AuthRegisterWithRoleRequest**](AuthRegisterWithRoleRequest.md) | Registration payload (email, password, firstName, lastName, projectId). |  |
-### Return type
-nil (empty response body)
-### Authorization
-No authorization required
-### HTTP request headers
-- **Content-Type**: application/json
-- **Accept**: application/json
-## multi_role_add_role
-> <MultiRoleToggleRole200Response> multi_role_add_role(project_id, multi_role_add_role_request)
-Add custom role
-Add a custom role to a project with specific permissions and signup endpoint. Optional **featurePermissions** must align with app JWT gates — see schema `AppRoleFeaturePermissions`. Accepts BearerToken (JWT) or ApiKeyAuth (X-API-Key).
-### Examples
-```ruby
-require 'time'
-require 'mudbase'
-# setup authorization
-Mudbase.configure do |config|
-  # Configure Bearer authorization (JWT): BearerToken
-  config.access_token = 'YOUR_BEARER_TOKEN'
-end
-api_instance = Mudbase::MultiRoleApi.new
-project_id = '685ad30be129932fbb7a1047' # String | Project ID.
-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
-  result = api_instance.multi_role_add_role(project_id, multi_role_add_role_request)
-  p result
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->multi_role_add_role: #{e}"
-end
-```
-#### Using the multi_role_add_role_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<MultiRoleToggleRole200Response>, Integer, Hash)> multi_role_add_role_with_http_info(project_id, multi_role_add_role_request)
-```ruby
-begin
-  # Add custom role
-  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 # => <MultiRoleToggleRole200Response>
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->multi_role_add_role_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **project_id** | **String** | Project ID. |  |
-| **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
-[**MultiRoleToggleRole200Response**](MultiRoleToggleRole200Response.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: application/json
-- **Accept**: application/json
-## multi_role_apply_role_feature_preset
-> multi_role_apply_role_feature_preset(project_id, role_slug, multi_role_apply_role_feature_preset_request)
-Apply Admin / User / Viewer feature permission preset
-Sets `featurePermissions` from preset `admin`, `user`, or `viewer`.
-### Examples
-```ruby
-require 'time'
-require 'mudbase'
-# setup authorization
-Mudbase.configure do |config|
-  # Configure Bearer authorization (JWT): BearerToken
-  config.access_token = 'YOUR_BEARER_TOKEN'
-end
-api_instance = Mudbase::MultiRoleApi.new
-project_id = 'project_id_example' # String | Project ID.
-role_slug = 'role_slug_example' # String | Role slug to apply the preset to (e.g. `customer`).
-multi_role_apply_role_feature_preset_request = Mudbase::MultiRoleApplyRoleFeaturePresetRequest.new({preset: 'admin'}) # MultiRoleApplyRoleFeaturePresetRequest | JSON body with `preset` set to `admin`, `user`, or `viewer`.
-begin
-  # Apply Admin / User / Viewer feature permission preset
-  api_instance.multi_role_apply_role_feature_preset(project_id, role_slug, multi_role_apply_role_feature_preset_request)
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->multi_role_apply_role_feature_preset: #{e}"
-end
-```
-#### Using the multi_role_apply_role_feature_preset_with_http_info variant
-This returns an Array which contains the response data (`nil` in this case), status code and headers.
-> <Array(nil, Integer, Hash)> multi_role_apply_role_feature_preset_with_http_info(project_id, role_slug, multi_role_apply_role_feature_preset_request)
-```ruby
-begin
-  # Apply Admin / User / Viewer feature permission preset
-  data, status_code, headers = api_instance.multi_role_apply_role_feature_preset_with_http_info(project_id, role_slug, multi_role_apply_role_feature_preset_request)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => nil
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->multi_role_apply_role_feature_preset_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **project_id** | **String** | Project ID. |  |
-| **role_slug** | **String** | Role slug to apply the preset to (e.g. &#x60;customer&#x60;). |  |
-| **multi_role_apply_role_feature_preset_request** | [**MultiRoleApplyRoleFeaturePresetRequest**](MultiRoleApplyRoleFeaturePresetRequest.md) | JSON body with &#x60;preset&#x60; set to &#x60;admin&#x60;, &#x60;user&#x60;, or &#x60;viewer&#x60;. |  |
-### Return type
-nil (empty response body)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: application/json
-- **Accept**: application/json
-## multi_role_get_available_roles
-> <MultiRoleGetAvailableRoles200Response> multi_role_get_available_roles(project_id)
-Get available roles for signup
-Get all available roles for user signup in a project. Accepts BearerToken (JWT) or ApiKeyAuth (X-API-Key).
-### Examples
-```ruby
-require 'time'
-require 'mudbase'
-# setup authorization
-Mudbase.configure do |config|
-  # Configure Bearer authorization (JWT): BearerToken
-  config.access_token = 'YOUR_BEARER_TOKEN'
-end
-api_instance = Mudbase::MultiRoleApi.new
-project_id = '685ad30be129932fbb7a1047' # String | Project ID.
-begin
-  # Get available roles for signup
-  result = api_instance.multi_role_get_available_roles(project_id)
-  p result
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->multi_role_get_available_roles: #{e}"
-end
-```
-#### Using the multi_role_get_available_roles_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<MultiRoleGetAvailableRoles200Response>, Integer, Hash)> multi_role_get_available_roles_with_http_info(project_id)
-```ruby
-begin
-  # Get available roles for signup
-  data, status_code, headers = api_instance.multi_role_get_available_roles_with_http_info(project_id)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <MultiRoleGetAvailableRoles200Response>
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->multi_role_get_available_roles_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **project_id** | **String** | Project ID. |  |
-### Return type
-[**MultiRoleGetAvailableRoles200Response**](MultiRoleGetAvailableRoles200Response.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json
-## multi_role_get_config
-> <MultiRoleGetConfig200Response> multi_role_get_config(project_id)
-Get multi-role feature configuration
-Returns project app roles (default one editable `customer` starter until you add more) and settings.
-### Examples
-```ruby
-require 'time'
-require 'mudbase'
-# setup authorization
-Mudbase.configure do |config|
-  # Configure Bearer authorization (JWT): BearerToken
-  config.access_token = 'YOUR_BEARER_TOKEN'
-end
-api_instance = Mudbase::MultiRoleApi.new
-project_id = '685ad30be129932fbb7a1047' # String | Project ID.
-begin
-  # Get multi-role feature configuration
-  result = api_instance.multi_role_get_config(project_id)
-  p result
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->multi_role_get_config: #{e}"
-end
-```
-#### Using the multi_role_get_config_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<MultiRoleGetConfig200Response>, Integer, Hash)> multi_role_get_config_with_http_info(project_id)
-```ruby
-begin
-  # Get multi-role feature configuration
-  data, status_code, headers = api_instance.multi_role_get_config_with_http_info(project_id)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <MultiRoleGetConfig200Response>
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->multi_role_get_config_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **project_id** | **String** | Project ID. |  |
-### Return type
-[**MultiRoleGetConfig200Response**](MultiRoleGetConfig200Response.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json
-## multi_role_get_permissions_matrix
-> <MultiRoleGetPermissionsMatrix200Response> multi_role_get_permissions_matrix(project_id)
-Get permissions matrix (collections + featurePermissions)
-Per-collection role actions and per-role `featurePermissions` for app-role gates.
-### Examples
-```ruby
-require 'time'
-require 'mudbase'
-# setup authorization
-Mudbase.configure do |config|
-  # Configure Bearer authorization (JWT): BearerToken
-  config.access_token = 'YOUR_BEARER_TOKEN'
-end
-api_instance = Mudbase::MultiRoleApi.new
-project_id = '685ad30be129932fbb7a1047' # String | Project ID whose multi-role matrix is returned.
-begin
-  # Get permissions matrix (collections + featurePermissions)
-  result = api_instance.multi_role_get_permissions_matrix(project_id)
-  p result
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->multi_role_get_permissions_matrix: #{e}"
-end
-```
-#### Using the multi_role_get_permissions_matrix_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<MultiRoleGetPermissionsMatrix200Response>, Integer, Hash)> multi_role_get_permissions_matrix_with_http_info(project_id)
-```ruby
-begin
-  # Get permissions matrix (collections + featurePermissions)
-  data, status_code, headers = api_instance.multi_role_get_permissions_matrix_with_http_info(project_id)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <MultiRoleGetPermissionsMatrix200Response>
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->multi_role_get_permissions_matrix_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **project_id** | **String** | Project ID whose multi-role matrix is returned. |  |
-### Return type
-[**MultiRoleGetPermissionsMatrix200Response**](MultiRoleGetPermissionsMatrix200Response.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: Not defined
-- **Accept**: application/json
-## multi_role_simulate_app_permissions
-> Object multi_role_simulate_app_permissions(project_id, multi_role_simulate_app_permissions_request)
-Simulate app-role feature permission for a path
-Given role slug and either `operationId` or HTTP method + pathname, returns whether `featurePermissions` would allow gated routes. Unmapped paths or unknown operation IDs return allowed with `no_feature_gate_for_path` or `no_feature_gate_for_operation_id`.
-### Examples
-```ruby
-require 'time'
-require 'mudbase'
-# setup authorization
-Mudbase.configure do |config|
-  # Configure Bearer authorization (JWT): BearerToken
-  config.access_token = 'YOUR_BEARER_TOKEN'
-end
-api_instance = Mudbase::MultiRoleApi.new
-project_id = 'project_id_example' # String | Project ID used to resolve role configuration.
-multi_role_simulate_app_permissions_request = Mudbase::MultiRoleSimulateAppPermissionsRequest.new({role: 'role_example'}) # MultiRoleSimulateAppPermissionsRequest | Role slug plus either OpenAPI `operationId` or HTTP `method` and `pathname` to evaluate.
-begin
-  # Simulate app-role feature permission for a path
-  result = api_instance.multi_role_simulate_app_permissions(project_id, multi_role_simulate_app_permissions_request)
-  p result
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->multi_role_simulate_app_permissions: #{e}"
-end
-```
-#### Using the multi_role_simulate_app_permissions_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(Object, Integer, Hash)> multi_role_simulate_app_permissions_with_http_info(project_id, multi_role_simulate_app_permissions_request)
-```ruby
-begin
-  # Simulate app-role feature permission for a path
-  data, status_code, headers = api_instance.multi_role_simulate_app_permissions_with_http_info(project_id, multi_role_simulate_app_permissions_request)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => Object
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->multi_role_simulate_app_permissions_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **project_id** | **String** | Project ID used to resolve role configuration. |  |
-| **multi_role_simulate_app_permissions_request** | [**MultiRoleSimulateAppPermissionsRequest**](MultiRoleSimulateAppPermissionsRequest.md) | Role slug plus either OpenAPI &#x60;operationId&#x60; or HTTP &#x60;method&#x60; and &#x60;pathname&#x60; to evaluate. |  |
-### Return type
-**Object**
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: application/json
-- **Accept**: application/json
-## multi_role_toggle_role
-> <MultiRoleToggleRole200Response> multi_role_toggle_role(project_id, role_slug, multi_role_toggle_role_request)
-Toggle role on/off
-Enable or disable a role for the project. When disabled, the role is no longer available for signup or assignment.
-### Examples
-```ruby
-require 'time'
-require 'mudbase'
-# setup authorization
-Mudbase.configure do |config|
-  # Configure Bearer authorization (JWT): BearerToken
-  config.access_token = 'YOUR_BEARER_TOKEN'
-end
-api_instance = Mudbase::MultiRoleApi.new
-project_id = '685ad30be129932fbb7a1047' # String | Project ID.
-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
-  # Toggle role on/off
-  result = api_instance.multi_role_toggle_role(project_id, role_slug, multi_role_toggle_role_request)
-  p result
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->multi_role_toggle_role: #{e}"
-end
-```
-#### Using the multi_role_toggle_role_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<MultiRoleToggleRole200Response>, Integer, Hash)> multi_role_toggle_role_with_http_info(project_id, role_slug, multi_role_toggle_role_request)
-```ruby
-begin
-  # Toggle role on/off
-  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 # => <MultiRoleToggleRole200Response>
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->multi_role_toggle_role_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **project_id** | **String** | Project ID. |  |
-| **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
-[**MultiRoleToggleRole200Response**](MultiRoleToggleRole200Response.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: application/json
-- **Accept**: application/json
-## multi_role_update_collection_permissions
-> <MultiRoleToggleRole200Response> multi_role_update_collection_permissions(project_id, role_slug, collection_id, multi_role_update_collection_permissions_request)
-Update collection permissions for a role
-Update collection-specific permissions for a role in a project. Accepts BearerToken (JWT) or ApiKeyAuth (X-API-Key).
-### Examples
-```ruby
-require 'time'
-require 'mudbase'
-# setup authorization
-Mudbase.configure do |config|
-  # Configure Bearer authorization (JWT): BearerToken
-  config.access_token = 'YOUR_BEARER_TOKEN'
-end
-api_instance = Mudbase::MultiRoleApi.new
-project_id = '685ad30be129932fbb7a1047' # String | Project ID.
-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.
-begin
-  # Update collection permissions for a role
-  result = api_instance.multi_role_update_collection_permissions(project_id, role_slug, collection_id, multi_role_update_collection_permissions_request)
-  p result
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->multi_role_update_collection_permissions: #{e}"
-end
-```
-#### Using the multi_role_update_collection_permissions_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <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
-  # Update collection permissions for a role
-  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 # => <MultiRoleToggleRole200Response>
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->multi_role_update_collection_permissions_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **project_id** | **String** | Project ID. |  |
-| **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
-[**MultiRoleToggleRole200Response**](MultiRoleToggleRole200Response.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: application/json
-- **Accept**: application/json
-## multi_role_update_role
-> <MultiRoleToggleRole200Response> multi_role_update_role(project_id, role_slug, multi_role_update_role_request)
-Update role configuration
-Update an app role — same fields as **Add custom role** (partial). `defaultPermissions` / `collectionPermissions` use the same normalization as on create. **featurePermissions:** see schema `AppRoleFeaturePermissions`.
-### Examples
-```ruby
-require 'time'
-require 'mudbase'
-# setup authorization
-Mudbase.configure do |config|
-  # Configure Bearer authorization (JWT): BearerToken
-  config.access_token = 'YOUR_BEARER_TOKEN'
-end
-api_instance = Mudbase::MultiRoleApi.new
-project_id = '685ad30be129932fbb7a1047' # String | Project ID.
-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
-  result = api_instance.multi_role_update_role(project_id, role_slug, multi_role_update_role_request)
-  p result
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->multi_role_update_role: #{e}"
-end
-```
-#### Using the multi_role_update_role_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<MultiRoleToggleRole200Response>, Integer, Hash)> multi_role_update_role_with_http_info(project_id, role_slug, multi_role_update_role_request)
-```ruby
-begin
-  # Update role configuration
-  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 # => <MultiRoleToggleRole200Response>
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->multi_role_update_role_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **project_id** | **String** | Project ID. |  |
-| **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
-[**MultiRoleToggleRole200Response**](MultiRoleToggleRole200Response.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: application/json
-- **Accept**: application/json
-## multi_role_update_settings
-> <MultiRoleUpdateSettings200Response> multi_role_update_settings(project_id, multi_role_update_settings_request)
-Update multi-role feature settings
-Update multi-role feature settings: enable/disable the feature, `defaultRole`, and `settings` (`allowMultipleRoles`, `requireRoleSelection`, `autoAssignDefault`, `dataOwnerField`). 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
-```ruby
-require 'time'
-require 'mudbase'
-# setup authorization
-Mudbase.configure do |config|
-  # Configure Bearer authorization (JWT): BearerToken
-  config.access_token = 'YOUR_BEARER_TOKEN'
-end
-api_instance = Mudbase::MultiRoleApi.new
-project_id = '685ad30be129932fbb7a1047' # String | Project ID.
-multi_role_update_settings_request = Mudbase::MultiRoleUpdateSettingsRequest.new # MultiRoleUpdateSettingsRequest | Feature flags only — not per-role approval. Use `settings.allowMultipleRoles`, `requireRoleSelection`, `autoAssignDefault`, `dataOwnerField`.
-begin
-  # Update multi-role feature settings
-  result = api_instance.multi_role_update_settings(project_id, multi_role_update_settings_request)
-  p result
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->multi_role_update_settings: #{e}"
-end
-```
-#### Using the multi_role_update_settings_with_http_info variant
-This returns an Array which contains the response data, status code and headers.
-> <Array(<MultiRoleUpdateSettings200Response>, Integer, Hash)> multi_role_update_settings_with_http_info(project_id, multi_role_update_settings_request)
-```ruby
-begin
-  # Update multi-role feature settings
-  data, status_code, headers = api_instance.multi_role_update_settings_with_http_info(project_id, multi_role_update_settings_request)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => <MultiRoleUpdateSettings200Response>
-rescue Mudbase::ApiError => e
-  puts "Error when calling MultiRoleApi->multi_role_update_settings_with_http_info: #{e}"
-end
-```
-### Parameters
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **project_id** | **String** | Project ID. |  |
-| **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;, &#x60;dataOwnerField&#x60;. |  |
-### Return type
-[**MultiRoleUpdateSettings200Response**](MultiRoleUpdateSettings200Response.md)
-### Authorization
-[BearerToken](../README.md#BearerToken)
-### HTTP request headers
-- **Content-Type**: application/json
-- **Accept**: application/json