​

Access and Permissions

​

How Users Enter the App

Scene Manager is normally accessed through a scene-specific URL. The primary route is /scenes/:sceneId, and scene links also depend on an organizationId query parameter behind the scenes.

​

Login Flow

If a user opens a scene while not authenticated:

1. Scene Manager stores the page the user tried to open.
2. The browser redirects to the external authentication service.
3. After successful authentication, the browser returns to the app.
4. The app completes token processing and sends the user back to the pending scene.

​

Authentication

After a successful login, the user is taken to the Scene Editor and can use it.

​

Logout

To sign out, open the profile menu and select Sign Out. After you sign out, you are logged out and returned to the login flow.

​

Unsupported Routes

Scene Manager can show a generic redirect screen for unsupported routes. If the user reaches an unsupported route inside this app, Scene Manager redirects to the dashboard’s VR trainings area.

​

Access Denied

If the current user does not have permission to open a scene or asset, the app shows an Access Denied dialog. The dialog includes the permission-related message and an Okay button that returns the user to the dashboard.

​

Required Access

Users must have:

• A valid authenticated session
• Membership in the target organization
• Permission to access the scene

Users may also be blocked from specific asset access, which triggers the same Access Denied dialog pattern.

​

Permission Behavior

If the app detects a Read-only permission state for a scene, it shows an access-denied experience instead of opening a customer-facing read-only authoring mode.

​

Object Restrictions

The editor intentionally limits actions for some objects:

• Initial User Position cannot be deleted
• Initial User Position cannot be hidden and has reduced editing controls