> ## Documentation Index
> Fetch the complete documentation index at: https://www.c1.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up a Fullstory connector

> C1 provides identity governance for Fullstory. Integrate your Fullstory instance with C1 for unified visibility and governance over user access.

## Capabilities

| Resource | Sync                                                          | Provision |
| :------- | :------------------------------------------------------------ | :-------- |
| Accounts | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |           |

## Gather Fullstory credentials

Configuring the connector requires a SCIM bearer token and your organization's SCIM base URL, both generated in Fullstory. Gather these credentials before you move on.

<Warning>
  A user with the Admin or Architect role in Fullstory must perform this task.
</Warning>

### Generate a SCIM token

For detailed instructions on enabling SCIM provisioning in Fullstory, see the [official Fullstory SCIM configuration guide](https://help.fullstory.com/hc/en-us/articles/30544962047383-Configuring-SCIM-for-Automated-User-Provisioning-in-Fullstory#h_01JP0WHM089K089M0K8JD8ZWK8).

<Steps>
  <Step>
    In Fullstory, navigate to **Settings** > **Account Management** > **SSO**.
  </Step>

  <Step>
    Enable **SCIM Provisioning** if it is not already active.
  </Step>

  <Step>
    Click **Generate Token** (or **Regenerate Token** if one already exists). Carefully copy and save the token — it will not be shown again.
  </Step>

  <Step>
    Copy the **SCIM Base URL** shown on the same page. It typically looks like `https://app.fullstory.com/scim/v2`.
  </Step>
</Steps>

**Done.** Next, move on to the connector configuration instructions.

## Configure the Fullstory connector

<Warning>
  To complete this task, you'll need:

  * The **Connector Administrator** or **Super Administrator** role in C1
  * Access to the set of Fullstory credentials generated by following the instructions above
</Warning>

<Tabs>
  <Tab title="Cloud-hosted">
    **Follow these instructions to use a built-in, no-code connector hosted by C1.**

    <Steps>
      <Step>
        In C1, navigate to **Integrations** > **Connectors** and click **Add connector**.
      </Step>

      <Step>
        Search for **Fullstory** and click **Add**.
      </Step>

      <Step>
        Choose how to set up the new Fullstory connector:

        * Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren't yet managed with C1)

        * Add the connector to a managed app (select from the list of existing managed apps)

        * Create a new managed app
      </Step>

      <Step>
        Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.

        If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.
      </Step>

      <Step>
        Click **Next**.
      </Step>

      <Step>
        Find the **Settings** area of the page and click **Edit**.
      </Step>

      <Step>
        Paste your SCIM base URL into the **SCIM Base URL** field and your SCIM token into the **SCIM Token** field.
      </Step>

      <Step>
        Click **Save**.
      </Step>

      <Step>
        The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing.
      </Step>
    </Steps>

    **Done.** Your Fullstory connector is now pulling access data into C1.
  </Tab>

  <Tab title="Self-hosted">
    **Follow these instructions to use the Fullstory 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](https://github.com/conductorone/baton-fullstory): Access the source code, report issues, or contribute to the project.

    ### Step 1: Set up a new Fullstory connector

    <Steps>
      <Step>
        In C1, navigate to **Integrations** > **Connectors** > **Add connector**.
      </Step>

      <Step>
        Search for **Baton** and click **Add**.
      </Step>

      <Step>
        Choose how to set up the new Fullstory connector:

        * Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren't yet managed with C1)

        * Add the connector to a managed app (select from the list of existing managed apps)

        * Create a new managed app
      </Step>

      <Step>
        Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.

        If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.
      </Step>

      <Step>
        Click **Next**.
      </Step>

      <Step>
        In the **Settings** area of the page, click **Edit**.
      </Step>

      <Step>
        Click **Rotate** to generate a new Client ID and Secret.

        Carefully copy and save these credentials. We'll use them in Step 2.
      </Step>
    </Steps>

    ### Step 2: Create Kubernetes configuration files

    Create two Kubernetes manifest files for your Fullstory connector deployment:

    #### Secrets configuration

    ```yaml expandable theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # baton-fullstory-secrets.yaml
    apiVersion: v1
    kind: Secret
    metadata:
      name: baton-fullstory-secrets
    type: Opaque
    stringData:
      # C1 credentials
      BATON_CLIENT_ID: <C1 client ID>
      BATON_CLIENT_SECRET: <C1 client secret>
      
      # Fullstory credentials
      BATON_SCIM_BASE_URL: <FullStory SCIM base URL>
      BATON_SCIM_TOKEN: <FullStory SCIM bearer token>
    ```

    See the connector's README or run `--help` to see all available configuration flags and environment variables.

    #### Deployment configuration

    ```yaml expandable theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # baton-fullstory.yaml
    apiVersion: apps/v1
    kind: Deployment
    metadata:
      name: baton-fullstory
      labels:
        app: baton-fullstory
    spec:
      selector:
        matchLabels:
          app: baton-fullstory
      template:
        metadata:
          labels:
            app: baton-fullstory
            baton: true
            baton-app: fullstory
        spec:
          containers:
          - name: baton-fullstory
            image: ghcr.io/conductorone/baton-fullstory:latest
            imagePullPolicy: IfNotPresent
            env:
            - name: BATON_HOST_ID
              value: baton-fullstory
            envFrom:
            - secretRef:
                name: baton-fullstory-secrets
    ```

    ### Step 3: Deploy the connector

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

      <Step>
        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 Fullstory connector to. Fullstory data should be found on the **Entitlements** and **Accounts** tabs.
      </Step>
    </Steps>

    **Done.** Your Fullstory connector is now pulling access data into C1.
  </Tab>
</Tabs>