Skip to content

docs: apply C1 rebrand to connector.mdx #33

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
gontzess merged 1 commit into from
Apr 7, 2026
Merged

docs: apply C1 rebrand to connector.mdx #33

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
44 changes: 22 additions & 22 deletions docs/connector.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,20 +1,20 @@
---
title: Set up Retool connector
og:title: Set up Retool connector - ConductorOne docs
og:description: Integrate your Retool instance with ConductorOne to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access.
description: ConductorOne provides identity governance and just-in-time provisioning for Retool. Integrate your Retool instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests.
og:title: Set up Retool connector - C1 docs
og:description: Integrate your Retool instance with C1 to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access.
description: C1 provides identity governance and just-in-time provisioning for Retool. Integrate your Retool instance with C1 to run user access reviews (UARs) and enable just-in-time access requests.
sidebarTitle: Retool
---

## Capabilities

| Resource | Sync | Provision |
| :--- | :--- | :--- |
| Accounts | <Icon icon="square-check" iconType="solid" color="#65DE23"/> | |
| Groups | <Icon icon="square-check" iconType="solid" color="#65DE23"/> | <Icon icon="square-check" iconType="solid" color="#65DE23"/> |
| Organizations | <Icon icon="square-check" iconType="solid" color="#65DE23"/> | |
| Pages (Apps) | <Icon icon="square-check" iconType="solid" color="#65DE23"/> | <Icon icon="square-check" iconType="solid" color="#65DE23"/> |
| Resources | <Icon icon="square-check" iconType="solid" color="#65DE23"/> | |
| Accounts | <Icon icon="square-check" iconType="solid" color="#c937ae"/> | |
| Groups | <Icon icon="square-check" iconType="solid" color="#c937ae"/> | <Icon icon="square-check" iconType="solid" color="#c937ae"/> |
| Organizations | <Icon icon="square-check" iconType="solid" color="#c937ae"/> | |
| Pages (Apps) | <Icon icon="square-check" iconType="solid" color="#c937ae"/> | <Icon icon="square-check" iconType="solid" color="#c937ae"/> |
| Resources | <Icon icon="square-check" iconType="solid" color="#c937ae"/> | |

## Gather Retool credentials

Expand Down Expand Up @@ -63,48 +63,48 @@ Compose and save the Retool connection string you'll use when setting up the con
<Warning>
To complete this task, you'll need:

- The **Connector Administrator** or **Super Administrator** role in ConductorOne
- The **Connector Administrator** or **Super Administrator** role in C1
- Access to the set of Retool credentials generated by following the instructions above
</Warning>

<Tabs>
<Tab title="Cloud-hosted">

**Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.**
**Follow these instructions to use a built-in, no-code connector hosted by C1.**

*Cloud-hosted connector not currently available.*
</Tab>
<Tab title="Self-hosted">
**Follow these instructions to use the Retool 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.
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-retool): Access the source code, report issues, or contribute to the project.
* [GitHub repository](https://github.com/conductorone/baton-retool): Access the source code, report issues, or contribute to the project.

### Step 1: Set up a new Retool connector

<Steps>
<Step>
In ConductorOne, navigate to **Integrations** > **Connectors** > **Add connector**.
In C1, navigate to **Integrations** > **Connectors** > **Add connector**.
</Step>
<Step>
Search for **Baton** and click **Add**.
</Step>
<Step>
Choose how to set up the new Retool 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 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
</Step>
<Step>
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.
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, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.
If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.
</Step>
<Step>
Click **Next**.
Expand Down Expand Up @@ -132,9 +132,9 @@ metadata:
name: baton-retool-secrets
type: Opaque
stringData:
# ConductorOne credentials
BATON_CLIENT_ID: <ConductorOne client ID>
BATON_CLIENT_SECRET: <ConductorOne client secret>
# C1 credentials
BATON_CLIENT_ID: <C1 client ID>
BATON_CLIENT_SECRET: <C1 client secret>

# Retool credentials
BATON_CONNECTION_STRING: <The Retool connection string, in format "user=baton password=secure-password host=localhost port=5432 dbname=hammerhead_production">
Expand Down Expand Up @@ -179,13 +179,13 @@ spec:

<Steps>
<Step>
Create a namespace in which to run ConductorOne connectors (if desired), then apply the secret config and deployment config files.
Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.
</Step>
<Step>
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 Retool connector to. Retool data should be found on the **Entitlements** and **Accounts** tabs.
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 Retool connector to. Retool data should be found on the **Entitlements** and **Accounts** tabs.
</Step>
</Steps>
**That's it!** Your Retool connector is now pulling access data into ConductorOne.
**That's it!** Your Retool connector is now pulling access data into C1.
</Tab>
</Tabs>

Loading