For successful authentication it’s required to generate a JWT with proper brand scopes.*
Basic Setup
To embed the Brand Editor, install and import the required components and styles:Publishing Hook
Similar to the Template Editor, the Brand Editor also provides a publishing hook that allows you to customize the publishing behavior. You can use theuseBrandActions hook to programmatically trigger brand updates and integrate them with your application’s workflow.
useBrandActions must be used inside of the <BrandProvider /> contextTheming and Customization
Apply visual styles directly to match each tenant’s brand:BrandEditor Props
| Prop | Type | Default | Description |
|---|---|---|---|
autoSave | boolean | true | Automatically save changes as they’re made |
autoSaveDebounce | number | 200ms | Delay before triggering auto-save |
hidePublish | boolean | false | Hides the “Publish Changes” button |
onChange | (value: BrandSettings) => void | — | Callback when brand settings are modified |
theme | ThemeObj / cssClass | — | Theme object or CSS class name |
value | BrandSettings | — | Initial values like colors, logos, and links |
variables | Record<string, any> | — | Variables used in brand content (e.g. footers) |
Required Authentication Scopes
-
tenant:${TENANT_ID}:brand:read| Allows the user to read brand data for a specific tenant. -
tenant:${TENANT_ID}:brand:write| Allows the user to write brand data for a specific tenant.