Skip to Content
Admin ConsoleBranding

Branding & Customization

The Branding section of the Auris Console controls the visual identity of all user-facing components managed by Auris: the hosted login page, email templates, and (optionally) the domain from which these are served. Customization is applied per tenant, so every application registered in your tenant inherits the same branding.

Branding Settings

The Branding page in the Console contains a live preview panel on the right side that updates in real time as you make changes. This lets you see the effect of each setting before saving.

Company Name

The company name is displayed in:

  • The hosted login page title (Sign in to [Company Name])
  • Email template subject lines and footers
  • The browser tab title for hosted login pages

Enter your company or product name exactly as you want it to appear to users.

Upload a logo image that appears in the header of the hosted login page and in the header of all outgoing email templates.

Supported formats: PNG, SVG, WebP, JPEG

Recommended specifications:

UseRecommended SizeMaximum File Size
Hosted login header200 × 60 pixels or proportional500 KB
Email header600 × 200 pixels or proportional500 KB

SVG files scale without quality loss at any size and are preferred for logos with text.

After uploading, the logo appears in the live preview immediately. Click Remove Logo to revert to showing the company name as text.

Primary Color

The primary color is applied to:

  • Call-to-action buttons (Sign In, Continue, Submit)
  • Link text on the login page
  • Progress indicators and loading states
  • Focus rings on interactive elements

Click the color swatch to open the color picker. You can select a color visually, enter a hex value (#1a73e8), or choose from the preset palette.

Preset palette: The console offers a set of 12 preset colors representing common brand colors. Clicking a preset fills the hex field and updates the preview.

Ensure your primary color has sufficient contrast against a white background to meet WCAG 2.1 AA accessibility standards (minimum contrast ratio of 4.5:1 for normal text). The Console displays a contrast warning if the selected color does not meet this threshold.

Background Color

The background color is applied to the login page’s outer background area (visible on large screens as the area surrounding the login card).

For a professional appearance, use a color that complements your primary color. Common choices are:

  • A very light tint of the primary color (for example, #f0f4ff for a blue primary)
  • A neutral near-white (#f8f9fa)
  • Your brand’s secondary/neutral color

Favicon

Upload a .ico, .png, or .svg file to use as the browser tab icon for hosted login pages. Recommended size: 32 × 32 pixels. The favicon is displayed in browser tabs, bookmarks, and browser history.

Transactional Emails

Auris sends transactional emails for thirteen event types — verification, password reset, invitation, MFA code, magic link, login alert, welcome, password changed, account locked, suspicious login, email changed, license issued, and CIBA sign-in approval. See Email Templates for the full catalog and the per-type variables.

Tenant Branding on Default Emails

As long as you have not saved a custom template, Auris renders the built-in templates with your tenant branding: your company name, your logo (falling back to the name as text when no logo is set), and your primary color. A custom template replaces the entire HTML, so branding inside it is fully under your control.

Two toggles at Console → Settings → Email control the footer of the default emails:

  • White-label emails — removes the “Powered by Altovar” attribution; the footer shows only your own copyright line. White-label tenants without a custom primary color get a neutral accent color instead of the platform default, so no platform branding leaks into your emails.
  • Hide footer — omits the footer band entirely.

Editing a Template

  1. Go to Console → Settings → Email Templates
  2. Click the template to open the editor and pick a mode: theme editor, visual builder, or code editor
  3. Edit the Subject line and the body — both support variables with {{variable}} syntax
  4. Click Send Test to send the current template, rendered with sample data, to your own admin email address (subject prefixed [TEST])
  5. Click Save to apply changes; Reset to default reverts the current language to the built-in template

Template Variables

Variables use the {{variable}} syntax and are replaced at send time with actual values — for example {{link}}, {{email}}, {{expiresIn}}. Each template type has its own variable set, and the date variables {{year}}, {{month}}, {{day}}, {{date}} are always available. Dot notation is not supported. Conditional blocks ({{#if variable}}...{{/if}}) keep content only when the variable has a value.

Do not remove the primary action link or code from any template ({{link}}, {{code}}, {{approveUrl}}, …). Removing it makes the email non-functional.

Custom Domains

By default, the Auris hosted login pages are served from the Auris platform domain. Custom domains allow you to white-label authentication under your own domain — for example, auth.yourdomain.com instead of the platform default.

When a custom domain is active, all hosted login pages, email links, and the OIDC Discovery document reference your custom domain. From the user’s perspective, the entire authentication flow appears to be operated by you.

Setting Up a Custom Domain

Add your domain

  1. Go to Console → Settings → Custom Domains
  2. Click Add Domain
  3. Enter the full subdomain you want to use (for example, auth.yourdomain.com)
  4. Click Add

Configure your DNS

After adding the domain, Auris generates DNS verification instructions. You need to add a CNAME record at your DNS provider pointing your subdomain to the Auris platform:

Type:   CNAME
Name:   auth         (or the subdomain you specified, without the root domain)
Value:  [auris-platform-hostname]
TTL:    300

The exact target hostname is shown in the Console after you add the domain. DNS propagation typically takes 5–30 minutes but can take up to 48 hours in some cases.

Verify domain ownership

Once your DNS records have propagated:

  1. Return to Settings → Custom Domains
  2. Click Verify next to your domain
  3. Auris performs a DNS lookup to confirm the CNAME record is in place

The status changes from Pending to Active once verification succeeds. SSL/TLS certificate provisioning happens automatically using Let’s Encrypt.

Set as primary domain

After the domain is verified and active, click Set as Primary to make it the domain used for all hosted login pages and email links.

You can register multiple domains (for example, for different environments) but only one can be primary at a time.

Note: SSL certificates are provisioned automatically via Let’s Encrypt once DNS verification succeeds. Certificate renewal is handled automatically. You do not need to upload or manage SSL certificates.

Domain Verification Statuses

StatusMeaning
PendingDomain added but DNS records not yet checked
VerifyingDNS lookup in progress
ActiveDNS verified, SSL provisioned, domain is ready
FailedDNS lookup failed — check your CNAME record and retry
DeletedDomain was removed from the Console

Applying Branding to Specific Applications

By default, all applications in your tenant share the same branding. For multi-product tenants where different applications have different branding requirements, you can override branding at the application level.

Application-level branding is configured on the application’s Settings tab in the Applications section of the Console. Available overrides:

  • Primary color
  • Logo URL
  • Application display name (shown on the hosted login page)

When a user is redirected to the hosted login page for a specific application (via the client_id parameter), Auris applies the application-level branding overrides on top of the tenant-level defaults.

Application branding also extends to emails: when a default (non-custom) email is triggered by a specific application — for example a magic link requested from that application’s login page — the email is rendered with the application’s name, logo, and color instead of the tenant’s. The footer chrome (white-label, hidden footer) always remains that of the tenant owning the application.

Users & RolesAuthentication Settings