Device settings control how your VR headsets behave: whether they show the tutorial, whether someone may play without selecting a trainee, and how a trainee identifies themselves before a training. You set this once in the panel — there is no need to touch each headset.

Settings work on two levels: defaults for the whole organization, and overrides for a single device. That way headsets on the shop floor can behave differently from the ones in the office, even though they belong to the same organization.

How it works

There are three levels, and a device always uses the most specific one:

1Device setting — if this device has its own override, it wins.
2Organization default — if the device inherits, it takes the organization value.
3System default — if the organization set nothing either, the built-in value applies.

Every option is resolved on its own. A device can override the tutorial and inherit everything else — nothing is all-or-nothing.

Changes apply the next time the headset starts

A headset fetches its settings when you launch the app on it (or when it resumes a session). There is no instant push to the device. If you change a setting mid-training, the headset finishes that session with the old behavior and picks up the new settings only after the app is restarted. Changing something before a class? Restart the headsets to be sure they have the current settings.

What you can set

Option	Choices	Default
Allow guest play	On / Off	On
Tutorial	Every time / Once per student / Disabled	Every time
Allow skipping the tutorial	On / Off	On
Student sign-in	Pick from list / Sign-in code	Pick from list
Student list shows	Nickname / First and last name / Employee ID	Nickname

The defaults mirror how the VR app behaved until now — until you change something, your headsets work exactly as before.

Set the defaults for your organization

1Open Organization → Devices → Device settings.
2Change the options you need.
3Click Save.

The settings apply to every device in the organization that has no override of its own.

Screenshot placeholder

The Organization → Device settings page with the option list and the Save button.

Override the settings on one device

1Open Organization → Devices and go into the device's details.
2Switch to the Settings tab.
3For the option you want to change, turn off the Inherit from organization toggle.
4Set the value and click Save.

While an option inherits, you see the organization's value next to it labelled Organization — so you know what the device will actually do without opening the organization settings.

Want to go back to the organization value? Turn Inherit from organization back on and save. The override disappears and the device follows the organization again — including any future change to the defaults.

Screenshot placeholder

The Settings tab in a device's details: one option overridden, the rest inheriting with the organization value visible.

Tutorial: shop floor vs office

The tutorial teaches how to use the headset and controllers. For someone who has never worn VR, it is the difference between a training and a fight with the hardware. For someone who uses a headset daily, it is wasted time.

That is why one answer rarely fits a whole company:

Headsets on the shop floor, where people with no VR exposure are trained — leave Tutorial: Every time and consider turning Allow skipping the tutorial off. Nobody jumps past the instructions and gets stuck in the scenario later.
Headsets in the safety office or at an instructor's desk, where someone launches the app a dozen times a day — set Tutorial: Disabled. Every launch starts with the training right away.
A training room with recurring groups — Once per student lands in the middle: instructions the first time, straight in afterwards.

Set the variant that fits most of your headsets as the organization default, and override the exceptions on the specific devices.

Guest mode: attributed completions vs demos

Guest mode lets someone start a training without selecting a trainee. It trades accountability for convenience — which is exactly why it is worth controlling per device:

Turn guest mode off when trainings have to count. With no trainee selected there is nobody to credit the completion to, so if you need reports and certificates tied to a specific person, require sign-in. This is the usual setting for company training headsets.
Turn guest mode on for headsets going to a trade show, an open day or a customer demo. A queue of people needs to play quickly, one after another, and creating a trainee account for each of them makes no sense — nobody is collecting results here.

A guest session is credited to nobody

A completion in guest mode is not attributed to any trainee — it will not appear in their history and cannot be used to issue a certificate. If someone goes through a training as a guest by mistake, it has to be repeated with a trainee selected.

A common setup: off in the organization defaults, on as an override on a single "demo" device.

How a trainee identifies themselves

Student sign-in decides what a trainee sees before starting:

Pick from list — the trainee finds themselves on a list. Simple for small groups, painful with hundreds of people.
Sign-in code — the trainee types their six-digit code. Faster in large organizations and no scrolling. See Trainee sign-in codes.

If you stay with the list, Student list shows decides what appears next to each person:

Nickname (the default) — the one field every trainee always has. If you enter no name and no employee ID, the other options render a blank row for that person, which makes the nickname the safe default.
First and last name — readable, but it requires you to have entered those details at all (they are optional) and to have a basis for processing them.
Employee ID — handy where the list is visible in a public spot and you would rather not show names.

Two people with the same name

The list shows one field, so two John Smiths are indistinguishable. If names repeat in your company, use the Nickname (give them distinct ones, e.g. smith-john-1) or the Employee ID — both are under your control and unique by design. Alternatively switch Student sign-in to Sign-in code: the trainee then never picks from a list, so the problem disappears.

Frequently asked questions

I changed a setting but the headset behaves the same. Why? Because the app on the headset has not been restarted. Settings are fetched when the app starts — close it and launch it again, and the change takes effect.

Can I have different settings on different headsets? Yes, that is what overrides are for. Set the organization defaults for the majority of devices, and configure the individual exceptions on that device's Settings tab.

I set something on a device and then changed the organization defaults. Which one wins? The device setting. An override always beats the organization default — separately for each option. If you want the device to follow the organization again, turn Inherit from organization back on for that option.

How do I know what the headset will actually do? Open the device's Settings tab. Overridden options show their own value; inherited ones show the organization's value labelled Organization. That is exactly what the device receives.

Will new headsets get my settings automatically? Yes. A new device starts with no overrides, so from its first launch it inherits the organization defaults.

Do I have to set anything to get started? No. The defaults mirror how the VR app behaved until now — if that suits you, there is nothing to do here.

Who can change these settings? An organization administrator. A regular member will not see this page.

I turned guest mode off but someone still trained as a guest. The session started before the headset fetched the new value. Restart the app on the headset — the next sessions will require a trainee.