Branding what your customers see

Public forms, acknowledgement emails and ticket replies are read by people who have never heard of RowFold and have no reason to. One settings page — logo, accent, background, typeface, organisation name — repaints every one of those surfaces across every workspace the account owns, immediately and without anyone touching a stylesheet. A workspace that trades under a different name can carry a brand of its own, and ticket replies can leave from your own email address. Set your identity Open Settings → Branding. Organisation name is used wherever there is no logo, in the footer of the emails you send your customers, and as the sender name on ticket replies — so it is worth setting even when you have a mark. Logo takes a PNG, JPG, GIF or WebP up to 2 MB. It is displayed up to 44px tall on a form or a booking page, and smaller where space is tighter — in an email, on the help centre, in the chat window — so a wide lockup works far better than a square icon. SVG is refused: an SVG is a document that can carry script, and this image is rendered on pages RowFold serves to the public. Colour and type Accent paints buttons, focus rings and highlights; Page background is the paper behind the card. You pick one accent and stop — the hover shade and the tint are derived from it, and the button's own label colour is chosen for contrast, so navy gets a white label and a bright lime gets a near-black one. Nobody ends up with an unreadable button because they liked a yellow. Both reach your customer emails too: a message sits on your page background rather than a stock grey, and its button takes the accent with the same contrast-checked label. Link text inside a message uses a darkened version of your accent instead — a pale brand stays readable as text, which the raw colour would not be. Typeface offers Modern sans, Classic serif, Friendly rounded and Technical mono. All four resolve to fonts the visitor's device already has, so a branded form downloads no web font, loads no slower, and leaks no visitor's IP address to a font CDN — which matters more here than on our own pages, because these are your customers. The RowFold badge The Made with RowFold footer is on by default and any account can switch it off, including one still on trial. Nothing on this page is plan-gated: the promise is that there is no tier above you holding features back, and a badge you had to upgrade to remove would be the one visible thing contradicting it - on a page your own customers see. One switch covers everywhere it shows: forms, booking pages, the help centre, the chat window, and the emails those surfaces send. It goes off everywhere at once — there is no per-surface copy of it to hunt down. See it before anyone else does The Preview card beside the settings renders roughly what someone filling in one of your forms will see, built from what is in the boxes right now. Nobody has to publish a form to find out what a colour looks like on it. The page also counts how many forms the change is about to repaint, because it is worth knowing that before pressing Save branding. Override it on one form The form designer's Look section can differ from the account brand in three ways and no more: Use a different accent here, Show the account logo off, and the after-submit redirect. Those are the pieces a single form plausibly needs of its own; anything further would be a second branding system to keep in step with the first. A form that overrides nothing simply follows the account, so changing the account brand moves every form with it. Where the brand turns up Everything a stranger can reach. On the web: the public form, your booking page and the manage-your-booking page behind it, the public help centre, and the chat widget. By email: the acknowledgement a form submitter gets with their answers echoed back, every booking confirmation, reminder, change and cancellation, the rating request after a ticket is closed, the transcript emailed at the end of a chat, and the replies your team sends. The emails wear the same brand the pages do — accent, page background, typeface and logo — so a confirmation and the page its button opens are the same colour rather than nearly. One brand, every anonymous surface, every workspace that has no brand of its own. A brand for one workspace An account that runs more than one business can give a workspace a brand of its own. On a help desk's status screen, Change beside Replies are signed opens that workspace's branding rather than the account default. Save there and everything that workspace publishes wears its own brand from then on; the default stops applying to it. A workspace that has never saved one keeps following the default, and its page says so. The first save starts from the look the workspace was already wearing, logo included, so nothing disappears at the moment it stops inheriting. Replies from your own address Ticket replies normally leave from RowFold's address with your organisation's name on them. To send them from your own address, such as support@yourcompany.com, use Replies from your own address on the branding page. It takes three steps, and replies keep coming from RowFold's address until all three pass. 1. Confirm the address. Enter it and press Email a confirmation link. Open the link from that mailbox and press Confirm this address. This proves your team can receive mail there, so nobody else can claim it. 2. Add the DNS records. The card lists two CNAME records for DKIM and one TXT record for DMARC. Add them at whoever hosts your domain's DNS. If the domain already has a DMARC record, keep it and skip that one: a domain may only have one. 3. Verify the domain with the mail provider. If the card shows Domain verified with our mail provider: Not yet, press the button beside it, then open the email that arrives at your address. Press Check now. When every row reads In place, replies go out from your address, and a customer's answer still lands on the ticket. The address is re-checked every day. If a record stops passing, replies fall back to RowFold's address rather than failing, your admins are told once, and it switches back on by itself when the record is fixed. This covers ticket replies. Rating requests, acknowledgements and chat transcripts still come from RowFold's address. Tips • Set the organisation name even when you have a logo — it is the sender name on ticket replies and the fallback anywhere an image can't be shown. • Pick the accent and stop: the hover shade, the tint and the button's text colour are all derived from it, correctly, every time. • Use a per-form accent for a one-off campaign page and leave the rest of the account alone. • A wide logo beats a square one — the header renders it at a fixed 44px height. Good to know • A colour that isn't a plain hex value is discarded rather than stored — the value lands inside a stylesheet on an anonymous page, so anything unrecognised is refused outright rather than half-applied. • SVG logos are not accepted; export a PNG or WebP instead. • Ticket replies carry your <em>name</em> but come from RowFold's address until your own address passes all three checks. Putting a domain in From without its DKIM records is what makes mail fail DMARC, which would cost you the replies entirely, so nothing switches on early. • Changing the sending address starts over from the confirmation link: every check belonged to the old address. • The logo appears in emails only when the server has a public base URL configured; without one your organisation name is used instead. • Saving repaints every existing public form on the account at once — there is no staged rollout. Who can do what • The account default is edited by the account owner; a member of somebody else's workspace has no business changing the logo their whole customer base sees. • A workspace's own brand, and the address its replies come from, are edited by that workspace's admins. • Someone who owns no workspace gets an explanation rather than a form: the brand on the forms they work belongs to the owner who pays for them.