Back to Use Cases
Admin Suite

Domains

Custom domains & DNS

Used byOperations

Own every link, pixel, and chat origin under domains you control and trust.

Domains is the Admin Suite control center for registering and managing custom domains across email tracking, short links, the web chat widget, and vanity workspace URLs. From one place you handle DNS verification, TLS certificates, security policies, and health diagnostics, so every customer-facing link and asset loads on a branded domain you fully control. It replaces scattered DNS tickets and certificate spreadsheets with verifiable, auditable domain operations.

8 use cases

Documented use cases

01

Stand Up a Branded Email Tracking Domain

Email marketing operations manager
Problem

Tracking links, open pixels, and hosted images that point at a generic vendor domain hurt deliverability and brand trust, and recipients increasingly distrust mismatched URLs. Setting up a custom tracking subdomain usually means back-and-forth tickets with IT, hand-edited DNS, and uncertainty about whether TLS is actually live before a send.

How BOL7 solves it

Register tracking.company.com with the Email Tracking & Assets role, then use the Verification & DNS tab to publish the CNAME/TXT records and confirm ownership. Once verified, provision TLS from the TLS & Certificates tab so link redirects, the open pixel, and hosted images all serve over HTTPS on your own domain.

Outcome

Tracking and assets load on a domain that matches your brand, supporting deliverability and recipient trust without ad hoc IT involvement.

EmailTrackingDNSTLS
02

Allow-List Your Site So Web Chat Loads Cleanly

Web/CX engineer
Problem

The chat widget silently fails to load when a site origin isn't recognized, leaving visitors with no way to reach support and no obvious error to debug. Teams burn hours guessing at CORS and origin issues across staging and production environments.

How BOL7 solves it

Register the website domain with the Web Chat Widget origin role and add the exact origin to the allow-list. The module scopes which origins may load the widget, so production and staging sites are explicitly authorized rather than blocked by default.

Outcome

The chat widget loads reliably on approved sites, and origin failures become a quick configuration check instead of a guessing game.

WebChatOriginsCX
04

Keep Certificates Renewed Without Manual Effort

DevOps / platform engineer
Problem

Manually issued certificates expire on a schedule nobody remembers until a browser throws a security warning on a live tracking or short-link domain. Each renewal is a manual, error-prone chore that risks an outage if it slips.

How BOL7 solves it

Provision a Let's Encrypt certificate from the TLS & Certificates tab using ACME HTTP-01 or DNS-01 validation, with automatic 90-day renewal handled by the module. Certificates reissue before expiry without anyone touching them.

Outcome

Domains stay continuously protected by valid TLS, eliminating surprise expirations and the manual renewal treadmill.

TLSLetsEncryptAutomation
06

Triage Certificates Before They Lapse

Security / infrastructure lead
Problem

Across dozens of domains it's hard to know which certificates are about to expire, and a single missed renewal can take down a customer-facing link with a TLS error. Tracking this in spreadsheets is tedious and quickly goes stale.

How BOL7 solves it

Use the saved Expiring Certificates view to surface every domain whose TLS is approaching expiry in one filtered list. From there you triage and act on at-risk certificates before they lapse.

Outcome

Expiring certificates are visible and actionable at a glance, so renewals happen ahead of any outage.

TLSSavedViewsSecurity
07

Export Certificate Data for Security Audits

Compliance / security auditor
Problem

Audits and security reviews require a clear record of which domains hold which certificates, their roles, and expiry status, and pulling that together by hand across systems is slow and inconsistent. Auditors want a portable artifact, not a screen-by-screen walkthrough.

How BOL7 solves it

Export certificate data as CSV directly from the module, producing a structured file of domains, certificate details, and status for the audit. The same Logs and Audit tabs back it with an event history when reviewers need more detail.

Outcome

Audit requests are answered with a clean, exportable record instead of manual data gathering, speeding the review.

ExportAuditCompliance
08

Request a Branded Vanity Workspace URL

Workspace administrator (reseller-managed)
Problem

A generic, vendor-shaped workspace URL undercuts brand consistency for teams and clients who live in the portal daily, and changing it informally has no clear, trackable process. Admins are left unsure who owns the change or whether it was applied correctly.

How BOL7 solves it

Request a vanity workspace URL change through the module, which routes the reseller-managed update with a clear record. The request and resulting change are captured in the Audit trail so the workspace identity is updated accountably.

Outcome

The workspace presents on a branded URL through a controlled, auditable request rather than an ad hoc handoff.

VanityURLWorkspaceBranding