Skip to main content

Capabilities

Credential issuance: C1 can issue an OpenAI API key against a service account. Issuing mints a new key on that service account and returns it; revoking deletes the key and leaves the service account in place. The connector issues keys with no scopes and no expiry: a service account’s access comes from its project role, and C1 revokes the key when the requested duration ends. Issued keys can be returned encrypted to a recipient key that C1 supplies, so the plaintext key never leaves the connector unencrypted. Issuance requires the Service account key resource type to be enabled. It is off by default. Enable it in the connector’s resource type settings. Syncing this type lists the project API keys of every active project, which an Admin API key created with All permissions can do.
The default-off behavior applies where C1 computes a resource type filter for your tenant. Without that, every resource type syncs, including this one, and listing project API keys needs the Admin API key with All permissions described in Gather OpenAI configuration information.
All service-account-owned project API keys are synced, not only the ones C1 issued, so that pre-existing keys appear in your credential inventory. Deleting a Service account key resource revokes that key in OpenAI, including keys created in the OpenAI console or by another tool. Requesting and expiring a vended credential only ever revokes the key C1 issued.
The endpoints behind issuance and revocation are verified working against the live OpenAI API, but OpenAI documents its delete-project-API-key endpoint as returning an error for keys owned by a service account. If that is ever enforced, revocation fails loudly and the key must be revoked by hand.
Predefined roles supported:
  • Organization roles: Owner, Reader
  • Project roles: Owner, Member, Viewer
Custom roles supported:
  • Organization custom roles (dynamic, fetched per organization)
  • Project custom roles (dynamic, fetched per project)
This connector syncs non-human identities and displays them on the Identities overview dashboard.
Group member listing requires a paid plan. Listing group members and syncing group-inherited role grants requires a Business, Enterprise, or higher OpenAI plan. Free plan accounts will not have group membership grants synced.
Archived projects are not synced. The connector only syncs active (non-archived) projects. Service accounts, groups, and role assignments that exist only under an archived project will not appear in C1.
Account provisioning requires a payment method on the organization. Inviting a user fails with a payment_method_required error if the OpenAI organization has no payment method on file. Add a payment method to the organization before using account provisioning.
Service accounts cannot be created or deleted through the connector. They must be created and deleted directly in OpenAI. The connector only syncs existing service accounts.
Custom project roles require project membership. To assign a custom project role to a user or group, they must already have a predefined project role (Owner, Member, or Viewer). If they don’t, the connector automatically adds them as a Member first.
Custom project roles cannot be assigned to service accounts via the API. The OpenAI API does not support assigning custom project roles to service accounts programmatically. The connector syncs existing custom project role assignments for service accounts, but provisioning (granting) a custom project role to a service account will fail. Use the OpenAI platform to manage custom project role assignments for service accounts.
Predefined organization roles on service accounts cannot be changed via the API. The OpenAI API’s user role update endpoint only accepts human user IDs. Attempting to revoke (downgrade) the owner predefined org role from a service account will fail with an error. Custom org roles on service accounts can still be revoked normally. Manage predefined org role assignments for service accounts directly in the OpenAI dashboard.
The reader organization role cannot be revoked from any principal. reader is the minimum required org role in OpenAI — every organization member must have at least this role. Revoking a reader grant will return an error. To remove all access for a user or service account, delete the principal from the organization entirely.
Organization owners are implicit project owners. OpenAI enforces that organization owners are automatically project owners for all projects. This grant is shown as inherited from the organization owner role and cannot be modified through the connector or the OpenAI API.
Invitation counts fluctuate between syncs. Pending and disabled invitations naturally come and go as users accept, expire, or are revoked. C1 skips sync anomaly detection on the Invitation resource type to avoid false-positive alerts from these expected changes.
Additional functionality: Supports automatic account provisioning and deprovisioning

SCIM provisioning notes

OpenAI supports SCIM-based directory sync for automating user provisioning and deprovisioning. However, there are important limitations to be aware of when planning your provisioning strategy.

Availability

SCIM is only available on certain OpenAI plans:
  • API Platform: Custom or Unlimited billing plans
  • ChatGPT: Enterprise or EDU plans
SCIM is not available on the Business plan. If you are on a plan that does not support SCIM, you must manage users manually or through the OpenAI Admin API.

Configuring SCIM

SCIM is not configured through the OpenAI API. Instead, organization owners enable directory sync through the Identity settings in the OpenAI Platform dashboard. This opens a setup flow through the WorkOS portal, where you connect your identity provider (IdP). Supported identity providers include Okta, Entra ID (Azure AD), Google Workspace, PingFederate, OneLogin, and Rippling, among others.

Limitation: no SCIM Groups support on the API Platform

OpenAI’s SCIM integration on the API Platform does not currently support SCIM Groups. This means:
  • Users provisioned via SCIM are automatically invited to the organization, but they are not assigned to any project.
  • There is no way to use SCIM to automatically map IdP groups to OpenAI projects or roles.
  • Each user provisioned via SCIM must be separately assigned to projects after they join the organization.
SCIM Groups are supported for ChatGPT Enterprise workspaces but not for the API Platform. If you use both products, be aware that group sync behavior differs between them.

Workaround: use the Admin API for project assignments

Because SCIM cannot assign users to projects, you can use the OpenAI Admin API’s Project Users endpoints to manage project membership after a user is provisioned via SCIM. The key endpoints are:
  • Add user to project: POST /v1/organization/projects/{project_id}/users — requires user_id and role (member or owner)
  • Modify project user role: POST /v1/organization/projects/{project_id}/users/{user_id} — update a user’s project role
  • Remove user from project: DELETE /v1/organization/projects/{project_id}/users/{user_id}
The C1 OpenAI connector uses the Admin API to manage project memberships. When you configure C1 to provision access to OpenAI projects, C1 handles these API calls for you, filling the gap that SCIM leaves for project-level access.

What SCIM provides vs. what requires the Admin API

Neither SCIM nor the Admin API currently supports automatically mapping IdP groups to OpenAI projects. To assign users to projects, use C1’s provisioning capabilities with the OpenAI connector, which calls the Admin API on your behalf.

Gather OpenAI configuration information

Configuring the connector requires you to pass in information from OpenAI. Gather these configuration details before you move on. Here’s the information you’ll need:
  • OpenAI Admin API Key (required) — This must be an Admin API key created with All permissions selected. The connector requires full admin permissions to manage users, projects, and invitations. Keys created with “Restricted” permissions will cause the connector to error.
To create the Admin API key:
  1. In the OpenAI platform, navigate to Settings > API keys in the Organization section.
  2. Click Create new admin key.
  3. When prompted to set permissions, select All. Do not select “Restricted”, as the connector requires access to all organization management endpoints.
  4. Copy and save the generated key.
See the OpenAI docs for more information: Admin API Keys documentation

Configure the OpenAI connector

To complete this task, you’ll need:
  • The Connector Administrator or Super Administrator role in C1
  • Access to the set of OpenAI configuration information gathered by following the instructions above
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 OpenAI 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 configuration information from the previous section.
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 OpenAI connector is now pulling access data into C1.