Set up a Document360 connector

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

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

Capabilities

Resource	Sync	Provision
Users
Groups

Gather Document360 credentials

To configure the Document360 connector, you need a Document360 API token with permission to read team accounts and team account groups. API tokens are scoped to a single project.

1. In the Document360 knowledge base portal, open Settings > Knowledge base portal > API tokens.

2. Create a new API token (or select an existing one) with read access to team accounts and team account groups. Copy the token value.

3. Note your project’s API host. Use https://apihub.document360.io for the default region, or https://apihub.us.document360.io if your project is hosted in the US data-residency region.

Configuration fields

Field	Required	Description
base-url	Yes	The Document360 API host for your project’s region, with no trailing slash and no path: https://apihub.document360.io or https://apihub.us.document360.io.
api-token	Yes	A Document360 API token. The token is sent as-is in the api_token request header and must be able to read team accounts and team account groups.

Synced resource types

• Users: Document360 team accounts (the people who author and manage the knowledge base).
• Groups: Document360 team account groups, each with a member entitlement.
• Group memberships: each user’s group memberships, granted against the matching group’s member entitlement.

Special notes

• Provisioning is not supported in the current build.
• The connector is read-only and authenticates by sending the API token as the bare value of the api_token header.
• Readers and reader groups (knowledge base consumers) are not synced; the connector covers team accounts only.
• API tokens are scoped to one Document360 project. To govern multiple projects, configure one connector per project.

Configure the Document360 connector

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 Document360 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. Paste the Document360 credentials into the relevant fields:

   • Document360 API URL: The API host for your project’s region.
   • API token: The Document360 API token.
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 Document360 connector is now pulling access data into C1.

Self-hosted

Follow these instructions to run the Document360 connector in your own environment.

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, set its name, description, and owners, and click Add.

4. In the Settings area, click Edit, then click Rotate to generate a new Client ID and Client Secret. Store these values securely for your deployment.

5. Configure C1 credentials and Document360 credentials as environment variables:

   BATON_CLIENT_ID=<C1 client ID>
   BATON_CLIENT_SECRET=<C1 client secret>
   BATON_HOST_ID=baton-document360
   BATON_BASE_URL=<Document360 API host for your region>
   BATON_API_TOKEN=<Document360 API token>
   
6. Deploy the connector using the Public ECR image:

   public.ecr.aws/conductorone/baton-document360:<version>
   

   Use a version tag without the leading v, such as 0.0.1.

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