Widget works on my live site but not on staging

Hi — thanks for the clear details. That pattern (bubble/script fine on the live domain, same snippet on staging but nothing appears, no obvious error) is almost always Allowed origins, not a broken install. DeskCrew only lets the widget talk to your workspace from web addresses you've explicitly allowlisted on the Install page, and the match has to be exact (scheme + host + port). Your live domain is already approved; your staging subdomain is a different origin, so it needs its own entry. What to change 1. Open Dashboard → Install → Allowed origins. 2. Add the exact staging origin from the browser address bar — for example https://staging.yoursite.com (copy everything up to, but not including, the first single / after the host). 3. If you also test locally, add that too (e.g. http://localhost:3000), matching the port your dev server actually uses. 4. Save, then hard-refresh staging (Ctrl/Cmd + Shift + R), or retry in a private window. Will this affect the live site? No. Allowed origins is an allowlist. Adding staging only expands where the widget may run; your production origin stays approved and unchanged. Common near-misses (each must be listed separately) - https vs http - www vs non-www - staging.example.com vs example.com - localhost vs 127.0.0.1, or different local ports If it still stays blank after you add the staging origin, open DevTools → Console/Network on staging and look for a CORS/403 on /api/widget/*. The origin quoted in that error is the exact string to paste into Allowed origins. Reply with your staging URL (and that console line if you have it) and I can confirm the entry format. — Support