How To

    White Label

    Run the platform under your own brand, domain and sender address

    Overview

    White Label lets a partner present urvo as their own product. Their customers sign in at the partner's domain, see the partner's name and logo, and receive email from the partner's address.

    This is a partner-programme feature. It appears under Settings → White Label for accounts enrolled as partners. If you do not see it, your account is not enrolled — contact urvo rather than looking for a setting to turn on.

    Configuration is grouped into five areas: brand identity, feature toggles, email, legal documents, and domain. Each is covered below. Changes are tracked as unsaved until you save.

    Brand identity

    • Company name — replaces "urvo" in the interface.
    • Primary colour — the accent colour, chosen with a picker.
    • Default theme — whether new visitors start in light or dark mode.
    • Company website — where your brand's name links to.
    • Logo, wordmark and favicon — uploaded images used across the dashboard and the browser tab.

    Upload both light and dark variants where you have them. A single dark logo disappears against a dark header, which is the most common branding complaint.

    Feature toggles

    • Google sign-in — controls whether your customers see "Continue with Google" on the login and signup screens. With it off, they use email and password only.
    • Advanced features — controls whether Workflows, Tools and Integrations appear in your customers' sidebar. Leave it off to present a simpler, voice-only product; turn it on to expose the full automation surface.

    Domain

    Choose one of two hosting options.

    A urvo.io subdomain

    The quickest option. Pick a name and your dashboard is served at yourname.urvo.io. Requirements:

    • 63 characters or fewer.
    • Lowercase letters, numbers and hyphens, starting and ending with a letter or number.
    • Not on the reserved list. Names urvo uses for its own services are rejected with "This subdomain is reserved" — pick another.

    Your own domain

    Serve the dashboard from a hostname you control, such as dashboard.acme.com.

    Apex domains are not supported. You cannot use acme.com directly; it must be a subdomain like dashboard.acme.com or app.acme.com. This is a DNS constraint, not a policy one: partner domains are attached with CNAME records, and the DNS standard does not allow a CNAME at the apex of a zone.

    Setting one up:

    1. Enter the hostname and save.
    2. urvo shows the DNS records to create. Add them at your DNS provider — these prove you control the domain and let a TLS certificate be issued.
    3. Click Verify. Verification is not instant; DNS changes take time to propagate and certificate issuance takes longer still. The page shows the current status and lets you retry.

    If certificate issuance keeps failing after the DNS records look correct, check for a CAA record on the domain. A CAA record restricts which authorities may issue certificates for it, and one that excludes urvo's provider will block issuance no matter how many times you retry.

    Email

    By default, email to your customers comes from urvo's sender address. You can replace it with your own so notifications look like they come from your brand.

    • Sender name — the display name on outgoing email. 2 to 80 characters, and it cannot contain ", < or >.
    • Sender domain — the domain you will send from. Requires DNS verification.
    • Sender email — the address itself. It must be on the sender domain, or a subdomain of it, so nobody can claim a sender on a domain they do not control.

    Sender domain and sender email go together: set both, or leave both blank to keep urvo's default sender. Setting only one is rejected.

    After adding the sender domain, add the DNS records urvo provides and run verification. The page reports pending and unsuccessful states and lets you retry. Until verification succeeds, mail continues to go out from the default sender rather than failing.

    Partners serve their own privacy policy and terms of service. Once provided, they are published on your domain at /privacy-policy and /terms-of-service, and the links in your customers' dashboard point at your documents rather than urvo's.

    Your customers are contracting with you, so these are the terms they see. That is the point of the feature and also its risk: publishing nothing, or publishing urvo's text under your own brand, leaves you without an agreement that describes what you actually provide. Have your own reviewed.

    Troubleshooting

    SymptomLikely causeFix
    "This subdomain is reserved"The name is used by urvo's own servicesChoose a different subdomain.
    Apex domain rejectedCNAMEs are not valid at a zone apexUse a subdomain such as dashboard.acme.com.
    Domain verification stuckDNS not yet propagated, or records mistypedRe-check the records against what urvo shows, then retry. Allow time between attempts.
    Certificate never issuesA CAA record is blocking the certificate authorityRemove or widen the CAA record on the domain.
    Email still from urvoSender domain not verified yetFinish DNS verification for the sender domain.
    Sender email rejectedAddress is not on the sender domainUse an address on that domain or one of its subdomains.
    Customers can't see Workflows or ToolsAdvanced features toggle is offTurn on Advanced features.

    Next steps

    Was this page helpful?