Why branding and deployment tools matter
PL
Parker Lin · Product Lead
"We're white-labeling SmartLite for our own customers. It needs to look like our product from the very first login — not a generic template with somebody else's logo in the corner."
And separately: once one org's configuration is right, rebuilding the same objects, fields, and rules by hand in every new environment is slow and error-prone.
Business outcome
A fully on-brand experience per customer, plus the ability to build a configuration once and roll it out to new orgs in minutes instead of rebuilding it by hand.Three admin-only tools
| Tool | What it controls |
|---|---|
| Branding | Logo, primary color, and display name — shown in the sidebar and email headers, effective immediately on save |
| Deployment | Exports the org's configuration (objects, fields, layouts, validation rules, workflow rules) as a JSON package — never record data — and can import that package into another org |
| Media Library | Stores images and PDFs, per-org, referenced by templates and layouts |
Import is idempotent
Re-importing the same package updates existing objects/fields by API name and creates anything new — safe to run more than once, e.g. to sync a sandbox back up to production configuration.Brand your org and export its configuration
Open BrandingSettings → Branding.
Upload a logo and pick a colorSave — refresh the page and confirm the sidebar updates immediately.
Export your configurationSettings → Deployment → Export Package — this downloads a JSON snapshot of your objects, fields, and rules.
Upload a media assetSettings → Media Library → upload an image, then copy its URL for use in an email template.
(Optional) Import elsewhereIf you have a second org or sandbox, import the exported package and confirm the same objects/fields appear.
Test what you learned
1. Does a Deployment export include an org's actual record data?
Yes, every record is included
No — only configuration: objects, fields, layouts, and rules
2. What happens if you import the same Deployment package twice into the same org?
It errors out — duplicate objects aren't allowed
It's safe — existing objects/fields are updated by API name, nothing is duplicated