This Functionality Requires the Application to Have Insights
ArborXR Insights is a product suite by ArborXR, and managing the User Identification Policies is one of the features Insights enables. For Insights features to work for your ArborXR organization, the applications you use must have Insights integrated into them by the content developer. Click here to learn more about Insights.
How User Identification Policies Support Authentication of Users
User Identification Policies can be managed at two levels currently, the Organization level, and the Group level. Group settings will override Organization-wide settings.
To find the Organization-wide settings, go to Organization Settings in the ArborXR Portal. Then navigate to Authentication.
Here, you'll see User Identification Policies for Applications:
💡 You'll notice we have a toggle for PII. The PII that is collected is stored by ArborXR to show to you, so you can view your data on a per-user level. PII stored by Insights includes location data and basic user information based on what you set for your policy.
Once you select one of these, every time an Insights-integrated application is launched on one of the headsets in your organization, the user will be prompted to input. Once they do, all data recorded for that session will be attributed to that users respective input, so you can understand how they're learning.
There are 4 options to choose from, which we'll go over in detail below:
LMS Integrations
If you've created an LMS connection already, then you'll be able to set it when choosing LMS PIN.
Once selected, when a user opens an insights-supported application, they'll see an input prompt for a PIN or QR Code within the headset experience. This is generated via the LMS:
💡 This is an example from a popular supported LMS, Moodle, of what the learner might see before putting on the headset.
Once they enter the PIN, or on supported headsets, scan the QR code, the user will begin their experience. After the experience is complete, all data from it will be tied to that specific user and shown both in the LMS and in ArborXR analytics.
When selecting LMS, there's also an option to select a Fallback method. This is so that if an Insights-supported application is launched that doesn't yet have an LMS connection created for it, you're still able to capture data on a per-user basis.
Email Domain
For the Email Domain option, you will input the expected email domain that all users will have, and confirm.
Once confirmed, when a user opens an insights-supported application, they'll see an input prompt for their email, with the domain prefilled for ease-of-use.
Once they enter the email, the user will begin their experience. After the experience is complete, all data from it will be tied to that specific user.
💡 This is a form of trust-based authentication, meaning that we cannot vet that they entered a correct or valid email. The data will be tied to whatever they inputted for that particular experience.
Name/ID/Custom
Finally, we provide a fully customizable input you can request as the user's identifier. This could be anything from a Learner ID, Student Number, First Name, etc.
Once confirmed, when a user opens an insights-supported application, they'll see an input prompt for whatever you enter here.
So for example, if I have 8 learners, and I assign each of them a 4-digit number that I tell them they must input, and call it their Learner ID, I would set this field to Learner ID.
Then, once they enter the number in the headset, the user will begin their experience. After the experience is complete, all data from it will be tied to that specific input.
💡 This is a form of trust-based authentication, meaning that we cannot vet that they entered a correct or valid input. The data will be tied to whatever they inputted for that particular experience.
Customizing at a Group Level
You may not want every group in your organization to have the exact same policy, so Insights also allows you to override your Organization-wide settings at the Group level.
To customize this:
First navigate to the group you want to customize within Devices & Groups
Navigate to the Kiosk Experience tab
Scroll down to find the User Identification Policy section and customize to your liking, selecting from the same options as described above
Once saved, when an Insights-integrated application is launched from a headset within that group, the correct input modal will display on experience launch.