OMB Cloud AES

Advanced: host the portal on your own subdomain

Run the client portal as clients.yourdomain.com instead of omb.cloud — fully branded with no OMB Cloud chrome.

For tenants who want maximum white-labeling, the client portal runs on your subdomain with auto-provisioned SSL.

Setup

  1. Decide on the subdomain. Common choices: clients.yourdomain.com, portal.yourdomain.com, my.yourdomain.com.
  2. Add a CNAME record in your DNS pointing the subdomain to portal.omb.cloud. TTL 300s for fast verification.
  3. In OMB Cloud → Master Billing → Brand kit → "Custom subdomain", enter the subdomain. OMB Cloud verifies the CNAME (takes 5-10 minutes).
  4. Once verified, OMB Cloud auto-provisions a Let's Encrypt SSL cert. Renewal is automatic.

What changes

All portal URLs change from omb.cloud/portal/... to clients.yourdomain.com/.... Existing magic links continue to work for 30 days, then redirect to the new domain. Email templates auto-update their portal links.

What stays the same

The admin app (where your team operates) remains at omb.cloud/app/. Only the client-facing portal is white-labeled. Backend, data, and admin URLs are unchanged.

Tips

  • Set up the custom subdomain before your big launch — once portal invites have gone out with the old URL, it's confusing to switch.
  • Document the subdomain choice with your IT team — they'll need to whitelist it on any corporate firewalls.

Was this article helpful?