Use cases
However you run portals, the loop is the same
Point at the live portal, restyle it, ship one clean stylesheet. What changes between a solo admin and an agency with thirty client portals is everything around that loop: organization, review, history, and handoff. That is what the account layer is for.
Single portal owner
Restyle your live portal yourself, copy the CSS, and test it in a sandbox the same afternoon. Upgrade later if the portal becomes ongoing work that deserves sync, history, and a deploy kit.
One portal, many styles
Holiday, event, dark-mode, campaign, and rebrand variants, all under the same portal. Approve one, archive the rest, and bring any of them back next season.
Company with many portals
Customer, partner, dealer, and support portals stay organized separately, while admins, designers, and developers share access to the themes that matter to them.
Freelancer or consultant
Each client portal stays cleanly separated. Duplicate a concept for a pitch, export a review preview the client can open in a browser, and hand off deploy-ready output.
Agency or SI partner
A book of client portals in one account: client workspaces, reusable base themes, review notes, and team roles, without unrelated customers ever mixing.
Developer handoff
Stable selectors, a merge conflict report, head-ready CSS, and a Salesforce CLI deploy kit. The developer gets a project to run, not snippets to interpret.
How the pieces fit together
| Piece | What it does for you | Who lives in it |
|---|---|---|
| Extension | Pick elements on the live portal, style them visually, test selectors, and preview everything in place. | Designers, admins, developers. |
| Account | Named themes, variants, review status, previews, merge, version history, and the deploy kit. | Teams, freelancers, agencies. |
| Web studio | Browser-based CSS generation, merge, and deploy kit when extensions are blocked or you just prefer no install. | Anyone, anywhere. |
How client work stays organized
Workspace
Client or organization
Portal
Theme
VersionsA one-company account stays flat and simple. Freelancers and agencies get a clean place to separate clients, so a dealer portal rebrand never sits next to an unrelated customer's support portal.