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.

Generate an API key

Only a PandaDoc account owner or admin can access Dev Center and generate API keys.

1. Enable Dev Center (Business plan only). If your organization is on the Business plan, Dev Center must be enabled before it appears in the navigation. In PandaDoc, go to Settings → API and Integrations → API and click Enable. This provides access to the Sandbox environment only.

   Enterprise plan accounts have Dev Center enabled by default.

2. In PandaDoc, navigate to Dev Center → Configuration.

3. In the API keys area, generate a Sandbox or Production API key.

   Production API keys require an active Enterprise plan. On Business plans, only Sandbox keys are available.

4. Carefully copy and save the API key.

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

Troubleshooting: Dev Center not visible

If Dev Center doesn’t appear in your PandaDoc navigation:

• Check your role. Only account owners and admins can see and use Dev Center.
• Check if it’s enabled. On Business plans, Dev Center must be manually enabled under Settings → API and Integrations → API.
• Check your plan. Dev Center is available on Business and Enterprise plans only.

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.

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

2. Search for PandaDoc 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 API key in the API Key field.

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

10. Click Save.

11. 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 Apps > Connectors and click Add connector.

2. Search for Baton 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. In the Settings area of the page, click Edit.

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