Skip to main content

Permissions and Device Access

Permissions and Device Access enforces camera and microphone authorization before starting a video session. The application requires explicit user consent to enable audio and video communication.


This screen includes:

  • Device Elements
    • Camera permission prompt
    • Microphone permission prompt
  • Application Elements (Fallback)
    • Permission guidance message
    • OK button
    • Get Assistance option
    • Close control

Workflow​

This flow starts when the user attempts to start a video session.

Primary Flow​

  1. Select Start Video.
  2. Trigger permission request.
  3. Grant camera and microphone access.
  4. Initialize video session.

Exit Conditions​

  • Granted permissions allow session start.
  • Missing permissions block session start.

Permission Handling​

Grant Flow​

  • Request camera and microphone access.
  • Validate both permissions before session start.

Denial Flow​

  • Display fallback guidance.
  • Require manual enablement in device or browser settings.
  • Allow retry after permissions update.

Grant Permissions Before Starting a Video Session​

important

Camera and microphone access is required to start a video appointment.

  1. On the Appointment Details screen, select Start Video.
  2. Review the permission request for camera and microphone access.
  3. Grant access when prompted by the operating system or browser.
  4. Confirm that the app validates both permissions.
  5. Join the active video session automatically after permissions are grant

Handle Permission Denial​

important

If the user denies access, the video session cannot start.

  1. Review the guidance message displayed by the app.
  2. Enable camera and microphone permissions in device or browser settings.
  3. Return to the app and retry Start Video.

Validations​

These scenarios describe how the app validates permission state before starting a session.

ScenarioApp BehaviorSDK Output
Camera or microphone permission is missing.The app blocks session start and displays guidance.Permission error or blocked action.
Only one permission is granted.The app prevents session start.Validation error for missing permission.
Both permissions are granted.The app starts the video session.Video room initialization response.
Permission prompt is dismissed.The app remains in a non-connected state.No session state change.

Actions​

These scenarios describe how the app responds to permission-related actions.

ScenarioApp BehaviorSDK Output
The user grants access.The app starts the video session.Session initialization state.
The user denies access.The app blocks the session and shows guidance.Authorization or permission error.
The user updates permissions in settings.The app allows retry of session start.Subsequent permission validation response.

WebView Considerations​

note

Permission handling differs in mobile WebView environments.

  • Only one native permission prompt appears per session.
  • After denial, the app cannot trigger another system prompt.
  • Always display a fallback modal with manual enablement steps for iOS and Android.

Endpoint Resources​

Video Permission​

PUT 

/video-permission

Displays the permission request dialog for the specified appointment.

Permission Request​

POST 

/video-permission/update

Updates permission state after the user grants or modifies access.