Events overviewBeta

An INVIA event comes in two shapes, and you choose the shape on one screen, What are you planning?, because a ride with friends and a weekend rally need very different amounts of setup.

Casual meet-ups#

A meet-up is one screen, so you can get a ride in front of your friends in a minute. Fill it in, then press Create & share.

• What's the plan?
• When
• Where (optional), pinned on the map so riders know where to gather.
• Details (optional)
• Who can come? Choose Friends only, an unlisted link anyone you send it to can use, or Public, which makes the meet-up discoverable in INVIA.
• Add routes from your collections, routes or rides, so everyone loads the same track before setting off.

Invite INVIA friends directly, or send the link to anyone you want on the ride.

Friends RSVP with one tap, I'm going or Interested, because a meet-up has no approvals and no pending list.

The ride page shows who is going and lists the routes with Send to device and Send all, so a rider can load the day onto a Garmin without asking you for files. It also draws a map of every attached route.

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 is credited to whoever built it.

Meet-ups.

Organized events#

Creating organized events needs an Organizer account. A casual meet-up is free and needs no Organizer account, so use a meet-up when you are riding with friends rather than running a rally.

The wizard has six steps.

1. What and when. The name, the kind of riding, the dates, and an optional registration link.
2. Where it starts.
3. Your route collections.
4. The story. A rich description with Write it with AI, a cover photo, a flyer, your logo.
5. Who can join. Open to everyone, Anyone with the invite, or My email list only.
6. Review.

INVIA does not take registrations or payments. Registration and pricing stay on your own site, and step 1 takes a link to that site so riders can reach it from the event page. The link is optional, because the roster, the check-in and the event page all work without it.

A new organized event is a private draft. Riders cannot see it yet. The event exists on your dashboard and you can keep editing it. Press Publish event on the dashboard Overview when you are ready for riders to see it.

The wizard.

Joining#

Every event gets a share link and a 6-letter code automatically, so you never have to create one. Who may use them is the organizer's choice.

A rider joins in one of three ways.

• From the share link.
• From Join with code on the Events page.
• From Discover, for public events.

Every rider accepts the event's release of liability before joining, so nobody reaches your roster without agreeing to 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 and is not approved yet, which means you can see who is waiting rather than losing the request. The organizer approves riders from Riders on the dashboard.

Meet-ups are RSVP only, so there is no approval step and no pending state.

Joining and the participant page.

The organizer dashboard#

• Overview: a readiness card, a quick 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 the list shrinks as you work. When nothing is missing, the card lists nothing.
• Riders: approve, reject, check in, 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. An invite-only event also gets an email access list, imported by paste or CSV.
• Routes: attach collections with a day number and a display label, so riders see the right routes on the right day. Attach individual routes too. Set the download dial. Write a per-route description with Describe with AI. Garmin maps built for the event can be saved or sent by riders.
• Team: invite staff by email. Staff submit routes to a pool and you choose what goes in, which means a sweep rider can propose a route without changing the event. Promote a staff member to sub-admin to post updates, upload documents and choose routes.
• Share: an email banner to copy into your mailing, the link, and social posts from the built-in studio. There is a printable QR poster and the join code. You can print the join code on public material, since who may use it is still governed by your who-can-join setting.
• Briefing: post updates with Info, Important or Urgent priority. An update goes to the event page and is emailed to riders, so a rider who does not open INVIA still gets it. A line tells you how many riders it reaches. Files are typed PDF, schedule, waiver, roadbook, GPX or route.
• Settings: details, who can join, and the event code. The lifecycle runs draft, published, active, completed, archived. Duplicate the event to run it again without building it from scratch.

Briefing files are stored privately, so each download link is made at the moment you click it and stops working 5 minutes later. Every event document and every Garmin map file attached to the event is handed out that way. Clicking again gives you a fresh link, which means an expired link is never a problem for you. A link you paste to someone else will be dead by the time they open it. When a link expires the file itself is still stored, which means nothing is lost. Open the file again from the dashboard.

Moving the event to completed changes almost nothing for a rider. The link still opens, the page marks the event Past event, it still appears in Discover, and the routes are still on it. Archiving stops the link and the join code working for anyone who has not joined. That rider lands on a page reading This event link is no longer active, which adds that the event may have ended, been removed, or the link is incorrect. Riders who already joined keep the event in their own list and can still open it, because joining is what gives a rider the event and archiving does not undo a join.

The download dial sets who can download the route files, so you decide whether a route file leaves the event.

The dashboard in depth.

What riders get#

The event page holds the about section, the flyer, the routes grouped by day with maps, who's going, documents and updates.

Approved riders use Import to Library, Send to Device, and Download GPX when the download dial allows it. With the dial on Nobody, a rider can still view the route and send it to a device. The dial governs the file copy, which means a rider on a closed event still rides the route.

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

Live tracking#

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

Positions come from satellite trackers. There are two sources, because riders either carry your fleet units or their own tracker.

• The organizer's own fleet units, handed to riders.
• A rider's SPOT or Garmin inReach share link, pasted once.

Riders opt in themselves, which means you cannot switch on a rider's location for them. On the event page a rider presses Share my live location.

Live sharing stops when the event ends. A rider does not have to switch it off. That rider's dot stops appearing on the map, and nothing else about the event changes, so the roster, the routes and the documents all stay as they were.

The map refreshes every 90 seconds and shows one dot per rider with a breadcrumb trail, so you can see which way a rider went rather than only where they are. It pins OK, help and SOS messages.

Live Tracking flags three problems: no check-in, stopped, and no signal. A flag marks the rider on the map, which means you can find that rider without searching the roster. A flag does not raise an SOS.

Tap the flagged name, because the panel that opens holds what you need to act on it. The map moves to that rider's last known position, and the panel shows their emergency contact with a Call link when one is on file. When none is on file the panel says there is no emergency contact on file for this event. For a fleet unit you handed out, the panel also carries the phone number of whoever is carrying it.

From the rider's row you can star that rider, which tints the row and the marker so they stay easy to find. You can also draw their trail to see which way they were heading, and send that rider's live position to staff out on the course as a maps link.

An SOS raises a band on the map with Show me, so a distress message is not one dot among many. Press Show me on the band.

By default only organizers and staff see rider locations, which means a rider who shares a position shares it with the event team and not with the field. Riders do not see each other on the map.

On the web, a rider shares through a satellite tracker, because the browser does not broadcast a position of its own. A rider with no satellite tracker shares no position from the browser, and that rider still joins the event, sees the routes and sends them to a device.

In the INVIA app, phone sharing lives on the Tracking tab. The browser has no Tracking tab and never switches phone sharing on for you, so from the web a satellite tracker is how your position reaches the map.

Live tracking and the public page.

Friends#

Outside events, Tracking on your profile shows friends who chose to share with you, so two people riding together need no event at all. A friend shares for 24 hours, a week, or always. Tracking also lists any SPOT or inReach feeds you follow.

Sharing is per person and one switch stops it, which means switching one person off leaves your other sharing switches on. That person stops seeing your position, and you switch it back on to share with them again.

A Pro account can also create a public tracking page for a feed, so family at home can follow the ride.