To manage VR training across sites, you need one place that knows who works where, which course each site owes and by when, and which headset a result came from. In Skillsive that place is a single organization: each site becomes a trainee group, each training gets one deadline for every group assigned to it, and every completion records the headset, language and country it came from.
That is the short answer. Below is how it looks in practice for a company with a few plants, warehouses or branches, and where the limits are.
Why several sites break a simple setup
A multi-site rollout fails on bookkeeping, not on the headsets. Each site ends up with its own spreadsheet, its own copy of the course list and its own idea of when the refresher is due. The fix is one register of people and one schedule, with the site as a label on top of it.
A VR course is the same everywhere. The trouble is everything around it. A plant in Poland, a warehouse in Germany and a sales office with two headsets will each invent a slightly different way of tracking who trained. Six months later, an auditor asks for one list and nobody can produce it.
One organization, a group per site
In Skillsive a trainee group is the natural unit for a site: the help center article on trainee groups lists "a shift, a site, a department" as typical uses. You create "Poznań Hub" or "Warehouse, shift A", add the people, and assign trainings to the group instead of to 30 people one by one.
A person can belong to several groups at once. A forklift operator in Poznań can sit in "Poznań Hub" and in "Forklift drivers", which matters when one training is site-wide and another follows the job.
The trainee record itself is light. It holds a nickname, optional employee ID and position, and a language and country. Licensing is per headset, not per person, so a site with 200 people and four headsets does not need 200 accounts.
Shared deadlines, local progress
A training in Skillsive is a course with a delivery window. Assign it to several site groups and each site gets its own progress view, while the deadline stays the same for all of them. That is usually what a central EHS team wants: one rule, measured site by site.
Each group page has a member matrix: one row per person, one column per training, with completed, in progress, not started or overdue in every cell. From there a site lead can send an e-mail reminder (it goes out in the trainee's language), issue certificates for everyone who finished, or export the matrix to CSV or Excel.
One detail catches people out. The deadline belongs to the training, not to the group. Edit it from one site's page and it moves for every site assigned to that training. If a site really needs a different date, give it its own training. For a yearly refresher, the "Duplicate training" option copies the same course into a new period with the same group assignments.
Content languages per organization
Multi-site often means multilingual. The organization chooses which content languages it uses and which one is the default, and the headset offers exactly those. Each trainee also carries their own language, so a German warehouse and a Polish plant can run the same course in their own language without separate copies of it.
Reports and certificates follow the same logic: you generate them in the language the document needs. The details are on the multi-language feature page.
Headsets: one default, local exceptions
Device settings work on two levels. You set defaults for the whole organization, such as whether guest play is allowed or how a trainee signs in, and override single options on individual headsets. A headset at a trade-show stand can allow guest play while every plant headset requires sign-in.
Name and number your headsets by site from day one. The device record has room for a name, number, color and country, and that record is what links a completed training to a physical headset. A name like "WRO-03" tells you more in a report than a serial number does.
Two practical points:
- A headset picks up changed settings when the app starts, so restart the app before the next session after a change.
- Locking a headset to a single app is a job for your mobile device management tool or Meta Quest kiosk mode, not for Skillsive. We cover the MDM side in VR headset fleet management.
That second point got more important this year. Meta stopped selling commercial Quest SKUs and Horizon managed services on 20 February 2026, made HMS licenses free, and will support existing customers until 4 January 2030 (Meta, 2026). Plan the MDM before you ship headsets to a new site.
Sites without reliable Wi-Fi
Remote sites are where offline mode earns its keep. A paired headset that has downloaded its courses runs them with no network for 30 days from its last connection, or 90 days on the Professional plan. Scores and lesson history stay on the headset and upload in the background when it next sees Wi-Fi.
The device list shows when each headset was last active, so the central team can spot the unit in a basement training room that has not synced for three weeks. More on the mechanics on the offline mode page.
One report for the whole company
Every completion records who trained, on which course and headset, in what language and country, when, for how long and with what score. The completions table filters by course, application, status and date range, and exports exactly what you filtered to CSV or XLSX. For a single site, the group's member matrix is the quicker view.
This is where the per-site naming pays off. If headsets are called "POZ-01" and "WRO-03", the device column in an export already tells you which site a result came from.
Where the setup has limits
Skillsive has no separate site level. Roles (Admin, Analyst, Finance, Device Admin) apply to the whole organization, so an Analyst sees results from every site. For most EHS teams that is the point: one person sees everything. If your sites must not see each other's data, raise it with us before the rollout and we will plan the structure with you.
A rollout order that works
- 1Import trainees by CSV with language and country filled in.
- 2Create one group per site, plus groups for roles that cross sites.
- 3Set organization defaults for headsets, then name and number every unit by site.
- 4Create each training once and assign all site groups to it.
- 5Check the member matrices weekly and send reminders before the deadline, not after it.
If you are still comparing platforms, our guide on how to choose a VR LMS covers the questions to ask any vendor. For the Skillsive side, start with the VR LMS overview or browse the VR training catalog to see which courses your sites could share.
