> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking Okta as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/okta

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://app.posthog.com` (app host for links).

## On this page

- [Schemas](#schemas)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

`npx @posthog/wizard warehouse`

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

The Okta connector can link users, groups, applications, logs (audit events), group rules, and user types to PostHog.

To link Okta:

1.  Go to the [sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section in PostHog.

2.  Click **\+ New source** and then click **Link** next to Okta.

3.  Enter your **Okta domain** (e.g., `your-org.okta.com`).

4.  Next, you need an API token from Okta. In the Okta Admin Console, go to **Security** > **API** > **Tokens** and click **Create token**. Give it a descriptive name and copy the token value.

    The token's user should have read access to the resources you want to sync. The following scopes are recommended:

    -   `okta.users.read`
    -   `okta.groups.read`
    -   `okta.apps.read`
    -   `okta.logs.read`
5.  Back in PostHog, paste the token in the **API token** field and click **Next**.

6.  Set up the schemas you want to sync and modify the method and frequency as needed. Once done, click **Import**.

Once the syncs are complete, you can start using Okta data in PostHog.

## Schemas

The following schemas are available:

| Schema | Sync mode | Description |
| --- | --- | --- |
| `users` | Incremental | Okta user accounts |
| `groups` | Incremental | Okta groups |
| `applications` | Incremental | Okta applications and SSO integrations |
| `logs` | Incremental (append-only) | Okta System Log audit events. Only syncs the last 90 days on initial sync. |
| `group_rules` | Full refresh | Group membership rules |
| `user_types` | Full refresh | Custom user type definitions |

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `Okta domain` | text | Yes |
| `API token` | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `users` | An Okta user account, with profile, credentials, and lifecycle status. | Incremental, Full refresh | lastUpdated | — |
| `groups` | An Okta group used to manage membership and assign apps and policies. | Incremental, Full refresh | lastUpdated | — |
| `applications` | An application integrated with Okta for single sign-on and provisioning. | Full refresh | — | — |
| `logs` | Only syncs the last 90 days on initial sync | Incremental, Full refresh | published | — |
| `group_rules` | A rule that automatically assigns users to Okta groups based on conditions. | Full refresh | — | — |
| `user_types` | A user type that defines the profile schema available to Okta users. | Full refresh | — | — |