When you sign in to Lapvio Pro you land on the Dashboard. The daily hub. It surfaces the things you act on most: your next event, who's registered, and a quick way to message drivers, so you rarely have to go hunting.
What's on the dashboard
The dashboard is built around your next event. At a glance you see:
- The upcoming event with its date, circuit and how many drivers are in.
- An Occupancy widget: how your next few events are filling per ticket type, with one percentage per event.
- Quick stats on your driver base and recent registrations.
- A composer to send a quick message, and shortcuts into the roster.
- A Feed widget to post an update to your public profile without leaving the dashboard.
- A calendar of what's coming up.
Operators land somewhere else
If your account is an operator (event-day crew), you skip the dashboard and land straight on the upcoming events list. The screens you actually use at the gate. More on roles in Your team & permissions.
What needs attention
The bell in the top bar is where the admin tells you what to fix before an event, and what people are saying to your organisation. Open it and you get two things:
- Readiness alerts, grouped as Urgent, Warning and Info. Each one is a live check against your data: unsigned waivers a week out, a closed driver portal, drivers who never got their link, an unmatched shop order, abandoned carts. Every alert has a button that takes you straight to the page where you fix it. Fix the cause and the alert goes away on its own.
- Conversations: comments and replies on your organisation's posts. These stay unread until you open them, so a glance at a waiver warning never hides a question someone asked you.
Some alerts you can clear by hand, with the small x next to the shortcut:
- Acknowledge hides the alert as long as nothing changes. If the situation moves on, say one more driver books without a waiver, it comes back with a note that it changed since you acknowledged it.
- Mute for this event hides the alert for that event for good. Use it for judgement calls: an event that deliberately has no briefing, or a weekend where you are not publishing photos.
Alerts that describe a real problem on event day, an urgent waiver reminder or a closed portal on the day, cannot be cleared by hand. They clear when you fix them. Acknowledge all info at the top of the list clears the blue ones in one go.
The badge on the bell counts what you have not looked at yet. Opening the bell clears the badge; the alerts themselves stay listed until they are fixed or cleared.
Make it yours
Every widget on the dashboard is optional. Click the small Customize link below the widgets (bottom right) to open the layout panel:
- Switch any widget on or off, including the Stats banner next to the greeting.
- Drag a widget by its handle to change the order; the grid follows.
- Reset to default brings the standard layout back.
The layout is saved to your account, so it follows you across devices. Each teammate arranges their own dashboard.
Finding your way around
Everything lives in the left sidebar, grouped by what it's for:
| Group | What's inside |
|---|---|
| Trackdays | Your events. Active, upcoming and archived |
| Drivers | Your driver CRM. Everyone who's registered with you |
| Commercial | Financials, Orders, and your Add-ons catalogue |
| Content | Briefings (modules & templates), Tracks, and the Feed |
| Settings | Organisation setup, Payments, Team, Sales channels, and this Guide |
You only see what you can use
The sidebar adapts to your permissions. If a teammate doesn't have access to Financials, that group simply isn't there for them. So your menu may be shorter or longer than a colleague's.
A good first hour
If you're setting up a brand-new organisation, do these in order. Each chapter walks you through one:
- Organisation & branding. Your name, logo, colours and contact details.
- Getting paid. Connect Stripe so you can take bookings.
- Your team & permissions. Invite staff and instructors.
- Integrations. Hook up email, waivers and your shop.
Then you're ready to build your first event.