From 5b288c22568fbc749e63ecc9f7016f636ee93525 Mon Sep 17 00:00:00 2001 From: "baton-admin[bot]" <2063555+baton-admin[bot]@users.noreply.github.com> Date: Tue, 7 Apr 2026 08:40:03 +0000 Subject: [PATCH 1/5] docs: sync connector docs from recent releases --- baton/artifactory.mdx | 60 ++++--- baton/claude-enterprise.mdx | 337 +++++++++++++++++++++--------------- baton/google-workspace.mdx | 72 ++++---- baton/oracle-idcs.mdx | 58 +++---- baton/salesforce.mdx | 82 ++++----- baton/tableau.mdx | 62 +++---- baton/workday.mdx | 62 +++---- baton/zoom.mdx | 65 +++---- docs.json | 4 +- 9 files changed, 443 insertions(+), 359 deletions(-) diff --git a/baton/artifactory.mdx b/baton/artifactory.mdx index 066faf58..460e8979 100644 --- a/baton/artifactory.mdx +++ b/baton/artifactory.mdx @@ -1,8 +1,8 @@ --- title: "Set up Artifactory connector" og:title: "Set up Artifactory connector" -description: "C1 provides identity governance and just-in-time provisioning for Artifactory. Integrate your Artifactory instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." -og:description: "C1 provides identity governance and just-in-time provisioning for Artifactory. Integrate your Artifactory instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "ConductorOne provides identity governance and just-in-time provisioning for Artifactory. Integrate your Artifactory instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "ConductorOne provides identity governance and just-in-time provisioning for Artifactory. Integrate your Artifactory instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "JFrog Artifactory" --- @@ -10,13 +10,23 @@ sidebarTitle: "JFrog Artifactory" | Resource | Sync | Provision | | :--- | :--- | :--- | -| Account | | | -| Group | | | -| Repository | | | +| Account | | | +| Administrator | | | +| Group | | | +| Repository | | | **Additional functionality:** -*None.* +- **Create user accounts** — Provision new Artifactory users with a randomly generated password. +- **Delete user accounts** — Remove users from Artifactory. +- **Grant/revoke Administrator role** — Assign or remove the platform admin flag on a user. +- **Grant/revoke group membership** — Add or remove users from Artifactory groups. +- **Grant/revoke repository permissions** — Manage per-repository permissions (Read, Write, Delete, Manage, Annotate, Managed Xray Metadata) for both users and groups. Permissions are managed via baton-owned permission targets. + +**Known limitations:** + +- Repository permissions granted via pre-existing Artifactory permission targets (not created by ConductorOne) cannot be revoked through this connector. Only permissions provisioned by ConductorOne can be revoked. +- When a user inherits a repository permission from multiple groups, the connector attributes the grant to one group. ## Gather Artifactory configuration information @@ -34,31 +44,31 @@ See the Artifactory docs for information on how to acquire credentials: [View th To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in ConductorOne - Access to the set of Artifactory configuration information gathered by following the instructions above -**Follow these instructions to use a built-in, no-code connector hosted by C1.** +**Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.** - In C1, navigate to **Integrations** > **Connectors** and click **Add connector**. + In ConductorOne, navigate to **Integrations** > **Connectors** and click **Add connector**. Search for **Artifactory** and click **Add**. Choose how to set up the new Artifactory 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 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 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. + 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**. @@ -77,37 +87,37 @@ To complete this task, you'll need: -**That's it!** Your Artifactory connector is now pulling access data into C1. +**That's it!** Your Artifactory connector is now pulling access data into ConductorOne. **Follow these instructions to use the Artifactory 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. +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 C1's support team](mailto:support@conductorone.com) to download the latest version of the connector. +[Contact ConductorOne's support team](mailto:support@conductorone.com) to download the latest version of the connector. ### Step 1: Set up a new Artifactory connector - In C1, navigate to **Integrations** > **Connectors** > **Add connector**. + In ConductorOne, navigate to **Integrations** > **Connectors** > **Add connector**. Search for **Baton** and click **Add**. Choose how to set up the new Artifactory 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 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 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. + 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**. @@ -135,9 +145,9 @@ metadata: name: baton-artifactory-secrets type: Opaque stringData: - # C1 credentials - BATON_CLIENT_ID: - BATON_CLIENT_SECRET: + # ConductorOne credentials + BATON_CLIENT_ID: + BATON_CLIENT_SECRET: # Artifactory config BATON_ARTIFACTORY_BASE_URL: @@ -183,14 +193,14 @@ spec: - Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files. + 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 C1, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Artifactory connector to. Artifactory data should be found on the **Entitlements** and **Accounts** tabs. + 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 Artifactory connector to. Artifactory data should be found on the **Entitlements** and **Accounts** tabs. -**That's it!** Your Artifactory connector is now pulling access data into C1. +**That's it!** Your Artifactory connector is now pulling access data into ConductorOne. diff --git a/baton/claude-enterprise.mdx b/baton/claude-enterprise.mdx index 92b5c4cf..6d2da01a 100644 --- a/baton/claude-enterprise.mdx +++ b/baton/claude-enterprise.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Claude Enterprise connector" og:title: "Set up a Claude Enterprise connector" -description: "C1 provides identity governance and just-in-time provisioning for Claude Enterprise. Integrate your Claude Enterprise instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." -og:description: "C1 provides identity governance and just-in-time provisioning for Claude Enterprise. Integrate your Claude Enterprise instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "ConductorOne provides identity governance and just-in-time provisioning for Claude Enterprise. Integrate your Claude Enterprise instance with ConductorOne to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "ConductorOne provides identity governance and just-in-time provisioning for Claude Enterprise. Integrate your Claude Enterprise instance with ConductorOne to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "Claude Enterprise" --- @@ -15,20 +15,64 @@ The Claude Enterprise connector syncs the following resources: | Resource | Sync | Provision | | :--- | :--- | :--- | -| Accounts | | | -| Groups | | | +| Accounts | | Create, Delete | +| Groups | | Grant, Revoke | {/* AUTO-GENERATED:END - capabilities */} +**Additional functionality:** + + Supports [automatic account provisioning and deprovisioning](/product/admin/account-provisioning) + +#### Account creation fields + +When provisioning a new Claude Enterprise user account, ConductorOne prompts for the following field: + +| Field | Required | Description | +| :--- | :--- | :--- | +| `display_name` | Yes | The user's first and last name, space-separated (e.g., "Jane Smith"). The first word is used as the given name; the remainder is used as the family name. | + +The user's email address is provided automatically by ConductorOne and is used as the SCIM username. No password is required — Claude Enterprise authenticates users through SSO, so accounts are created without credentials. + +## SCIM-only connector + +This connector uses the SCIM 2.0 API exclusively. Claude Enterprise does not currently offer an Admin API for managing users and groups, so SCIM is the only programmatic interface available. + +### What this means in practice + +- **Only SCIM-managed users and groups are visible.** Users or groups created directly through the Claude Enterprise UI will not appear in syncs. To get full visibility, all user management should flow through SCIM. +- **Groups are managed through SCIM only.** The connector can sync groups and grant or revoke group membership, but it cannot create or delete groups. Groups must be created outside of ConductorOne (e.g., through your identity provider or directly via the SCIM API). +- **Claude Enterprise uses WorkOS under the hood** for its SCIM implementation. The SCIM endpoint URL provided during setup points to the WorkOS SCIM service. + +### What SCIM provides + +| Capability | Supported | +| :--- | :--- | +| Provision (create) user | | +| Deprovision (delete) user | | +| Add user to group | | +| Remove user from group | | +| Sync all users | | +| Sync all groups and memberships | | +| Create or delete groups | | +| Assign roles | | +| Manage workspace settings | | + + +If Anthropic adds an Admin API in the future, the connector can be extended to support additional capabilities such as role management. + + ## Gather Claude Enterprise credentials +Configuring the connector requires you to generate SCIM credentials in Claude Enterprise. Gather these credentials before you move on. + -To configure the Claude Enterprise connector, the Primary Owner of the Claude Enterprise organization must first enable SCIM provisioning. SCIM is only available on Enterprise plans. +The **Primary Owner** of the Claude Enterprise organization must perform this task. SCIM provisioning is only available on Enterprise plans. - In Claude Enterprise, navigate to **Settings** > **Identity and access** > **Setup SCIM**. + Sign into [claude.ai](https://claude.ai) and navigate to **Settings** > **Identity and access** > **Setup SCIM**. @@ -40,183 +84,202 @@ To configure the Claude Enterprise connector, the Primary Owner of the Claude En - -The SCIM connector only sees users and groups managed through SCIM. Users added via the Claude Enterprise UI will not appear in syncs. - +**That's it!** Next, move on to the connector configuration instructions. ## Configure the Claude Enterprise connector + +To complete this task, you'll need: + +- The **Connector Administrator** or **Super Administrator** role in ConductorOne +- Access to the Claude Enterprise SCIM 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**. - + **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 **Claude Enterprise** and click **Add**. - + + Search for **Claude Enterprise** and click **Add**. + - - Choose how to set up the new Claude Enterprise connector: + + Choose how to set up the new Claude Enterprise connector: - - Add the connector to a currently unmanaged app - - Add the connector to a managed app - - Create a new managed app - + - 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. - + + 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. - - Click **Next**. - + If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process. + - - Find the **Settings** area of the page and click **Edit**. - + + Click **Next**. + + + + Find the **Settings** area of the page and click **Edit**. + {/* AUTO-GENERATED:START - config-params Generated from config_schema.json. Do not edit manually. */} - - Enter the required configuration: + + Enter the required configuration: - - **SCIM Token** (required): SCIM bearer token for Claude Enterprise (from claude.ai > Settings > Identity and access) - - **SCIM URL**: SCIM endpoint URL. Defaults to the WorkOS SCIM endpoint configured during setup. - + - **SCIM Token** (required): The SCIM bearer token for Claude Enterprise (from claude.ai > Settings > Identity and access). + - **SCIM URL** (required): The SCIM endpoint URL provided during SCIM setup (from claude.ai > Settings > Identity and access). This is the WorkOS SCIM endpoint generated for your organization. + {/* AUTO-GENERATED:END - config-params */} - - Click **Save**. - + + Click **Save**. + + + + The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. + + - - 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 Claude Enterprise connector is now pulling access data into ConductorOne. - **That's it!** Your Claude Enterprise connector is now pulling access data into C1. - Follow these instructions to use the [Claude Enterprise](https://github.com/ConductorOne/baton-claude-enterprise) 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. + **Follow these instructions to use the Claude Enterprise 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 - ### Step 1: Set up a new Claude Enterprise connector + * [Official download center](https://dist.conductorone.com/ConductorOne/baton-claude-enterprise): For stable binaries (Windows/Linux/macOS) and container images. - - - In C1, navigate to **Integrations** > **Connectors** > **Add connector**. - + * [GitHub repository](https://github.com/ConductorOne/baton-claude-enterprise): Access the source code, report issues, or contribute to the project. - - Search for **Baton** and click **Add**. - + ### Step 1: Set up a new Claude Enterprise connector - - Choose how to set up the new Claude Enterprise connector: + + + In ConductorOne, navigate to **Integrations** > **Connectors** > **Add connector**. + - - Add the connector to a currently unmanaged app - - Add the connector to a managed app - - Create a new managed app - + + Search for **Baton** and click **Add**. + - - Set the owner for this connector. - + + Choose how to set up the new Claude Enterprise connector: - - Click **Next**. - + - Add the connector to a currently unmanaged app + - Add the connector to a managed app + - Create a new managed app + - - In the **Settings** area of the page, click **Edit**. - + + 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. - - Click **Rotate** to generate a new Client ID and Secret. + If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process. + - Carefully copy and save these credentials. - - + + Click **Next**. + - ### Step 2: Create Kubernetes configuration files + + In the **Settings** area of the page, click **Edit**. + - Create two Kubernetes manifest files for your Claude Enterprise connector deployment: + + Click **Rotate** to generate a new Client ID and Secret. - #### Secrets configuration + Carefully copy and save these credentials. We'll use them in Step 2. + + - ```yaml expandable - # baton-claude-enterprise-secrets.yaml - apiVersion: v1 - kind: Secret - metadata: - name: baton-claude-enterprise-secrets - type: Opaque - stringData: - # C1 credentials - BATON_CLIENT_ID: - BATON_CLIENT_SECRET: + ### Step 2: Create Kubernetes configuration files - # Claude Enterprise SCIM credentials - BATON_SCIM_TOKEN: - BATON_SCIM_URL: - ``` + Create two Kubernetes manifest files for your Claude Enterprise connector deployment: - See the connector's README or run `--help` to see all available configuration flags and environment variables. + #### Secrets configuration - #### Deployment configuration + ```yaml expandable + # baton-claude-enterprise-secrets.yaml + apiVersion: v1 + kind: Secret + metadata: + name: baton-claude-enterprise-secrets + type: Opaque + stringData: + # ConductorOne credentials + BATON_CLIENT_ID: + BATON_CLIENT_SECRET: - ```yaml expandable - # baton-claude-enterprise.yaml - apiVersion: apps/v1 - kind: Deployment - metadata: - name: baton-claude-enterprise - labels: + # Claude Enterprise SCIM credentials + BATON_SCIM_TOKEN: + BATON_SCIM_URL: + ``` + + See the connector's README or run `--help` to see all available configuration flags and environment variables. + + #### Deployment configuration + + ```yaml expandable + # baton-claude-enterprise.yaml + apiVersion: apps/v1 + kind: Deployment + metadata: + name: baton-claude-enterprise + labels: + app: baton-claude-enterprise + spec: + selector: + matchLabels: app: baton-claude-enterprise - spec: - selector: - matchLabels: + template: + metadata: + labels: app: baton-claude-enterprise - template: - metadata: - labels: - app: baton-claude-enterprise - baton: "true" - baton-app: claude-enterprise - spec: - containers: - - name: baton-claude-enterprise - image: public.ecr.aws/conductorone/baton-claude-enterprise:latest - imagePullPolicy: IfNotPresent - env: - - name: BATON_HOST_ID - value: baton-claude-enterprise - envFrom: - - secretRef: - name: baton-claude-enterprise-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 **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the Claude Enterprise connector to. Claude Enterprise data should be found on the **Entitlements** and **Accounts** tabs. - - - - **That's it!** Your Claude Enterprise connector is now pulling access data into C1. + baton: "true" + baton-app: claude-enterprise + spec: + containers: + - name: baton-claude-enterprise + image: public.ecr.aws/conductorone/baton-claude-enterprise:latest + imagePullPolicy: IfNotPresent + env: + - name: BATON_HOST_ID + value: baton-claude-enterprise + envFrom: + - secretRef: + name: baton-claude-enterprise-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 **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the Claude Enterprise connector to. Claude Enterprise data should be found on the **Entitlements** and **Accounts** tabs. + + + + **That's it!** Your Claude Enterprise connector is now pulling access data into ConductorOne. + diff --git a/baton/google-workspace.mdx b/baton/google-workspace.mdx index a2277cdd..96b5256f 100644 --- a/baton/google-workspace.mdx +++ b/baton/google-workspace.mdx @@ -1,23 +1,23 @@ --- title: "Set up a Google Workspace connector" og:title: "Set up a Google Workspace connector" -description: "C1 provides identity governance and just-in-time provisioning for Google Workspace. Integrate your Google Workspace instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." -og:description: "C1 provides identity governance and just-in-time provisioning for Google Workspace. Integrate your Google Workspace instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "ConductorOne provides identity governance and just-in-time provisioning for Google Workspace. Integrate your Google Workspace instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "ConductorOne provides identity governance and just-in-time provisioning for Google Workspace. Integrate your Google Workspace instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Google Workspace" --- -**This is an updated and improved version of the Google Workspace integration!** If you're setting up a Google Workspace connector with C1 for the first time, you're in the right place. +**This is an updated and improved version of the Google Workspace integration!** If you're setting up a Google Workspace connector with ConductorOne for the first time, you're in the right place. ## Capabilities | Resource | Sync | Provision | | :--- | :--- | :--- | -| Accounts | | | -| Groups | | | -| Roles | | | -| Enterprise Applications | | | +| Accounts | | | +| Groups | | | +| Roles | | | +| Enterprise Applications | | | The Google Workspace connector supports [automatic account provisioning and deprovisioning](/product/admin/account-provisioning). @@ -25,7 +25,7 @@ Enable **Sync Enterprise Apps** to track which users have accessed OAuth and SAM ### Connector actions -Connector actions are custom capabilities that extend C1 automations with app-specific operations. You can use connector actions in the [Perform connector action](/product/admin/automations-steps-reference#perform-connector-action) automation step. +Connector actions are custom capabilities that extend ConductorOne automations with app-specific operations. You can use connector actions in the [Perform connector action](/product/admin/automations-steps-reference#perform-connector-action) automation step. | Action name | Additional fields | Description | |-------------|-------------------|-------------| @@ -64,7 +64,7 @@ In the toolbar, open the project select dropdown and click **NEW PROJECT**. Create a new project for your organization: - - **Project Name**: Choose a names, such as "C1 Integration" + - **Project Name**: Choose a names, such as "ConductorOne Integration" - **Organization/Location**: Choose the appropriate Organization/Location @@ -86,7 +86,11 @@ Click **Enable**. -**Optional.** If you want to use the group settings connector action, you must also search for, select, and enable the **Groups Settings API**. +**Optional.** If you want to use the group settings connector action, you must also search for, select, and enable the **Groups Settings API**. + + + + **Optional.** If you want to enable **Sync Enterprise Apps**, you must also search for, select, and enable the **Cloud Identity API**. @@ -104,8 +108,8 @@ Select **CREATE CREDENTIALS** > **Service Account**. Under **Service account details**, fill in the following: - - **Service account name:** C1 Integration - - **Service account description:** for example, "Service account for C1 Google Workspace Integration" + - **Service account name:** ConductorOne Integration + - **Service account description:** for example, "Service account for ConductorOne Google Workspace Integration" - Click **CREATE AND CONTINUE** @@ -161,7 +165,7 @@ Click **Add new** and fill out the form: - **Client ID**: The service account's unique ID - **OAuth Scopes**: Copy and paste in the relevant scopes - Use the following scopes to give C1 **READ** access (for syncing access data): + Use the following scopes to give ConductorOne **READ** access (for syncing access data): ```bash https://www.googleapis.com/auth/admin.directory.domain.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.directory.group.member.readonly, https://www.googleapis.com/auth/admin.directory.rolemanagement.readonly, https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly @@ -187,7 +191,7 @@ Click **Add new** and fill out the form: - Scope: https://www.googleapis.com/auth/admin.reports.audit.readonly
Purpose: To sync usage events and admin events (used in conjunction with incremental sync). - Use the following scopes to give C1 **READ/WRITE** access (for syncing access data and provisioning access): + Use the following scopes to give ConductorOne **READ/WRITE** access (for syncing access data and provisioning access): ```bash https://www.googleapis.com/auth/admin.directory.domain.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.directory.group.member, https://www.googleapis.com/auth/admin.directory.rolemanagement, https://www.googleapis.com/auth/admin.directory.user, https://www.googleapis.com/auth/admin.reports.audit.readonly, https://www.googleapis.com/auth/admin.datatransfer, https://www.googleapis.com/auth/admin.directory.group, https://www.googleapis.com/auth/admin.directory.user.security, https://www.googleapis.com/auth/apps.groups.settings @@ -263,16 +267,16 @@ Click **Manage Domains**. Locate and copy the domain labeled as the **Primary Do ## Configure the Google Workspace connector -This task requires either the **Connector Administrator** or **Super Administrator** role in C1. +This task requires either the **Connector Administrator** or **Super Administrator** role in ConductorOne. -**Follow these instructions to use a built-in, no-code connector hosted by C1.** +**Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.** -In C1, navigate to **Integrations** > **Connectors** and click **Add connector**. +In ConductorOne, navigate to **Integrations** > **Connectors** and click **Add connector**. Search for **Google Workspace v2** and click **Add**. @@ -280,21 +284,21 @@ Search for **Google Workspace v2** and click **Add**. Choose how to set up the new Google Workspace 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 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 C1 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 ConductorOne users. Setting multiple owners is allowed. Click **Next**. - **If you are the connector owner**, go on to the next step. - - **If someone else is the connector owner**, you can stop here. C1 will notify the connector owner by email that their help is needed to complete the setup process. + - **If someone else is the connector owner**, you can stop here. ConductorOne will notify the connector owner by email that their help is needed to complete the setup process. Find the **Settings** area of the page and click **Edit**. @@ -303,7 +307,7 @@ Find the **Settings** area of the page and click **Edit**. In the **Customer ID** field, enter the Google Workspace customer ID. -**Optional.** If you want to limit which domains C1 syncs, in the **Domain** field, enter the primary domain from Step 6. If you leave this field blank, C1 will sync all available domains. +**Optional.** If you want to limit which domains ConductorOne syncs, in the **Domain** field, enter the primary domain from Step 6. If you leave this field blank, ConductorOne will sync all available domains. In the **Administrator email** field, enter the email address associated with your domain or a super admin. @@ -322,25 +326,25 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**That's it!** Your Google Workspace connector is now pulling access data into C1. +**That's it!** Your Google Workspace connector is now pulling access data into ConductorOne. **Follow these instructions to use the Google Workspace 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. +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 * [Official download center](https://dist.conductorone.com/ConductorOne/baton-google-workspace): For stable binaries (Windows/Linux/macOS) and container images. -* [GitHub repository](https://github.com/conductorone/baton-google-workspace): Access the source code, report issues, or contribute to the project. +* [GitHub repository](https://github.com/ConductorOne/baton-google-workspace): Access the source code, report issues, or contribute to the project. ### Step 1: Set up a new Google Workspace connector -In C1, navigate to **Integrations** **Connectors** > **Add connector** +In ConductorOne, navigate to **Integrations** **Connectors** > **Add connector** Search for **Baton** and click **Add** @@ -380,9 +384,9 @@ metadata: name: baton-google-workspace-secrets type: Opaque data: - # C1 credentials - BATON_CLIENT_ID: - BATON_CLIENT_SECRET: + # ConductorOne credentials + BATON_CLIENT_ID: + BATON_CLIENT_SECRET: # Google Workspace specific credentials BATON_CUSTOMER_ID: @@ -390,7 +394,7 @@ data: BATON_ADMINISTRATOR_EMAIL: BATON_CREDENTIALS_JSON: - # Optional: include if you want C1 to provision access using this connector + # Optional: include if you want ConductorOne to provision access using this connector BATON_PROVISIONING: true # Optional: enable enterprise application and login activity syncing (requires additional OAuth scopes) @@ -438,20 +442,20 @@ spec: -Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files. +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 C1, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Google Workspace connector to. Google Workspace data should be found on the **Entitlements** and **Accounts** tabs. +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 Google Workspace connector to. Google Workspace data should be found on the **Entitlements** and **Accounts** tabs. -**That's it!** Your Google Workspace connector is now pulling access data into C1. +**That's it!** Your Google Workspace connector is now pulling access data into ConductorOne. ### What's next? -If Google Workspace is your company's identity provider (meaning that it is used to SSO into other software), the integration sync will automatically create applications in C1 for all of your SCIMed software. Before you move on, review the [Create applications](/product/admin/applications) page for important information about how to set up integrations with the SCIMed apps. +If Google Workspace is your company's identity provider (meaning that it is used to SSO into other software), the integration sync will automatically create applications in ConductorOne for all of your SCIMed software. Before you move on, review the [Create applications](/product/admin/applications) page for important information about how to set up integrations with the SCIMed apps. ## Troubleshooting the Google Workspace integration @@ -485,7 +489,7 @@ Re-add the relevant scopes: Read/Write - ```bash + ```bash https://www.googleapis.com/auth/admin.directory.domain.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.directory.group.member, https://www.googleapis.com/auth/admin.directory.rolemanagement, https://www.googleapis.com/auth/admin.directory.user, https://www.googleapis.com/auth/admin.reports.audit.readonly, https://www.googleapis.com/auth/admin.datatransfer, https://www.googleapis.com/auth/admin.directory.group, https://www.googleapis.com/auth/admin.directory.user.security, https://www.googleapis.com/auth/apps.groups.settings ``` diff --git a/baton/oracle-idcs.mdx b/baton/oracle-idcs.mdx index 05d70ea0..646cb3cd 100644 --- a/baton/oracle-idcs.mdx +++ b/baton/oracle-idcs.mdx @@ -1,8 +1,8 @@ --- title: "Set up an Oracle IDCS connector" og:title: "Set up an Oracle IDCS connector" -description: "C1 provides identity governance for Oracle Identity Cloud Service (IDCS). Integrate your Oracle IDCS instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." -og:description: "C1 provides identity governance for Oracle Identity Cloud Service (IDCS). Integrate your Oracle IDCS instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "ConductorOne provides identity governance for Oracle Identity Cloud Service (IDCS). Integrate your Oracle IDCS instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "ConductorOne provides identity governance for Oracle Identity Cloud Service (IDCS). Integrate your Oracle IDCS instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Oracle Identity Cloud Service" --- @@ -14,16 +14,16 @@ sidebarTitle: "Oracle Identity Cloud Service" | Resource | Sync | Provision | | :--- | :--- | :--- | -| Accounts | | | -| Groups | | | -| Applications | * | ** | -| Application roles | * | ** | +| Accounts | | | +| Groups | | | +| Applications | * | ** | +| Application roles | * | ** | The Oracle IDCS connector supports [automatic account provisioning and deprovisioning](/product/admin/account-provisioning). *You must opt into syncing application and application role data; these are not synced by default. -**Application access and application roles that are inherited via group membership cannot be deprovisioned using C1. +**Application access and application roles that are inherited via group membership cannot be deprovisioned using ConductorOne. ## Performance considerations @@ -55,7 +55,7 @@ In the domain's navigation menu, click **Integrated applications**. Click **Add application**, select **Confidential application**, and then click **Launch workflow**. -Enter a name for the application, such as "C1", then click **Next**. +Enter a name for the application, such as "ConductorOne", then click **Next**. On the **OAuth Configuration** page, click **Edit OAuth configuration** and select **Configure this application as a client**. @@ -89,17 +89,17 @@ Activate the application using the **Actions** button in the top right, then cli To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in ConductorOne - Access to the set of Oracle IDCS credentials generated by following the instructions above -**Follow these instructions to use a built-in, no-code connector hosted by C1.** +**Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.** -In C1, navigate to **Integrations** > **Connectors** and click **Add connector**. +In ConductorOne, navigate to **Integrations** > **Connectors** and click **Add connector**. Search for **Oracle IDCS** and click **Add**. @@ -107,16 +107,16 @@ Search for **Oracle IDCS** and click **Add**. Choose how to set up the new Oracle IDCS 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 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 C1 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 ConductorOne 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. + 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**. @@ -143,23 +143,23 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**That's it!** Your Oracle IDCS connector is now pulling access data into C1. +**That's it!** Your Oracle IDCS connector is now pulling access data into ConductorOne. **Follow these instructions to use the Oracle IDCS 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. +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 C1's support team](mailto:support@conductorone.com) to download the latest version of the connector. +[Contact ConductorOne's support team](mailto:support@conductorone.com) to download the latest version of the connector. ### Step 1: Set up a new Oracle IDCS connector -In C1, navigate to **Integrations** > **Connectors** > **Add connector**. +In ConductorOne, navigate to **Integrations** > **Connectors** > **Add connector**. Search for **Baton** and click **Add**. @@ -167,16 +167,16 @@ Search for **Baton** and click **Add**. Choose how to set up the new Oracle IDCS 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 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 C1 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 ConductorOne 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. + 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**. @@ -205,19 +205,19 @@ metadata: name: baton-oracle-idcs-secrets type: Opaque stringData: - # C1 credentials - BATON_CLIENT_ID: - BATON_CLIENT_SECRET: + # ConductorOne credentials + BATON_CLIENT_ID: + BATON_CLIENT_SECRET: # Oracle IDCS credentials BATON_API_ACCESS_ID: BATON_API_ACCESS_SECRET: BATON_API_BASE_DOMAIN: - # Optional: include if you want C1 to provision access using this connector + # Optional: include if you want ConductorOne to provision access using this connector BATON_PROVISIONING: true - # Optional: include if you want C1 to sync application and application role data + # Optional: include if you want ConductorOne to sync application and application role data BATON_SYNC_APPS_AND_ROLES: true ``` @@ -260,14 +260,14 @@ spec: -Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files. +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 C1, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Oracle IDCS connector to. Oracle IDCS data should be found on the **Entitlements** and **Accounts** tabs. +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 Oracle IDCS connector to. Oracle IDCS data should be found on the **Entitlements** and **Accounts** tabs. -**That's it!** Your Oracle IDCS connector is now pulling access data into C1. +**That's it!** Your Oracle IDCS connector is now pulling access data into ConductorOne. diff --git a/baton/salesforce.mdx b/baton/salesforce.mdx index 12b9d2a7..e907614e 100644 --- a/baton/salesforce.mdx +++ b/baton/salesforce.mdx @@ -1,18 +1,18 @@ --- title: Set up a Salesforce connector -og:title: Set up a Salesforce connector - C1 docs -og:description: Integrate your Salesforce 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 for Salesforce. Integrate your Salesforce instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a Salesforce connector - ConductorOne docs +og:description: Integrate your Salesforce 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 for Salesforce. Integrate your Salesforce instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: "Salesforce" --- -**This is an updated and improved version of the Salesforce connector!** If you're setting up Salesforce with C1 for the first time, you're in the right place. +**This is an updated and improved version of the Salesforce connector!** If you're setting up Salesforce with ConductorOne for the first time, you're in the right place. ## Availability -C1 only integrates with the Salesforce editions with API access: Salesforce Enterprise, Unlimited, Developer, and Performance editions. +ConductorOne only integrates with the Salesforce editions with API access: Salesforce Enterprise, Unlimited, Developer, and Performance editions. You cannot use this connector successfully with Group or Essentials editions, or with Professional edition without an API add-on. @@ -22,13 +22,13 @@ Learn more about which Salesforce editions support API access in the [Salesforce | Resource | Sync | Provision | | :--- | :--- | :--- | -| Accounts* | | | -| Groups | | | -| Roles | | | -| Permission sets | | | -| Permission set groups | | | -| Profiles | | | -| Connected apps | | | +| Accounts* | | | +| Groups | | | +| Roles | | | +| Permission sets | | | +| Permission set groups | | | +| Profiles | | | +| Connected apps | | | The Salesforce connector supports [automatic account provisioning](/product/admin/account-provisioning). @@ -38,7 +38,7 @@ This connector does not support account deprovisioning. You must deprovision acc ### Connector actions -Connector actions are custom capabilities that extend C1 automations with app-specific operations. You can use connector actions in the [Perform connector action](/product/admin/automations-steps-reference#perform-connector-action) automation step. +Connector actions are custom capabilities that extend ConductorOne automations with app-specific operations. You can use connector actions in the [Perform connector action](/product/admin/automations-steps-reference#perform-connector-action) automation step. | Action name | Additional fields | Description | |-------------|-------------------|-------------| @@ -54,7 +54,7 @@ The owner of a Salesforce user account with a profile that includes the **API En ### Enable API access for your Salesforce user -Before you begin, make sure that the Salesforce user who will set up the integration with C1 has a profile that includes the **API Enabled** and **View Setup and Configuration** permissions. +Before you begin, make sure that the Salesforce user who will set up the integration with ConductorOne has a profile that includes the **API Enabled** and **View Setup and Configuration** permissions. To edit a profile so that it includes the **API Enabled** and **View Setup and Configuration** permissions: @@ -87,7 +87,7 @@ Your user's profile can now access Salesforce APIs. Log into the Salesforce admin panel and copy the URL from your browser. - C1 integrates with domains that use one of the following Salesforce URL structures: + ConductorOne integrates with domains that use one of the following Salesforce URL structures: - `my.salesforce.com` - `sandbox.my.salesforce.com` @@ -105,17 +105,17 @@ Log into the Salesforce admin panel and copy the URL from your browser. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in ConductorOne - Access to the set of Salesforce credentials generated by following the instructions above -**Follow these instructions to use a built-in, no-code connector hosted by C1.** +**Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.** -In C1, navigate to **Integrations** > **Connectors** and click **Add connector**. +In ConductorOne, navigate to **Integrations** > **Connectors** and click **Add connector**. Search for **Salesforce v2** and click **Add**. @@ -123,16 +123,16 @@ Search for **Salesforce v2** and click **Add**. Choose how to set up the new Salesforce 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 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 C1 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 ConductorOne 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. + 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**. @@ -148,7 +148,7 @@ Select your method of authenticating to Salesforce and click either **OAuth** or 1. In the **Domain** field, enter your Salesforce domain. - 2. **Optional.** Check the box to tell C1 to use Salesforce usernames as the email addresses for your organization's accounts. This option is especially helpful if your organization uses multiple service accounts that all share a `noreply@salesforce.com` email address. + 2. **Optional.** Check the box to tell ConductorOne to use Salesforce usernames as the email addresses for your organization's accounts. This option is especially helpful if your organization uses multiple service accounts that all share a `noreply@salesforce.com` email address. 3. **Optional.** Check the box if you want the connector to sync connected apps. @@ -156,15 +156,15 @@ Select your method of authenticating to Salesforce and click either **OAuth** or 5. **Optional.** Check the box if you want the connector to sync users on non-standard licenses, such as external users. - 6. **Optional.** Create a map of the Salesforce license types used by your organization and the profile associated with each license type that has the fewest permissions. C1 will use this information when deprovisioning user profiles to automatically reassign the user to the least-privilege profile associated with their license type. + 6. **Optional.** Create a map of the Salesforce license types used by your organization and the profile associated with each license type that has the fewest permissions. ConductorOne will use this information when deprovisioning user profiles to automatically reassign the user to the least-privilege profile associated with their license type. 7. Click **Save**. 8. Click **Login with OAuth**. - 9. Log in and authorize C1 with your Salesforce instance. + 9. Log in and authorize ConductorOne with your Salesforce instance. - 10. You will then be redirected back to the Salesforce setup page in C1, where you'll see an authorization message. + 10. You will then be redirected back to the Salesforce setup page in ConductorOne, where you'll see an authorization message. If you chose **Username and password**: @@ -174,7 +174,7 @@ Select your method of authenticating to Salesforce and click either **OAuth** or 3. In the **Domain** field, enter your Salesforce domain. - 4. **Optional.** Check the box to tell C1 to use Salesforce usernames as the email addresses for your organization's accounts. This option is especially helpful if your organization uses multiple service accounts that all share a `noreply@salesforce.com` email address. + 4. **Optional.** Check the box to tell ConductorOne to use Salesforce usernames as the email addresses for your organization's accounts. This option is especially helpful if your organization uses multiple service accounts that all share a `noreply@salesforce.com` email address. 5. **Optional.** Check the box if you want the connector to sync connected apps. @@ -182,7 +182,7 @@ Select your method of authenticating to Salesforce and click either **OAuth** or 7. **Optional.** Check the box if you want the connector to sync users on non-standard licenses, such as external users. - 8. **Optional.** Create a map of the Salesforce license types used by your organization and the profile associated with each license type that has the fewest permissions. C1 will use this information when deprovisioning user profiles to automatically reassign the user to the least-privilege profile associated with their license type. + 8. **Optional.** Create a map of the Salesforce license types used by your organization and the profile associated with each license type that has the fewest permissions. ConductorOne will use this information when deprovisioning user profiles to automatically reassign the user to the least-privilege profile associated with their license type. 9. Click **Save**. @@ -191,24 +191,24 @@ Select your method of authenticating to Salesforce and click either **OAuth** or -**That's it!** Your Salesforce connector is now pulling access data into C1. +**That's it!** Your Salesforce connector is now pulling access data into ConductorOne. **Follow these instructions to use the Salesforce 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. +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 * [Official download center](https://dist.conductorone.com/ConductorOne/baton-salesforce): For stable binaries (Windows/Linux/macOS) and container images. -* [GitHub repository](https://github.com/conductorone/baton-salesforce): Access the source code, report issues, or contribute to the project. +* [GitHub repository](https://github.com/ConductorOne/baton-salesforce): Access the source code, report issues, or contribute to the project. ### Step 1: Set up a new Salesforce connector -In C1, navigate to **Integrations** > **Connectors** > **Add connector**. +In ConductorOne, navigate to **Integrations** > **Connectors** > **Add connector**. Search for **Baton** and click **Add**. @@ -216,16 +216,16 @@ Search for **Baton** and click **Add**. Choose how to set up the new Salesforce 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 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 C1 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 ConductorOne 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. + 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**. @@ -253,9 +253,9 @@ metadata: name: baton-salesforce-secrets type: Opaque stringData: - # C1 credentials - BATON_CLIENT_ID: - BATON_CLIENT_SECRET: + # ConductorOne credentials + BATON_CLIENT_ID: + BATON_CLIENT_SECRET: # Salesforce credentials BATON_INSTANCE_URL: @@ -263,7 +263,7 @@ stringData: BATON_SALESFORCE_USERNAME: BATON_SECURITY_TOKEN: - # Optional: include if you want C1 to provision access using this connector + # Optional: include if you want ConductorOne to provision access using this connector BATON_PROVISIONING: true # Optional: include if you want to sync access to connected apps @@ -321,14 +321,14 @@ spec: -Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files. +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 C1, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Salesforce connector to. Salesforce data should be found on the **Entitlements** and **Accounts** tabs. +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 Salesforce connector to. Salesforce data should be found on the **Entitlements** and **Accounts** tabs. -**That's it!** Your Salesforce connector is now pulling access data into C1. +**That's it!** Your Salesforce connector is now pulling access data into ConductorOne. diff --git a/baton/tableau.mdx b/baton/tableau.mdx index 0737b537..4666eb08 100644 --- a/baton/tableau.mdx +++ b/baton/tableau.mdx @@ -1,8 +1,8 @@ --- title: Set up a Tableau connector -og:title: Set up a Tableau connector - C1 docs -og:description: Integrate your Tableau 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 for Tableau. Integrate your Tableau instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a Tableau connector - ConductorOne docs +og:description: Integrate your Tableau 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 for Tableau. Integrate your Tableau instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: Tableau --- @@ -10,13 +10,13 @@ sidebarTitle: Tableau | Resource | Sync | Provision | | ------------ | ---- | --------- | -| Accounts | | | -| Groups | | | -| Sites | | | -| Licenses | | | -| Projects | | | -| Workbooks | | | -| Views | | | +| Accounts | | | +| Groups | | | +| Sites | | | +| Licenses | | | +| Projects | | | +| Workbooks | | | +| Views | | | The Tableau connector supports [automatic account provisioning and deprovisioning](/product/admin/account-provisioning). @@ -50,7 +50,7 @@ Sign into Tableau Server or Tableau Cloud. In the menu bar at the top of the page, click your profile image or initials and select **My Account Settings** from the menu. -In the **Personal Access Tokens** area of the page, enter a name for your new token (such as "C1 integration") and then click **Create**. +In the **Personal Access Tokens** area of the page, enter a name for your new token (such as "ConductorOne integration") and then click **Create**. Carefully copy and save the newly generated token and its name. @@ -81,17 +81,17 @@ For a Tableau Cloud instance with the URL `https://10ay.online.tableau.com#/site To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in ConductorOne - Access to the set of Tableau credentials generated by following the instructions above -**Follow these instructions to use a built-in, no-code connector hosted by C1.** +**Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.** -In C1, navigate to **Integrations** > **Connectors** and click **Add connector**. +In ConductorOne, navigate to **Integrations** > **Connectors** and click **Add connector**. Search for **Tableau** and click **Add**. @@ -99,16 +99,16 @@ Search for **Tableau** and click **Add**. Choose how to set up the new Tableau 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 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 C1 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 ConductorOne 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. + 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**. @@ -132,24 +132,24 @@ 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 Tableau connector is now pulling access data into C1. +**That's it!** Your Tableau connector is now pulling access data into ConductorOne. **Follow these instructions to use the Tableau 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. +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 * [Official download center](https://dist.conductorone.com/ConductorOne/baton-tableau): For stable binaries (Windows/Linux/macOS) and container images. -* [GitHub repository](https://github.com/conductorone/baton-tableau): Access the source code, report issues, or contribute to the project. +* [GitHub repository](https://github.com/ConductorOne/baton-tableau): Access the source code, report issues, or contribute to the project. ### Step 1: Set up a new Tableau connector -In C1, navigate to **Integrations** > **Connectors** > **Add connector**. +In ConductorOne, navigate to **Integrations** > **Connectors** > **Add connector**. Search for **Baton** and click **Add**. @@ -157,16 +157,16 @@ Search for **Baton** and click **Add**. Choose how to set up the new Tableau 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 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 C1 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 ConductorOne 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. + 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**. @@ -194,9 +194,9 @@ metadata: name: baton-tableau-secrets type: Opaque stringData: - # C1 credentials - BATON_CLIENT_ID: - BATON_CLIENT_SECRET: + # ConductorOne credentials + BATON_CLIENT_ID: + BATON_CLIENT_SECRET: # Tableau credentials BATON_ACCESS_TOKEN_NAME: @@ -204,7 +204,7 @@ stringData: BATON_SERVER_PATH: BATON_SITE_ID: - # Optional: include if you want C1 to provision access using this connector + # Optional: include if you want ConductorOne to provision access using this connector BATON_PROVISIONING: true ``` @@ -247,14 +247,14 @@ spec: -Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files. +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 C1, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Tableau connector to. Tableau data should be found on the **Entitlements** and **Accounts** tabs. +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 Tableau connector to. Tableau data should be found on the **Entitlements** and **Accounts** tabs. -**That's it!** Your Tableau connector is now pulling access data into C1. +**That's it!** Your Tableau connector is now pulling access data into ConductorOne. diff --git a/baton/workday.mdx b/baton/workday.mdx index cf52f438..0a42a1e6 100644 --- a/baton/workday.mdx +++ b/baton/workday.mdx @@ -1,14 +1,14 @@ --- title: Set up a Workday connector -og:title: Set up a Workday connector - C1 docs -og:description: Integrate your Workday 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 Workday. Integrate your Workday instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a Workday connector - ConductorOne docs +og:description: Integrate your Workday 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 Workday. Integrate your Workday instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: "Workday" --- ## Which Workday connector should I use? -C1 offers two Workday connectors: Workday and Workday Accounts (WQL). How you want to work with Workday in C1 will determine which one you should set up. +ConductorOne offers two Workday connectors: Workday and Workday Accounts (WQL). How you want to work with Workday in ConductorOne will determine which one you should set up. * **[Workday connector](/baton/workday)**: This connector is the best choice if you want to use Workday as a [directory](/product/admin/directory). You’ll also need it if you want to enable access requests for Workday role and group assignments. @@ -28,9 +28,9 @@ C1 offers two Workday connectors: Workday and Workday Accounts (WQL). How you wa | Resource | Sync | Provision | | :--- | :--- | :--- | -| Accounts | | | -| Roles | | | -| Security groups | | | +| Accounts | | | +| Roles | | | +| Security groups | | | ## Gather Workday credentials @@ -41,9 +41,9 @@ To authenticate with Workday, you can use either a Report-as-a-service (RaaS) ** **Which authentication method should I use?** -The **RaaS custom report option** is the more popular option, and is often preferred by Workday Admins and HR teams, as it’s Workday’s preferred integration method. RaaS allows you fine-grained control over what data is sent to C1. Additionally, it allows you to transform the format of Workday attributes as needed before sending them to C1. +The **RaaS custom report option** is the more popular option, and is often preferred by Workday Admins and HR teams, as it’s Workday’s preferred integration method. RaaS allows you fine-grained control over what data is sent to ConductorOne. Additionally, it allows you to transform the format of Workday attributes as needed before sending them to ConductorOne. -The **API client option** pulls available data about Workday accounts, such as each account's manager and manager email, which can be used as [user attributes](/product/admin/attributes). The custom report method only pulls data that is explicitly named in the report into C1. +The **API client option** pulls available data about Workday accounts, such as each account's manager and manager email, which can be used as [user attributes](/product/admin/attributes). The custom report method only pulls data that is explicitly named in the report into ConductorOne. Follow the relevant set of instructions below to generate your credentials. @@ -110,7 +110,7 @@ Add the following fields to the custom report **in this order**: * Organization Type - The fields needed in custom reports can vary depending on how your Workday installation is configured. Contact C1 support if you need help figuring out which fields to include. + The fields needed in custom reports can vary depending on how your Workday installation is configured. Contact ConductorOne support if you need help figuring out which fields to include. 5. Create the custom report. @@ -148,7 +148,7 @@ In Workday, use the search bar to look up "Create Integration System User". -In the **Create Integration System User** modal, enter a **User Name**, such as "C1 integration". +In the **Create Integration System User** modal, enter a **User Name**, such as "ConductorOne integration". @@ -177,7 +177,7 @@ In the **Maintain Permissions for Security Group** modal, make sure the **Mainta In the **Source Security Group** field, navigate to **By Type** > **Integration System Security Group**. -Create a new security group. Give it a name, such as "C1 integration security group". +Create a new security group. Give it a name, such as "ConductorOne integration security group". On the new group's **Domain Security Policy Permissions** tab, leave the **Select All** box checked. @@ -259,7 +259,7 @@ Review the changes and if everything looks good, click the **Confirm** checkbox, In Workday, use the search bar to look up "Register API Client for Integrations". Make sure to select this name from the results, not the similarly named "Register API Client". -Give the new API client a name, such as "C1 integration". +Give the new API client a name, such as "ConductorOne integration". In the **Integration System User** field, select the ISU you created earlier. This is crucial for associating the API client with the correct permissions. @@ -300,18 +300,18 @@ Carefully copy and save the new refresh token. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in ConductorOne - Access to the set of Workday credentials generated by following the instructions above -**Follow these instructions to use a built-in, no-code connector hosted by C1.** +**Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.** -In C1, navigate to **Integrations** > **Connectors** and click **Add connector**. +In ConductorOne, navigate to **Integrations** > **Connectors** and click **Add connector**. Search for **Workday** and click **Add**. @@ -319,16 +319,16 @@ Search for **Workday** and click **Add**. Choose how to set up the new Workday 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 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 C1 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 ConductorOne 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. + 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**. @@ -362,14 +362,14 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**That's it!** Your Workday connector is now pulling access data into C1. +**That's it!** Your Workday connector is now pulling access data into ConductorOne. **Follow these instructions to use the Workday 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. +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 @@ -379,7 +379,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Integrations** > **Connectors** > **Add connector**. +In ConductorOne, navigate to **Integrations** > **Connectors** > **Add connector**. Search for **Baton** and click **Add**. @@ -387,14 +387,14 @@ Search for **Baton** and click **Add**. Choose how to set up the new Workday 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 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 C1 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 ConductorOne 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. + 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**. @@ -422,9 +422,9 @@ metadata: name: baton-workday-secrets type: Opaque stringData: - # C1 credentials - BATON_CLIENT_ID: - BATON_CLIENT_SECRET: + # ConductorOne credentials + BATON_CLIENT_ID: + BATON_CLIENT_SECRET: # Workday credentials if using an API client to authenticate BATON_WORKDAY_CLIENT_ID: @@ -480,13 +480,13 @@ spec: -Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files. +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 C1, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Workday connector to. Workday data should be found on the **Entitlements** and **Accounts** tabs. +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 Workday connector to. Workday data should be found on the **Entitlements** and **Accounts** tabs. -**That's it!** Your Workday connector is now pulling access data into C1. +**That's it!** Your Workday connector is now pulling access data into ConductorOne. ## Troubleshooting the Workday connector diff --git a/baton/zoom.mdx b/baton/zoom.mdx index e7602a8c..a19fc85f 100644 --- a/baton/zoom.mdx +++ b/baton/zoom.mdx @@ -1,8 +1,8 @@ --- title: Set up a Zoom connector -og:title: Set up a Zoom connector - C1 docs -og:description: Integrate your Zoom 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 for Zoom. Integrate your Zoom instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a Zoom connector - ConductorOne docs +og:description: Integrate your Zoom 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 for Zoom. Integrate your Zoom instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: Zoom --- @@ -14,10 +14,11 @@ This connector works with Zoom on the Pro, Business, Business Plus, or Enterpris | Resource | Sync | Provision | | ------------ | ---- | --------- | -| Accounts | | | -| Groups | | | -| Roles | | | -| Contact groups | | | +| Accounts | | | +| Groups | | | +| Roles | | | +| Contact groups | | | +| Invites | | | The Zoom connector supports [automatic account provisioning](/product/admin/account-provisioning). @@ -44,7 +45,7 @@ Click **Develop** and select **Build App**. Locate the **Server-to-Server OAuth** option and click **Create**. -Give your app a name, such as "C1" and click **Create**. +Give your app a name, such as "ConductorOne" and click **Create**. A page for the newly created app opens. Copy and save the Account ID, Client ID, and Client secret shown on this page. @@ -75,7 +76,7 @@ On the **Scopes** page, click **+ Add Scopes**. Give the app the following set o - user:read:user:admin - user:read:list_users:admin - If you want to use C1 to provision and deprovision Zoom permissions, add these scopes as well: + If you want to use ConductorOne to provision and deprovision Zoom permissions, add these scopes as well: - role:write:member:admin - role:delete:member:admin @@ -100,18 +101,18 @@ On the **Activation** page, click **Activate your app**. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in ConductorOne - Access to the set of Zoom credentials generated by following the instructions above -**Follow these instructions to use a built-in, no-code connector hosted by C1.** +**Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.** -In C1, navigate to **Integrations** > **Connectors** and click **Add connector**. +In ConductorOne, navigate to **Integrations** > **Connectors** and click **Add connector**. Search for **Zoom** and click **Add**. @@ -119,16 +120,16 @@ Search for **Zoom** and click **Add**. Choose how to set up the new Zoom 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 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 C1 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 ConductorOne 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. + 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**. @@ -143,29 +144,32 @@ Enter the account ID for the new app into the **Account ID** fields. Enter the Client ID and Client secret into the **Client ID** and **Client secret** fields. +Optionally, enable **Sync Inactive Users** to include deactivated Zoom users in the sync. When enabled, inactive users appear with a disabled status in ConductorOne. This is disabled by default. + + 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 Zoom connector is now pulling access data into C1. +**That's it!** Your Zoom connector is now pulling access data into ConductorOne. **Follow these instructions to use the Zoom 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. +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 -* [GitHub repository](https://github.com/conductorone/baton-zoom): Access the source code, report issues, or contribute to the project. +* [GitHub repository](https://github.com/ConductorOne/baton-zoom): Access the source code, report issues, or contribute to the project. ### Step 1: Set up a new Zoom connector -In C1, navigate to **Integrations** > **Connectors** > **Add connector**. +In ConductorOne, navigate to **Integrations** > **Connectors** > **Add connector**. Search for **Baton** and click **Add**. @@ -173,16 +177,16 @@ Search for **Baton** and click **Add**. Choose how to set up the new Zoom 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 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 C1 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 ConductorOne 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. + 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**. @@ -210,17 +214,20 @@ metadata: name: baton-zoom-secrets type: Opaque stringData: - # C1 credentials - BATON_CLIENT_ID: - BATON_CLIENT_SECRET: + # ConductorOne credentials + BATON_CLIENT_ID: + BATON_CLIENT_SECRET: # Zoom credentials BATON_ACCOUNT_ID: BATON_ZOOM_CLIENT_ID: BATON_ZOOM_CLIENT_SECRET: - # Optional: include if you want C1 to provision access using this connector + # Optional: include if you want ConductorOne to provision access using this connector BATON_PROVISIONING: true + + # Optional: sync deactivated Zoom users (disabled by default) + BATON_SYNC_INACTIVE_USERS: true ``` See the connector's README or run `--help` to see all available configuration flags and environment variables. @@ -262,14 +269,14 @@ spec: -Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files. +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 C1, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Zoom connector to. Zoom data should be found on the **Entitlements** and **Accounts** tabs. +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 Zoom connector to. Zoom data should be found on the **Entitlements** and **Accounts** tabs. -**That's it!** Your Zoom connector is now pulling access data into C1. +**That's it!** Your Zoom connector is now pulling access data into ConductorOne. diff --git a/docs.json b/docs.json index 69fe3c80..41cf66fd 100644 --- a/docs.json +++ b/docs.json @@ -355,6 +355,7 @@ "baton/duo", "baton/cisco-meraki", "baton/claude-developer-platform", + "baton/claude-enterprise", "baton/clickhouse-cloud", "baton/cloudamqp", "baton/cloudflare", @@ -428,8 +429,8 @@ "baton/microsoft-dynamics", "baton/microsoft-dynamics-fo", "baton/microsoft-entra", - "baton/fileshare", "baton/sharepoint", + "baton/fileshare", "baton/miro", "baton/mode", "baton/monday", @@ -782,4 +783,3 @@ }, "theme": "aspen" } - From d8adefddbd65e264a6bbcae04cac2fabb68ed332 Mon Sep 17 00:00:00 2001 From: Mindy Moreland Date: Tue, 7 Apr 2026 12:57:03 -0700 Subject: [PATCH 2/5] docs: restore C1 rebrand in synced connector docs Synced content introduced ConductorOne in prose and reverted icon color to #65DE23. This commit restores C1 in prose and #c937ae icon color, while preserving all new capabilities, sections, and steps from the sync. GitHub org URLs (github.com/ConductorOne) are unchanged. Co-Authored-By: Claude Sonnet 4.6 --- baton/artifactory.mdx | 52 +++++++++++------------ baton/claude-enterprise.mdx | 66 ++++++++++++++--------------- baton/google-workspace.mdx | 64 ++++++++++++++--------------- baton/oracle-idcs.mdx | 58 +++++++++++++------------- baton/salesforce.mdx | 82 ++++++++++++++++++------------------- baton/tableau.mdx | 62 ++++++++++++++-------------- baton/workday.mdx | 64 ++++++++++++++--------------- baton/zoom.mdx | 60 +++++++++++++-------------- 8 files changed, 254 insertions(+), 254 deletions(-) diff --git a/baton/artifactory.mdx b/baton/artifactory.mdx index 460e8979..04f0f727 100644 --- a/baton/artifactory.mdx +++ b/baton/artifactory.mdx @@ -1,8 +1,8 @@ --- title: "Set up Artifactory connector" og:title: "Set up Artifactory connector" -description: "ConductorOne provides identity governance and just-in-time provisioning for Artifactory. Integrate your Artifactory instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests." -og:description: "ConductorOne provides identity governance and just-in-time provisioning for Artifactory. Integrate your Artifactory instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1 provides identity governance and just-in-time provisioning for Artifactory. Integrate your Artifactory instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1 provides identity governance and just-in-time provisioning for Artifactory. Integrate your Artifactory instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "JFrog Artifactory" --- @@ -10,10 +10,10 @@ sidebarTitle: "JFrog Artifactory" | Resource | Sync | Provision | | :--- | :--- | :--- | -| Account | | | -| Administrator | | | -| Group | | | -| Repository | | | +| Account | | | +| Administrator | | | +| Group | | | +| Repository | | | **Additional functionality:** @@ -25,7 +25,7 @@ sidebarTitle: "JFrog Artifactory" **Known limitations:** -- Repository permissions granted via pre-existing Artifactory permission targets (not created by ConductorOne) cannot be revoked through this connector. Only permissions provisioned by ConductorOne can be revoked. +- Repository permissions granted via pre-existing Artifactory permission targets (not created by C1) cannot be revoked through this connector. Only permissions provisioned by C1 can be revoked. - When a user inherits a repository permission from multiple groups, the connector attributes the grant to one group. ## Gather Artifactory configuration information @@ -44,31 +44,31 @@ See the Artifactory docs for information on how to acquire credentials: [View th 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 Artifactory configuration information gathered by following the instructions above -**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.** - In ConductorOne, navigate to **Integrations** > **Connectors** and click **Add connector**. + In C1, navigate to **Integrations** > **Connectors** and click **Add connector**. Search for **Artifactory** and click **Add**. Choose how to set up the new Artifactory 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 - 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. + 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**. @@ -87,37 +87,37 @@ To complete this task, you'll need: -**That's it!** Your Artifactory connector is now pulling access data into ConductorOne. +**That's it!** Your Artifactory connector is now pulling access data into C1. **Follow these instructions to use the Artifactory 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 -[Contact ConductorOne's support team](mailto:support@conductorone.com) to download the latest version of the connector. +[Contact C1's support team](mailto:support@conductorone.com) to download the latest version of the connector. ### Step 1: Set up a new Artifactory connector - In ConductorOne, navigate to **Integrations** > **Connectors** > **Add connector**. + In C1, navigate to **Integrations** > **Connectors** > **Add connector**. Search for **Baton** and click **Add**. Choose how to set up the new Artifactory 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 - 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. + 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**. @@ -145,9 +145,9 @@ metadata: name: baton-artifactory-secrets type: Opaque stringData: - # ConductorOne credentials - BATON_CLIENT_ID: - BATON_CLIENT_SECRET: + # C1 credentials + BATON_CLIENT_ID: + BATON_CLIENT_SECRET: # Artifactory config BATON_ARTIFACTORY_BASE_URL: @@ -193,14 +193,14 @@ spec: - 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. - 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 Artifactory connector to. Artifactory 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 Artifactory connector to. Artifactory data should be found on the **Entitlements** and **Accounts** tabs. -**That's it!** Your Artifactory connector is now pulling access data into ConductorOne. +**That's it!** Your Artifactory connector is now pulling access data into C1. diff --git a/baton/claude-enterprise.mdx b/baton/claude-enterprise.mdx index 6d2da01a..73b6738d 100644 --- a/baton/claude-enterprise.mdx +++ b/baton/claude-enterprise.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Claude Enterprise connector" og:title: "Set up a Claude Enterprise connector" -description: "ConductorOne provides identity governance and just-in-time provisioning for Claude Enterprise. Integrate your Claude Enterprise instance with ConductorOne to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." -og:description: "ConductorOne provides identity governance and just-in-time provisioning for Claude Enterprise. Integrate your Claude Enterprise instance with ConductorOne to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1 provides identity governance and just-in-time provisioning for Claude Enterprise. Integrate your Claude Enterprise instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1 provides identity governance and just-in-time provisioning for Claude Enterprise. Integrate your Claude Enterprise instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "Claude Enterprise" --- @@ -15,24 +15,24 @@ The Claude Enterprise connector syncs the following resources: | Resource | Sync | Provision | | :--- | :--- | :--- | -| Accounts | | Create, Delete | -| Groups | | Grant, Revoke | +| Accounts | | Create, Delete | +| Groups | | Grant, Revoke | {/* AUTO-GENERATED:END - capabilities */} **Additional functionality:** - Supports [automatic account provisioning and deprovisioning](/product/admin/account-provisioning) + Supports [automatic account provisioning and deprovisioning](/product/admin/account-provisioning) #### Account creation fields -When provisioning a new Claude Enterprise user account, ConductorOne prompts for the following field: +When provisioning a new Claude Enterprise user account, C1 prompts for the following field: | Field | Required | Description | | :--- | :--- | :--- | | `display_name` | Yes | The user's first and last name, space-separated (e.g., "Jane Smith"). The first word is used as the given name; the remainder is used as the family name. | -The user's email address is provided automatically by ConductorOne and is used as the SCIM username. No password is required — Claude Enterprise authenticates users through SSO, so accounts are created without credentials. +The user's email address is provided automatically by C1 and is used as the SCIM username. No password is required — Claude Enterprise authenticates users through SSO, so accounts are created without credentials. ## SCIM-only connector @@ -41,19 +41,19 @@ This connector uses the SCIM 2.0 API exclusively. Claude Enterprise does not cur ### What this means in practice - **Only SCIM-managed users and groups are visible.** Users or groups created directly through the Claude Enterprise UI will not appear in syncs. To get full visibility, all user management should flow through SCIM. -- **Groups are managed through SCIM only.** The connector can sync groups and grant or revoke group membership, but it cannot create or delete groups. Groups must be created outside of ConductorOne (e.g., through your identity provider or directly via the SCIM API). +- **Groups are managed through SCIM only.** The connector can sync groups and grant or revoke group membership, but it cannot create or delete groups. Groups must be created outside of C1 (e.g., through your identity provider or directly via the SCIM API). - **Claude Enterprise uses WorkOS under the hood** for its SCIM implementation. The SCIM endpoint URL provided during setup points to the WorkOS SCIM service. ### What SCIM provides | Capability | Supported | | :--- | :--- | -| Provision (create) user | | -| Deprovision (delete) user | | -| Add user to group | | -| Remove user from group | | -| Sync all users | | -| Sync all groups and memberships | | +| Provision (create) user | | +| Deprovision (delete) user | | +| Add user to group | | +| Remove user from group | | +| Sync all users | | +| Sync all groups and memberships | | | Create or delete groups | | | Assign roles | | | Manage workspace settings | | @@ -91,18 +91,18 @@ The **Primary Owner** of the Claude Enterprise organization must perform this ta 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 Claude Enterprise SCIM credentials generated by following the instructions above - **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.** - In ConductorOne, navigate to **Integrations** > **Connectors** and click **Add connector**. + In C1, navigate to **Integrations** > **Connectors** and click **Add connector**. @@ -112,15 +112,15 @@ To complete this task, you'll need: Choose how to set up the new Claude Enterprise 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 - 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. @@ -152,7 +152,7 @@ To complete this task, you'll need: - **That's it!** Your Claude Enterprise connector is now pulling access data into ConductorOne. + **That's it!** Your Claude Enterprise connector is now pulling access data into C1. @@ -160,11 +160,11 @@ To complete this task, you'll need: **Follow these instructions to use the Claude Enterprise 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 - * [Official download center](https://dist.conductorone.com/ConductorOne/baton-claude-enterprise): For stable binaries (Windows/Linux/macOS) and container images. + * [Official download center](https://dist.conductorone.com/C1/baton-claude-enterprise): For stable binaries (Windows/Linux/macOS) and container images. * [GitHub repository](https://github.com/ConductorOne/baton-claude-enterprise): Access the source code, report issues, or contribute to the project. @@ -172,7 +172,7 @@ To complete this task, you'll need: - In ConductorOne, navigate to **Integrations** > **Connectors** > **Add connector**. + In C1, navigate to **Integrations** > **Connectors** > **Add connector**. @@ -188,9 +188,9 @@ To complete this task, you'll need: - 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. @@ -222,9 +222,9 @@ To complete this task, you'll need: name: baton-claude-enterprise-secrets type: Opaque stringData: - # ConductorOne credentials - BATON_CLIENT_ID: - BATON_CLIENT_SECRET: + # C1 credentials + BATON_CLIENT_ID: + BATON_CLIENT_SECRET: # Claude Enterprise SCIM credentials BATON_SCIM_TOKEN: @@ -270,15 +270,15 @@ To complete this task, you'll need: - 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. - Check that the connector data uploaded correctly. In ConductorOne, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the Claude Enterprise connector to. Claude Enterprise data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the Claude Enterprise connector to. Claude Enterprise data should be found on the **Entitlements** and **Accounts** tabs. - **That's it!** Your Claude Enterprise connector is now pulling access data into ConductorOne. + **That's it!** Your Claude Enterprise connector is now pulling access data into C1. @@ -286,5 +286,5 @@ To complete this task, you'll need: --- -All versions of this connector are available at [dist.conductorone.com](https://dist.conductorone.com/ConductorOne/baton-claude-enterprise). +All versions of this connector are available at [dist.conductorone.com](https://dist.conductorone.com/C1/baton-claude-enterprise). diff --git a/baton/google-workspace.mdx b/baton/google-workspace.mdx index 96b5256f..0ece91c5 100644 --- a/baton/google-workspace.mdx +++ b/baton/google-workspace.mdx @@ -1,23 +1,23 @@ --- title: "Set up a Google Workspace connector" og:title: "Set up a Google Workspace connector" -description: "ConductorOne provides identity governance and just-in-time provisioning for Google Workspace. Integrate your Google Workspace instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests." -og:description: "ConductorOne provides identity governance and just-in-time provisioning for Google Workspace. Integrate your Google Workspace instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1 provides identity governance and just-in-time provisioning for Google Workspace. Integrate your Google Workspace instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1 provides identity governance and just-in-time provisioning for Google Workspace. Integrate your Google Workspace instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Google Workspace" --- -**This is an updated and improved version of the Google Workspace integration!** If you're setting up a Google Workspace connector with ConductorOne for the first time, you're in the right place. +**This is an updated and improved version of the Google Workspace integration!** If you're setting up a Google Workspace connector with C1 for the first time, you're in the right place. ## Capabilities | Resource | Sync | Provision | | :--- | :--- | :--- | -| Accounts | | | -| Groups | | | -| Roles | | | -| Enterprise Applications | | | +| Accounts | | | +| Groups | | | +| Roles | | | +| Enterprise Applications | | | The Google Workspace connector supports [automatic account provisioning and deprovisioning](/product/admin/account-provisioning). @@ -25,7 +25,7 @@ Enable **Sync Enterprise Apps** to track which users have accessed OAuth and SAM ### Connector actions -Connector actions are custom capabilities that extend ConductorOne automations with app-specific operations. You can use connector actions in the [Perform connector action](/product/admin/automations-steps-reference#perform-connector-action) automation step. +Connector actions are custom capabilities that extend C1 automations with app-specific operations. You can use connector actions in the [Perform connector action](/product/admin/automations-steps-reference#perform-connector-action) automation step. | Action name | Additional fields | Description | |-------------|-------------------|-------------| @@ -64,7 +64,7 @@ In the toolbar, open the project select dropdown and click **NEW PROJECT**. Create a new project for your organization: - - **Project Name**: Choose a names, such as "ConductorOne Integration" + - **Project Name**: Choose a names, such as "C1 Integration" - **Organization/Location**: Choose the appropriate Organization/Location @@ -108,8 +108,8 @@ Select **CREATE CREDENTIALS** > **Service Account**. Under **Service account details**, fill in the following: - - **Service account name:** ConductorOne Integration - - **Service account description:** for example, "Service account for ConductorOne Google Workspace Integration" + - **Service account name:** C1 Integration + - **Service account description:** for example, "Service account for C1 Google Workspace Integration" - Click **CREATE AND CONTINUE** @@ -165,7 +165,7 @@ Click **Add new** and fill out the form: - **Client ID**: The service account's unique ID - **OAuth Scopes**: Copy and paste in the relevant scopes - Use the following scopes to give ConductorOne **READ** access (for syncing access data): + Use the following scopes to give C1 **READ** access (for syncing access data): ```bash https://www.googleapis.com/auth/admin.directory.domain.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.directory.group.member.readonly, https://www.googleapis.com/auth/admin.directory.rolemanagement.readonly, https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.reports.audit.readonly @@ -191,7 +191,7 @@ Click **Add new** and fill out the form: - Scope: https://www.googleapis.com/auth/admin.reports.audit.readonly
Purpose: To sync usage events and admin events (used in conjunction with incremental sync). - Use the following scopes to give ConductorOne **READ/WRITE** access (for syncing access data and provisioning access): + Use the following scopes to give C1 **READ/WRITE** access (for syncing access data and provisioning access): ```bash https://www.googleapis.com/auth/admin.directory.domain.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.directory.group.member, https://www.googleapis.com/auth/admin.directory.rolemanagement, https://www.googleapis.com/auth/admin.directory.user, https://www.googleapis.com/auth/admin.reports.audit.readonly, https://www.googleapis.com/auth/admin.datatransfer, https://www.googleapis.com/auth/admin.directory.group, https://www.googleapis.com/auth/admin.directory.user.security, https://www.googleapis.com/auth/apps.groups.settings @@ -267,16 +267,16 @@ Click **Manage Domains**. Locate and copy the domain labeled as the **Primary Do ## Configure the Google Workspace connector -This task requires either the **Connector Administrator** or **Super Administrator** role in ConductorOne. +This task requires either the **Connector Administrator** or **Super Administrator** role in C1. -**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.** -In ConductorOne, navigate to **Integrations** > **Connectors** and click **Add connector**. +In C1, navigate to **Integrations** > **Connectors** and click **Add connector**. Search for **Google Workspace v2** and click **Add**. @@ -284,21 +284,21 @@ Search for **Google Workspace v2** and click **Add**. Choose how to set up the new Google Workspace 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 -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. Click **Next**. - **If you are the connector owner**, go on to the next step. - - **If someone else is the connector owner**, you can stop here. ConductorOne will notify the connector owner by email that their help is needed to complete the setup process. + - **If someone else is the connector owner**, you can stop here. C1 will notify the connector owner by email that their help is needed to complete the setup process. Find the **Settings** area of the page and click **Edit**. @@ -307,7 +307,7 @@ Find the **Settings** area of the page and click **Edit**. In the **Customer ID** field, enter the Google Workspace customer ID. -**Optional.** If you want to limit which domains ConductorOne syncs, in the **Domain** field, enter the primary domain from Step 6. If you leave this field blank, ConductorOne will sync all available domains. +**Optional.** If you want to limit which domains C1 syncs, in the **Domain** field, enter the primary domain from Step 6. If you leave this field blank, C1 will sync all available domains. In the **Administrator email** field, enter the email address associated with your domain or a super admin. @@ -326,17 +326,17 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**That's it!** Your Google Workspace connector is now pulling access data into ConductorOne. +**That's it!** Your Google Workspace connector is now pulling access data into C1. **Follow these instructions to use the Google Workspace 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 -* [Official download center](https://dist.conductorone.com/ConductorOne/baton-google-workspace): For stable binaries (Windows/Linux/macOS) and container images. +* [Official download center](https://dist.conductorone.com/C1/baton-google-workspace): For stable binaries (Windows/Linux/macOS) and container images. * [GitHub repository](https://github.com/ConductorOne/baton-google-workspace): Access the source code, report issues, or contribute to the project. @@ -344,7 +344,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In ConductorOne, navigate to **Integrations** **Connectors** > **Add connector** +In C1, navigate to **Integrations** **Connectors** > **Add connector** Search for **Baton** and click **Add** @@ -384,9 +384,9 @@ metadata: name: baton-google-workspace-secrets type: Opaque data: - # ConductorOne credentials - BATON_CLIENT_ID: - BATON_CLIENT_SECRET: + # C1 credentials + BATON_CLIENT_ID: + BATON_CLIENT_SECRET: # Google Workspace specific credentials BATON_CUSTOMER_ID: @@ -394,7 +394,7 @@ data: BATON_ADMINISTRATOR_EMAIL: BATON_CREDENTIALS_JSON: - # Optional: include if you want ConductorOne to provision access using this connector + # Optional: include if you want C1 to provision access using this connector BATON_PROVISIONING: true # Optional: enable enterprise application and login activity syncing (requires additional OAuth scopes) @@ -442,20 +442,20 @@ spec: -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. -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 Google Workspace connector to. Google Workspace 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 Google Workspace connector to. Google Workspace data should be found on the **Entitlements** and **Accounts** tabs. -**That's it!** Your Google Workspace connector is now pulling access data into ConductorOne. +**That's it!** Your Google Workspace connector is now pulling access data into C1. ### What's next? -If Google Workspace is your company's identity provider (meaning that it is used to SSO into other software), the integration sync will automatically create applications in ConductorOne for all of your SCIMed software. Before you move on, review the [Create applications](/product/admin/applications) page for important information about how to set up integrations with the SCIMed apps. +If Google Workspace is your company's identity provider (meaning that it is used to SSO into other software), the integration sync will automatically create applications in C1 for all of your SCIMed software. Before you move on, review the [Create applications](/product/admin/applications) page for important information about how to set up integrations with the SCIMed apps. ## Troubleshooting the Google Workspace integration diff --git a/baton/oracle-idcs.mdx b/baton/oracle-idcs.mdx index 646cb3cd..05d70ea0 100644 --- a/baton/oracle-idcs.mdx +++ b/baton/oracle-idcs.mdx @@ -1,8 +1,8 @@ --- title: "Set up an Oracle IDCS connector" og:title: "Set up an Oracle IDCS connector" -description: "ConductorOne provides identity governance for Oracle Identity Cloud Service (IDCS). Integrate your Oracle IDCS instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests." -og:description: "ConductorOne provides identity governance for Oracle Identity Cloud Service (IDCS). Integrate your Oracle IDCS instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1 provides identity governance for Oracle Identity Cloud Service (IDCS). Integrate your Oracle IDCS instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1 provides identity governance for Oracle Identity Cloud Service (IDCS). Integrate your Oracle IDCS instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Oracle Identity Cloud Service" --- @@ -14,16 +14,16 @@ sidebarTitle: "Oracle Identity Cloud Service" | Resource | Sync | Provision | | :--- | :--- | :--- | -| Accounts | | | -| Groups | | | -| Applications | * | ** | -| Application roles | * | ** | +| Accounts | | | +| Groups | | | +| Applications | * | ** | +| Application roles | * | ** | The Oracle IDCS connector supports [automatic account provisioning and deprovisioning](/product/admin/account-provisioning). *You must opt into syncing application and application role data; these are not synced by default. -**Application access and application roles that are inherited via group membership cannot be deprovisioned using ConductorOne. +**Application access and application roles that are inherited via group membership cannot be deprovisioned using C1. ## Performance considerations @@ -55,7 +55,7 @@ In the domain's navigation menu, click **Integrated applications**. Click **Add application**, select **Confidential application**, and then click **Launch workflow**. -Enter a name for the application, such as "ConductorOne", then click **Next**. +Enter a name for the application, such as "C1", then click **Next**. On the **OAuth Configuration** page, click **Edit OAuth configuration** and select **Configure this application as a client**. @@ -89,17 +89,17 @@ Activate the application using the **Actions** button in the top right, then cli 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 Oracle IDCS credentials generated by following the instructions above -**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.** -In ConductorOne, navigate to **Integrations** > **Connectors** and click **Add connector**. +In C1, navigate to **Integrations** > **Connectors** and click **Add connector**. Search for **Oracle IDCS** and click **Add**. @@ -107,16 +107,16 @@ Search for **Oracle IDCS** and click **Add**. Choose how to set up the new Oracle IDCS 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 -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. Click **Next**. @@ -143,23 +143,23 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**That's it!** Your Oracle IDCS connector is now pulling access data into ConductorOne. +**That's it!** Your Oracle IDCS connector is now pulling access data into C1. **Follow these instructions to use the Oracle IDCS 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 -[Contact ConductorOne's support team](mailto:support@conductorone.com) to download the latest version of the connector. +[Contact C1's support team](mailto:support@conductorone.com) to download the latest version of the connector. ### Step 1: Set up a new Oracle IDCS connector -In ConductorOne, navigate to **Integrations** > **Connectors** > **Add connector**. +In C1, navigate to **Integrations** > **Connectors** > **Add connector**. Search for **Baton** and click **Add**. @@ -167,16 +167,16 @@ Search for **Baton** and click **Add**. Choose how to set up the new Oracle IDCS 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 -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. Click **Next**. @@ -205,19 +205,19 @@ metadata: name: baton-oracle-idcs-secrets type: Opaque stringData: - # ConductorOne credentials - BATON_CLIENT_ID: - BATON_CLIENT_SECRET: + # C1 credentials + BATON_CLIENT_ID: + BATON_CLIENT_SECRET: # Oracle IDCS credentials BATON_API_ACCESS_ID: BATON_API_ACCESS_SECRET: BATON_API_BASE_DOMAIN: - # Optional: include if you want ConductorOne to provision access using this connector + # Optional: include if you want C1 to provision access using this connector BATON_PROVISIONING: true - # Optional: include if you want ConductorOne to sync application and application role data + # Optional: include if you want C1 to sync application and application role data BATON_SYNC_APPS_AND_ROLES: true ``` @@ -260,14 +260,14 @@ spec: -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. -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 Oracle IDCS connector to. Oracle IDCS 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 Oracle IDCS connector to. Oracle IDCS data should be found on the **Entitlements** and **Accounts** tabs. -**That's it!** Your Oracle IDCS connector is now pulling access data into ConductorOne. +**That's it!** Your Oracle IDCS connector is now pulling access data into C1. diff --git a/baton/salesforce.mdx b/baton/salesforce.mdx index e907614e..83641b1e 100644 --- a/baton/salesforce.mdx +++ b/baton/salesforce.mdx @@ -1,18 +1,18 @@ --- title: Set up a Salesforce connector -og:title: Set up a Salesforce connector - ConductorOne docs -og:description: Integrate your Salesforce 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 for Salesforce. Integrate your Salesforce instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a Salesforce connector - C1 docs +og:description: Integrate your Salesforce 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 for Salesforce. Integrate your Salesforce instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: "Salesforce" --- -**This is an updated and improved version of the Salesforce connector!** If you're setting up Salesforce with ConductorOne for the first time, you're in the right place. +**This is an updated and improved version of the Salesforce connector!** If you're setting up Salesforce with C1 for the first time, you're in the right place. ## Availability -ConductorOne only integrates with the Salesforce editions with API access: Salesforce Enterprise, Unlimited, Developer, and Performance editions. +C1 only integrates with the Salesforce editions with API access: Salesforce Enterprise, Unlimited, Developer, and Performance editions. You cannot use this connector successfully with Group or Essentials editions, or with Professional edition without an API add-on. @@ -22,13 +22,13 @@ Learn more about which Salesforce editions support API access in the [Salesforce | Resource | Sync | Provision | | :--- | :--- | :--- | -| Accounts* | | | -| Groups | | | -| Roles | | | -| Permission sets | | | -| Permission set groups | | | -| Profiles | | | -| Connected apps | | | +| Accounts* | | | +| Groups | | | +| Roles | | | +| Permission sets | | | +| Permission set groups | | | +| Profiles | | | +| Connected apps | | | The Salesforce connector supports [automatic account provisioning](/product/admin/account-provisioning). @@ -38,7 +38,7 @@ This connector does not support account deprovisioning. You must deprovision acc ### Connector actions -Connector actions are custom capabilities that extend ConductorOne automations with app-specific operations. You can use connector actions in the [Perform connector action](/product/admin/automations-steps-reference#perform-connector-action) automation step. +Connector actions are custom capabilities that extend C1 automations with app-specific operations. You can use connector actions in the [Perform connector action](/product/admin/automations-steps-reference#perform-connector-action) automation step. | Action name | Additional fields | Description | |-------------|-------------------|-------------| @@ -54,7 +54,7 @@ The owner of a Salesforce user account with a profile that includes the **API En ### Enable API access for your Salesforce user -Before you begin, make sure that the Salesforce user who will set up the integration with ConductorOne has a profile that includes the **API Enabled** and **View Setup and Configuration** permissions. +Before you begin, make sure that the Salesforce user who will set up the integration with C1 has a profile that includes the **API Enabled** and **View Setup and Configuration** permissions. To edit a profile so that it includes the **API Enabled** and **View Setup and Configuration** permissions: @@ -87,7 +87,7 @@ Your user's profile can now access Salesforce APIs. Log into the Salesforce admin panel and copy the URL from your browser. - ConductorOne integrates with domains that use one of the following Salesforce URL structures: + C1 integrates with domains that use one of the following Salesforce URL structures: - `my.salesforce.com` - `sandbox.my.salesforce.com` @@ -105,17 +105,17 @@ Log into the Salesforce admin panel and copy the URL from your browser. 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 Salesforce credentials generated by following the instructions above -**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.** -In ConductorOne, navigate to **Integrations** > **Connectors** and click **Add connector**. +In C1, navigate to **Integrations** > **Connectors** and click **Add connector**. Search for **Salesforce v2** and click **Add**. @@ -123,16 +123,16 @@ Search for **Salesforce v2** and click **Add**. Choose how to set up the new Salesforce 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 -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. Click **Next**. @@ -148,7 +148,7 @@ Select your method of authenticating to Salesforce and click either **OAuth** or 1. In the **Domain** field, enter your Salesforce domain. - 2. **Optional.** Check the box to tell ConductorOne to use Salesforce usernames as the email addresses for your organization's accounts. This option is especially helpful if your organization uses multiple service accounts that all share a `noreply@salesforce.com` email address. + 2. **Optional.** Check the box to tell C1 to use Salesforce usernames as the email addresses for your organization's accounts. This option is especially helpful if your organization uses multiple service accounts that all share a `noreply@salesforce.com` email address. 3. **Optional.** Check the box if you want the connector to sync connected apps. @@ -156,15 +156,15 @@ Select your method of authenticating to Salesforce and click either **OAuth** or 5. **Optional.** Check the box if you want the connector to sync users on non-standard licenses, such as external users. - 6. **Optional.** Create a map of the Salesforce license types used by your organization and the profile associated with each license type that has the fewest permissions. ConductorOne will use this information when deprovisioning user profiles to automatically reassign the user to the least-privilege profile associated with their license type. + 6. **Optional.** Create a map of the Salesforce license types used by your organization and the profile associated with each license type that has the fewest permissions. C1 will use this information when deprovisioning user profiles to automatically reassign the user to the least-privilege profile associated with their license type. 7. Click **Save**. 8. Click **Login with OAuth**. - 9. Log in and authorize ConductorOne with your Salesforce instance. + 9. Log in and authorize C1 with your Salesforce instance. - 10. You will then be redirected back to the Salesforce setup page in ConductorOne, where you'll see an authorization message. + 10. You will then be redirected back to the Salesforce setup page in C1, where you'll see an authorization message. If you chose **Username and password**: @@ -174,7 +174,7 @@ Select your method of authenticating to Salesforce and click either **OAuth** or 3. In the **Domain** field, enter your Salesforce domain. - 4. **Optional.** Check the box to tell ConductorOne to use Salesforce usernames as the email addresses for your organization's accounts. This option is especially helpful if your organization uses multiple service accounts that all share a `noreply@salesforce.com` email address. + 4. **Optional.** Check the box to tell C1 to use Salesforce usernames as the email addresses for your organization's accounts. This option is especially helpful if your organization uses multiple service accounts that all share a `noreply@salesforce.com` email address. 5. **Optional.** Check the box if you want the connector to sync connected apps. @@ -182,7 +182,7 @@ Select your method of authenticating to Salesforce and click either **OAuth** or 7. **Optional.** Check the box if you want the connector to sync users on non-standard licenses, such as external users. - 8. **Optional.** Create a map of the Salesforce license types used by your organization and the profile associated with each license type that has the fewest permissions. ConductorOne will use this information when deprovisioning user profiles to automatically reassign the user to the least-privilege profile associated with their license type. + 8. **Optional.** Create a map of the Salesforce license types used by your organization and the profile associated with each license type that has the fewest permissions. C1 will use this information when deprovisioning user profiles to automatically reassign the user to the least-privilege profile associated with their license type. 9. Click **Save**. @@ -191,16 +191,16 @@ Select your method of authenticating to Salesforce and click either **OAuth** or -**That's it!** Your Salesforce connector is now pulling access data into ConductorOne. +**That's it!** Your Salesforce connector is now pulling access data into C1. **Follow these instructions to use the Salesforce 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 -* [Official download center](https://dist.conductorone.com/ConductorOne/baton-salesforce): For stable binaries (Windows/Linux/macOS) and container images. +* [Official download center](https://dist.conductorone.com/C1/baton-salesforce): For stable binaries (Windows/Linux/macOS) and container images. * [GitHub repository](https://github.com/ConductorOne/baton-salesforce): Access the source code, report issues, or contribute to the project. @@ -208,7 +208,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In ConductorOne, navigate to **Integrations** > **Connectors** > **Add connector**. +In C1, navigate to **Integrations** > **Connectors** > **Add connector**. Search for **Baton** and click **Add**. @@ -216,16 +216,16 @@ Search for **Baton** and click **Add**. Choose how to set up the new Salesforce 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 -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. Click **Next**. @@ -253,9 +253,9 @@ metadata: name: baton-salesforce-secrets type: Opaque stringData: - # ConductorOne credentials - BATON_CLIENT_ID: - BATON_CLIENT_SECRET: + # C1 credentials + BATON_CLIENT_ID: + BATON_CLIENT_SECRET: # Salesforce credentials BATON_INSTANCE_URL: @@ -263,7 +263,7 @@ stringData: BATON_SALESFORCE_USERNAME: BATON_SECURITY_TOKEN: - # Optional: include if you want ConductorOne to provision access using this connector + # Optional: include if you want C1 to provision access using this connector BATON_PROVISIONING: true # Optional: include if you want to sync access to connected apps @@ -321,14 +321,14 @@ spec: -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. -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 Salesforce connector to. Salesforce 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 Salesforce connector to. Salesforce data should be found on the **Entitlements** and **Accounts** tabs. -**That's it!** Your Salesforce connector is now pulling access data into ConductorOne. +**That's it!** Your Salesforce connector is now pulling access data into C1. diff --git a/baton/tableau.mdx b/baton/tableau.mdx index 4666eb08..8373c824 100644 --- a/baton/tableau.mdx +++ b/baton/tableau.mdx @@ -1,8 +1,8 @@ --- title: Set up a Tableau connector -og:title: Set up a Tableau connector - ConductorOne docs -og:description: Integrate your Tableau 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 for Tableau. Integrate your Tableau instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a Tableau connector - C1 docs +og:description: Integrate your Tableau 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 for Tableau. Integrate your Tableau instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: Tableau --- @@ -10,13 +10,13 @@ sidebarTitle: Tableau | Resource | Sync | Provision | | ------------ | ---- | --------- | -| Accounts | | | -| Groups | | | -| Sites | | | -| Licenses | | | -| Projects | | | -| Workbooks | | | -| Views | | | +| Accounts | | | +| Groups | | | +| Sites | | | +| Licenses | | | +| Projects | | | +| Workbooks | | | +| Views | | | The Tableau connector supports [automatic account provisioning and deprovisioning](/product/admin/account-provisioning). @@ -50,7 +50,7 @@ Sign into Tableau Server or Tableau Cloud. In the menu bar at the top of the page, click your profile image or initials and select **My Account Settings** from the menu. -In the **Personal Access Tokens** area of the page, enter a name for your new token (such as "ConductorOne integration") and then click **Create**. +In the **Personal Access Tokens** area of the page, enter a name for your new token (such as "C1 integration") and then click **Create**. Carefully copy and save the newly generated token and its name. @@ -81,17 +81,17 @@ For a Tableau Cloud instance with the URL `https://10ay.online.tableau.com#/site 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 Tableau credentials generated by following the instructions above -**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.** -In ConductorOne, navigate to **Integrations** > **Connectors** and click **Add connector**. +In C1, navigate to **Integrations** > **Connectors** and click **Add connector**. Search for **Tableau** and click **Add**. @@ -99,16 +99,16 @@ Search for **Tableau** and click **Add**. Choose how to set up the new Tableau 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 -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. Click **Next**. @@ -132,16 +132,16 @@ 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 Tableau connector is now pulling access data into ConductorOne. +**That's it!** Your Tableau connector is now pulling access data into C1. **Follow these instructions to use the Tableau 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 -* [Official download center](https://dist.conductorone.com/ConductorOne/baton-tableau): For stable binaries (Windows/Linux/macOS) and container images. +* [Official download center](https://dist.conductorone.com/C1/baton-tableau): For stable binaries (Windows/Linux/macOS) and container images. * [GitHub repository](https://github.com/ConductorOne/baton-tableau): Access the source code, report issues, or contribute to the project. @@ -149,7 +149,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In ConductorOne, navigate to **Integrations** > **Connectors** > **Add connector**. +In C1, navigate to **Integrations** > **Connectors** > **Add connector**. Search for **Baton** and click **Add**. @@ -157,16 +157,16 @@ Search for **Baton** and click **Add**. Choose how to set up the new Tableau 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 -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. Click **Next**. @@ -194,9 +194,9 @@ metadata: name: baton-tableau-secrets type: Opaque stringData: - # ConductorOne credentials - BATON_CLIENT_ID: - BATON_CLIENT_SECRET: + # C1 credentials + BATON_CLIENT_ID: + BATON_CLIENT_SECRET: # Tableau credentials BATON_ACCESS_TOKEN_NAME: @@ -204,7 +204,7 @@ stringData: BATON_SERVER_PATH: BATON_SITE_ID: - # Optional: include if you want ConductorOne to provision access using this connector + # Optional: include if you want C1 to provision access using this connector BATON_PROVISIONING: true ``` @@ -247,14 +247,14 @@ spec: -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. -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 Tableau connector to. Tableau 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 Tableau connector to. Tableau data should be found on the **Entitlements** and **Accounts** tabs. -**That's it!** Your Tableau connector is now pulling access data into ConductorOne. +**That's it!** Your Tableau connector is now pulling access data into C1. diff --git a/baton/workday.mdx b/baton/workday.mdx index 0a42a1e6..afe4d316 100644 --- a/baton/workday.mdx +++ b/baton/workday.mdx @@ -1,14 +1,14 @@ --- title: Set up a Workday connector -og:title: Set up a Workday connector - ConductorOne docs -og:description: Integrate your Workday 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 Workday. Integrate your Workday instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a Workday connector - C1 docs +og:description: Integrate your Workday 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 Workday. Integrate your Workday instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: "Workday" --- ## Which Workday connector should I use? -ConductorOne offers two Workday connectors: Workday and Workday Accounts (WQL). How you want to work with Workday in ConductorOne will determine which one you should set up. +C1 offers two Workday connectors: Workday and Workday Accounts (WQL). How you want to work with Workday in C1 will determine which one you should set up. * **[Workday connector](/baton/workday)**: This connector is the best choice if you want to use Workday as a [directory](/product/admin/directory). You’ll also need it if you want to enable access requests for Workday role and group assignments. @@ -28,9 +28,9 @@ ConductorOne offers two Workday connectors: Workday and Workday Accounts (WQL). | Resource | Sync | Provision | | :--- | :--- | :--- | -| Accounts | | | -| Roles | | | -| Security groups | | | +| Accounts | | | +| Roles | | | +| Security groups | | | ## Gather Workday credentials @@ -41,9 +41,9 @@ To authenticate with Workday, you can use either a Report-as-a-service (RaaS) ** **Which authentication method should I use?** -The **RaaS custom report option** is the more popular option, and is often preferred by Workday Admins and HR teams, as it’s Workday’s preferred integration method. RaaS allows you fine-grained control over what data is sent to ConductorOne. Additionally, it allows you to transform the format of Workday attributes as needed before sending them to ConductorOne. +The **RaaS custom report option** is the more popular option, and is often preferred by Workday Admins and HR teams, as it’s Workday’s preferred integration method. RaaS allows you fine-grained control over what data is sent to C1. Additionally, it allows you to transform the format of Workday attributes as needed before sending them to C1. -The **API client option** pulls available data about Workday accounts, such as each account's manager and manager email, which can be used as [user attributes](/product/admin/attributes). The custom report method only pulls data that is explicitly named in the report into ConductorOne. +The **API client option** pulls available data about Workday accounts, such as each account's manager and manager email, which can be used as [user attributes](/product/admin/attributes). The custom report method only pulls data that is explicitly named in the report into C1. Follow the relevant set of instructions below to generate your credentials. @@ -110,7 +110,7 @@ Add the following fields to the custom report **in this order**: * Organization Type - The fields needed in custom reports can vary depending on how your Workday installation is configured. Contact ConductorOne support if you need help figuring out which fields to include. + The fields needed in custom reports can vary depending on how your Workday installation is configured. Contact C1 support if you need help figuring out which fields to include. 5. Create the custom report. @@ -148,7 +148,7 @@ In Workday, use the search bar to look up "Create Integration System User". -In the **Create Integration System User** modal, enter a **User Name**, such as "ConductorOne integration". +In the **Create Integration System User** modal, enter a **User Name**, such as "C1 integration". @@ -177,7 +177,7 @@ In the **Maintain Permissions for Security Group** modal, make sure the **Mainta In the **Source Security Group** field, navigate to **By Type** > **Integration System Security Group**. -Create a new security group. Give it a name, such as "ConductorOne integration security group". +Create a new security group. Give it a name, such as "C1 integration security group". On the new group's **Domain Security Policy Permissions** tab, leave the **Select All** box checked. @@ -259,7 +259,7 @@ Review the changes and if everything looks good, click the **Confirm** checkbox, In Workday, use the search bar to look up "Register API Client for Integrations". Make sure to select this name from the results, not the similarly named "Register API Client". -Give the new API client a name, such as "ConductorOne integration". +Give the new API client a name, such as "C1 integration". In the **Integration System User** field, select the ISU you created earlier. This is crucial for associating the API client with the correct permissions. @@ -300,18 +300,18 @@ Carefully copy and save the new refresh token. 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 Workday credentials generated by following the instructions above -**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.** -In ConductorOne, navigate to **Integrations** > **Connectors** and click **Add connector**. +In C1, navigate to **Integrations** > **Connectors** and click **Add connector**. Search for **Workday** and click **Add**. @@ -319,16 +319,16 @@ Search for **Workday** and click **Add**. Choose how to set up the new Workday 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 -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. Click **Next**. @@ -362,24 +362,24 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**That's it!** Your Workday connector is now pulling access data into ConductorOne. +**That's it!** Your Workday connector is now pulling access data into C1. **Follow these instructions to use the Workday 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 -* [Official download center](https://dist.conductorone.com/ConductorOne/baton-workday): For stable binaries (Windows/Linux/macOS) and container images. +* [Official download center](https://dist.conductorone.com/C1/baton-workday): For stable binaries (Windows/Linux/macOS) and container images. ### Step 1: Set up a new Workday connector -In ConductorOne, navigate to **Integrations** > **Connectors** > **Add connector**. +In C1, navigate to **Integrations** > **Connectors** > **Add connector**. Search for **Baton** and click **Add**. @@ -387,14 +387,14 @@ Search for **Baton** and click **Add**. Choose how to set up the new Workday 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 -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. Click **Next**. @@ -422,9 +422,9 @@ metadata: name: baton-workday-secrets type: Opaque stringData: - # ConductorOne credentials - BATON_CLIENT_ID: - BATON_CLIENT_SECRET: + # C1 credentials + BATON_CLIENT_ID: + BATON_CLIENT_SECRET: # Workday credentials if using an API client to authenticate BATON_WORKDAY_CLIENT_ID: @@ -480,13 +480,13 @@ spec: -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. -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 Workday connector to. Workday 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 Workday connector to. Workday data should be found on the **Entitlements** and **Accounts** tabs. -**That's it!** Your Workday connector is now pulling access data into ConductorOne. +**That's it!** Your Workday connector is now pulling access data into C1. ## Troubleshooting the Workday connector diff --git a/baton/zoom.mdx b/baton/zoom.mdx index a19fc85f..fb2c2da7 100644 --- a/baton/zoom.mdx +++ b/baton/zoom.mdx @@ -1,8 +1,8 @@ --- title: Set up a Zoom connector -og:title: Set up a Zoom connector - ConductorOne docs -og:description: Integrate your Zoom 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 for Zoom. Integrate your Zoom instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a Zoom connector - C1 docs +og:description: Integrate your Zoom 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 for Zoom. Integrate your Zoom instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: Zoom --- @@ -14,11 +14,11 @@ This connector works with Zoom on the Pro, Business, Business Plus, or Enterpris | Resource | Sync | Provision | | ------------ | ---- | --------- | -| Accounts | | | -| Groups | | | -| Roles | | | -| Contact groups | | | -| Invites | | | +| Accounts | | | +| Groups | | | +| Roles | | | +| Contact groups | | | +| Invites | | | The Zoom connector supports [automatic account provisioning](/product/admin/account-provisioning). @@ -45,7 +45,7 @@ Click **Develop** and select **Build App**. Locate the **Server-to-Server OAuth** option and click **Create**. -Give your app a name, such as "ConductorOne" and click **Create**. +Give your app a name, such as "C1" and click **Create**. A page for the newly created app opens. Copy and save the Account ID, Client ID, and Client secret shown on this page. @@ -76,7 +76,7 @@ On the **Scopes** page, click **+ Add Scopes**. Give the app the following set o - user:read:user:admin - user:read:list_users:admin - If you want to use ConductorOne to provision and deprovision Zoom permissions, add these scopes as well: + If you want to use C1 to provision and deprovision Zoom permissions, add these scopes as well: - role:write:member:admin - role:delete:member:admin @@ -101,18 +101,18 @@ On the **Activation** page, click **Activate your app**. 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 Zoom credentials generated by following the instructions above -**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.** -In ConductorOne, navigate to **Integrations** > **Connectors** and click **Add connector**. +In C1, navigate to **Integrations** > **Connectors** and click **Add connector**. Search for **Zoom** and click **Add**. @@ -120,16 +120,16 @@ Search for **Zoom** and click **Add**. Choose how to set up the new Zoom 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 -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. Click **Next**. @@ -144,7 +144,7 @@ Enter the account ID for the new app into the **Account ID** fields. Enter the Client ID and Client secret into the **Client ID** and **Client secret** fields. -Optionally, enable **Sync Inactive Users** to include deactivated Zoom users in the sync. When enabled, inactive users appear with a disabled status in ConductorOne. This is disabled by default. +Optionally, enable **Sync Inactive Users** to include deactivated Zoom users in the sync. When enabled, inactive users appear with a disabled status in C1. This is disabled by default. Click **Save**. @@ -153,13 +153,13 @@ 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 Zoom connector is now pulling access data into ConductorOne. +**That's it!** Your Zoom connector is now pulling access data into C1. **Follow these instructions to use the Zoom 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 @@ -169,7 +169,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In ConductorOne, navigate to **Integrations** > **Connectors** > **Add connector**. +In C1, navigate to **Integrations** > **Connectors** > **Add connector**. Search for **Baton** and click **Add**. @@ -177,16 +177,16 @@ Search for **Baton** and click **Add**. Choose how to set up the new Zoom 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 -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. Click **Next**. @@ -214,16 +214,16 @@ metadata: name: baton-zoom-secrets type: Opaque stringData: - # ConductorOne credentials - BATON_CLIENT_ID: - BATON_CLIENT_SECRET: + # C1 credentials + BATON_CLIENT_ID: + BATON_CLIENT_SECRET: # Zoom credentials BATON_ACCOUNT_ID: BATON_ZOOM_CLIENT_ID: BATON_ZOOM_CLIENT_SECRET: - # Optional: include if you want ConductorOne to provision access using this connector + # Optional: include if you want C1 to provision access using this connector BATON_PROVISIONING: true # Optional: sync deactivated Zoom users (disabled by default) @@ -269,14 +269,14 @@ spec: -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. -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 Zoom connector to. Zoom 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 Zoom connector to. Zoom data should be found on the **Entitlements** and **Accounts** tabs. -**That's it!** Your Zoom connector is now pulling access data into ConductorOne. +**That's it!** Your Zoom connector is now pulling access data into C1. From 7cb5153469c85fab380799233a0056cfff344ba3 Mon Sep 17 00:00:00 2001 From: Mindy Moreland Date: Tue, 7 Apr 2026 12:59:11 -0700 Subject: [PATCH 3/5] docs: restore ConductorOne in dist.conductorone.com URLs Co-Authored-By: Claude Sonnet 4.6 --- baton/claude-enterprise.mdx | 4 ++-- baton/google-workspace.mdx | 2 +- baton/salesforce.mdx | 2 +- baton/tableau.mdx | 2 +- baton/workday.mdx | 2 +- 5 files changed, 6 insertions(+), 6 deletions(-) diff --git a/baton/claude-enterprise.mdx b/baton/claude-enterprise.mdx index 73b6738d..dda3a187 100644 --- a/baton/claude-enterprise.mdx +++ b/baton/claude-enterprise.mdx @@ -164,7 +164,7 @@ To complete this task, you'll need: ### Resources - * [Official download center](https://dist.conductorone.com/C1/baton-claude-enterprise): For stable binaries (Windows/Linux/macOS) and container images. + * [Official download center](https://dist.conductorone.com/ConductorOne/baton-claude-enterprise): For stable binaries (Windows/Linux/macOS) and container images. * [GitHub repository](https://github.com/ConductorOne/baton-claude-enterprise): Access the source code, report issues, or contribute to the project. @@ -286,5 +286,5 @@ To complete this task, you'll need: --- -All versions of this connector are available at [dist.conductorone.com](https://dist.conductorone.com/C1/baton-claude-enterprise). +All versions of this connector are available at [dist.conductorone.com](https://dist.conductorone.com/ConductorOne/baton-claude-enterprise). diff --git a/baton/google-workspace.mdx b/baton/google-workspace.mdx index 0ece91c5..e6cbce77 100644 --- a/baton/google-workspace.mdx +++ b/baton/google-workspace.mdx @@ -336,7 +336,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an ### Resources -* [Official download center](https://dist.conductorone.com/C1/baton-google-workspace): For stable binaries (Windows/Linux/macOS) and container images. +* [Official download center](https://dist.conductorone.com/ConductorOne/baton-google-workspace): For stable binaries (Windows/Linux/macOS) and container images. * [GitHub repository](https://github.com/ConductorOne/baton-google-workspace): Access the source code, report issues, or contribute to the project. diff --git a/baton/salesforce.mdx b/baton/salesforce.mdx index 83641b1e..d855ece7 100644 --- a/baton/salesforce.mdx +++ b/baton/salesforce.mdx @@ -200,7 +200,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an ### Resources -* [Official download center](https://dist.conductorone.com/C1/baton-salesforce): For stable binaries (Windows/Linux/macOS) and container images. +* [Official download center](https://dist.conductorone.com/ConductorOne/baton-salesforce): For stable binaries (Windows/Linux/macOS) and container images. * [GitHub repository](https://github.com/ConductorOne/baton-salesforce): Access the source code, report issues, or contribute to the project. diff --git a/baton/tableau.mdx b/baton/tableau.mdx index 8373c824..bf382784 100644 --- a/baton/tableau.mdx +++ b/baton/tableau.mdx @@ -141,7 +141,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an ### Resources -* [Official download center](https://dist.conductorone.com/C1/baton-tableau): For stable binaries (Windows/Linux/macOS) and container images. +* [Official download center](https://dist.conductorone.com/ConductorOne/baton-tableau): For stable binaries (Windows/Linux/macOS) and container images. * [GitHub repository](https://github.com/ConductorOne/baton-tableau): Access the source code, report issues, or contribute to the project. diff --git a/baton/workday.mdx b/baton/workday.mdx index afe4d316..cf52f438 100644 --- a/baton/workday.mdx +++ b/baton/workday.mdx @@ -373,7 +373,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an ### Resources -* [Official download center](https://dist.conductorone.com/C1/baton-workday): For stable binaries (Windows/Linux/macOS) and container images. +* [Official download center](https://dist.conductorone.com/ConductorOne/baton-workday): For stable binaries (Windows/Linux/macOS) and container images. ### Step 1: Set up a new Workday connector From 4334ee979e3c2f932a09129f8cb32717f1d29124 Mon Sep 17 00:00:00 2001 From: Mindy Moreland Date: Tue, 7 Apr 2026 13:00:52 -0700 Subject: [PATCH 4/5] docs: remove re-introduced image from google-workspace Co-Authored-By: Claude Sonnet 4.6 --- baton/google-workspace.mdx | 4 ---- 1 file changed, 4 deletions(-) diff --git a/baton/google-workspace.mdx b/baton/google-workspace.mdx index e6cbce77..092239f0 100644 --- a/baton/google-workspace.mdx +++ b/baton/google-workspace.mdx @@ -87,10 +87,6 @@ Click **Enable**. **Optional.** If you want to use the group settings connector action, you must also search for, select, and enable the **Groups Settings API**. - - - - **Optional.** If you want to enable **Sync Enterprise Apps**, you must also search for, select, and enable the **Cloud Identity API**. From 1f1ade7b3799f5779030d7e8cfca6095c1cedd35 Mon Sep 17 00:00:00 2001 From: Mindy Moreland Date: Tue, 7 Apr 2026 13:11:22 -0700 Subject: [PATCH 5/5] docs: update Artifactory capabilities with provisioning support Co-Authored-By: Claude Sonnet 4.6 --- baton/capabilities.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/baton/capabilities.mdx b/baton/capabilities.mdx index eaeb0877..567bbef3 100644 --- a/baton/capabilities.mdx +++ b/baton/capabilities.mdx @@ -34,7 +34,7 @@ og:description: "A quick reference for how each connector can be set up and what | [Airflow](/baton/airflow) | | | | | [Amazon EKS](/baton/eks) | | | | | [ArgoCD](/baton/argo-cd) | | | | -| [Artifactory](/baton/artifactory) | | | | +| [Artifactory](/baton/artifactory) | | | | | [Asana](/baton/asana) | | | | | [Atlassian](/baton/atlassian) | | | | | [Auth0](/baton/auth0) | | | |