Security and procurement
Local-first styling for Salesforce portals.
OmniStyler does not connect to your Salesforce org, does not ask for Salesforce credentials, and does not require a managed package. The free editor runs in your browser; account features store only the themes you choose to sync.
Short version: no Salesforce login, no org API connection, optional per-site browser access, local free editing, and deploy output through standard Head Markup or static resources.
Chrome extension permissions
| Permission | Why OmniStyler needs it |
|---|---|
activeTab | Lets OmniStyler inspect and style the current portal tab after the user opens the side panel or starts the picker. |
scripting | Injects the picker, live preview stylesheet, selector test outline, and saved theme runtime into the current page. |
storage | Saves local per-origin rules, undo state, account token, and API base URL in Chrome storage. |
sidePanel | Keeps the editor visible while the user scrolls and tests the real portal page. |
Optional <all_urls> | Not granted by default. OmniStyler requests access only for the current portal or staging domain so custom Experience Cloud hostnames work. |
Data handling
- Free editing stays local. Rules persist in the browser for the portal origin being styled.
- OmniStyler never asks for Salesforce credentials. It styles the page already open in the user's browser session.
- Pasted CSS is private user data. It is used for the merge operation and must not be logged.
- Account sync is optional. When signed in, OmniStyler stores theme rules, labels, lifecycle status, notes, and version snapshots.
- Backend services. The API runs on Cloudflare Workers/D1, sign-in email uses Resend, and billing uses Stripe Checkout/webhooks.
Procurement and AppExchange status
OmniStyler is not listed on AppExchange yet. It does not install a Salesforce package in your org. Output ships through standard Experience Cloud Head Markup, Theme CSS, or static resources generated in a Salesforce CLI deploy kit.
For security review, procurement, SSO, custom terms, or high portal counts, contact [email protected].
Blocked extensions
If company policy blocks Chrome extensions, use the Web Studio. It cannot point-and-click on the live portal by itself, but it can generate scoped portal CSS, merge existing Head Markup CSS, produce tokens, and download the same deploy kit without installing anything.