Set up a Notion connector

Availability

C1 currently only integrates with Notion Enterprise. You cannot use this connector successfully with the Free, Plus, or Business editions of Notion.

Capabilities

Resource	Sync	Provision
Accounts
Groups
Roles

The Notion connector supports automatic account provisioning, account deprovisioning (removal from the workspace), and role provisioning. All operations are performed against the Notion SCIM API. Role resources model the four workspace role values Notion exposes through the SCIM extension (owner, membership_admin, member, restricted_member) — see the “Provision restricted members through SCIM” section of the Notion help center for the value enum. Notion users must always carry a role, so revoking a role is modelled as a downgrade to restricted_member. To fully remove a user from the workspace, deprovision the account. Account deprovisioning removes the user from the workspace and revokes their active sessions. As documented by Notion, this does not permanently delete the underlying user account — that step must be performed manually in Notion.

“License” in Notion product terminology means paid seat — i.e. one workspace member — and is binary (member vs. guest), not tiered. See the Notion billing help center for details. The Notion SCIM API does not expose a /Licenses endpoint, which is why this connector models the workspace role (rather than a “license”) as a first-class resource.

Gather Notion credentials

Configuring the connector requires you to pass in credentials generated in Notion. Gather these credentials before you move on.

A user with the Organization Owner role in Notion must perform this task.

Create a SCIM API token

In the Notion workspace switcher, select Manage organization.

Navigate to Settings > Identity > SCIM Provisioning.

Follow the prompts to generate a SCIM API token.

Carefully copy and save the SCIM API token.

For more information, see Provision users & groups with SCIM.

Configure the Notion connector

To complete this task, you’ll need:

The Connector Administrator or Super Administrator role in C1
Access to the set of Notion credentials generated by following the instructions above

Cloud-hosted
Self-hosted

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

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

Search for Notion and click Add.

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.

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

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

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

Find the Settings area of the page and click Edit.

Paste the SCIM API token into the Notion SCIM API token field.

Click Save.

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

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

Follow these instructions to use the Notion connector, hosted and run in your own environment.When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1 UI for access reviews and access requests.

Resources

GitHub repository: Access the source code, report issues, or contribute to the project.

Step 1: Set up a new Notion connector

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

Search for Baton and click Add.

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

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

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

In the Settings area of the page, click Edit.

Click Rotate to generate a new Client ID and Secret.Carefully copy and save these credentials. We’ll use them in Step 2.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your Notion connector deployment.The Secret carries the credentials the connector needs at runtime:

scim-token (required): The Notion SCIM token used to connect to the Notion SCIM API.

Secrets configuration

# baton-notion-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-notion-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>

  # Notion credentials
  BATON_SCIM_TOKEN: <Token used to connect to the Notion SCIM API>

  # Optional: include if you want C1 to provision access using this connector
  BATON_PROVISIONING: true

Deployment configuration

# baton-notion.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-notion
  labels:
    app: baton-notion
spec:
  selector:
    matchLabels:
      app: baton-notion
  template:
    metadata:
      labels:
        app: baton-notion
        baton: true
        baton-app: notion
    spec:
      containers:
      - name: baton-notion
        image: ghcr.io/conductorone/baton-notion:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-notion
        envFrom:
        - secretRef:
            name: baton-notion-secrets

Step 3: Deploy the connector

Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.

Check that the connector data uploaded correctly. In C1, click Apps. On the Managed apps tab, locate and click the name of the application you added the Notion connector to. Notion data should be found on the Entitlements and Accounts tabs.

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

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

Set up a Notion connector

Availability

Capabilities

Gather Notion credentials

Create a SCIM API token

Configure the Notion connector

Resources

Step 1: Set up a new Notion connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

​Availability

​Capabilities

​Gather Notion credentials

​Create a SCIM API token

​Configure the Notion connector

​Resources

​Step 1: Set up a new Notion connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Availability

Capabilities

Gather Notion credentials

Create a SCIM API token

Configure the Notion connector

Resources

Step 1: Set up a new Notion connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector