The dashboardBeta

The dashboard is the organizer's side of an event, and it opens on its own for the people who run the event, so you never have to look for a separate admin screen. Organizers and sub-admins land on the dashboard. Riders land on the participant page instead, because they need the joining view rather than the controls.

The sidebar holds nine sections, and two of them are grouped under Routes & Files while three sit under Settings, so the everyday work stays above the setup you do once.

Overview#

The Overview answers the question you ask most often, which is whether the event is ready for riders yet.

The hero is the cover photo, and Change photo replaces it. Under the hero sit the status badge, the countdown and the join code, because those are the three things riders ask you for.

The readiness card#

Before you share this lists only what is missing or waiting, so the card shrinks as you work rather than growing into a wall of ticks. A finished item is never listed.

Every line carries a link to the section that fixes it, so you go straight from the warning to the control instead of hunting for it.

Press Not needed to drop a line you do not want, which is how you tell INVIA that a missing description or an unset location is your decision rather than an oversight.

What you see after Not needed:

• The line is off the readiness card.
• The event is unchanged. Nothing was added and nothing was deleted.
• The card disappears once no line is left.

Two lines have no Not needed button, because they describe people waiting on you rather than a setting you chose. Access list is empty, riders are locked out and N riders waiting stay until you act on them.

A draft event#

An event starts as a draft so you can build it in private, which means nobody sees a half-finished page while you are still deciding the route. A draft shows a banner: Riders can't see this event yet.

What is true while the event is a draft:

• Riders cannot see the event.
• Every dashboard section is open to you.
• Nothing you have set up is lost.

To go live:

1. Press Publish event on the draft banner.
2. INVIA confirms Your event is live.

Tiles, actions and activity#

Post an update writes a briefing message without leaving the Overview, so a change of plan reaches your riders in one step. Two tiles count Routes and Files. The quick actions jump to live tracking, the public page, Share, routes, briefing and details, which saves you the trip back through the sidebar. Recent activity lists the newest update and the four riders who joined last, so you can tell whether people are still arriving.

Riders#

The count line reads N total · N pending · N checked in, which tells you how many people are still waiting on a decision from you before you open the list at all.

Filter the list with All, Pending, Approved, Checked In and Rejected.

Each rider row offers approve, reject, Check In and remove. Set a role of rider, sweep, lead or marshal so the people helping you run the day are marked on the roster.

Select riders to open the batch bar, which carries Approve, Reject, Check in and Remove so a hundred approvals take one press rather than a hundred.

Reject and remove are different#

Both come off the same row menu, so the table below says what each one leaves behind.

Reject leaves the rider one line on their own participant page, in the place the Join event button used to be: Your request to join wasn't approved.

No reason is given and there is nothing on that screen to ask again with, so tell the rider yourself if you want them to know why or to try again.

Removing a rider does not change that rider's own INVIA library. Their saved routes and rides stay where they are, because removing someone touches your roster and nothing in their account.

The access list#

An email-list event carries an access list, which is the set of addresses allowed to join, and RosterImport fills it from a spreadsheet rather than making you type a hundred addresses by hand.

1. Paste the email column, or drop a CSV file.
2. Set Map the columns.
3. Read Preview.
4. Read Review before adding.
5. Confirm the add.

Review before adding sorts every row into four kinds, fine, possible typo, duplicate and invalid, so you catch a mistyped address before it locks a rider out rather than afterwards.

What you see after the add:

• An address that looks fine is added.
• An address already on the access list is marked as a duplicate and is not added again.
• An address that is not a valid email is marked as invalid and is not added.
• The addresses already on the access list are left as they are.

Routes#

The section holds two lists, Individual routes and Collections, because most events attach a whole day of riding at once rather than one file at a time.

Collection controls:

• Attach puts a collection on the event.
• Ordering moves a collection up or down, which sets the order riders see.
• Batch Send to Device writes the selected collections to a connected Garmin.
• Batch Share copies a share link for each selected collection.
• Describe with AI drafts a route description.

Edit Collection sets DISPLAY LABEL and DAY NUMBER (leave blank for all days), so a rider on a four-day event can tell which day each collection belongs to.

Garmin Maps built for the event sit at the bottom of the same section, and riders download them from the event page or send them to a connected Garmin. If the map-building service is unreachable, maps already attached stay downloadable, so a map you built last week is still there on the day.

What you see while the map-building service is unreachable:

• A notice above the map list reads The map-building service isn't reachable right now and says that attaching new maps needs it.
• The same notice adds Already-attached maps stay downloadable for participants.
• Attach Map is greyed out, so you cannot attach a new map until the service is reachable again.
• Maps already attached to the event are still listed on the event page.
• Riders still download them and still send them to a connected Garmin.
• Try again later.

