Skip to main content
These settings live in the Portal & Domain and Single Sign-On sections of Settings, under the Organisation group in the left nav rail.
Both sections are plan-gated and permission-gated. They are available only on the Business and Enterprise plans and are hidden on Starter. Portal & Domain requires manager access; Single Sign-On requires administrator access. If you don’t see a section, your plan or role doesn’t include it — contact your organisation administrator.

​
Portal & Domain

The white-label portal lets you serve your customers a branded experience on your own domain. Configuration runs top to bottom in three parts: Domain, Deployment, and Theme.
The Portal & Domain settings — custom domain, verification, and nameserver delegation

​
Domain

One custom domain powers your portal URL, outbound email, and DKIM signing. Use a subdomain you control, such as portal.yourcompany.com.au.
1

Add your domain

Enter the subdomain and click Add Domain. Utilified provisions a hosted zone for it.
2

Delegate your nameservers

Under Delegate your domain, copy the four nameservers shown and set them as the nameservers for your domain at your registrar. Utilified then manages DKIM, SPF, MX, and the SSL certificate automatically.
3

Wait for verification

The status badge moves from Awaiting DNS to Verified once delegation propagates — usually 5–15 minutes. The page re-checks automatically every 30 seconds; you can also click Check now.
4

Enable email delivery

Once verified, toggle Outbound email (notifications from no-reply@yourdomain) and Inbound email (mail to addresses like invoices@yourdomain). Both require a verified domain.
Use Change domain or the delete icon to tear down the current domain — both stop email on that domain and take down a live portal, so they ask you to confirm.

​
Deployment

With a verified domain (hosted zone and certificate in place), click Deploy portal to stand up a dedicated portal instance. Deployment typically takes 3–5 minutes, after which the portal’s live URL is shown. The instance configuration (image version, resources) is managed server-side. Use Update to redeploy or Delete portal to remove it.

​
Theme

The Theme editor controls white-label branding, with a live preview below:
  • Theme name — a descriptive label for the theme.
  • Colours — primary, secondary, and background.
  • Typography — separate font configuration for Body, Button, and Heading text.
  • Branding & links — logo_url, favicon_url, support_url, terms_of_use, and privacy_policy.
Click Save Theme to apply changes, or Reset to Default to return to the Utilified theme (you must still save to apply the reset).

​
Single Sign-On

UMS supports OpenID Connect (OIDC) single sign-on, with a built-in Microsoft 365 / Entra ID provider. Configuration lives under two tabs — SSO Configurations and User Mappings — with summary cards for providers, configurations, and active configs.
The Single Sign-On settings — provider setup and SSO configurations
1

Create a provider

If no provider exists, click Create Microsoft 365 Provider to register the Microsoft 365 / Entra ID OIDC provider.
2

Add a configuration

Click Add Configuration and complete the form:
  • client_id — the application (client) ID from your identity provider.
  • client_secret — the client secret from your identity provider.
  • tenant_id — the directory (tenant) ID from your identity provider.
3

Set user provisioning

Toggle Automatically create users on first login (auto_provision_users), then choose a Default Access Group — Account Viewer, Account User, Account Manager, or Organisation Admin. Optionally restrict sign-in to specific Allowed Email Domains (leave empty to allow all).
4

Adjust claim mapping (optional)

Under Advanced Settings, edit the claim_mapping JSON to map identity-provider claims to user fields (email, first_name, last_name, username).
5

Enable and save

Toggle Enable this SSO configuration (is_active), then click Create Configuration.
Before relying on SSO, use the Test Connection action (flask icon) on the configuration to confirm the credentials and tenant are correct. Use Sync Users (sync icon) to pull users from the identity provider. Only active configurations can be tested or synced.