Most organisers don't run events alone. Lapvio splits your people into staff and instructors (who appear on events) and admin users (who sign in and manage things), with roles that control exactly what each admin can touch.
Staff & instructors
Open Settings → Team. It has two tabs:
- Staff. Your event crew: operators, photographers, support, catering. Add them with a name, contact and role; you assign them to events later.
- Instructors. Your coaches. Add a local instructor, or link a coach who already has a Lapvio profile. You can record their bio, specializations, languages, day rate and reviews.
Instructors can be linked to Lapvio coaches
If a coach has published their own Lapvio profile, you can link to it instead of re-typing everything. Their bio, reviews and details come along, and they appear on your events as a bookable instructor.
Admin users & roles
People who actually sign in to Pro are managed separately:
- System Users (super-admin only). Invite an admin by email and give them a role.
- Roles (super-admin only). Define what each role can do.
The built-in roles:
| Role | Can do |
|---|---|
| Admin | Everything |
| Operator | Event-day only. Roster, operations and the check-in scanner; no money or CRM |
| Custom | Exactly the permissions you pick |
Give people the narrowest role that works
Permissions map to sections. Trackdays, Drivers, Financials, Orders, Briefings, Branding, and the per-event tabs. An operator at the gate doesn't need your financials; a custom role lets you hand out just the keys someone needs. Their sidebar then shows only what they can use. The role dialog also has a Dashboard widgets section, so you decide which dashboard cards each role sees; some widgets additionally need their section's permission (the CRM widgets need Driver CRM, the Feed post widget needs News & content).