Set up a PostHog connector

C1 provides identity governance for PostHog. Integrate your PostHog organization with C1 for unified visibility and governance over user access.

C1 provides identity governance for PostHog. Integrate your PostHog organization with C1 for unified visibility and governance over user access.

Capabilities

Resource	Sync	Provision
Users
Roles

Gather PostHog credentials

Use a PostHog Personal API key with read access to organization members and roles. The key must belong to a member of the organization you want to sync.

1. In PostHog, open Settings > Personal API keys and create a key. Grant it read access to organization members and roles (organization_member:read and organization:read).

2. Copy the key value. PostHog shows it only once.

3. Find your organization id in Settings, or copy it from the dashboard URL. Build the organization API base URL from your region host and that id, for example https://us.posthog.com/api/organizations/<organization_id>. Use https://eu.posthog.com for the EU region, or your own host for a self-hosted deployment.

Configuration fields

Field	Required	Description
base-url	Yes	Your PostHog organization API base URL, ending in /api/organizations/<organization_id>. One connector instance syncs one organization.
api-token	Yes	A PostHog Personal API key, sent as a bearer token.

Synced resource types

• Users: organization members from /members/. The organization seat (member, administrator, or owner) is recorded on the user profile.
• Roles: access-control roles from /roles/.
• Role memberships: each role’s members from /roles/{role_id}/role_memberships/, surfaced as grants on the role’s member entitlement.

Special notes

• The connector is read-only. It does not create or change PostHog members or roles.
• One connector instance syncs exactly one organization, set by the organization id in the base URL. To sync more than one organization, add a connector instance per organization.

Configure the PostHog connector

Cloud-hosted

Follow these instructions to use a built-in, no-code connector hosted by C1.

1. In C1, navigate to Apps > Connectors and click Add connector.

2. Search for PostHog and click Add.

3. Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).

   If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.

4. Set the connector’s Name and, optionally, a Description.

5. Click the pencil icon next to Owners to choose who can configure and manage this connector.

6. Click Add. The connector is created and its configuration page opens.

7. Find the Settings area of the page and click Edit.

8. Enter the PostHog credentials:

   • Organization API base URL: The base URL ending in /api/organizations/<organization_id>.
   • Personal API key: The PostHog Personal API key.
9. Click Save.

10. The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

Done. Your PostHog connector is now pulling access data into C1.

Self-hosted

Follow these instructions to run the PostHog connector in your own environment.

1. In C1, navigate to Apps > Connectors and click Add connector.

2. Search for Baton and click Add, then set the owner and click Next.

3. Configure C1 credentials and PostHog credentials as environment variables:

   BATON_CLIENT_ID=<C1 client ID>
   BATON_CLIENT_SECRET=<C1 client secret>
   BATON_HOST_ID=baton-posthog
   BATON_BASE_URL=<Organization API base URL ending in /api/organizations/{organization_id}>
   BATON_API_TOKEN=<PostHog Personal API key>
   
4. Deploy the connector using your standard self-hosted connector process.

Done. Your PostHog connector is now pulling access data into C1.