Brand DMLY as your own

Your branding lives in the reseller dashboard and applies to everything your clients see: the app name in their browser tab, the logo in the sidebar, the accent colour, and the Powered by line on your public booking pages and invoices.

​

Set your brand

​

Logo

Logo URL takes a link to an image you host, or select Or upload a logo to upload one (PNG, JPG or WebP, up to 2 MB and 4096 × 4096). An upload replaces the URL. It replaces the DMLY logo for your clients. If you leave it blank, your clients see the DMLY logo. Dark-mode logo URL sets a separate logo for clients using dark mode, and can be uploaded the same way. Leave it blank and your main logo is used in dark mode too.

​

Favicon

Favicon URL sets the small icon in the browser tab, or select Or upload a favicon (PNG or JPG, up to 1 MB and 1024 × 1024; a square image works best). Your clients see it in the dashboard’s browser tab on your branded domain and in the Live Chat widget.

​

Colour

Primary color is a single colour. There is no full palette editor; you pick one colour and DMLY applies it to buttons, links and accents across the app. The lighter tints and darker shades the app needs, such as tinted backgrounds and focus outlines, are worked out from that one colour. The colour is saved as a six-digit hex code like #4f46bb, which is what the picker always gives you. Anything else is refused with Colours must be 6-digit hex codes, like #4f46bb. under the field.

​

Help centre link

Help centre link takes a link to your own documentation. It becomes the Help Center item at the foot of your clients’ sidebar, and opens in a new tab. It saves with the rest of the Brand section under Save brand, not with a button of its own. Leave it blank and that menu item does not appear for your clients at all; they are never sent to DMLY’s documentation. Your own workspace is the exception on the DMLY app host. You are a DMLY customer underneath your agency, so there you keep DMLY’s docs whatever you set here. On your own domain the item is hidden for your workspace. The value must be a full http:// or https:// address, up to 2,048 characters. Typing help.acme.com without the scheme is rejected with a validation error under the field.

​

What Powered by renders

Powered by appears on your public booking pages, on the HTML version of an invoice, in notification emails, and in the footer of the Live Chat widget your clients embed on their own sites. It reads as your brand, not DMLY’s:

• The label is your App name (shown to customers). If that’s blank, it falls back to your Agency name.
• It links to your Powered by link. If you leave that blank, it links to your custom domain instead. If you have neither, the label renders as plain text with no link.

​

What you cannot change

​

Sending email as yourself

Branding your app name doesn’t change who your clients’ emails come from. To send from your own domain, fill in the Email (SMTP) section on the same Settings page and select Save SMTP. As the confirmation says: set SPF/DKIM for your domain so those emails land in inboxes.

​

Adding your own scripts

The Custom scripts section on Settings adds your own code (analytics, pixels, a chat widget) to pages on your domain. Paste it into Scripts inside the <head> tag or Scripts before the </body> tag, then select Save scripts. Only the agency owner can see or change this section. Team members see Only the agency owner can view or change custom scripts. Ask them if you need analytics, a chat widget or a pixel added. in its place, whatever their role. No role you build on Team can grant it: the Edit sign-up page and customer workspace options permission covers the Customer signup & workspaces panel, not scripts.

​

Where your scripts run

Your scripts are added in two places, both on your domain:

• Your public sign-up page, for visitors who aren’t signed in. It’s the only page a signed-out visitor gets them on.
• Your customers’ dashboard pages, such as the inbox, the members page and their billing page, when a customer of your agency is signed in.

They are deliberately left off these pages:

• Your Reseller Dashboard, and the page a new team member opens from their invitation.
• Sign-in, password, two-factor and email verification pages.
• A customer’s profile and security pages, their workspace Settings page (where they create API keys) and Workspace Services page (where their own service credentials are saved), the integration pages where they manage API keys and other credentials, and the pages where they connect WhatsApp.

And they don’t run at all for these people, on any page:

• You, and anyone on your team or on another agency’s team.
• DMLY staff.
• Anyone inside a client workspace through Open, including you.
• A customer who also belongs to a workspace outside your agency.

Scripts also stop running while your agency is suspended, and never run on the DMLY address.

​

Next