Brand your donate pages
Set your logo, colour, and policy links in one place. Donate pages and emailed receipts pick them up.
Branding lives at the organisation level. Set it once and every surface that supports branding reads from the same fields. Plan for five minutes.
Before you start
You need:
- ADMIN role on your org.
- Your logo as a hosted image URL served over HTTPS (PNG or SVG, transparent background works best). If you do not have one yet, Cloudinary and similar hosts give you a URL in seconds.
- Your brand colour as a hex code (for example
#0f766e). Donors see it on your donate form's buttons and on the Pay button in their emailed receipt. - A URL for your public website and a URL for your privacy policy.
Steps
-
Go to Settings -> Branding.
Settings > Branding. -
Fill in the four fields. None of them are required, but each one improves a different surface.
Field What it does Primary colour Hex accent colour used on your donate form's buttons and on emailed receipt buttons and headings. Logo URL Renders at the top of the donate page and at the top of emailed receipts. HTTPS only. Website URL Linked from the footer of emailed receipts ("Visit our website"). Not shown on the donate page itself. Privacy policy Linked from the donate form, under the consent text. Donors with privacy questions look here first. -
Click Save changes.
-
Open your donate page in a fresh tab to confirm the logo and privacy link render. The public URL is the slug column of any form at Engage -> Forms, under
{slug}.alltogether.giving/donate/<form-slug>.What donors see at /donate/general after publishing your form.
Where each field lands
Branding flows to different surfaces. Today, this is the matrix.
| Surface | Logo | Primary colour | Website | Privacy policy |
|---|---|---|---|---|
Donate page (/donate) | yes | yes | no | yes |
Checkout link (/c) | no | no | no | no |
| Emailed receipts | yes | yes | yes | no |
A few notes on what that means in practice:
- Donate pages show your logo at the top and link to your privacy policy beneath the form. Your primary colour drives the donate form's main controls - the donate button, the highlighted suggested-amount, and the one-time/recurring toggle.
- Checkout links (
/c/<code>) are server-side redirects, so there is no Together-rendered screen for them; the donor goes straight to Stripe Checkout. Stripe Checkout has its own styling that you cannot brand from Together. - Emailed receipts are the most heavily-branded surface: logo at the top, primary colour on the Pay-button-style call to action, and website URL in the footer.
What it does not change
- The Together admin shell (the area you are signed in to now). That stays in the platform's neutral palette so you can tell the two contexts apart at a glance.
- The Stripe-hosted payment sheet inside donate. Stripe styles its own checkout and ignores your Together brand colour.
- Receipts that have already been sent. Existing receipt emails do not retroactively re-render with the new branding.
HTTPS-only on logo URLs. Together refuses to render a logo URL that doesn't
start with https://, so an http://... link silently falls back to no logo.
Host on a static-asset CDN if you do not have HTTPS on your main site.
What to do next
- Connect Stripe if you have not already: Connect Stripe.
- Invite your team at Settings -> Users.
- Share your first form by copying the public URL from Engage -> Forms.
New here? Start with Your first sign-in for the lay of the land.