Linking Descope as a source
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.
This source is currently in alpha. The interface and available tables may change.
The Descope connector syncs your identity and access management data – users, audit trail events, tenants, roles, and access keys – into the PostHog data warehouse, so you can analyze authentication patterns, user management, and security events alongside your product data.
Prerequisites
- A Descope project.
- A Management Key with read permissions. You can create one in the Descope Console under Project Settings > Company/Management Keys.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
When linking Descope, you'll need:
- Project ID – your Descope project identifier. Find it in the Descope Console under Project Settings.
- Management Key – create one in the Descope Console under Project Settings > Company/Management Keys. The key must have read permissions for the data you want to sync.
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
The users table supports incremental sync on either createdTime or modifiedTime. The audit table supports incremental sync on occurred. The tenants, roles, and access_keys tables are full refresh only because the Descope API doesn't expose incremental filters for these endpoints.
Configuration
| Option | Type | Required |
|---|---|---|
Project ID | text | Yes |
Management key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
Users | Users registered in the Descope project, searchable across tenants, roles, and status. | Incremental, Full refresh | createdTime, modifiedTime | — |
Audit | Authentication and management audit trail events for the project, available for up to the last 30 days. | Incremental, Full refresh | occurred | — |
Tenants | Tenants configured in the Descope project. | Full refresh | — | — |
Roles | Roles defined in the Descope project, with their granted permissions. | Full refresh | — | — |
AccessKeys | Access keys used to authenticate machine-to-machine requests against the Descope project. | Full refresh | — | — |
Troubleshooting
- Authentication errors – Your Project ID or Management Key may be invalid or expired. Verify them in the Descope Console under Project Settings and reconnect.
- Missing data in the audit table – The audit table generates a synthetic unique ID from event fields because the Descope API doesn't provide one. Audit data is available for up to the last 30 days. If you see unexpected duplicates, contact support.
- Permissions errors – Your Management Key may not have sufficient read permissions. Check key permissions in the Descope Console.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.