Domain Settings

Configure custom domains for your OpsPilot365 platform instance and client portal access. Custom domains provide a professional, branded experience for both your MSP team and your customers.

Custom Domain Overview

OpsPilot365 supports custom domains for two distinct access points:

Setting	Description	Example
Platform domain	Custom domain for the admin/MSP portal	`manage.yourcompany.com`
Client domain	Custom domain for the customer-facing portal	`portal.yourcompany.com`
SSL certificate	Auto-provisioned via Let’s Encrypt	Automatic

Note: Both domains can be configured independently. You can use a custom domain for the client portal while keeping the default platform domain, or vice versa.

DNS Configuration

Follow these steps to configure a custom domain:

Add CNAME record — Point your subdomain to the OpsPilot365 endpoint
Verify domain ownership — The platform validates DNS records automatically
SSL certificate provisioned — Let’s Encrypt certificate is issued automatically
Domain active — Your custom domain is live within minutes

CNAME Record Example


Host: portal
Type: CNAME
Value: portal.opspilot365.com
TTL: 3600

Platform Domain

The platform domain is used by your MSP staff to access the administration console. Configure this to reinforce your brand identity with your team.

URL format: https://manage.yourcompany.com
All platform features accessible via custom domain
Existing bookmarks and saved URLs continue to work via redirect

Client Portal Domain

The client portal domain is the URL your customers use to access their self-service portal. This is especially important for white-label branding.

URL format: https://portal.yourcompany.com
Login page displays your custom branding
Email notifications reference your custom domain
SSO redirects use the custom domain

SSL Certificate Management

SSL certificates are automatically managed:

Feature	Details
Provider	Let’s Encrypt
Certificate type	Domain Validated (DV)
Auto-renewal	Yes, before expiry
Wildcard support	Not required (per-subdomain)
HTTPS enforcement	Automatic HTTP to HTTPS redirect

Domain Verification

After adding DNS records, the platform verifies ownership:

Verification check — Runs automatically every few minutes
Propagation time — DNS changes can take up to 48 hours
Status indicators — Pending, Verified, or Failed with error details
Retry — Manual re-verification available if initial check fails

Warning: Do not remove the CNAME record after verification. The record must remain in place for the custom domain to function.

Troubleshooting

Common issues with custom domain setup:

Issue	Cause	Resolution
Verification pending	DNS not propagated	Wait up to 48 hours
SSL certificate error	CNAME not pointing correctly	Verify CNAME target
Domain not loading	DNS cache	Clear browser/OS DNS cache
Mixed content warnings	Hard-coded HTTP URLs	Contact support

Best Practices

Use subdomains rather than root domains (e.g., portal.yourcompany.com not yourcompany.com)
Keep TTL values low during initial setup for faster propagation
Test the domain in an incognito/private browser window after setup
Update any documentation or onboarding materials with the new URLs

API Reference

GET /api/msp-portal/settings/domain — Get current domain settings
PUT /api/msp-portal/settings/domain — Update domain configuration
POST /api/msp-portal/settings/domain/verify — Trigger domain verification
GET /api/msp-portal/settings/domain/status — Check verification status