> ## Documentation Index
> Fetch the complete documentation index at: https://www.c1.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Set up a Snipe-IT connector
> C1 provides identity governance and just-in-time provisioning for Snipe-IT. Integrate your Snipe-IT instance with C1 to run user access reviews (UARs) and enable just-in-time access requests.
## Capabilities
| Resource | Sync | Provision |
| :---------- | :------------------------------------------------------------ | :------------------------------------------------------------ |
| Accounts | | |
| Groups | | |
| Permissions | | |
## Gather Snipe-IT credentials
Configuring the connector requires you to pass in credentials generated in Snipe-IT. Gather these credentials before you move on.
### Generate an API token
In the Snipe-IT web interface, click your user name and select **Manage API keys**.
Click **Create New Token**.
Carefully copy and save the new token.
**Done.** Next, move on to the connector configuration instructions.
## Configure the Snipe-IT connector
To complete this task, you'll need:
* The **Connector Administrator** or **Super Administrator** role in C1
* Access to the set of Snipe-IT credentials generated by following the instructions above
**Follow these instructions to use a built-in, no-code connector hosted by C1.**
In C1, navigate to **Integrations** > **Connectors** and click **Add connector**.
Search for **Snipe-IT** and click **Add**.
Choose how to set up the new Snipe-IT 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
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.
Click **Next**.
Find the **Settings** area of the page and click **Edit**.
Enter your Snipe-IT base URL into the **Base URL** field.
Paste the access token you generated in Step 1 into the **Access token** field.
Click **Save**.
The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing.
**Done.** Your Snipe-IT connector is now pulling access data into C1.
**Follow these instructions to use the Snipe-IT 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](https://github.com/conductorone/baton-snipe-it): Access the source code, report issues, or contribute to the project.
### Step 1: Set up a new Snipe-IT connector
In C1, navigate to **Integrations** > **Connectors** > **Add connector**.
Search for **Baton** and click **Add**.
Choose how to set up the new Snipe-IT 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
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.
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 Snipe-IT connector deployment:
#### Secrets configuration
```yaml theme={"theme":{"light":"css-variables","dark":"css-variables"}}
# baton-snipe-it-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
name: baton-snipe-it-secrets
type: Opaque
stringData:
# C1 credentials
BATON_CLIENT_ID:
BATON_CLIENT_SECRET:
# Snipe-IT credentials
BATON_ACCESS_TOKEN:
BATON_BASE_URL:
# Optional: include if you want C1 to provision access using this connector
BATON_PROVISIONING: true
```
See the connector's README or run `--help` to see all available configuration flags and environment variables.
#### Deployment configuration
```yaml expandable theme={"theme":{"light":"css-variables","dark":"css-variables"}}
# baton-snipe-it.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: baton-snipe-it
labels:
app: baton-snipe-it
spec:
selector:
matchLabels:
app: baton-snipe-it
template:
metadata:
labels:
app: baton-snipe-it
baton: true
baton-app: snipe-it
spec:
containers:
- name: baton-snipe-it
image: ghcr.io/conductorone/baton-snipe-it:latest
imagePullPolicy: IfNotPresent
env:
- name: BATON_HOST_ID
value: baton-snipe-it
envFrom:
- secretRef:
name: baton-snipe-it-secrets
```
### Step 3: Deploy the connector
Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.
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 Snipe-IT connector to. Snipe-IT data should be found on the **Entitlements** and **Accounts** tabs.
**Done.** Your Snipe-IT connector is now pulling access data into C1.