Run the same workflow under as many brands as you serve
Per-project brand layers — logo, palette, typography. Asset libraries. No SourceToDocs branding on outputs. Designed for agencies, franchises, and multi-brand operators.
Agencies, franchises, and multi-brand operators share a problem most document tools weren’t built for: the underlying workflow is the same across all of their clients or brands, but every output needs to look like it came from a different organization. A marketing agency’s monthly report for one client should look like that client’s brand. The same report for the next client should look like that client’s brand. The agency producing both should be invisible in the output.
This is the white-label use case. SourceToDocs supports it as a first-class concept rather than a workaround.
What it does
A brand profile is a set of overrides — logo, primary color, accent color, typography, footer text, and similar surface-level branding elements — attached to a project. When a generation runs under a project, the active brand profile is applied to the placeholder regions designed for branding.
The master template stays the same across all brand profiles. The brand layer is what changes. One template, many brand identities, generated outputs that each look native to their respective brand.
Output is unbranded. Generated documents carry no SourceToDocs watermark, no “powered by” footer, no platform logo. The document looks like a document from your client or your portfolio brand — not a document from a tool.
For teams with downstream client-facing artifacts (delivery emails, document portals), additional white-label options are available on the Enterprise plan — custom email FROM domains, custom subdomain for delivery URLs, removal of platform references from notification copy. These typically involve some DNS configuration on your side and are scoped during onboarding.
How it works
- Define a brand profile. Upload the logo, set the color palette, pick the typography, write the footer text. This is usually a 5-minute task per brand.
- Attach the brand profile to a project. Each project carries one active brand. Workspaces can host many projects, each with its own brand.
- Build the master template once. Inside the template, mark which regions should pick up the brand layer — typically the logo placeholder, the primary color regions, headers, footers. The rest of the template structure stays neutral.
- Generate. At generation time, the active brand profile is composed onto the template. The output reflects the brand.
Adding a new brand later means creating a new project, uploading the brand assets, and pointing it at the same template. No template duplication. No fork-and-modify. The template is the structural source of truth; the brand is the surface layer on top.
What’s included
- Brand profiles per project. Logo, primary color, secondary/accent colors, typography (heading and body font families), footer text.
- Brand asset library. Versioned storage for logos and brand imagery. Update the logo in one place; future generations pick up the new version.
- Unbranded output. Generated documents carry no SourceToDocs marks.
- Multi-template per brand. A single brand can have multiple template variants — a long-form report, a short summary, an executive one-pager — all sharing the same brand layer.
- Workspace isolation. Projects, brand profiles, and brand assets are scoped to a workspace. Members see only what they’re given access to.
Enterprise customers with more involved white-label needs can also enable:
- Custom domain for delivery URLs — generated document links can be served from a domain you control. Requires CNAME setup on your side.
- Custom email FROM domain — delivery emails can come from your domain with appropriate DKIM/SPF configuration.
- Removal of platform references from notification copy.
These tend to be specified during onboarding rather than self-served in the UI.
Where it fits
Marketing agencies producing reports for multiple clients. Same underlying reporting structure across all clients, but each client sees a deliverable that matches their own brand book. The agency name doesn’t appear inside the document unless the agency wants it to.
Holding companies and portfolio operators. A parent organization with multiple consumer-facing brands can run shared workflows centrally while preserving each brand’s identity in the output. Reporting structures stay consistent; brand presentation stays differentiated.
Franchises producing per-location reports. A franchise operation where each location needs its own branded performance report — same template, same data structure, branded as the location.
White-label SaaS resellers. Software companies that want to add document generation as a feature inside their own product, with their own brand on the output. The integration is typically API-driven (see the API) with branding applied per their own customer.
Honest limits
- Brand overrides apply to designated regions, not arbitrary template areas. The template author decides which regions are “brandable” by where they place the placeholder. We don’t auto-detect and restyle anything that happens to look like a logo or a brand color elsewhere in the template.
- One brand per generation. A single document is generated under one active brand. We don’t currently support per-recipient brand switching mid-generation (some recipients see brand A, others see brand B from the same run). If you need that, you run one generation per brand.
- Custom domains require DNS configuration on your side. We can’t proxy through DNS we don’t control. The setup is straightforward — a CNAME record, a small amount of certificate work — but it’s not a one-click toggle.
- Reseller scope is an Enterprise concern. If you’re using white-label to deliver document automation as a service to your own paying customers (rather than as part of standard client work), the commercial terms differ from the off-the-shelf Small/Medium plans. Worth flagging early in pricing conversations so we can scope it cleanly.
- No client-facing portal yet. White-label currently means white-label outputs — branded documents delivered through email, Drive, or your own systems. We don’t currently provide a client-portal interface where your end clients log in to view their own documents directly. Most teams pipe documents into a client portal they already operate.
FAQ
Can my clients log into a white-labeled portal?
Not directly today. The platform produces documents; if you operate a client portal, you fetch generated documents via the API and serve them through your own interface. This works well in practice — most agency-grade portals are bespoke anyway, and the API integration is a few hours of work.
Can the delivery email come from my domain?
Yes, on the Enterprise plan, with DNS configuration. You set up SPF and DKIM records pointing at our sending infrastructure, and emails carry your domain as the sender. Setup is part of onboarding.
What happens to invoicing — is SourceToDocs visible anywhere to my clients?
Invoicing and platform billing stay between us and you. Your clients don’t see anything from SourceToDocs unless you want them to. Generated documents, delivery emails (if configured with your domain), and any portal you build on top all carry your brand.
Does this affect which plan I need?
If white-label is for delivering your own internal documents under different brands (a holding company across portfolio brands, an agency producing client deliverables as part of standard service work), Small or Medium covers it — brand profiles are included on every plan. If white-label is for reselling document automation as a SaaS feature to your own paying customers, that’s the Enterprise plan with reseller terms.
Can I have hundreds of brand profiles?
Yes — there’s no hard cap on brand profile count. Performance-wise, profiles are cheap; each one is just a small bundle of overrides. The practical limit is operational, not technical: maintaining 200+ active brand profiles takes some ops discipline regardless of tooling.