
Sign-in theming
The Theming page (route /theming) controls how your organisation’s sign-in screen looks. Instead of a point-and-click editor, the portal takes a theme archive containing your logo, colours, and custom HTML and CSS, and serves it on every sign-in page your users see.

Purpose
Every organisation has a distinct sign-in URL (your issuer, for example https://auth.dbt.agilicus.cloud). The Theming page uploads a custom theme to that issuer so the sign-in screen carries your branding: your logo, your colour scheme, and any custom HTML or CSS you want. The platform serves the theme with the identity-aware proxy, so it applies consistently across every resource sign-in.
A theme is a zip or tar archive that contains a stylesheet at the path theme/styles.css. You start from the provided default theme, customise it, and upload it here.

Why use it
- Put your organisation’s logo and colours on the sign-in screen so users recognise the page they are authenticating to.
- Carry your own HTML and CSS for the sign-in layout, matching your corporate identity.
- Reuse the same theme across sub-organisations that share your issuer, or give each one its own theme when they have their own issuer (see Sub-organisations).
When to use it
- During initial setup, after you have configured your identity providers (see Getting started: identify users).
- When your branding changes (a new logo, a re-brand, a colour change).
- When you need to fix a theme that is not rendering correctly.
Prerequisite: permission to administer issuers (an owner or administrator role). The page shows a no permissions message otherwise.
How to use it
- Open Authentication > Theming from the left navigation. The page shows the issuer URL your theme applies to.

- If you do not have a theme yet, download the default theme, unpack it, and edit
theme/styles.css(and the theme’s HTML) with your logo and colours. - Select UPLOAD THEME and choose your zip or tar archive. The upload starts immediately and a progress bar shows its status. When it completes, the Current Theme panel shows the archive name, its size, and the last-updated timestamp.

- Select DOWNLOAD THEME to download the currently active theme archive, for example to back it up or to edit it.
- To remove the theme and return to the default appearance, select DELETE THEME.
Fields and controls reference
| Field or control | Purpose | Required | Default | Valid values | Notes |
|---|---|---|---|---|---|
| Issuer | The sign-in URL the theme applies to | Read-only | n/a | Your organisation’s issuer URI | Shown at the top of the page |
| Current Theme > Name | The uploaded archive’s file name | Read-only | n/a | Any file name | Example: auth-theme.tar.gz |
| Current Theme > Size | The archive’s size in a human-readable format | Read-only | n/a | Any size | Example: 382.15 KiB |
| Current Theme > Last Updated | When the theme was last uploaded | Read-only | n/a | A date and time | |
| UPLOAD THEME | Uploads a new theme archive | n/a | n/a | A zip or tar archive | Must contain theme/styles.css |
| DOWNLOAD THEME | Downloads the current theme archive | n/a | n/a | n/a | Disabled when no theme is set |
| DELETE THEME | Removes the current theme | n/a | n/a | n/a | Disabled when no theme is set |
Dialogs and popups
There are no configuration dialogs on this screen. Selecting UPLOAD THEME opens your browser’s file picker, and invalid uploads are reported with a notification message rather than a dialog.

Configuration versus diagnostics versus confirmation
- Configuration: uploading and downloading the theme.
- Diagnostics: the Current Theme panel is read-only information about the active archive; there are no live diagnostics.
- Confirmation: DELETE THEME removes the current theme immediately, with no confirmation step. Re-upload the archive to restore it.
Pagination and async behaviour
- There is no table on this screen, so no pagination applies.
- Theme upload is asynchronous: the file uploads in the background, the progress bar fills, and a success notification appears. After an upload, reload the page (or open a fresh sign-in URL) to confirm the new theme is being served. Allow a short propagation delay before expecting the theme on live sign-in pages.
Troubleshooting
- The upload says “Not a valid file type”: the file must be a zip or tar archive. Save your theme in one of those formats and retry.
- The upload says “Not a valid directory structure”: the archive must contain a stylesheet at exactly
theme/styles.css. Check the paths inside the archive. - My theme is not showing on the sign-in page: confirm the upload succeeded, then wait for propagation and hard-refresh the sign-in page. The browser may have cached the previous theme.
- I want to start over: download the default theme and upload it, or select DELETE THEME.
See also
- Identity and authentication
- Authentication overview
- Authentication policy
- Sub-organisations
- Getting started: identify users