Browse all guides

Docs Handbook

Publishing the volunteer map

Publish the volunteer map so anyone with the printed event code can open it in the Turfile app, and unpublish it the moment you want it gone.

Publishing takes a copy of your volunteer map and makes it publicly visible. Anyone holding the event code can open that copy in the Turfile app, with no account and no invitation.

Volunteers get an Event Info page in the app alongside the map: links and PDF documents you attach, each with a title and an optional description, such as a tee sheet, a parking map, or a shift schedule.

Open the Event tool and scroll to Event information. Click Add link or Add PDF, fill in the Title and optional Description, then paste the address or choose the file. Links must be full https:// addresses; PDFs are the only file type, up to 10 MB each, 20 items in total. Arrows reorder the rows (volunteers read them in that order), the pencil edits a row, and the bin removes it. Editing a PDF row doesn’t swap the file; remove the row and add the new one.

Nothing here is public until you publish, and everything here goes public when you do.

Publish it

  1. Switch the Handbook to Volunteers and click the publish tool. Its label tracks the map’s state: Publish, Republish, Publish changes, or Publish again. While it reads Checking status…, give it a moment; Entries didn’t load means publishing is blocked, so reload the page.

  2. Read How access works at the top of the panel: anyone with the code can open the map, it stays published until you unpublish, republishing keeps the same code, and Unpublish ends access immediately.

  3. Name the event. It’s required, and volunteers see it on the map.

  4. Review the list. Map entries shows every entry about to go public, the full text of every note, and a thumbnail of every photo. Event information shows each link’s full web address and each PDF’s file name, exactly what will become public. If the list can’t be read, publishing is blocked; reload and try again.

  5. Tick I understand this becomes publicly visible. Publish stays disabled until you do, and until the map has at least one entry.

  6. Click Publish. Photos are re-encoded one at a time, so a photo-heavy map takes a few minutes; leave the panel open. When it finishes you get the Event code.

The published copy is frozen at the moment you publish. Later edits go live only when you republish. Nothing expires on its own; a map you publish in January is still open in June unless you unpublish it.

The Event panel

The Event tool in the control bar carries the current publication:

  • the status: Not published, Published, or Unpublished changes;
  • the Event code, with Copy code;
  • Event information: the links and PDFs;
  • App download codes: App Store and Google Play QR codes as downloadable PNGs. They carry no event code and never change, so the same images work for every event;
  • Unpublish, at the bottom.

If you’ve edited since publishing, the panel says so; volunteers see the previously published version until you republish. Adding or editing a link or PDF counts as a change, the same as moving a pin.

Republishing

Click Republish, review the list again, and confirm; the review and the acknowledgement are required every time. While the map is live, republishing keeps the same event code, so anything printed stays valid. After an unpublish, publishing again issues a new code and the old one stops working.

Unpublish

Unpublish is in the Event panel, under End access. Confirm and the public copy is gone immediately, including for anyone who has it open. Your volunteer map itself isn’t touched, and you can publish it again later.

Turning the property’s Volunteer map setting off does not unpublish. While a map is live, the Staff / Volunteers switch and the Event tool stay put so you can always revoke it.

If a publish is refused, the panel names exactly what to fix: a note that’s too long, a shape to redraw, a link or PDF that isn’t valid, or too many attachments. Fix what it names and publish again; nothing becomes public from a refused publish. If it keeps failing, contact support@turfile.com.