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

# Integrations Overview

> Connect Regentra with Microsoft Entra ID, Level.io RMM, Stripe, and cloud providers. All credentials are encrypted with AES-256-GCM.

Regentra integrates with the tools MSPs already use. Each integration runs at the organization level with credentials encrypted using AES-256-GCM before storage.

## Available integrations

<CardGroup cols={2}>
  <Card title="Microsoft Entra ID" icon="microsoft" href="/integrations/microsoft-entra">
    SSO, user/device sync, conditional access + MFA evidence.
  </Card>

  <Card title="Microsoft 365 SSO" icon="microsoft" href="/integrations/microsoft365-sso">
    Staff and portal login through your Microsoft tenant.
  </Card>

  <Card title="Level.io RMM" icon="server" href="/integrations/level-rmm">
    Device and asset sync with real-time webhook updates.
  </Card>

  <Card title="Okta" icon="key" href="/integrations/okta">
    User provisioning, MFA enrollment, sign-in event poll.
  </Card>

  <Card title="Cisco Duo" icon="shield-check" href="/integrations/duo">
    MFA enrollment, global policy, admin inventory, auth-log aggregate.
  </Card>

  <Card title="Google Workspace" icon="google" href="/integrations/google-workspace">
    User directory sync via service-account delegation.
  </Card>

  <Card title="Proofpoint SAT" icon="graduation-cap" href="/integrations/proofpoint-sat">
    Training-completion and phishing-simulation results.
  </Card>

  <Card title="Huntress Managed SAT" icon="graduation-cap" href="/integrations/huntress-sat">
    Workforce coverage and phishing-simulation evidence.
  </Card>

  <Card title="GitHub" icon="github" href="/integrations/github">
    Change-management evidence from repository activity.
  </Card>

  <Card title="Jira" icon="ticket" href="/integrations/jira">
    Issue tracking integration for change management.
  </Card>

  <Card title="Stripe" icon="credit-card" href="/integrations/stripe">
    Per-org PSA invoicing and platform subscription billing.
  </Card>

  <Card title="QuickBooks Online" icon="book" href="/integrations/quickbooks">
    Customer + invoice push with Stripe-paid bridging.
  </Card>

  <Card title="Microsoft Teams — Chat Bridge" icon="comments" href="/integrations/teams-chat-bridge">
    Bidirectional bridge between Teams chats and PSA tickets.
  </Card>

  <Card title="Regentra Bot — Teams" icon="robot" href="/integrations/regentra-bot">
    Compliance + ticket commands inside Teams.
  </Card>
</CardGroup>

<Note>
  AWS and GCP **evidence collection** runs on a separate code path from the
  Settings → Integrations card list — it's configured under
  **Compliance → Settings → Evidence Collection**. The cards above are the
  ones surfaced on the per-org Integrations page.
</Note>

## How integrations work

Each integration stores encrypted credentials at the organization level. Regentra uses **AES-256-GCM** encryption for all stored secrets (API keys, OAuth tokens, client secrets). Credentials are decrypted only at the moment of use and never logged.

Integrations sync data on a schedule (typically every 6 hours) and can also be triggered manually. Some integrations support real-time updates via webhooks.

## Connecting an integration

<Steps>
  <Step title="Navigate to integrations">
    Go to **Settings → Integrations** to see all available integrations.
  </Step>

  <Step title="Select the integration">
    Click on the integration you want to connect. Each one has its own setup flow.
  </Step>

  <Step title="Enter credentials">
    Provide the required credentials — API keys, OAuth consent, or connection details depending on the integration.
  </Step>

  <Step title="Test the connection">
    Click **Test Connection** to verify that Regentra can communicate with the external service.
  </Step>

  <Step title="Save and enable">
    Save the configuration. The integration begins syncing data on its next scheduled run, or you can trigger an immediate sync.
  </Step>
</Steps>

## Connection status

Each integration shows its current status on the integrations page:

| Status             | Meaning                                                          |
| ------------------ | ---------------------------------------------------------------- |
| **Connected**      | Credentials are valid and the last sync succeeded                |
| **Error**          | The last sync failed — check credentials or service availability |
| **Not configured** | The integration has not been set up yet                          |

<Tip>
  If an integration shows an error, click into it to see the error details. Common issues include expired OAuth tokens (re-authorize) and revoked API keys (regenerate).
</Tip>