Skip to main content
Each client gets a dedicated support portal — a white-label interface where their end users can submit tickets, chat with your team, browse KB articles, and view their assets. The portal runs on your custom domain and carries your branding.

​
Portal features

Submit tickets

End users create support requests with title, description, priority, an optional asset link (from their organization’s inventory), and file attachments.

View ticket status

Customers see real-time status updates on their open and resolved tickets.

Live chat

Real-time messaging with your technicians. Starting a chat creates a ticket immediately, with the opening message as its first reply.

Knowledge base

Public KB articles are searchable and browsable from the portal.

Asset view

Customers see devices associated with their account, synced from Entra ID, Level.io, and NinjaOne.

​
Custom branding

Customize the portal appearance under PSA → Support Portal (also reachable from the Support Portal tile on the main Settings page):
  • Logo — Displayed in the portal header and login page
  • Colors — Primary and accent colors applied to buttons, links, and headers
  • Custom CSS — Override any portal style with your own CSS for full control
There is one support portal per MSP organization — every one of your clients signs in to the same branded portal (differentiated by their own login, not by separate per-client branding). Branding fields live on your organization, not per client.

​
Custom domain setup

Host your portal on your own domain (e.g., support.yourmspname.com), used by all of your clients:
1

Add the domain

Open PSA → Support Portal, scroll to the Custom Domain section, and enter the desired subdomain.
2

Configure DNS

Add a CNAME record pointing your subdomain to the Regentra portal endpoint provided in the setup wizard.
3

Verify and activate

Regentra verifies DNS propagation and provisions an SSL certificate automatically.
DNS propagation can take up to 48 hours. The portal will not be accessible on the custom domain until verification completes.

​
Portal authentication

There’s no open self-registration — a technician creates the portal contact (manually or via Entra sync) and sends an invite; the end user follows the emailed link to set their own password.

​
Contact management

Portal contacts are the end users who can access the portal. Contacts can be:
  • Manually created on the PSA → Contacts page
  • Synced from Microsoft Entra ID — Users from the client’s Entra tenant are automatically imported as portal contacts
Synced contacts update automatically every 4 hours. Changes to user attributes in Entra (name, email, department) are reflected in the portal on the next sync.