> ## Documentation Index
> Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt
> Use this file to discover all available pages before exploring further.

# RingCentral

> Configure and manage the RingCentral telephony integration, including OAuth connection, extension mapping, and test calls.

RingCentral integration settings page at `/settings/integrations/ringcentral` for configuring telephony connectivity, managing extensions, and testing the phone integration.

## Overview

The RingCentral Settings page consolidates telephony configuration into a tabbed interface with sections for Quick Setup, Extensions management, and connection testing. It uses `useRingCentralConfig` and `useRingCentralSetup` to fetch and update configuration, and `useEmbeddable` to manage the embedded widget state. The page displays connection status badges and supports a **Test Call** action via `TestCallDialog`. Extension management is handled by `RingCentralExtensionsManager`. No route-level `RequirePermission` guard is present; access control may be enforced within sub-components.

## Who it's for

Access follows your organization's role and module configuration. SME: confirm whether staff must hold a specific permission to complete the OAuth setup flow.

## Before you start

* Your organization must have a RingCentral account.
* You must have access to the RingCentral admin portal to retrieve OAuth credentials.
* The Entra ID / Microsoft integration does not need to be configured first — RingCentral is independent.

## Steps

1. Navigate to `/settings/integrations/ringcentral`.
2. Use the **Quick Setup** tab to authorize the RingCentral connection via OAuth.
3. After authorization, verify the connection status badge shows as connected.
4. On the **Extensions** tab, map RingCentral extensions to platform users.
5. Use **Test Call** to verify the integration is working end-to-end.

## Key concepts

**Embeddable widget** — An embedded RingCentral dialer/messenger widget. Managed via `useEmbeddable` and rendered in the platform UI.

**Extension mapping** — Associates a RingCentral extension with a platform user record for call routing. Managed via `RingCentralExtensionsManager`.

**Connection status** — Displayed as a badge; reflects whether the OAuth token is valid and the API is reachable.

## Related

<Columns cols={2}>
  <Card title="Platform Foundation" icon="layer-group" href="/pf/overview">
    Platform Foundation overview.
  </Card>

  <Card title="Governance & parity" icon="scale-balanced" href="/governance/index" />
</Columns>

<Note>
  This page documents shipped product behavior. It is not medical, legal, or
  billing advice. Verify against your organization's policies and applicable
  regulations before using it for clinical, compliance, or billing decisions.
  Protected health information (PHI) shown in the product is governed by your
  tenant's access controls and is never exposed in this documentation.
</Note>

<Accordion title="Documentation sources">
  * src/routes/platform.tsx
  * src/platform/settings/pages/RingCentralSettingsPage.tsx
  * src/platform/integrations/hooks/useRingCentralConfig.ts
  * src/platform/telephony/hooks/useEmbeddable.ts
</Accordion>