Skip to main content
Custom domains and “Remove Powered by” branding require a Business or Enterprise plan. The Customization fields (logo, organization name, contact email, address, terms, privacy) are available on every plan, including Pay As You Go. View plans
The Customization page is the single place where you turn Invent into your brand. It has three cards:
  • Domain: the domain your team and your customers use to reach the organization. It unlocks branded emails and a URL that never mentions useinvent.com.
  • Branding: the logo, organization name, contact email, address, terms, and privacy links. They appear to members, in branded emails, in portals, and in invites.
  • Modules: which sections of the product are visible in this organization. Shown to members who can manage the organization.
Access the Customization page at useinvent.com/o/settings/customization.
Customization page with the Domain card on top, then Branding and Modules
Sub-organizations have their own Whitelabel. The settings on this page apply only to the organization you’re currently in. Every sub-organization has its own Customization tab that you configure separately. Jump to Whitelabel for sub-organizations below for the full flow.

Customization

The Customization tab holds the fields that appear wherever Invent renders your brand: the sidebar logo, invitation emails, member-facing pages, and the sign-in screen on your custom domain. Logo recommendations: SVG for best quality, square (1:1) or landscape (2:1), under 2 MB. PNG and JPG also supported. Click Save changes at the bottom to apply your updates. The logo uploads immediately when selected; the text fields save when you click the button.

Domain

A custom domain is what turns an Invent organization into a branded organization. Without it, invitation links still read useinvent.com/... and outgoing emails still fall back to Invent’s default sender. With it, both switch to your brand. The Domain card sits at the top of Customization. Its Organization domain picker sets the domain members use:
Domain card with a domain that is Not connected yet and the CNAME record to add

Adding a Domain

1

Pick a subdomain, not your root domain

Use a subdomain like assistants.yourcompany.com, chat.yourcompany.com, or app.yourcompany.com. Do not use the root (apex) domain itself (yourcompany.com). Most DNS providers do not allow a CNAME record on the root, so the verification fails with a “Custom hostname does not CNAME to this zone” error.
Reserve a dedicated prefix like assistants.yourcompany.com if you plan to create sub-organizations later. You can then use one wildcard CNAME to cover every sub-org automatically. See Wildcard for agencies.
2

Add your domain

Open the Organization domain picker, choose Add your domain, enter the full hostname (for example assistants.yourcompany.com), and click Add.
3

Add the CNAME to your DNS provider

The domain row shows the exact record to add:
If you use Cloudflare, set the record to DNS only (grey cloud ☁️). Leaving it proxied (orange cloud) blocks the verification because Invent needs to terminate TLS for your hostname directly.
4

Wait for the connection

Invent checks the record every few minutes, or click Check now. DNS usually propagates in a few minutes but can take up to 24 hours. Until then the domain shows Not connected yet and members keep the domain they had. Once the record resolves, it shows Connected and members switch to it on their own.

Domain Statuses

What Changes Once the Domain Is Active

  • Organization URL: the organization is reachable at https://assistants.yourcompany.com in addition to the default Invent hostname. Share that URL with your team and clients instead of the useinvent.com one.
  • Invitation and notification emails: the “from” name becomes your Organization name (from Customization). The sender address switches from the default Invent sender to a brand-neutral address that never mentions Invent. Replies route to your Contact email when it is set.
  • Sign-in on your domain: users signing in from your custom URL see your logo and a sign-in flow with no Invent branding.
Sending from your own address (for example support@yourcompany.com) is set up under Settings → Emails: once the sender is verified, broadcasts and assistant emails go out from it. Invitation and notification emails on a custom domain still use the brand-neutral sender with your organization name, and replies route to your contact email.
Members on a custom domain see every organization they belong to. The domain sets the logo, the sign-in page and the emails; it never limits which organizations open. Someone who belongs to no organization sees the “Nothing here for this account” screen: invite them from Settings → Members & Roles.

Deleting a Domain

Click Remove on the domain row to remove it. Picking another choice in the Organization domain picker removes it too, after you confirm. The CNAME record in your DNS provider is not touched. Remove it there separately if you don’t plan to reuse the hostname. After deletion, organization links and emails revert to the default Invent branding immediately.

When the Subscription Ends

Custom domains are a Business and Enterprise feature. When the subscription ends, by cancellation or downgrade, the domain keeps working for 5 more days. After that, visitors on that hostname see a “Site Unavailable” page until the organization subscribes again. Your DNS record and the domain setup are kept, so nothing has to be added again. A sub-organization’s domain follows the parent organization’s subscription.

Modules

The Modules card turns whole sections of the product on or off for this organization: Inbox, Analytics, Assistants, Knowledge, Broadcasts, Channels, Audience and the rest. A module you turn off disappears from the sidebar for everyone, Admins included, and its pages show a not-available placeholder if someone opens a direct link. Inside a module that is on, each role still sees only what its permissions allow, so Modules is the coarse switch and roles are the fine one.
Modules card with a switch per section of the product, and the Sidebar card
Every organization has its own Modules card, main organizations and sub-organizations alike. The card is visible to members who can manage the organization (Admins, or a custom role with that permission). For a sub-organization, the parent reaches the same card from the sub-org’s dashboard, see Modules there.

Whitelabel for Sub-Organizations

