## Immerse Sessions tab
Immerse Sessions are more flexible than Spaces which preceded them. Session owners have more control over content access permissions, whether they are multi or single user and also their expiration date.
**Invitations** - Sessions to which you've been invited (via email)
**My Sessions** - Active Sessions owned by you
**History** - Sessions you've previously created which have now expired
**Legacy spaces** - Spaces created using earlier versions of the Immerse Platform - read earlier documentation for an overview.
If the new Session sub-tab is not visible to you please contact [[email protected]](🔗).
## Creating an Immerse Session
Starting on the **My Sessions** sub-tab, click **(CREATE SESSION)**, which will reveal the New Session panel
To create a new Session:
**Enter a name** for your Session
**Attach a [Scene](🔗)** to your Session
**Choose a geographical region** where the Session will be hosted. By default this will be physically closest to you.
**Choose whether the Session will be 'Single User' or 'Multi User'**. The difference being that a single user session can only be joined by a lone user, whereas multi-user sessions can be joined by multiple people at the same time.
**Choose whether the Session can only be accessed by users who have authenticated via SSO**, to provide extra security. **This feature is only visible to organisations which have Single Sign-On enabled**.
**Invite participants via specific email address or via link**. Adding participants here will trigger a customised email to be delivered to each one, detailing the Session URL (which in turn is used to generate a PIN). Selecting '**via link**' will generate a URL.
**Session URL** - a unique URL which can be shared, to provide access to the Session (e.g. from a learning management system, etc.)
## Session details
**1 Session details**, including name and expiration date
**2 Get PIN reveals a unique 6-digit number**, to be used when joining the Session on a standalone VR headset (e.g. Oculus Quest)
**3 Join Session now**
**4 Manage invited participants**
Show, edit, delete and add participants
Reassign Session ownership
**5 Copy or delete the Session**
## Joining an Immerse Session in a web browser
Only Google Chrome is currently supported for WebGL / browser access
To join an Immerse VR Session, access the join URL (in the form _vr.immerse.io/#########_) using the Google Chrome browser.
(Immerse browser Sessions require use of the laptop microphone and audio, so these are checked before each session. )
If Chrome reports that _vr.immerse.io wants to use your microphone_, you must select _[Allow]_ or you will be unable to join
After access has been granted, an option to join via _[Web]_ or _[VR]_ will be offered - choose _[Web]_
Wait a moment whilst the WebGL content is downloaded.
### The Immerse Session web user interface
_VR user view_ View the [Immerse Scene](🔗) through the eyes of any VR participant (Session owner only)
_Static camera view_ View the [Immerse Scene](🔗) through third person [cameras](🔗) defined in Unity (Session owner only)
_VR view_ Select to view immersive / 3D content (Session owner only)
_Reset scene_ Perform a hard reset, ejecting all users from the Session (Session owner only)
_User list_ View Session participants, check whether they are speaking and mute/unmute them (if Session owner)
## Joining an Android (Oculus Quest) Session
### Installing the APK
Due to licensing restrictions, the Immerse Platform is unable to install APK applications directly to an Oculus Quest. This can currently be done in several ways:
[**Install directly via ADB** ](🔗) (specific [Oculus Quest instructions ](🔗))
[**Deploy via App Lab** ](🔗)
[**Oculus for Business, Oculus-Hosted Apps and Release Channels **](🔗) - for enterprise deployments, this is the recommended process.
### Joining a session
**To join an Immerse Session on an android device as as the Oculus Quest, a PIN must first be entered**. This can be revealed to the attendee in a number of ways:
**1. Via an invitation Email.** When invited to a Session, the user will receive an Email containing their unique PIN **2. Via the _(Get PIN) _button** in the Invitations sub-tab **3. By clicking on a session link** and revealing the URL; choosing Get PIN when prompted.
Due to current platform limitations to create a session and get a pin you must have a scene with a Windows or WebGL build uploaded, if the pin options still do not show please message your Immerse contact for access.
Upon launching the respective Oculus Quest application, built with the latest Immerse SDK, the Session participant will be presented with a PINpad, which is used to enter the PIN.
## Joining an Immerse Session on an HTC Vive / Oculus Rift
**Desktop Immerse VR Sessions are joined via the Google Chrome browser on a Windows PC, with SteamVR enabled.**
To join a Session in a headset, the Immerse VR Launcher application must first be installed. This will be used to initiate every VR session. The Immerse Launcher is a small, executable application, installed on a PC running VR hardware. Once installed, it will initialise when an Immerse VR session has been started and manage the downloading of VR content to the headset. The Immerse Launcher will cache VR content, reducing download times.
**Download and install the Immerse VR Launcher** Firstly download and run the [Immerse Launcher](🔗) . During installation, select _[Yes]_ if asked whether the _Visual C++ 2015 64-Bit Redistributable_ can be installed
**Join Immerse VR Session** Access the join URL (in the form vr.immerse.io/s/#########) using the Google Chrome browser.
(An Immerse VR session requires use of the microphone and headphones on the HMD, so these will be checked before each session. )
If Chrome notifies you that "_vr.immerse.io wants to use your microphone and / or camera_" you must select ‘Allow’ or you will not be able to join the session.
After access has been granted, an option to join via _[Web]_ or _[VR]_ will be offered - choose _[VR]_
The previously installed Immerse Launcher will initialise bringing up this message in Chrome:
Select _[Open ImmerseVRLauncher]_ when prompted.
When the Session is loaded, put on the VR headset.
## Voice communication in an Immerse Session (PCVR / web browser)
When using the Google Chrome browser and PCVR headset, user voice data is sent and received via the browser, ensuring a consistent experience across all platforms.
To mute themselves, a VR user must first remove the headset and use the mute button in the browser.
Voice communication in the Oculus Quest is handled directly in the Immerse app.
## The Immerse Launcher
The Immerse Launcher is a small, executable application, installed on a PC running VR hardware. Once installed, it will initialise when an Immerse VR session has been started and manage the downloading of VR content to the headset.
The Immerse Launcher will cache VR content, reducing download times.
View the [Immerse Launcher release notes](🔗).