Dashboard Appearance and Account Integrations

Open Settings and select Appearance or Integrations. These settings are separate from the storefront design and storefront tracking integrations.

Dashboard appearance

1. Open Appearance and review the available dashboard styles.
2. Select the desired style and wait for its save/confirmation.
3. Choose the offered light, dark or system color mode.
4. Use the reset/default action if you want the inherited platform appearance.
5. Navigate to another dashboard page and verify readability and saved appearance.

Appearance changes do not translate product content, change chatbot response language or alter the storefront theme. Use Storefront Design for customer-facing styling.

Standard and simplified forms

Open Settings > Appearance > Form experience and choose Standard forms or Simplified forms. Wait for the saved confirmation. This preference is separate from the dashboard style, navigation layout and light/dark mode.

• Standard forms shows all available settings and remains the default during the beta.
• Simplified forms shows essential inputs first. Open Advanced settings inside a supported form to reveal optional SEO, AI, media and technical controls.
• Use inherited default clears your personal choice and follows the tenant default, then the platform default.

The preference is personal: it does not force other team members to use your mode. Closing Advanced settings hides inputs without deleting their saved values. Inputs required for the selected task remain visible, and short or specialist forms may not need an Advanced control. Form controls use the selected panel language across the 18 supported languages.

Simplified mode covers the main catalog, services, content, storefront, shipping, notifications, widget, Chat Studio, connections, checkout and Auto Replies workflows. If a field seems missing, open Advanced settings or switch to Standard forms. Changing the form experience does not change permissions, plan allowances or public website content. During administrator impersonation, mode changes are a local preview and are not saved as the tenant's preference.

Account API key

The Integrations tab shows the current key's masked state and creation information, where available.

1. Generate a key only when you need it for an authorized integration.
2. Copy the newly displayed value into the intended integration securely.
3. Treat Regenerate as a key rotation: existing clients using the old key may stop working.
4. Revoke only when you intend to disable access through that key.
5. Test the specific integration after rotation or revocation.

Never place keys in Business Profile, Knowledge Base articles, public source code or support screenshots. A masked key display is not the full secret. Domain allowlists and other authorization requirements still apply.

Connection summaries

Review commerce and messaging connection summaries in this tab, then use their dedicated management screens for setup and diagnostics. An account key is not a marketplace token or a payment-gateway merchant key.

Verification and troubleshooting

If style changes do not persist, check save errors and the selected account. If an integration breaks after rotation, update its configured key and verify its allowed domain/permissions. Do not regenerate repeatedly while investigating a network failure.

See Widget, Connections, Messaging Channels and Storefront Integrations.