> ## 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 Mode connector
> ConductorOne provides identity governance and just-in-time provisioning for Mode. Integrate your Mode instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests.
**This connector is in beta.** This means it's undergoing ongoing testing and development while we gather feedback, validate functionality, and improve stability. Beta connectors are generally stable, but they may have limited feature support, incomplete error handling, or occasional issues.
We recommend closely monitoring workflows that use this connector and contacting our Support team with any issues or feedback.
## Capabilities
| Resource | Sync | Provision |
| :------- | :------------------------------------------------------------ | :-------- |
| Account | | |
| Group | | |
**Additional functionality:**
*None.*
## Gather Mode configuration information
Configuring the connector requires you to pass in information from Mode. Gather these configuration details before you move on.
Here's the information you'll need:
* API Key
* API Secret
* Workspace
See the Mode docs for information on how to acquire credentials: [View the documentation](https://mode.com/developer/api-reference/authentication/)
## Configure the Mode connector
To complete this task, you'll need:
* The **Connector Administrator** or **Super Administrator** role in ConductorOne
* Access to the set of Mode 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 **Mode** and click **Add**.
Choose how to set up the new Mode 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 Mode connector is now pulling access data into ConductorOne.
**Follow these instructions to use the Mode 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 Mode connector
In ConductorOne, navigate to **Integrations** > **Connectors** > **Add connector**.
Search for **Baton** and click **Add**.
Choose how to set up the new Mode 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 Mode connector deployment:
#### Secrets configuration
```yaml expandable theme={null}
# baton-mode-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
name: baton-mode-secrets
type: Opaque
stringData:
# ConductorOne credentials
BATON_CLIENT_ID:
BATON_CLIENT_SECRET:
# Mode config
BATON_MODE_API_KEY:
BATON_MODE_API_SECRET:
BATON_MODE_WORKSPACE:
```
See the connector's README or run `--help` to see all available configuration flags and environment variables.
#### Deployment configuration
```yaml expandable theme={null}
# baton-mode.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: baton-mode
labels:
app: baton-mode
spec:
selector:
matchLabels:
app: baton-mode
template:
metadata:
labels:
app: baton-mode
baton: true
baton-app: mode
spec:
containers:
- name: baton-mode
image: ghcr.io/conductorone/baton-mode:latest
imagePullPolicy: IfNotPresent
env:
- name: BATON_HOST_ID
value: baton-mode
envFrom:
- secretRef:
name: baton-mode-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 mode connector to. mode data should be found on the **Entitlements** and **Accounts** tabs.
**That's it!** Your Mode connector is now pulling access data into ConductorOne.