This article is about the Proxi admin app at app.proxi.co, and the experience editor released September 15, 2026. Not sure which you have? Open your experience's participation link, the one participants use. If it starts with app.proxi.co, this is the right article. If it starts with map.proxi.co, yours is a legacy experience; look for the legacy article instead.
An experience goes live on its own at its start time and wraps up at its end, with nothing to switch on. This article covers the dates, the status you'll see in the header, pausing, the web address, and what happens when you edit something people are already playing.
Dates and Status
Under Settings → General, set Starts and Ends. Leave them blank and the experience runs anytime. The status pill in the editor header tells you where things stand: Goes live in 3 days, Live · ends Sunday, Paused, or Ended. On your Experiences page each card shows Live, Upcoming, Ended, or Paused.
Click the status pill for two shortcuts: Go live now (when the start is still in the future) and Pause or Resume. Pausing stops check-ins without deleting anything; resume when you're ready.
One thing worth knowing if you also have legacy experiences: their cards say Registration Open, which is a different idea. Registration being open means people can sign up; Live means the experience itself is running. In the new editor those are separate settings. (See Who Can Join, and When.)
The Rest of Settings → General
Name and Description — the description shows on the participant's About tab.
Terms — shown under Terms on the About tab; leave it empty to hide the section.
Help for Participants and Help Email — shown as a Need a hand? card on the About tab so a stuck player knows who to ask. Something like "Stuck on a check-in? Ask at any participating shop, or email us." Leave both empty to hide it.
Timezone — appears when you have daily or weekly limits, like "vote once a day". Those reset at midnight in this timezone.
The Web Address
Every experience gets a short link like app.proxi.co/c/riverbend-restaurant-week. Change the last part under Web Address and click Apply. If you change it later, the old address keeps working and sends people to the new one, so a sign you've already printed doesn't break. (If your workspace has a custom domain, the link uses that instead.)
Saved, Unsaved, and Couldn't Save
The editor saves as you go. The header shows Unsaved for a second after you type, then Saving..., then Saved. If a save fails you'll see Couldn't save with a Retry link, and leaving the page asks you to stay or leave anyway. Leaving with everything saved never asks.
Editing Something That's Already Live
Once an experience has started, your edits don't go public the moment you type them. They're staged, and the header shows an amber Draft — not live yet pill with two buttons:
Publish — anyone playing right now sees the changes the next time their screen refreshes.
Discard — throws away your unpublished changes; the live version stays as it is.
Say you notice a typo in a clue on Saturday morning. Fix it, check it in the preview, click Publish. Until you do, players keep seeing the old clue. On your Experiences page, a card with staged edits shows an Unpublished changes badge so it isn't forgotten. Before the start date there's no draft step at all; edits save straight through, because nobody's playing yet.
A few controls act immediately even while live, because you'd want them to: Pause and Resume, Go live now, adding a tester, and changing the web address.
Good to Know
Publishing swaps the setup only. Nobody's progress, points, or badges are touched. A place you remove just stops counting; a badge already earned stays earned.
View as participant in the header always shows your staged version, so you can check before you publish.