Four tools — Branding, Deployment, the App Marketplace, and Media Library — let your org look like its own product, copy a working setup in minutes, and jump-start new apps from a ready-made template.
⏱ ~10 min to complete80 pts available🏅 Badge: Platform Configurator
"We're white-labeling SmartLite for our own customers." (White-labeling means reselling a product under your own brand, so it looks like you built it.) "It needs to look like our product from the very first login — not a generic template with somebody else's logo in the corner."
Here's a separate problem: once you get one org's setup just right, rebuilding those same objects, fields, and rules by hand in every new environment is slow. It's also easy to get wrong.
What this means for you
Each customer gets a fully on-brand experience. Plus, you can build a setup once and roll it out to new orgs in minutes, instead of rebuilding it by hand every time.
Your logo, main color, and display name — shown in the menu and email headers, and it takes effect the moment you save. It also sets where the menu sits: in a side menu on the left with each person's photo and profile (the default), or across the top
Deployment → Export/Import
Exports your organization's setup — objects, fields, layouts, validation rules, workflow rules, record types, custom scripts — as a single downloadable file (JSON format). It never includes your actual record data, and you can load that file into another org
Deployment → Marketplace
Browse ready-made industry packages (Real Estate, Fitness & Gym, Inventory and more) and install one in a click. Each card has a "How to use" link to its Academy guide
Sandboxes
Separate copies of your org's setup (no records) where you build and test without touching production, then move finished work across with Deployment
Tests
Checks you write once, like "a Closed Won opportunity needs an amount". Every Deployment Validate and Import runs them with the package applied, and Import changes nothing if one fails
Media Library
Stores images and PDFs for your organization, so templates and page layouts can use them
Safe to import more than once
If you import the same package again, it updates existing objects and fields (matched by name) and creates anything new. It's safe to run more than once — for example, to bring finished work from a sandbox (a safe testing copy, see below) into production (the live version).
Upload a logo and pick a colorSave, then refresh the page and confirm the sidebar updates right away.
Choose where the menu sitsEvery org uses the side menu by default: the app's tabs, the app switcher and your profile photo sit in a menu on the left, and the top bar is a welcome bar in your main color with search and the bell. Click your photo or View my profile to open your profile; Sign out is the last button at the top right, after the ? help icon. Setup opens in the same menu, and admins move between the app and Setup with the App | Setup switch under their photo. The logo sits at the bottom of the menu: the app's own logo if it has one (App Manager → the app → App Detail → Logo), otherwise your Branding logo. Collapse shrinks the menu to icons. To put the tabs across the top instead, pick Top menu under Navigation Style and save; pick Side menu to come back. On a phone the app always uses the side menu, whichever style you pick: tap ☰ on the welcome bar to slide it in. Setup is not available on a phone; open it on a computer.
Export your configurationGo to Settings → Deployment → Export Package. This downloads a snapshot (a JSON file) of your objects, fields, and rules.
Upload a media assetGo to Settings → Media Library, upload an image, then copy its URL to use in an email template.
(Optional) Import elsewhereIf you have a second org or sandbox, import the file you exported and confirm the same objects and fields show up.
Browse the MarketplaceGo to Settings → Deployment → Marketplace tab, then pick an industry card and click Install. It installs in the background; you get a notification and an email with its how-to-use guide when the new app is ready. Click "How to use" on the card to open its guide.
Create the sandboxGo to Setup → Sandboxes → New Sandbox. Give it a name (or leave it blank for "Your org Sandbox") and click Create Sandbox. Your whole setup is copied in the background; you get a notification and an email to set its password when it's ready. Sandboxes are in beta: not on the Trial plan, and on a paid plan SmartLite Support turns them on for you.
Set your sandbox passwordThe list shows the sandbox admin's username, your own username, a dot and the sandbox name (e.g. priya.uat), and an email goes to you to set its password. Didn't get it? Click Resend email on the sandbox's row.
Sign in to the sandboxSign out, then sign in with the sandbox username at the same address. An indigo Sandbox bar across the top tells everyone they are not in production.
Build and testChange objects, fields, layouts and rules, add test records, try your workflow rules. Nothing here touches production.
Move finished work to productionIn the sandbox, go to Setup → Deployment → Export Package. In production, go to Setup → Deployment → Import, click Validate first to see what it would change and whether your tests pass, then Import. Import runs the tests again and applies nothing if one fails.
Clean upBack in production, go to Setup → Sandboxes and delete a sandbox you no longer need. Everything in it is deleted; production is not affected.
Open TestsGo to Setup → Tests → New Test, give it a name that says what it protects, and pick the object.
Describe the saveUnder Create a record with, add a row per field: the field's name and its value. To test an edit instead, tick Then update it, and test the update and add the values the edit changes.
Say what should happenChoose It saves, and optionally the values the record should end with (for example the status a workflow rule sets), or It is blocked, with words from the error message, such as Amount is required.
Run itClick the run button on the test's row, or Run All Tests. Each test saves through the same checks a user's save goes through, then everything is undone. Nothing is kept and nothing is sent: no emails, SMS or webhooks.
Let deployments use itLeave the test Active. Every Validate and Import in Setup → Deployment applies the package in a trial run, runs your active tests, re-saves a few existing records of each object the package touches, and checks the package's rules only use fields that exist. If anything fails, Import applies nothing and shows why.
One test per rule that matters
Write a test for each rule your business depends on: one that should save and one that should be blocked. Build them in a sandbox: they travel in the exported package and run in production before the package is applied.
The full guide
The Sandboxes trail covers everything: what is copied, signing in, outgoing messages, moving work to production, limits, and how it compares with Salesforce.
What a sandbox doesn't copy
Records, other users, webhooks, and email and messaging settings. Add test records yourself, and invite colleagues to the sandbox like any org.
A sandbox only sends system email
Your workflow rules come along, so a sandbox could otherwise email a real customer or call a real system. By default it sends only system email (activation, invitations, password resets): workflow emails, record emails, campaigns, scheduled reports, SMS/WhatsApp and webhooks are held back, and a workflow rule notes "skipped" instead of failing. To test messages, an admin in the sandbox can switch Setup → Sandboxes → Outgoing messages to Everything, with test addresses.