Use MediaSFU dashboards

MediaSFU dashboards give signed-in users a place to configure and operate the products they have access to. You can use a lightweight workspace for everyday meetings and calls, a developer workspace for building integrations, or an Agents workspace for agent and handoff operations.

This guide covers the parts intended for ordinary account users. What appears in the navigation depends on your account, role, enabled products, and current entitlements. A hidden or disabled section is an access decision, not a signal to expose a key or bypass the dashboard.

Choose your dashboard

Workspace	Best for	Typical work
Lite	Everyday use with a small operational surface	Start meetings, review calls and recordings, manage contacts or campaigns, and update personal settings
Developer	Building and operating a MediaSFU integration	Configure rooms and events, widgets, recording, translation and notes, domains, application keys, and activity
Agents	Running AI-assisted support or voice workflows	Configure agents, review sessions, manage handoff workflows, and monitor operator work

You can move between workspaces from the signed-in dashboard navigation. Start with Lite when you only need to run sessions. Choose Developer when you are embedding MediaSFU in your application. Choose Agents when your main task is agent configuration, conversations, or human handoff.

Lite dashboard

The Lite dashboard keeps everyday work in one small workspace. Depending on your role and entitlements, it can include meetings, calendar, calls, recordings, contacts, campaigns, support, and personal settings.

Developer dashboard

The Developer dashboard is for building and operating an integration. Its available sections can include rooms, room and event settings, activity, recording setup, AI Notes, translation and notes setup, Widget Builder, agent configuration, domains, and application keys.

Agents workspace

The Agents workspace focuses on agent configuration, sessions, and human handoff. It is useful when an operator needs a focused view of assigned agent work instead of the broader developer workspace.

What you can manage

The following areas are designed for account owners and other roles granted access by the account:

• Overview and Activity: review account-level usage and recent activity.
• Rooms and Room & Event Settings: create rooms and choose defaults for meetings, calls, recording, translation, and AI Notes.
• Calls and Call History: start supported call workflows and review the history available to your account.
• Recordings: find recordings your account is allowed to access. Configure recording before the session; an authorized host may start recording during a session where recording is supported. Content from before recording starts cannot be captured retroactively.
• AI Notes and Translation & Notes Setup: configure transcription, translation, summaries, and follow-up notes where the selected services and entitlement allow them.
• Widget Builder: configure embeddable call, meeting, agent, and dashboard surfaces. See Embed MediaSFU widgets for the public widget integration contract.
• Agents, Agent Configs, and Phone & SIP Setup: configure agent-facing workflows and their approved voice or telephony connections. Provider credentials remain account secrets and belong in the protected configuration flow, never in a browser snippet.
• Profile, App Settings, Billing History, Credits & Balance, and Support: manage the account information and support or billing views made available to your role.

The dashboard may show an upgrade, request-access, or unavailable state instead of a section. Follow that state or contact the account owner; do not copy a credential from another user or attempt to call a private service directly.

Open a dashboard section

These links open the Developer dashboard. Sign in first; the selected section still requires the appropriate account role and entitlement.

Section	Use it for
Rooms	Room management
Room & Event Settings	Session defaults
Cloud Recording Setup	Recording configuration
Recordings	Authorized recording access
AI Notes	Session notes and summaries
Translation & Notes Setup	Language and notes configuration
Phone & SIP Setup	Approved telephony configuration
Widget Builder	Embed configuration
Allowed Domains	Approved application origins
Profile	Personal account settings
Sub-Users	Delegated account access where your role permits it
Support Tickets	Account support

Account permissions and privacy

Dashboard visibility is scoped to the signed-in identity. Account owners may see more configuration and billing information than a delegated user. Some roles can use meetings and calls while remaining unable to view balance, subscription, or other account-owner information.

The MediaSFU Copilot can explain the public dashboard documentation and point you to the relevant guide. It cannot inspect your plan, balance, recordings, call history, role, or private dashboard state, and it cannot change those values for you. Never paste API keys, provider tokens, session grants, passwords, private URLs, or customer records into a chat or browser console.

A safe first run

1. Sign in with the account and role that should own the work.
2. Choose Lite, Developer, or Agents based on the job above.
3. Open the relevant setup section and confirm the available entitlement before creating a room, widget, agent, or call workflow.
4. Run a small test with non-sensitive data. For a room, verify entry, participant media, the intended recording or notes behavior, and a clean leave before inviting users.
5. For an embed, restrict its allowed origins and use a short-lived, server-issued session grant. Keep reusable MediaSFU and provider credentials on your authenticated backend.

Recover when something is missing

• The workspace or section is absent: confirm that you are signed in with the intended account and role. Ask the account owner to check entitlement or access rather than sharing credentials.
• A room will not start or join: verify the room name, browser permissions, network access, and the authenticated room-entry flow. Retry with a fresh short-lived grant if the previous one expired.
• A recording or note is missing: check the recording setup and whether recording actually started for the relevant part of the session. For notes, check that AI Notes was enabled and the selected translation configuration is available to the account.
• A widget or agent is rejected: verify the widget key, allowed origin, configured surface, and backend authorization. A public widget key does not grant access to account data or operator actions.
• A call or handoff is unavailable: confirm that the selected telephony or agent capability is enabled and that the assigned role permits the action. Contact support with a timestamp and non-sensitive session identifier.

Before sharing or releasing

• Test with the exact role and entitlement your users will have.
• Keep secrets, provider credentials, and reusable room authority on your backend.
• Restrict widget origins and embedded-frame permissions.
• Confirm recordings, notes, calls, and agent data are visible only to the intended audience.
• Test browser permissions, expired grants, reconnect, leave, and cleanup.
• Review local privacy, recording-consent, and retention requirements.

For custom room interfaces, continue with UI modes and ownership. For secure room creation and joining, see Secure backend proxy. For embeddable surfaces, see Embed MediaSFU widgets.