On any domain but useinvent.com, a sub-organization’s invitations and notifications carry its parent’s brand: the parent’s name as the sender and in the header, the parent’s contact email for replies, and the parent’s address in the footer. A sub-organization keeps its own Logo and Organization name; when it sets its own logo, its emails show that logo instead of the parent’s. Its contact email, address, terms and privacy come from the parent, so those fields don’t appear in a sub-organization’s Customization. The domain is the one thing a parent can share. A sub-organization can follow the parent’s domain with one click, from the Organization domain picker or from Add domain in the Sub-Organizations list. New sub-organizations follow the parent by default; you can pick another domain when you create one. This way an agency’s clients get invitations and notifications under the agency’s brand, not Invent’s. Organizations without a parent keep their own branding.

Where the Sub-Organization Whitelabel Lives

From the parent organization, go to Settings → Sub-organizations and click the row of the sub-org you want to brand. The row opens that sub-org’s management dashboard, which has its own Customization tab, mirroring the parent’s Customization page.
Sub-Organizations list. Click any row to open that sub-org's management dashboard.
The Customization tab behaves exactly like the parent’s version above, just scoped to this sub-org.

Branding a Sub-Organization End-to-End

1

Open the sub-organization

From the parent organization, go to Settings → Sub-organizations and click the row of the sub-org you want to brand. Its management dashboard opens with Overview, Members, Roles, Customization, and Billing tabs.
2

Fill in Customization

Open the Customization tab and set the sub-org’s own Logo and Organization name. Its contact email, address, terms and privacy come from the parent organization.
Customization tab inside a sub-organization with branding fields
On any domain but useinvent.com, invitation and notification emails from this sub-org go out under the parent’s name, with the sub-org’s logo when it has one and the parent’s logo otherwise.
3

Pick the domain

In the Domain card at the top of Customization, keep the parent’s domain, or open the Organization domain picker, choose Add your domain, and enter a hostname dedicated to this sub-org, for example acme.assistants.yourcompany.com. Then add the CNAME record shown under it, exactly as described in Adding a Domain above.
If you plan to add domains for many sub-orgs, set up a wildcard CNAME once and every sub-org hostname under that prefix verifies instantly. See Wildcard for agencies.
Until this sub-org’s own domain is connected, its members keep the domain they had, for example the parent’s.
4

Invite members

Once Customization is filled and the sub-org’s domain is Connected, new invitations sent from this sub-org carry its logo, the parent’s name as the sender, a brand-neutral sender address, and a sign-in link on its custom hostname. Invite members from the sub-org’s Members tab.
A member signing in through the sub-org’s URL sees every organization they belong to. Someone who belongs to none sees “Nothing here for this account”. Invite them to the sub-org first, then they can sign in through the custom URL.
For the broader sub-organization feature (members, modules, billing, spending limits), see Sub-Organizations.

Wildcard for Agencies

If you plan to run many sub-organizations, each under its own hostname like acme.assistants.yourcompany.com, brightsmile.assistants.yourcompany.com, or so-easy.assistants.yourcompany.com, add one wildcard CNAME in your DNS provider and every sub-org hostname verifies instantly with no DNS change per client.

Step 1: Add the wildcard record in your DNS provider

In your DNS provider (not in Invent), add a single wildcard CNAME on a dedicated prefix:
The wildcard lives only in your DNS provider. Invent does not accept *.assistants.yourcompany.com in the Add domain input. Inside Invent you always enter a full hostname like acme.assistants.yourcompany.com.
Do not wildcard the apex (*.yourcompany.com). It would catch every other record on your domain like www, mail, and so on. Always scope the wildcard to a dedicated prefix you reserve for Invent.
You can also keep a plain record for the parent organization itself (for example assistants.yourcompany.com → cname.useinvent.com) alongside the wildcard.

Step 2: Add the hostname to each sub-organization

For each sub-organization:
  1. From the parent organization, go to Settings → Sub-organizations and click the sub-org’s row. Its management dashboard opens.
  2. Open the Customization tab.
  3. In the Domain card, open the Organization domain picker, choose Add your domain, and enter a hostname under your wildcard prefix, for example acme.assistants.yourcompany.com.
  4. The domain verifies instantly because the wildcard CNAME is already pointing at Invent. No per-sub-org DNS change required.
Repeat for every sub-organization. Each one gets its own branded URL without any extra work in your DNS provider.

Plan Availability

Troubleshooting

You’re trying to verify a root (apex) domain like yourcompany.com. Most DNS providers do not allow a CNAME on the root. Use a subdomain instead (for example assistants.yourcompany.com, chat.yourcompany.com, or app.yourcompany.com) and add the CNAME under that name.
Cloudflare proxies CNAME records by default (the orange cloud ☁️). Invent needs to terminate TLS directly, so switch the proxy status to DNS only (grey cloud ☁️) and click Check now again.
On useinvent.com, a sub-organization’s emails keep Invent’s brand. In the sub-org’s Customization, pick another domain in the Domain card: the parent’s domain, ondash.app, or its own. Its invitations then go out under the parent’s name. Branding a Sub-Organization End-to-End →
The account belongs to no organization yet. Invite them from Settings → Members & roles in the organization that owns the domain, and have them accept the invite before signing in through the custom URL again.
DNS normally propagates in minutes but can take up to 24 hours. Run dig CNAME assistants.yourcompany.com (or any DNS lookup tool) to confirm the record resolves to cname.useinvent.com globally before clicking Check now again.
The preview inside the dashboard always shows the badge. It is removed on the live widget on any website where your users actually embed it, and on any assistant accessed through your custom domain. Check a live embed or the custom-domain URL in an incognito window to confirm.

Next Steps

Sub-Organizations

Run independent sub-organizations for each client or team, each with its own branding

Members

Invite teammates so they land on your branded organization on first sign-in