Appearance
Configure visual branding from Appearance in the sidebar.Platform Identity
Logo
Upload logos for light and dark modes:Colors
Customize the color scheme:
Configure separate colors for dark mode to ensure readability.
Typography
Set custom fonts:
Fonts are loaded from Google Fonts or custom URLs.
Custom CSS
For advanced customization, inject custom CSS: CSS URL: Link to an external stylesheet Inline CSS: Add CSS directlyConsole Domains
When several organizations share one platform, each of them can have the console served on its own DNS, such asai.acme.com. Linking that DNS to an organization gives its sign-in page the organization’s look and SSO buttons, before anyone signs in.
Only a platform super admin links console domains. An organization admin could otherwise claim the DNS of another organization and show its name or its SSO buttons there.
Linking a Domain
- Go to Governe → Platform → Organizations
- Open the actions menu of the organization and select Console domains
- Type the hostname, for example
ai.acme.com, and click Add - Turn on Primary organization for each domain whose sign-in page shows this organization’s branding
- Click Save
https://, no path, no port and no * wildcard. Hostnames are stored in lowercase. The dialog refuses an invalid hostname before anything is sent. An entry saved before this check that is no hostname is flagged in the dialog and removed on save.
To unlink a domain, remove it from the list and click Save. It stops being primary at the same time.
Primary Organization
Several organizations can share a domain, for example the subsidiaries of a group onai.acme.com. One of them at most is its primary organization, the one whose branding the sign-in page shows.
Making a second organization primary on the same domain is refused with “ai.acme.com already has another primary organization”. Turn off Primary organization on the current one first.
What the Sign-in Page Shows
The sign-in page reads its look and its SSO buttons from the domain it is opened on.
Only the public part of the branding reaches the sign-in page: the platform name, the logos, the favicon and the colors. Custom CSS, fonts and legal pages apply once signed in.
Hiding an SSO button on other domains is a display choice, not an access control. Email discovery still picks the provider from the user’s email domain, on every domain.
Once Signed In
After sign-in, the console shows:- the active organization’s own look, taken as a whole, when it sets a name, a logo, a favicon or a color of its own;
- otherwise the look of the domain’s primary organization, but only when the user has no active organization or when the active organization is linked to this domain;
- otherwise the platform’s default look. A member of an organization foreign to the domain never sees another organization’s branding.
API configuration
API configuration
Console domains are two fields of the organization, written by a super admin:
Removing a domain from
domains also removes it from primaryDomains. Sending back the stored values unchanged is accepted from any admin, so a client that saves the whole organization is not refused.GET /v2/login/providers adds a branding object (platformName, logo, favicon, colors) when the requesting domain has a primary organization. The domain is read from the Origin header, or the Referer when there is none. GET /v2/me returns the domains of the active organization.Technical details
Technical details
- Propagation: the gateway keeps an in-memory index of console domains, updated on every organization change and reloaded every 10 minutes as a safety net
- Uniqueness: a domain may be listed by several organizations, but is primary for one at most
- Not the SSO domains: the
domainsof an SSO provider are email domains used for discovery, unrelated to console domains
Legal Pages & App Modals
Governe lets you configure legal content (Terms of Use, Privacy Policy) and per-app warning modals, all managed from the Appearance → Legal & Warnings tab.Terms of Use (CGU)
Configure a Terms of Use page accessible at/cgu:
- Go to Governe → Appearance → Legal & Warnings
- Edit the Terms of Use content using the rich-text editor
- Click Save
Privacy Policy Page
Configure a Privacy Policy page accessible at/privacy-policy:
- Go to Governe → Appearance → Legal & Warnings
- Edit the Privacy Policy content using the rich-text editor
- Click Save
App Warning Modals
Display a warning modal when users open a specific app (e.g., Chat). The modal requires acknowledgement before the user can proceed.- Go to Governe → Appearance → Legal & Warnings
- In the App Modals section, select the target app (e.g.,
secure-chat) - Edit the warning content using the rich-text editor
- Click Save
Modals are app-specific: each app slug (e.g.,
secure-chat, agent-factory) can have its own independent warning content and version.
Technical details
Technical details
- Storage: Content is stored as HTML files in the
ai-governance-v2workspace via thev1/legal/:typeendpoint - Branding metadata: Version tracking is stored in
org.branding.appModals[appSlug].version - Client acknowledgement: Stored in
localStorageasprisme:modal-seen:{orgSlug}:{appSlug}with{ version, sessionId } - Display logic: The modal is mounted only when the current route matches
/apps/:appSlugand a version exists for that app slug
Privacy Policy Link
Add an external link to your organization’s privacy policy, displayed in the footer.Menu Editor
Customize the navigation structure from Menu Editor in the sidebar.Home Page
The Home Page setting controls which page users see when they navigate to the root URL (/). By default, users land on Chat.
- Go to Governe → Menu Editor
- Find the Home Page dropdown at the top of the editor
- Select from:
- Default (Chat): platform default
- Any menu item with a link (e.g., “Agent Creator”, “Knowledges”)
- Click Save Changes
API configuration
API configuration
Update the organization’s
navigation object:The
homePage value must:- Start with
/ - Contain only alphanumeric characters, hyphens, underscores, and forward slashes
- Match the pattern:
^\/[a-zA-Z0-9\-_\/]*$
Technical details
Technical details
- Redirect type:
replace(doesn’t pollute browser history) - Timing: Redirect happens client-side after authentication
- Scope: Per-organization setting (each org can have a different home page)
- Storage: Stored in
organization.navigation.homePage
Navigation Structure
The menu consists of:Menu Item Types
Item Properties
An item can carry features that attach behavior to its surface — most commonly a help agent, the embedded assistant users see on that page.
Permission-Based Visibility
Navigation items are filtered based on the user’s role permissions at two levels: Server-side: The IAM Context endpoint filters the navigation before returning it, removing items the user cannot access. Client-side: The platform shell applies the same filtering logic:- Items with
permissionsare shown if the user matches any listed permission (OR logic). Wildcard matching applies:agent-factory:*matchesagent-factory:agents:read. - Items without
permissions(empty or omitted) are only shown to platform super admins (least privilege by default). Add a*permission filter to explicitly show the item to every user/role - Categories are hidden if they have zero visible children after filtering.
- Features within items are also filtered by their own
permissionsarray.
Tier-Based Visibility
Restrict items to subscription tiers:Agent & Template Links
Add dynamic links to agents or templates:Template features power Builder’s “Create new workspace” tiles. For the full publishing walkthrough (preparing the source workspace, configuration forms, permissions), see Workspace Templates.
Editing the Menu
- Go to Menu Editor
- Click items to edit properties
- Drag items to reorder
- Click Add Item to create new entries
- Click Save to apply changes
Menu Item Examples
External LinkBest Practices
Brand Consistency
Match colors and fonts to your brand guidelines
Test Dark Mode
Verify logos and colors work in both modes
Simplify Navigation
Keep menus focused; hide rarely-used items
Use Permissions
Show items only to users who can access them
White-Label Configuration
For complete white-labeling (Enterprise tier):- Replace all logos with your brand
- Set platform name to your product name
- Configure colors to match brand palette
- Add custom CSS for fine-tuning
- Customize menu to show only relevant features
- Add privacy policy link
Enterprise Features
Troubleshooting
- Logo Not Displaying
- Colors Not Applying
- Check image URL is publicly accessible
- Verify image format (PNG, SVG recommended)
- Check for CORS errors in browser console
- Try clearing browser cache
Next Steps
Identity & Access
Configure SSO for branded login
Model Governance
Control AI features available to users