Platform

Availableapp.erp.io/settings/org/branding

Branding

Branding applies to the surfaces your customers see, not to the workspace your team works in.

Applies to
Client-facing surfaces
Logo
Uploaded once
Colour
One accent
Full white label
Scale plan

What branding reaches

SurfaceBrandedNotes
Invoices and statementsYesLogo and accent colour on the document.
Signing envelopesYesWhat a counterparty sees when they open a request.
Client PortalYesPer brand, not just per organisation — see below.
Client-facing emailPartlyLogo yes; the sending domain is ours unless white label is on.
The workspace itselfNoYour team sees erp.io. That is deliberate.

The last row surprises people, so it is worth the sentence: branding the internal workspace makes support harder and buys nothing, because the people looking at it already work for you. Branding is for the surfaces where the audience is your customer.

Brands inside one organisation

If you trade under several names, the Client Portal carries brands as a first-class thing inside a single organisation. Each brand has its own address that clients sign in to, its own logo, and its own look, and a client sees only theirs. That is how an agency with several trading names runs one workspace rather than several.

app.erp.io/settings/org/branding
Branding
PreviewSave
Save branding
Settings → Branding. Applied everywhere a customer of yours sees a page.

White label

On the Scale plan and above, client-facing surfaces can drop our name entirely and run on your own domain. That covers the portal address your clients use and the sending domain on client-facing mail. It is a setup step rather than a switch, because it needs DNS records on your side that we verify.

Authenticate the sending domain properly or mail quietly disappears

Sending as your own domain requires the DNS records to be published and verified. A partially configured domain does not bounce — it delivers to spam, or is accepted and dropped, which looks exactly like the product not sending. We verify before switching it on for that reason.

What this does not do

No theming of the internal workspace

Your team sees erp.io. Only client-facing surfaces are branded.

One accent colour

There is no full design-token system; a logo and an accent is the whole of it.

No custom fonts

Client-facing surfaces use the platform typeface.

No per-document templates

You cannot upload a bespoke invoice layout. Logo, colour and footer are the controls.

Questions

Can each brand have its own domain?

Yes, through the Client Portal. Brands are addresses, not just logos.

Does branding apply to exported PDFs?

Yes — invoices and signed documents carry it.

Can we remove erp.io from the portal footer?

On Scale and above, yes.