Appearance and Branding

Interface language

Choose your language in Account settings → General. The SaaS interface supports English, Czech, German, Spanish, French, Italian, Polish, Russian and Ukrainian. An explicit browser language choice takes precedence over a saved profile preference; without either, the app negotiates the browser language and falls back to English. Unsupported locale values are ignored.

Language changes affect interface labels, validation and system notifications, not text you authored on a page. New block defaults are localized when the block is created; changing language does not rewrite existing content. Invitation language hints are validated and passed to the hosted Logto screens; the normal callback and registration policy remain unchanged. Emails use the recipient's resolved language.

Your account: Appearance

Open Account settings → Appearance to choose your personal interface style: Page Default, RC Olive, RC Apricot, RC Ocean, RC Forest, RC Royal Purple, or RC Slate. Page Default has neutral white surfaces in light mode and graphite surfaces in dark mode. The other presets combine palettes and shapes: warm rounded olive, soft apricot curves, cool clean ocean blues, natural forest greens, elegant purple curves, or strict slate geometry. Palettes do not change fonts.

Your selection is stored locally for your user in this browser. Another user in the same browser has a separate preference. It does not change your organization's branding or what clients see on portal pages. There is no cross-device or cross-browser sync; clearing browser storage removes the saved preference. Reset to default still restores RC Olive, not Page Default, without changing organization branding or page color schemes.

Light and dark modes are independent

System, Light, and Dark are color-mode choices managed by next-themes, separately from the style preset. System follows your device's light/dark setting. Choosing a preset does not switch the color mode: you can use the same preset in either light or dark mode. Color mode is a browser preference, not a synchronized account setting.

Each page: Color scheme

In the editor's Page section, use Color scheme to choose a palette for that page. Only the page canvas and its client-facing rendering change; editor controls keep your personal Appearance. Other pages and the main interface stay unchanged. Ordinary page colors do not require a white-label entitlement.

The choice is saved with the page's versioned content. Draft changes do not alter the live page until you publish that version. Previewing or publishing an older version uses that version's choice.

Organization default means no explicit page palette. Missing settings on existing pages behave the same way: inherit the organization's branding when it is eligible under the existing white_label rules; otherwise use Page Default. This is inheritance, not a frozen copy of the organization's palette.

An explicit page palette takes precedence over the organization's palette and accent override, including when you explicitly choose Page Default. Eligible organization typography is maintained: a page palette does not change fonts. The organization name, logo, and resultspace identity remain governed by the existing white_label rules; changing ordinary page colors does not unlock or change white-label identity.

Your organization: Branding

Open Organization settings → General → Branding to choose the default style that clients see on public portal pages. This is an organization setting, not your personal Appearance preference. Saving it leaves your personal interface unchanged; pages with an explicit color scheme keep their own palette.

Organization branding applies only when the organization's white_label feature flag is enabled. Without that flag, pages keep the default resultspace identity and use Page Default unless a page has its own explicit palette. A personal Appearance or page Color scheme selection cannot enable or override white-label identity.

The organization's Style preset supplies the base palette and shapes. An explicit Accent color overrides its accent on pages inheriting the organization default. Typography is a separate setting, with Inter as the default; style palettes do not select a font. Click the selected accent swatch or font button again to clear that override. The two overrides are independent: you can keep a custom accent while inheriting the default font.

Organization branding is saved for the organization and shared with its portal visitors. The lack of cross-device sync applies to personal browser preferences, not to organization branding or versioned page color schemes. These settings do not copy into one another.

Page density

Open Organization settings → General → Page density to choose Compact, Standard, or Spacious. This controls the spacing between page blocks, not your personal interface, card padding, or section padding. Standard is the default. This setting does not require or enable white-label branding.

In the editor's Page section, Density can follow the organization or choose a preset for that page. Stack and Columns use the same small, medium, and large spacing scale; Section, Card and the page root use medium spacing. Columns become a single column below 768px while retaining the spacing and reading order.

An explicit page density is saved with its version. As organization is live inheritance: changing the organization default affects inheriting published pages on their next load, without republishing. Historical versions that inherit also use the current organization default; they are not frozen screenshots.

Whole-page imports and version restores preserve an explicit page density. Content-only template insertion keeps the destination page's settings. A shared snapshot without organization context uses its explicit density, or Standard if none was selected. Choose an explicit preset when matching spacing across organizations matters.

Preview, welcome, and access

The Branding preview is a sample of the selected organization defaults. It is not an entitlement check or an exact preview of every page: an explicit page palette wins, and organization defaults require eligible white_label settings. A logo alone does not make the current organization branding eligible.

The first-visit welcome screen on public pages is dismissible onboarding, not a login barrier. Its login button returns to the page after Logto sign-in; Skip or a previous browser-local welcome marker can show public content without login. Signed-in visitors can also see welcome before the marker is set. Restricted page access is enforced by server-side visibility, membership and audience checks.

Client health monitoring, OAuth-expiry alerts and reconnect workflows remain planned features. A configured feature flag or a successful service health check does not mean those features are implemented, nor does an e2ee flag establish that any payload is encrypted.