A published map cannot be edited
Your Map is published, you have opened it to fix something, and everything is locked. The editor says so: This map is published and cannot be edited directly. Create a new version to make an editable draft.
Nothing is broken and nothing needs support. This is how publishing works here, and it is not how any other editor you have used works — which is why every map creator meets this page exactly once.
What to do instead, in one step
Use 📝 Create New Version. That gives you an editable draft copy of your Map, with everything in it — image, Anchor Points, Areas, floors, names — and the published one stays live the whole time you work on the draft. When you are ready, you submit the draft, and it becomes the newest Map Version.
The full procedure is create a new Map Version.
That is the answer. The rest of this page is why, and what it means for the people using your Map.
Why a published Map is frozen
Because other people have it, and are using it right now.
A Map is not a document you own privately once it is in the catalog — it is a thing somebody has installed and is walking around a venue with. If editing were live:
- A calibration change would move everybody mid-event, without warning, on the day you happened to be tidying up.
- Renaming an Area would silently change what a notification said for people already relying on the old name.
- Deleting an Area would remove a Group’s Meeting Point while they were walking to it.
None of those has a good failure mode, and none of them would be visible to the person affected as anything but the app misbehaving. So a published Map is fixed, and change arrives as a new Map Version that each installer chooses to take. Their side of that choice is a new version of this map is available.
What is and is not locked
| Part of the Map | Published Map | New Map Version (a draft) |
|---|---|---|
| The image | Locked | Editable |
| Anchor Points and calibration | Locked | Editable |
| Areas of Interest, names, icons, floors | Locked | Editable |
| The Map’s name and icon | Locked | Editable |
| Taking it out of the catalog | Allowed | — |
| Deleting it | Allowed | Allowed |
So the two things you can still do to a published Map are stop publishing it and delete it, both of which affect its installers — my map was delisted and delete a map.
The practical consequence: get calibration right before publishing
Calibration is far and away the change people want to make after publishing, because it is the one whose faults only show up when real people walk the venue. And it is the change that costs a new Map Version.
So before you submit, spend the extra ten minutes:
- Four or five Anchor Points rather than three, so the error figure means something — what calibration is.
- The heat map read once, looking for one intense region — read the accuracy heat map.
- Area names as they will read on somebody else’s phone, since renaming later has the same cost.
What support cannot do
Nobody can unlock a published Map for you. There is no admin override, no request form and no exception — the Map that is published is the thing other people installed, and editing it in place would change what they have without their knowledge. The new Map Version is not a workaround for a missing feature; it is the feature.
A worked example
A festival Map has been public for a week and somebody reports that the second stage is drawn fifty metres out.
- You open the Map. Everything is locked and the editor tells you why.
- You use 📝 Create New Version. A draft appears with everything copied.
- In the draft you find the bad Anchor Point with the heat map, correct its coordinates, and watch the figure drop into the Good band.
- You submit the draft for approval. Throughout, the published Map is still live and everybody at the festival is still using it — with the fault, but working.
- It is approved. Installers are offered the newer Map Version and each decides when to take it.
At no point was anybody’s Map changed under them, and at no point was the venue without a Map.