Customising Meerkat
Meerkat serves pages of its own - the sign-in flow, the unavailable page - and it injects a little of itself into the applications behind it. Both can be made to look like your product rather than ours.
What is customisable, and where
| What | Where it is set | Scope |
|---|---|---|
| The palette | Application > Built-in pages, Theme tab | global |
| The arrangement of the pages | same screen, Layout tab | global, Enterprise |
| Name, logo, favicon, background | same screen, Branding tab | global |
| Imposed light or dark on those pages | same screen, on the preview | global |
| The application catalogue | Application > Portal | global |
| The offered languages | Routes > a route > Locales | declared per route, the offer is their union |
| How an application consumes light and dark | the route | per route |
| Extra CSS and JavaScript | the route | per route |
| The user button, its corner and its menu | the route | per route |
One sign-in, one identity
The theme and the branding are decided once, globally: one sign-in procedure serves every application behind the gateway, so it has one look and one name. Several themes can coexist, but exactly one is active - themes are colour trials, and the identity does not fork with them.
The admin console keeps its own look and is not themed: it is an operator's tool, not part of your product's surface.
What is not customisable
- Per organisation. There is no per-tenant theme, branding or portal. That would be the product's first per-tenant visual override: it is planned, and written down rather than half-built.
- Per application. A group of routes sharing their own branding and locales does not exist: the configuration is global and a route belongs to no group.
- Your own HTML for the flow pages. The arrangement is a closed catalogue of layouts shipped with the product; replacing a page's markup is not built.
What travels
Everything on this page is configuration, so it travels in a configuration export - except the pictures. A plain YAML export never carries an image and says what it left behind; a .zip package carries the logos and the background. See backup and restore.