Skip to content
Documentation

Get started with RTC

You need a CHAMPREP account with RTC enabled for the profile you intend to use. Use a current WebRTC-capable browser and HTTPS. A microphone and camera are needed to publish your own audio and video; your browser asks for permission. Do not record another person without the appropriate notice and permission.

  1. Open CHAMPREP RTC.
  2. Select Sign in or Get started. Both use CHAMPREP’s central account flow; you do not create a separate RTC password.
  3. Return to RTC and confirm the active profile in the header. Use the profile menu to switch accounts when necessary.
  4. If prompted, enter your organization name and select Create organization. This initializes the RTC workspace; it does not create an independent paid subscription or grant a plan that you do not have.

The header’s plan control shows the current plan and available RTC allowances. If access is denied, first check your profile and subscription rather than creating another organization.

  1. Open Projects and select Create project.
  2. Enter a descriptive name, such as Customer conversations, and select Create.
  3. Use Copy project ID when configuring a server integration.

Projects group your application’s resources. Create separate projects and keys for integrations that should not share room and recording access. A name is not an authorization boundary; permissions follow the project identifier and key.

  1. Open Rooms and select Create room.
  2. Choose the project, enter a name, and set Participants per room within the displayed allowance.
  3. Select Create, then Join on the room row.
  4. Allow the browser’s microphone and camera requests if you want to publish. Permission denial can prevent local media even when a connection is established.
  5. Use Mute microphone, Toggle camera, and Share screen as needed. Screen sharing opens the browser’s source chooser.
  6. Choose Low bandwidth under Receive quality to request lower-quality incoming video. Adaptive video restores the normal receive mode.
  7. Select Leave call when finished.

Leave call disconnects you, not everyone. End room closes the room to new joins and ends its active sessions. An ended room cannot be reopened with the current API; create another room for a new session.

The console is a developer testing surface, not a public meeting invitation system. To admit your application’s users, implement the participant token flow.

PageUse it to
API keysCreate a scoped key, copy its secret once, or revoke it
RecordingsInspect recording status, stop an active job, and download ready tracks
UsageView completed connections, participant minutes, and plan allowances
WebhooksSet an HTTPS event destination and rotate its signing secret

Use Refresh to reload a list after an asynchronous operation. Search filters the records already loaded on that page, not the complete account history. Lists currently return up to 100 records; see current limitations.

The header also offers notifications, service navigation, profile controls, and appearance settings consistent with the wider CHAMPREP workspace.