Beacon · embedded support
Each portal below is a real, separate tenant — its own project, signing secret and widget configuration in the database. The pages differ only in which project they boot. Everything else you can see between them — the shape of the launcher, which tabs exist, the tenant's own CSS, the pages it appears on — is server-side configuration an Admin changes without anyone touching the portal's code.
Loading…
Open the same widget on two portals and note that nothing on the host page changes: the widget lives in a shadow root, so their CSS cannot reach in and its styles cannot leak out. And on Globex, try the checkout link — the widget is not hidden there, it is absent. That is a display rule, not a permission: the API answers on that page exactly as it does on any other.