Branding your organisation

Branding is set once, in Admin → Settings → Branding, and applied everywhere your organisation is rendered.

What you can set

Name. Shown in the header, in page titles, and on certificates.

Logo. Shown in the header of all three consoles and on the sign-in page. An SVG or a PNG with a transparent background works best — the logo sits on both light and dark surfaces, and a baked-in white rectangle shows on the dark one.

Primary colour. Buttons, links, active states and highlights. Pick the colour your organisation already uses; the platform derives the lighter and darker shades around it, so there is one value to set rather than seven.

Where it is applied

Everywhere, including places that are easy to forget:

• All three consoles, from the first frame of the first page load.
• The sign-in page, which is served from your own address.
• These documentation pages, when read at yourorg.rukialabs.com/docs.
• Certificates and shared badge pages.

The general documentation at docs.rukialabs.com keeps Rukia Labs' own branding. It is the same content — only the colours differ, because that copy belongs to no single organisation.

Light and dark

Set a colour for each mode if the two need to differ. A mid-tone that works on white often lacks contrast on the dark background, and a single value has to compromise between them.

Set only the light colour and the dark one is derived from it, which is a reasonable default and not as good as choosing.

When it does not appear

Branding is applied at page load. After saving, an open tab keeps the old values until it is reloaded — reload before concluding that a change did not save.

If a change is still missing after a reload, it is usually a browser cache; a hard refresh settles it.