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, each starting with
http://orhttps://.
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. Must start with http://orhttps://.Privacy policy Linked from the donate form, under the consent text. Donors with privacy questions look here first. Must start with http://orhttps://. -
Click Save changes.
-
Optionally set a custom receipt message in the "Email receipt" panel. This replaces the opening line of the receipt donors get by email. Leave it blank to keep the default ("Thank you for your donation to your organisation. Here are the details for your records."). Two placeholders fill themselves in when the receipt is sent:
- Your organisation's name
- The donation amount (for example $100.00)
A live preview shows how it will read. The donation details below the message are always included automatically.
-
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 |
Give page (/give) | yes | yes | no | no |
Checkout link (/c) | yes | yes | no | yes |
| 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.
- Give pages (
/give) show your logo at the top, above the page heading, and your primary colour drives the form's main controls (the Continue-to-payment button and the selected payment-method tile) - the same way donate pages do. Website and privacy policy links are not applied to this surface yet. - Checkout links (
/c/<code>) open a Together-rendered page styled just like your donate page - your logo at the top, your primary colour on the controls, and the privacy link beneath the form - with the amount locked and the donor's details pre-filled. The Stripe-hosted payment fields inside it keep their own styling, the same as on a donate page. - 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. The opening line is editable from the Email receipt panel; everything below it is filled in automatically.
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. The
Website URL and Privacy policy URL are less strict - they accept http:// or
https:// (but not other schemes) since they render as links, not images.
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.