Branding is one form, saved in one go. It holds a single set of values per organization — your name and site, three colours, links to your logo files, the addresses transactional email is sent from and replied to, how customers reach support, your social profiles, and a custom CSS block. The row is created the first time you press Save branding; before that you are editing defaults.
What you can actually set #
Every field is optional. Colours are the exception to "leave it blank": they always have a value, defaulting to a blue primary, a darker blue secondary and a green accent, and the swatch row under the pickers previews the three together before you save.
| Field | What it does |
|---|---|
| Website name | Your public-facing name. |
| Website URL | A full URL, including the scheme. |
| Custom domain | A domain you own. See below — entering it here does not make it live. |
| Primary / Secondary / Accent | Three hex colours, picked with the colour control or typed as #rrggbb or #rgb. Anything else is rejected on save. |
| Logo (light) / Logo (dark) / Favicon | URLs, not uploads. Host the image files yourself and paste the links; there is no file picker on this form. |
| From name / From address / Reply-to | The sender identity for transactional email. The two address fields must be valid email addresses. |
| Support email / Support phone / Footer text | Contact details and the footer line, up to 1,000 characters. |
| Social links | Exactly five platforms: Facebook, Twitter, LinkedIn, Instagram and YouTube. Blank ones are dropped rather than stored empty, and no other platform can be added. |
| Custom CSS | A free-text stylesheet block, up to 20,000 characters. |
Who can change it #
Saving is restricted to owners and admins. Anyone signed in can open the page and read the current values, but a save from an agent is rejected outright. If you need someone to maintain branding without giving them the run of the workspace, admin is the smallest role that can do it — see roles and permissions.
There is one branding record per organization, so this is not a per-user preference: what you save, your whole team gets.
The custom domain field #
The field records which domain you intend to use, and nothing more. Next to it sits a Verified / Not verified badge that this form cannot change — verification is flipped by the platform operator, not by saving here, and there is no self-serve DNS check in the app.
So the domain needs two things beyond typing it in. In your DNS, the hostname has to resolve to the server this deployment runs on — that is a record you add at your registrar or DNS provider, using the target the operator gives you, because the form does not publish one. Then the operator has to serve and certify that hostname and mark the domain verified.
Plans carry white-label and custom-domain flags of their own, so whether a domain is offered to you at all is a billing question, separate from what this form will let you type.