Documentation/Studio
Back
  • Getting started
    • Key concepts
    • Sign in
    • Create and switch organisations
  • Registers
    • Create and change a register
    • Upload and download entries
    • Add, edit and deactivate entries
    • Groups
    • Challenge codes
    • Connect and test an external register
    • Register activity
  • Membership definition
    • Add and order register assignments
    • Filters and outcomes
    • Preview and test before saving
    • Save and version history
  • Communities
    • Create, rename and delete a community
    • Filter by register, status, groups and claims
  • Members directory
    • Find a member
    • Look up the checks of a member code
    • Deactivate a membership
  • Frontends
    • Create a frontend
    • Frontend keys
    • Sign-in settings
    • Sign-in branding
  • Login with appsolut
    • Sign-up and onboarding
    • Sign-in and sign-out
    • Support requests
  • Frontend users
    • Find a frontend user
    • Membership and activations
    • Block a frontend user
    • Export a frontend user's data
    • Disconnect a frontend
  • Membership check
    • Check modes
    • Results and the check log
    • Rate limits
    • Grace rule
  • Organisation settings
    • Organisation profile
    • Studio users and roles
    • Billing
    • Roadmap and feature requests

Sign-in branding

Set how the sign-in screens of all your frontends look, and where support requests go.

Studio roles: "Owner", "Administrator" and "Frontend manager".

The sign-in branding is how your organisation's sign-in surface looks to frontend users: layout, colour, logo, legal links and the support address. You set it once for the organisation, and it applies to every frontend. A frontend cannot change it. The organisation's name on the screens comes from its settings.

Until you save a sign-in branding, the screens show your organisation's name in a plain look, and frontend users cannot send a support request, because there is no support address.

Set the sign-in branding

  1. Open "Frontends" and choose "Sign-in branding".
  2. Under "Layout", choose "Centered" (the sign-in card alone in the middle of the screen) or "Split" (the sign-in card beside your side image).
  3. Under "Colour", enter the colour for buttons and links as #rrggbb, for example #0f5c8c. The text on it is white, so a colour too light for white text is refused.
  4. Under "Dark-mode colour", enter the colour for dark mode, for example #6fb3dc, or choose "Suggest from the colour". The sign-in screens follow the visitor's light or dark setting, and one colour cannot serve both.
  5. Under "Logo", upload a wide logo as SVG, PNG or WebP, at most 512 KB. Without a logo, the organisation's name is shown as text.
  6. Optionally, under "Dark-mode logo", upload a logo for dark mode. Without it, dark mode shows your logo on a light plate.
  7. For the split layout, upload a "Side image" as JPG or WebP, at most 2 MB.
  8. Under "Support email", enter the address support requests are sent to, for example support@pannoniqa.example.
  9. Optionally, enter the links to your "Privacy policy" and "Imprint". They start with https:// and are shown below the sign-in card.
  10. Choose "Save branding".
The Sign-in branding page of Pannoniqa AG with the layout, colours, logo and support emailThe Sign-in branding page of Pannoniqa AG with the layout, colours, logo and support email

Good to know

  • A colour is refused when its contrast is below 4.5:1, so the sign-in screens stay readable.
  • Scripts and external references in an SVG logo are removed.
  • The side image is kept when you switch to "Centered", so you can switch back.
  • If someone else saved the branding while you were editing, the Studio says so. Reload the page to see their changes, then save again.

What frontend users see on the sign-in surface is described in Login with appsolut.