EventsBeta

An INVIA event is a ride you put in front of other riders, and it comes in two shapes because a Saturday loop with friends and a weekend rally need different amounts of setup. You choose the shape on one screen, What are you planning?. Read the six pages in this section in order, because each one goes deeper into the part of Events that the page before it introduced.

Casual meet-ups#

A meet-up is free, takes up to 25 riders and fits on one screen, so you can put a ride in front of your friends in a minute. Fill in What's the plan?, When, Where (optional) and Details (optional), choose Friends only or Public under Who can come?, attach routes from your library, then press Create & share.

A meet-up has no approvals and no pending list, so friends answer with one tap of I'm going or Interested. The count line then reads how many riders to expect before you set off.

The ride page draws every attached route on a map and carries Send to device and Send all, so a rider loads the day onto a Garmin without asking you for files. Riders can submit their own routes for the host to add, which is how a group ride picks up local knowledge you do not have. A submitted route stays credited to whoever built it.

Deleting a meet-up takes the ride away and nothing else, so your routes, rides and collections are still in your library. Anyone opening the old link reads Event not found., and there is no undo, so make a new meet-up and send the new link when you delete one you still want. Meet-ups.

Organized events#

Creating an organized event needs an Organizer account, so use a meet-up when you are riding with friends rather than running a rally.

The wizard runs to six steps, and every press of Next saves before it opens the next step, which means a closed laptop costs you no more than the step you were typing.

1. What and when. The name, the kind of riding, the dates, and an optional link to your own sign-up page.
2. Where it starts. A pin you drop on the map, so you never type coordinates and never mistype them.
3. Your route collections. The routes riders receive when they join.
4. The story. A description with WRITE IT WITH AI, a cover photo, a flyer and your logo.
5. Who can join. Open to everyone, Anyone with the invite, or My email list only.
6. Review. Every earlier step in one list, so you can see what is still missing.

The name is the one field you cannot skip. A step you leave empty reads Not set on the review rather than blocking you, so the event saves either way and you fill in the rest from the dashboard.

A new organized event is a private draft, so riders cannot see it yet.

The draft is in your events list and every dashboard section is open to you, so you keep building it in private. Publish event on the dashboard Overview is what puts the event in front of riders.

INVIA takes no registrations and no payments, so pricing and sign-ups stay on your own site, and step 1 takes the link that puts a Register button on your event page. The wizard.

Joining#

Every event gets a share link and a 6-letter code automatically, so there is nothing for you to generate, and your who-can-join setting decides who may use them.

A rider joins from the link, from Join with code on the Events page, or from Discover for public events. Each way in ends at the same Release of Liability & Terms, because nobody reaches your roster without accepting it.

An organized event can require approval, so a rider moves through pending, then approved, then checked in. A pending rider is already on the roster, which means the organizer has the request rather than losing it, and approvals happen under Riders on the dashboard. Meet-ups have no approval step and no pending state, because the RSVP buttons are the whole join step.

After a join the event is listed in the Joined tab on the Events page, so a rider comes back to it without hunting for the link again. Joining and the participant page.

The organizer dashboard#

Organizers and sub-admins land on the dashboard, and riders land on the participant page instead, because a rider needs the joining view rather than the controls.

• Overview: the readiness card, Post an update, tiles and Publish event. The readiness card lists only what is missing, such as no date, no routes or riders waiting, so it shrinks as you work and disappears once nothing is left on it.
• Riders: approve, reject, check in and remove, in batches, because a rally roster is too long to work one rider at a time. The roles are rider, sweep, lead and marshal, and an email-list event also carries an access list you fill from a paste or a CSV.
• Routes: attach collections with a day number and a display label, so riders see the right routes on the right day. Set the download dial here, and offer the Garmin maps you built for the event.
• Team: invite staff by email. Staff submit routes to a pool and you choose what goes on the event, which means a sweep rider can propose a route without changing what riders see.
• Share: an email banner, the link, social posts, a printable QR poster and the join code. INVIA hands you the material and mails nothing for you, so nothing goes out under your name unless you sent it.
• Briefing: post updates as Info, Important or Urgent, and upload files typed PDF, Schedule, Waiver, Roadbook, GPX or Route. An update reaches the event page and the riders' email, so a rider who does not open INVIA still gets it.
• Settings: the details, who can join, the event code, and a lifecycle of draft, published, active, completed and archived. Duplicate the event to run it again without building it from scratch.

