> ## Documentation Index
> Fetch the complete documentation index at: https://conductorone-docs-iga-1271.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# Set up Gong connector
> ConductorOne provides identity governance and just-in-time provisioning for Gong. Integrate your Gong instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests.
## Capabilities
| Resource | Sync | Provision |
| :-------- | :------------------------------------------------------------ | :-------- |
| Account | | |
| Profile | | |
| Workspace | | |
**Additional functionality:**
*None.*
## Gather Gong configuration information
Configuring the connector requires you to pass in information from Gong. Gather these configuration details before you move on.
Here's the information you'll need:
* Access Key
* Base URL
* Secret Key
See the Gong docs for information on how to acquire credentials: [View the documentation](https://help.gong.io/docs/receive-access-to-the-api)
This connector requires the following scopes:
* api:users:read
* api:workspaces:read
## Configure the Gong connector
To complete this task, you'll need:
* The **Connector Administrator** or **Super Administrator** role in ConductorOne
* Access to the set of Gong configuration information gathered by following the instructions above
**Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.**
In ConductorOne, navigate to **Integrations** > **Connectors** and click **Add connector**.
Search for **Gong** and click **Add**.
Choose how to set up the new Gong 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 ConductorOne)
* Add the connector to a managed app (select from the list of existing managed apps)
* Create a new managed app
Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.
If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.
Click **Next**.
Find the **Settings** area of the page and click **Edit**.
Enter the configuration information from the previous section.
Click **Save**.
The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing.
**That's it!** Your Gong connector is now pulling access data into ConductorOne.
**Follow these instructions to use the Gong connector, hosted and run in your own environment.**
When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests.
### Resources
[Contact ConductorOne's support team](mailto:support@conductorone.com) to download the latest version of the connector.
### Step 1: Set up a new Gong connector
In ConductorOne, navigate to **Integrations** > **Connectors** > **Add connector**.
Search for **Baton** and click **Add**.
Choose how to set up the new Gong 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 ConductorOne)
* Add the connector to a managed app (select from the list of existing managed apps)
* Create a new managed app
Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.
If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.
Click **Next**.
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 Gong connector deployment:
#### Secrets configuration
```yaml expandable theme={null}
# baton-gong-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
name: baton-gong-secrets
type: Opaque
stringData:
# ConductorOne credentials
BATON_CLIENT_ID:
BATON_CLIENT_SECRET:
# Gong config
BATON_GONG_ACCESS_KEY:
BATON_GONG_BASE_URL:
BATON_GONG_SECRET_KEY:
```
See the connector's README or run `--help` to see all available configuration flags and environment variables.
#### Deployment configuration
```yaml expandable theme={null}
# baton-gong.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: baton-gong
labels:
app: baton-gong
spec:
selector:
matchLabels:
app: baton-gong
template:
metadata:
labels:
app: baton-gong
baton: true
baton-app: gong
spec:
containers:
- name: baton-gong
image: ghcr.io/conductorone/baton-gong:latest
imagePullPolicy: IfNotPresent
env:
- name: BATON_HOST_ID
value: baton-gong
envFrom:
- secretRef:
name: baton-gong-secrets
```
### Step 3: Deploy the connector
Create a namespace in which to run ConductorOne connectors (if desired), then apply the secret config and deployment config files.
Check that the connector data uploaded correctly. In ConductorOne, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the gong connector to. gong data should be found on the **Entitlements** and **Accounts** tabs.
**That's it!** Your Gong connector is now pulling access data into ConductorOne.