Taking routes off the event#

Removing a collection asks you to confirm, and the confirmation states that the routes stay in your library, because taking routes off an event is not the same as deleting them.

What you see afterwards:

• The collection is off the event.
• The collection is still in your INVIA library.
• Riders no longer see those routes on the event page.

The download dial#

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

The dial controls the permanent copy only. A rider can always view the routes and send them to a GPS, whatever the dial is set to.

One checkbox sits with the dial.

Show route thumbnails on the event page (names and distances, never the GPX)

Switch it on and the event page lists route names and distances, which gives a rider enough to judge the day without putting the GPX file on that page.

Team#

Invite staff by email so other people can build the event alongside you.

1. Type the address.
2. Press invite. INVIA copies the invite link and says Invite link copied. Send it however you like.
3. Send that link yourself, because INVIA does not mail it for you.

The invite link is a staff link and nothing else, because whoever opens it becomes a contributor on your event, so send it only to the person whose address you typed.

The link riders use is a different link, and it sits under Share, labelled Share the link, with the six-character Join code beside it.

Staff send routes to a pool rather than onto the event itself, so nothing reaches a rider until you choose it: Submissions are invisible to riders until you add them.

Promote a staff member to sub-admin when you want them running the event with you, and INVIA confirms what that hands over: They can now post updates, upload documents and choose submitted routes.

What you see after removing a staff member:

• The person is off the team.
• Routes they already submitted stay where they are.
• They cannot submit any more routes.

Share & promote#

Email it, share the link, post it, print it. INVIA mails and posts nothing for you.

You send the email. You post the picture. INVIA hands you the material and stops there, so nothing goes out under your name unless you sent it.

The section has five parts.

Put the code on public material adds the code to the printable poster and to social captions. Leave it off and the code stays off public material, which is how you advertise an event openly while still choosing who gets in. Email you send to your own list always carries the code.

Briefing#

Post messages and share files with your riders. Newest first.

Riders check this section for news and paperwork, so anything they need on the day belongs here rather than in a group chat you have to keep repeating.

Posting a message#

1. Write a title and a body.
2. Choose Info, Important or Urgent.
3. Press Post Update.

The toast counts the riders notified, so you know the message went out rather than sitting unread. With nobody joined yet, the toast says the update is sitting on the event page, waiting for the first rider who arrives.

Editing an update afterwards does not notify riders again. Deleting an update does not take back a notification riders already had, which is why a correction works better as a new update than as an edit.

Posting a file#

1. Drop a file, or pick one.
2. Give it a title.
3. Choose a type: PDF, Schedule, Waiver, Roadbook, GPX or Route.
4. Upload it.

Files are stored privately rather than at a public address, so a waiver full of names is not left open to anyone who finds the link. INVIA opens each one through a link that lasts five minutes.

What you see once a link has expired:

• The file is still in the Briefing list.
• Open it again and INVIA makes a new link.

Settings#

Details holds everything that describes the event: the name, the description with WRITE IT WITH AI, the dates, the location, the cover, FLYER and ORGANIZER LOGO.

Registration holds WHO CAN JOIN and the read-only EVENT CODE, which is the code riders type to join, so you read it off this screen rather than setting it.

The lifecycle#

An event is in one of five states: draft, published, active, completed or archived. The buttons below move it between those states, so you can take an event down or bring it back without building it again.

Neither Deactivate nor Archive takes the event away from a rider who already joined, so that rider keeps it and can still open their event page.

Nobody new can join, because the shared link and the join code stop working for a rider who has not joined yet. They get This event link is no longer active.

Delete Event#

Delete Event is a soft delete, which means the event leaves your list without being destroyed, so a delete you regret is still recoverable. INVIA warns you that it cannot be undone easily.

What you see after the delete:

• The event is off your events list.
• The event is in the Organizer console, under the Cancelled filter.
• Restore on its row menu brings it back as a draft.

What is not deleted:

• The collections you attached are still in your INVIA library.
• Your routes and rides are untouched.

Organizer console#

Organizer console opens from the Events page and gathers every event you organize into one list, so you can work across a whole season rather than opening one event at a time.

The portfolio view holds:

• Search events, which filters by name.
• The filters All, Upcoming, Drafts, Past and Cancelled.
• A row menu of Open, Duplicate, Archive, Restore and Delete.

Delete here asks you to confirm, then takes the event off your events list. The toast carries an Undo for six seconds. Miss it and the event sits under Cancelled, where Restore brings it back as a draft.

Registrations is the second view, and it lists riders waiting for approval across every event you organize, so you approve or reject them in one place instead of opening each event in turn.

Screen text, word for word#

Three sections carry whole sentences as on-screen labels, and the rows below quote them exactly so you can match what you read here against what is on your screen.