The Skillsive update released on July 16, 2026 is mostly about the headsets: who is using them, how they behave, and whether they are being used at all. Alongside that, the panel gained data exports and a much faster, interruption-tolerant way of uploading VR app versions.
This is the customer-facing summary — what you will actually see in the panel and on the goggles. If you administer a VR training program, the short version is this: you can now tell who took a training on a shared headset, configure the headsets from one place, and see which ones are gathering dust.
Learner login codes: who actually took the training
Every learner now has a unique six-digit code that they enter on the VR headset to identify themselves. It works offline, which is the point — training rooms and production halls rarely have reliable Wi-Fi, and the code is what ties a completed scenario to a real person rather than to a shared device.
The code is visible directly in the learner list and in the learner's details; one click copies it. You can set a code manually or generate a new one, and from the list toolbar you can download a print-ready PDF with cards (first name, last name and code) to cut out and hand over. Codes reach the headsets during synchronization.
Bulk operations landed in the same list. Select several people and generate new codes, activate or deactivate them in one go. Before the operation runs, Skillsive shows how many learners it affects and what will happen to them; afterwards, how many succeeded. Activation and deactivation only apply to the selected learners they actually make sense for, so with an all-active selection the "Activate" button does not appear at all.
The whole flow is described in a new Learner login codes guide in the Help Center, under Groups and participants.
Device settings: one configuration for the fleet, exceptions where you need them
In the organization panel, under Devices, you can now set the default behaviour of the VR headsets: guest mode, how the tutorial runs (every time, once per learner, or off), whether the tutorial can be skipped, how a learner logs in (pick from a list or enter a code), and what the learner list shows — nickname, full name or employee number.
Each device either inherits the organization settings or has its own. That distinction is what makes a mixed fleet manageable: the headsets on the shop floor can require the tutorial and code login, while the two you take to trade shows allow guest mode and skip straight into the scenario. Settings are applied the next time the app starts on the device.
There is a new Device settings guide in the Help Center, under VR devices, covering each option.
One small consequence of this: the learner form field called "Nickname — the name shown in the app" is now just Nickname, because what appears on the goggles is decided by the "Learner list shows" setting instead.
Device statistics: which headsets are gathering dust
The device details now have a working Statistics tab. It shows how many courses were started and completed, the completion rate, how many learners were trained, and the total time spent in VR — for the last 30, 90 or 365 days.
Above that there is one sentence about hardware utilization ("used on 6 of 30 days") with the date of the last activity. That line is deliberately blunt: on a fleet of twenty headsets, the ones that never left the cabinet are the first thing worth acting on. Below it, a day-by-day activity chart and a list of the courses launched most often on that device, with the average score.
The Applications tab in the same view is clearer too. Instead of a barely visible checkmark, there is a Logged in or Logged out label, and for a logged-in app also the account it was logged in with and the date. You can see at a glance whether a headset is ready for training and who prepared it. Both the applications and completions tabs now page properly instead of stopping at ten rows.
Table exports: your data in Excel or CSV
Course completions, app completions, devices, members and learners can now be downloaded from the organization panel with one click, as CSV or Excel. The file contains every row matching the filters you set, not just the page you are looking at, with headers in the language of the panel.
The app completions table also gained filters by application and completion status, so "only the people who completed application X, with their scores" is a filter and an export rather than a support request.
App version uploads: faster, and resumable
If you publish your own VR app versions through Skillsive, this is the section for you. Uploads now send only the packages that actually changed. Packages identical to what is already in the cloud are marked No change on the list and skipped, and above the progress bar you can see how many files and megabytes that saved. For a typical update touching a few scenes, this cuts the upload time substantially.
You also see the cost before you commit. After you point at the build folder, before clicking "Create", the panel tells you what will really be sent: "To upload: 340 MB of 4.2 GB — the rest is already in the cloud". The version number itself is read from the build's catalog file rather than typed by hand, with a note about which file it came from; if the folder is wrong, the panel says so immediately instead of failing halfway through the upload.
Files that fail to send no longer disappear quietly. They are retried, and when that does not help they land on a list with a reason: no connection, expired link, server error. Closing the tab mid-upload asks for confirmation.
The important one: a version whose upload was interrupted now has a Resume upload action in its menu. You point at the same build folder and the panel sends only the missing files, under the same version number. Previously a taken version number could not be reused, so an interrupted upload meant rebuilding the package in Unity with a higher number.
Smaller things you will notice
- Error messages in your language. Server-side errors (a failed reCAPTCHA check, too many attempts, a wrong two-factor code) now appear in the language of the panel (Polish, English, German) as a readable message instead of raw technical text.
- Cookie consent by category. The privacy banner has a "Settings" button and lets visitors accept analytics and marketing separately. Accepting analytics no longer switches on advertising cookies.
- "Learn more" links. Panel pages that have a matching guide (devices, device settings, learners, members, certificates, custom courses, organization profile and security) now link to it from the header, opening in a new tab in the panel's language.
- New public pages. Pricing with four plans, contact, "About us" and descriptions of six platform features, in Polish, English and German. On the contact page you can book an online meeting by picking a free slot in the calendar. The home page has an FAQ covering the platform, VR headsets, offline mode, languages and certificates.
What to do after the update
Most of it works immediately: codes are generated for existing learners, and every device inherits the organization settings until you decide otherwise. Two things are worth ten minutes.
First, go to Devices and decide how the headsets should behave — especially whether learners log in by picking a name or by entering a code. That single setting is what makes the completion data trustworthy. Second, open the Statistics tab on a few devices and look at the utilization line; unused headsets are usually a scheduling problem, not a hardware one, and they are cheap to fix once you can see them.
If you are new to the platform, the previous update from July 6 covers certificates, organization joining and login, and the VR training catalog shows what you can run on the headsets today. For the reasoning behind all of this, why VR training is more effective than traditional training is the place to start.
