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

# Cloud Services

> Connect Google Workspace and Kaltura to a Digital Twin so it can work with calendars, documents, mail, and video.

Cloud Services let a Digital Twin reach into Google Workspace and Kaltura on behalf of your users. You configure them per instance in the **Configuration and Integrations** tab of the instance editor.

<Info>
  Cloud Services are available to account admins with the **`institutions.edit`** entitlement — no help from the Praxis team required.
</Info>

## Google Services

Enable the Google capabilities your Twin should be able to use:

| Service              | What it enables                             |
| -------------------- | ------------------------------------------- |
| **Gmail**            | Read and send mail                          |
| **Google Drive**     | Read files and metadata                     |
| **Google Calendar**  | Read calendars and events                   |
| **Google Meet**      | Meeting context                             |
| **Google Sheets**    | Read spreadsheets                           |
| **Google Docs**      | Read documents                              |
| **Google Slides**    | Read presentations                          |
| **Google Classroom** | Read courses and coursework                 |
| **Google Maps**      | Location lookups (API-key based, not OAuth) |

<Note>
  Enabling a service requests only the OAuth scopes that service needs (for example, read-only Drive access or Calendar events). Some services depend on others — Docs, Sheets, and Slides require Drive, and Meet requires Calendar; enabling a child service automatically enables its parent.
</Note>

### Two ways to connect

When you enable Google Services you choose **how** the Twin authenticates:

<Tabs>
  <Tab title="Personal accounts (default)">
    Each user connects **their own** Google account. The Twin acts on that user's data using their individual authorization. This is the default when **Use Digital Twin identity** is off.

    Users authorize and revoke their own access from their profile — see [Google Services](/mdx/user-guide/profile-settings/google-services).
  </Tab>

  <Tab title="Shared Digital Twin identity">
    Turn on **Use Digital Twin identity** to connect **one shared Google account** for the whole Twin. Every user reaches Google through that single account, which an admin authorizes once via **Connect Google Account**.

    Use this when the Twin should operate against an institutional mailbox, drive, or calendar rather than each user's personal data.
  </Tab>
</Tabs>

<Steps>
  <Step title="Open the instance editor">
    **Admin → Digital Twin → edit an instance → Configuration and Integrations**, then scroll to **Google Services**.
  </Step>

  <Step title="Enable access">
    Turn on **Enable Access** to make Google Services available in this Twin.
  </Step>

  <Step title="Choose the identity model">
    Leave **Use Digital Twin identity** off for personal accounts, or turn it on for a shared institutional account.
  </Step>

  <Step title="Select services">
    Toggle on the specific Google services the Twin should use.
  </Step>

  <Step title="Connect (shared mode only)">
    If you enabled the shared identity, click **Connect Google Account** and complete the Google OAuth consent for the institutional account. Once connected, the page shows the connected email address and the last token refresh; tokens refresh automatically in the background. Click **Disconnect** to revoke the authorization and clear the institution credentials.
  </Step>
</Steps>

<Warning>
  When a shared Digital Twin identity is connected, it takes precedence over any personal Google account a user may have authorized — everyone reaches Google through the shared account. Service selection is also locked while connected; to change which services are enabled, disconnect and reconnect.
</Warning>

<Warning>
  Google Services require platform-level Google OAuth credentials to be configured for Pria. If the **Connect Google Account** flow fails or services don't appear, contact the Praxis AI team at [humans@praxis-ai.com](mailto:humans@praxis-ai.com) to confirm Google OAuth is set up for your environment.
</Warning>

## Kaltura

The same Configuration tab includes **Kaltura** settings for connecting your video platform, so the Twin can search and reference video content hosted in your Kaltura account:

| Field               | Purpose                                                                                                                                            |
| ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Partner ID**      | Your Kaltura account (partner) identifier — found in the Kaltura Management Console under **Settings → Integration Settings**                      |
| **Secret**          | The Kaltura API secret, found alongside the Partner ID. Can be an **Admin Secret** (full account access) or a **User Secret** (limited, read-only) |
| **Is Admin Secret** | Turn on when the secret is an admin-level secret; when off, a **Client ID** (the Kaltura User ID associated with the secret) is also required      |

<Warning>The Kaltura secret is a sensitive credential. It is stored encrypted and excluded from API responses by default.</Warning>

## Related

* [Google Services (user guide)](/mdx/user-guide/profile-settings/google-services) — how users authorize their own accounts
* [Google Workspace integration](/mdx/integrations/google-workspace/overview) — integration overview
* [Configuration](/mdx/admin-guide/configuration) — the rest of the instance configuration tab
* [Tools](/mdx/admin-guide/tools) — enabling the tools that act on connected services