Briefing files are stored privately rather than at a public address, so each download link lasts five minutes. When a link expires the file is still in the Briefing list, so open it again from the dashboard and INVIA makes a new link.

Who can download the route files is one dial, and it decides who may keep a copy of your GPX files.

The dial governs the permanent copy and nothing else, which means a rider can always view a route and send it to a Garmin whatever the dial is set to.

Delete Event takes the event off your events list without destroying it, so a delete you regret is still recoverable. The event sits in the Organizer console under the Cancelled filter, and Restore on its row menu brings it back as a draft. The collections you attached are still in your INVIA library. The dashboard in depth.

What riders get#

The event page is one scrolling column, holding the about section, the flyer, the routes grouped by day with their maps, who's going, the documents and the updates.

An approved rider gets Import to Library and Send to Device on every route, plus Download GPX when the dial allows it. A route with two of those three controls is a download setting rather than a fault, so press Import to Library to take the route with you.

Rider data reaches only the people on the roster, which means nobody outside the event sees it, and INVIA never relays medical information.

Live tracking#

Live Tracking is a full-screen map on the dashboard with a LIVE switch, so you can watch the whole field while the event runs.

Positions come from satellite trackers, either a fleet unit you hand a rider or a rider's own SPOT or Garmin inReach share feed, pasted once. INVIA does not broadcast a position from a browser. A rider with no satellite tracker shares no position from a browser, and that rider still joins the event, sees the routes and sends them to a Garmin.

Riders opt in themselves by pressing Share my live location on the event page, which means you cannot switch on a rider's location for them. Live sharing stops when the event ends, so a rider does not have to switch it off. That rider's dot stops appearing on the map, and the roster, the routes and the documents all stay as they were.

The map refreshes every 90 seconds and draws one dot per rider with a breadcrumb trail, so you can see which way a rider went rather than only where they are. Flags mark three problems, no check-in, stopped and no signal, so you can find that rider without searching the roster, and a flag does not raise an SOS. An SOS raises a band across the map with Show me on it, because a call for help is not one dot among many.

Only organizers and staff see rider locations by default, which means riders do not see each other on the map. Set Who can see rider locations to Everyone in the event to open the live map to the field.

A Pro account can create a public tracking page for a feed, so family at home follow the ride from a link of their own. Live tracking and the public page.

1. 1
   Events overviewBeta

   The two shapes of an INVIA event, casual meet-ups and organized events, how riders join, what the organizer dashboard holds, what riders get, and how live tracking works. Beta.

2. 2
   Meet-upsBeta

   Casual meet-ups: the one-screen form, Friends only or Public, attaching routes, Create and share, RSVP with I'm going or Interested, inviting friends, and the ride page. Beta.

3. 3
   The organized event wizardBeta

   The six steps of creating an organized event: what and when, where it starts, routes, the description and media, who can join, and review, plus drafts and Save and exit. Beta.

4. 4
   Joining and the participant pageBeta

   How riders join an event by link, six-letter code or Discover, the release of liability, approval states, and what the participant page shows: routes by day, who's going, documents, updates. Beta.

5. 5
   The dashboardBeta

   The organizer dashboard section by section: Overview and readiness, Riders, Routes and the download dial, Team, Share and promote, Briefing, Settings and the lifecycle, and the Organizer console. Beta.

6. 6
   Live tracking and the public pageBeta

   Organizer live tracking with SPOT and inReach trackers, the LIVE switch, problem chips, SOS, rider opt-in, who can see locations, the public tracking link, and the public event page. Beta.