# What each CMS needs to register a Pearl device

*Applies to: Pearl-2, Pearl Mini, Pearl Nano, Pearl Nexus.*

Gather these details before you begin. Every CMS integration starts on the same page of the Pearl Admin panel: log in as **admin**, go to **Configuration**, then **CMS**, and select your platform from the **Choose CMS** drop down.

| CMS platform | Details required to register the Pearl device |
|---|---|
| **Panopto** | Service URL (for example `https://<myorg>.hosted.panopto.com/`) and a Panopto-generated **Registration key**. A **Device name** is optional. |
| **Kaltura** | Either your **Partner ID** and **Administrator secret**, or an application **Token ID** and **Token value**. When using an application token, the **Token hash type** must match the hash type set on the token; the default is **SHA1**. A **Resource name** is optional. |
| **YuJa** | **YuJa Service URL**, an **Authentication token** (called an API Token in YuJa), the **User ID Type**, and the **User ID**. |
| **Opencast** | **Service URL**, **username**, and **password** for an Opencast user that holds the required capture-agent roles. |
| **EchoVideo (Echo360)** | **Client ID** and **Client Secret** from EchoVideo. The Echo360 application must be installed on the Pearl device first, which requires the device to be registered with Epiphan servers, running firmware 4.24.5 or newer, and to have storage installed. |

Where to obtain each credential, and the full registration procedure, is documented in the guide for each platform.

**Device differences**

- **Pearl Nano:** Pearl Nano does not support EchoVideo (Echo360). It does not support application containers, so the Echo360 application cannot be installed.

> product: cms · topic: cms-integration · source: pearl-cms-common.md · updated: Sep 28, 2026