Set up a PandaDoc connector

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

Capabilities

Resource	Sync	Provision
Accounts
Roles
Workspaces

Gather PandaDoc credentials

Each setup method requires you to pass in credentials generated in PandaDoc. Gather these credentials before you move on.

A an Org Admin* in PandaDoc must perform this task.

Generate an API key

1. In PandaDoc, navigate to Dev center and click Configuration.

2. In the API keys area of the page, create a sandbox or production API key (production keys require approval from the PandaDoc team).

3. Carefully copy and save the API key.

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

Configure the PandaDoc connector

To complete this task, you’ll need:

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

Cloud-hosted

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

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

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

2. Search for PandaDoc and click Add.

3. Choose how to set up the new PandaDoc 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

4. 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.

5. Click Next.

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

7. Enter the API key in the PandaDoc API key field.

8. If you use PanadaDoc’s European API instance, check the Use PandaDoc Europe domain box.

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 PandaDoc connector is now pulling access data into C1.

Self-hosted

Follow these instructions to use the PandaDoc 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: Configure the PandaDoc connector

1. In C1, navigate to Integrations > Connectors > Add connector.

2. Search for Baton and click Add.

3. Choose how to set up the new PandaDoc 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

4. 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.

5. Click Next.

6. In the Settings area of the page, click Edit.

7. 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 PandaDoc connector deployment:

Secrets configuration

# baton-panda-doc-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-panda-doc-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>
  
  # PandaDoc credentials
  BATON_API_KEY: <PandaDoc API key>

  # Optional: include if you're using the European API instance
  BATON_API_DOMAIN: true

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

Deployment configuration

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

Step 3: Deploy the connector

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

2. 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 PandaDoc connector to. PandaDoc data should be found on the Entitlements and Accounts tabs.

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