diff --git a/baton/1password.mdx b/baton/1password.mdx index 28961373..e221445a 100644 --- a/baton/1password.mdx +++ b/baton/1password.mdx @@ -1,17 +1,17 @@ --- title: "Set up 1Password connector" -description: "C1 provides identity governance and just-in-time provisioning for 1Password. Integrate your 1Password instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for 1Password. Integrate your 1Password instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." og:title: "Set up 1Password connector" -og:description: "C1 provides identity governance and just-in-time provisioning for 1Password. Integrate your 1Password instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for 1Password. Integrate your 1Password instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "1Password" --- **Why does this connector look different from most others?** -Unlike most of the software C1 integrates with, 1Password doesn’t expose APIs that can be used to connect the two systems. Additionally, 1Password data can only be gathered from unlocked vaults, which means that a user must unlock the vault and manually kick off the data collection process; a periodic automated data pull won’t work. +Unlike most of the software C1.ai integrates with, 1Password doesn’t expose APIs that can be used to connect the two systems. Additionally, 1Password data can only be gathered from unlocked vaults, which means that a user must unlock the vault and manually kick off the data collection process; a periodic automated data pull won’t work. -To work around these issues, C1’s [1Password Baton connector](https://github.com/conductorone/baton-1password) uses the [1Password CLI](https://developer.1password.com/docs/cli/) to interact with your vaults. Once the CLI is set up, `baton-1password` uses it to interact with your 1Password vaults. The connector will capture user and entitlement data in a file that you upload to C1. +To work around these issues, C1.ai’s [1Password Baton connector](https://github.com/conductorone/baton-1password) uses the [1Password CLI](https://developer.1password.com/docs/cli/) to interact with your vaults. Once the CLI is set up, `baton-1password` uses it to interact with your 1Password vaults. The connector will capture user and entitlement data in a file that you upload to C1.ai. ## Capabilities @@ -30,14 +30,14 @@ Note that if you’re using a service account to run the connector, you can only **To complete this task, you’ll need:** -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - [1Password 8](https://1password.com/downloads/mac/) on a Families, Teams, Business, or Enterprise plan - A 1Password vault -**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 C1.ai.** *Cloud-hosted connector not currently available.* @@ -90,11 +90,11 @@ Note that if you’re using a service account to run the connector, you can only -### Step 3: Configure the 1Password connector in C1 +### Step 3: Configure the 1Password connector in C1.ai - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -132,14 +132,14 @@ Note that if you’re using a service account to run the connector, you can only Run `baton-1password --help` to see the list of flags to be used when passing your credentials to the connector. - The connector syncs current data, uploads it to C1, and prints a `Task complete!` message when finished. + The connector syncs current data, uploads it to C1.ai, and prints a `Task complete!` message when finished. - 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 Baton connector to. The data should be found on the **Resources** and **Accounts** tabs, as appropriate. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Baton connector to. The data should be found on the **Resources** and **Accounts** tabs, as appropriate. -**That’s it!** Your 1Password connector is now pulling access data into C1 +**That’s it!** Your 1Password connector is now pulling access data into C1.ai diff --git a/baton/_release-notes.mdx b/baton/_release-notes.mdx index ed377fd6..bb8dd128 100644 --- a/baton/_release-notes.mdx +++ b/baton/_release-notes.mdx @@ -1,7 +1,7 @@ --- title: "Connector release notes" sidebarTitle: "Release notes" -description: "Here you'll find the latest on new connectors, connector updates, and other connector news from C1." +description: "Here you'll find the latest on new connectors, connector updates, and other connector news from C1.ai." --- {/* Editor Refresh: 2026-09-11 */} @@ -58,7 +58,7 @@ The [Databricks](/baton/databricks) connector's personal access token and userna * The [Okta](/baton/okta) connector adds `update_profile` and `update_user` connector actions. -* The [Salesforce Tableau](/baton/tableau) connector now tracks license tiers by site role and purchased/consumed seat counts for use with C1 License Management. +* The [Salesforce Tableau](/baton/tableau) connector now tracks license tiers by site role and purchased/consumed seat counts for use with C1.ai License Management. ### File connector updates @@ -321,7 +321,7 @@ The [Databricks](/baton/databricks) connector's personal access token and userna * The [Claude Enterprise](/baton/claude-enterprise) connector now supports a **Compliance API mode** (recommended) that syncs all users and groups — including console-invited identities, not just SCIM-provisioned ones — and streams usage events from the activity feed. Configure a Compliance Access Key alongside optional SCIM credentials to enable this mode. -* The [Salesforce](/baton/salesforce) connector now syncs **Agents** (Agentforce agents and Einstein Bots) as an opt-in resource type. Enable the Agent resource type in C1 to include them in syncs. +* The [Salesforce](/baton/salesforce) connector now syncs **Agents** (Agentforce agents and Einstein Bots) as an opt-in resource type. Enable the Agent resource type in C1.ai to include them in syncs. * The [Workday](/baton/workday) connector now offers a new **Custom Report with API Client** authentication option, combining RaaS custom reports with OAuth for environments that require OAuth without an Integration System User. @@ -560,7 +560,7 @@ The [Databricks](/baton/databricks) connector's personal access token and userna * The [Coupa](/baton/coupa) connector now supports syncing and provisioning for Account Groups. This resource type is opt-in. -* The [Dayforce](/baton/dayforce) connector now supports account provisioning (hiring new employees) and role provisioning (granting and revoking security role assignments on existing employees). Account deprovisioning is not supported — C1 removes access by revoking role grants rather than deleting employee records. +* The [Dayforce](/baton/dayforce) connector now supports account provisioning (hiring new employees) and role provisioning (granting and revoking security role assignments on existing employees). Account deprovisioning is not supported — C1.ai removes access by revoking role grants rather than deleting employee records. * The [Microsoft Entra](/baton/microsoft-entra) connector now includes an option to skip enterprise applications with no app role assignments. Enabling **Skip enterprise applications without assignments** can substantially reduce sync output in tenants with many auto-registered service principals. @@ -676,7 +676,7 @@ The [Databricks](/baton/databricks) connector's personal access token and userna * The [Slack Enterprise Grid](/baton/slack-enterprise) connector now supports provisioning for user groups. -* The [Microsoft Entra ID](/baton/microsoft-entra) connector now supports a `create_group` connector action that lets you create new groups in Microsoft Entra ID directly from C1. +* The [Microsoft Entra ID](/baton/microsoft-entra) connector now supports a `create_group` connector action that lets you create new groups in Microsoft Entra ID directly from C1.ai. * The [Netsuite](/baton/netsuite) connector now supports syncing custom employee fields. We've added a new configuration field to support this capability. @@ -713,7 +713,7 @@ The [Databricks](/baton/databricks) connector's personal access token and userna - The [Google Workspace](/baton/google-workspace) connector has two new connector actions: **Modify group settings** lets you update group options such as allowing external members, enabling web posting, controlling who can post, and adjusting the message moderation level. **Update user manager** lets you change a user's manager relationship so that reporting, directory entries, and manager-based workflows reflect the new manager. -- The [Active Directory](/baton/active-directory) connector now supports syncing custom user attributes. Use the `custom-user-attributes` configuration option to specify additional LDAP attribute names to include in user profiles in C1, where they can be used for account correlation. +- The [Active Directory](/baton/active-directory) connector now supports syncing custom user attributes. Use the `custom-user-attributes` configuration option to specify additional LDAP attribute names to include in user profiles in C1.ai, where they can be used for account correlation. - The [LDAP](/baton/ldap) connector now supports POSIX account provisioning with automatic UID number assignment. When creating a new POSIX account, the connector can look up the highest `uidNumber` currently in use and assign the next available value automatically. @@ -815,7 +815,7 @@ Connectors running in service mode can now expose HTTP health check endpoints fo ### Connector capability updates - The [Docusign](/baton/docusign) connector now syncs signing groups and supports provisioning for groups, signing groups, and permission profiles. The connector also now supports account deprovisioning. -- When the [Workday](/baton/workday) connector is configured using a custom report, you can now specify additional fields from Workday user data to be included in the user profiles in C1. We've added a new configuration field to support this capability. +- When the [Workday](/baton/workday) connector is configured using a custom report, you can now specify additional fields from Workday user data to be included in the user profiles in C1.ai. We've added a new configuration field to support this capability. - The [Microsoft Entra ID](/baton/microsoft-entra) connector can now be configured to support provisioning users as members of exchange groups. See the connector's docs for details on additional required configuration steps of you want to use this capability. @@ -831,7 +831,7 @@ Connectors running in service mode can now expose HTTP health check endpoints fo ### Connector capability updates - You can now configure the [Microsoft Azure DevOps](/baton/azure-devops) connector to perform "incremental syncs", which means reading audit logs and capturing updates between full syncs. We've added a new configuration field to support this capability. -- When setting up the [ServiceNow](/baton/servicenow) connector, you can now specify a list of allowed email domains. The email address associated with an account must be associated with one of these allowed domains in order to be synced to C1. We've added a new configuration field to support this capability. +- When setting up the [ServiceNow](/baton/servicenow) connector, you can now specify a list of allowed email domains. The email address associated with an account must be associated with one of these allowed domains in order to be synced to C1.ai. We've added a new configuration field to support this capability. @@ -966,7 +966,7 @@ Connectors running in service mode can now expose HTTP health check endpoints fo ### Connector monitoring -- When a significant drop in resources is detected during a connector sync, C1 does not immediately apply the change as a precaution against unintentionally removing access. Click **Confirm changes** in the banner on the application's page to let C1 know that the change is expected and that it's safe to proceed. +- When a significant drop in resources is detected during a connector sync, C1.ai does not immediately apply the change as a precaution against unintentionally removing access. Click **Confirm changes** in the banner on the application's page to let C1.ai know that the change is expected and that it's safe to proceed. ### Connector capability updates - The [Oracle Identity Cloud Service](/baton/oracle-idcs) connector can be used to access data from and provision access to Oracle apps including **Work and Asset Cloud Service (Oracle WACS)** and **Customer Cloud Service (Oracle CCS)**. @@ -1163,7 +1163,7 @@ We now automatically pause a connector's sync cycle and alert you if significant ### Connector capability updates -- You can now use a GitHub app to configure the [GitHub Enterprise](/baton/github-enterprise) connector. When using this config method, you must set up a separate app and connector for each GitHub organization you want to integrate with C1. +- You can now use a GitHub app to configure the [GitHub Enterprise](/baton/github-enterprise) connector. When using this config method, you must set up a separate app and connector for each GitHub organization you want to integrate with C1.ai. - The [Atlassian](/baton/atlassian) connector now supports provisioning workplace roles. - The [AWS](/baton/aws) connector now supports org-level access and shows grant sources for permission sets. @@ -1266,7 +1266,7 @@ We now automatically pause a connector's sync cycle and alert you if significant ### Connector capability updates - The [Workday Account](/baton/workday-wql) connector now syncs user-based security groups as a separate resource type from other security groups. The connector also now supports provisioning for user-based security groups. New configuration fields on the connector have been added to support these capabilities. -- You can now use a GitHub app to configure the [GitHub](/baton/github) connector. When using this config method, you must set up a separate app and connector for each GitHub organization you want to integrate with C1. +- You can now use a GitHub app to configure the [GitHub](/baton/github) connector. When using this config method, you must set up a separate app and connector for each GitHub organization you want to integrate with C1.ai. - The [ServiceNow](/baton/servicenow) connector now supports account, role, and group provisioning. ### Backend fixes and updates @@ -1307,7 +1307,7 @@ We now automatically pause a connector's sync cycle and alert you if significant - [Zendesk v2](/baton/zendesk) - Adds support for syncing roles and provisioning roles, orgs, and groups. Learn more about [connector versions and migration](/baton/migration). ### Connector capability updates -- You can now specify which [user attributes](/product/admin/attributes) a connector syncs to C1. Go to [Select which attributes a connector syncs](/baton/configure/) to get started. +- You can now specify which [user attributes](/product/admin/attributes) a connector syncs to C1.ai. Go to [Select which attributes a connector syncs](/baton/configure/) to get started. - A new configuration field on the [Snyk](/baton/snyk) connector adds support for users who use regional hostnames other than `api.snyk.io`. - We've added a configuration field to the [Okta AWS Federation](/baton/okta-aws-federation) connector that opts into the conversion of user assignments to direct assignments. diff --git a/baton/active-directory.mdx b/baton/active-directory.mdx index f16f5e38..dd9a7afc 100644 --- a/baton/active-directory.mdx +++ b/baton/active-directory.mdx @@ -1,8 +1,8 @@ --- title: "Set up an Active Directory connector" og:title: "Set up an Active Directory connector" -description: "C1 provides identity governance and just-in-time provisioning for Active Directory. Integrate your on-prem Active Directory domains 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 Active Directory. Integrate your on-prem Active Directory domains with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for Active Directory. Integrate your on-prem Active Directory domains with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Active Directory. Integrate your on-prem Active Directory domains with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "Connector setup" --- @@ -18,7 +18,7 @@ The Active Directory connector is self-hosted and runs on a **Windows Server** j | Groups | | | | Group Managed Service Accounts (gMSAs) | | | -The Active Directory connector supports [automatic account provisioning and deprovisioning](/product/admin/account-provisioning). When a new account is created by C1, the account's password is sent to a [vault](/product/admin/vaults). +The Active Directory connector supports [automatic account provisioning and deprovisioning](/product/admin/account-provisioning). When a new account is created by C1.ai, the account's password is sent to a [vault](/product/admin/vaults). **Highlights:** @@ -35,7 +35,7 @@ User profiles include UAC-derived state booleans, FILETIME timestamps, and confi ### 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 C1.ai 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. **Global actions** (connector-level): @@ -68,7 +68,7 @@ You can define additional actions backed by PowerShell scripts in the config fil ### Resources -- [C1 download center](https://dist.conductorone.com/ConductorOne/baton-active-directory): For stable release binaries. +- [C1.ai download center](https://dist.conductorone.com/ConductorOne/baton-active-directory): For stable release binaries. ## Gather Active Directory credentials @@ -190,13 +190,13 @@ Your service account is now ready. Continue to the connector configuration. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - An Active Directory service account with the appropriate permissions (see above) The Active Directory connector is self-hosted — it runs on a Windows Server in your environment with direct network access to your domain controllers. -Once installed and configured, the connector runs as a Windows service. The service maintains contact with C1, syncs and uploads data at regular intervals, and passes that data to the C1 UI for access reviews and access requests. +Once installed and configured, the connector runs as a Windows service. The service maintains contact with C1.ai, syncs and uploads data at regular intervals, and passes that data to the C1.ai UI for access reviews and access requests. ### Requirements @@ -209,13 +209,13 @@ Once installed and configured, the connector runs as a Windows service. The serv **Network:** -- Outbound TCP/443 to your C1 tenant +- Outbound TCP/443 to your C1.ai tenant - Outbound LDAP (TCP/UDP 389), LDAPS (TCP 636), and Kerberos (TCP/UDP 88) to each domain controller the connector talks to. Global Catalog adds TCP 3268 / 3269. For the full multi-domain port list, see [Multi-domain and cross-forest sync](#multi-domain-and-cross-forest-sync). **Identity:** - An Active Directory service account with appropriate permissions (see [Gather Active Directory credentials](#gather-active-directory-credentials) above) -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai ### File locations @@ -227,11 +227,11 @@ Default file locations (`%PROGRAMDATA%` is typically `C:\ProgramData`): The service account must have **Modify** access to `%PROGRAMDATA%\ConductorOne` so the connector can write to the log file. If the connector can't write to this directory, the service will fail to start. -### Step 1: Set up a new Active Directory connector in C1 +### Step 1: Set up a new Active Directory connector in C1.ai - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -273,7 +273,7 @@ The service account must have **Modify** access to `%PROGRAMDATA%\ConductorOne` - Download the latest Windows MSI from the [C1 download center](https://dist.conductorone.com/ConductorOne/baton-active-directory). + Download the latest Windows MSI from the [C1.ai download center](https://dist.conductorone.com/ConductorOne/baton-active-directory). **Security prompts during download and install.** The Windows MSI and `.exe` are not yet code-signed, so Microsoft Defender SmartScreen and some antivirus products may warn that the publisher is unknown or quarantine the download. This is expected for unsigned binaries — it is not an indication of tampering. To proceed safely: @@ -322,7 +322,7 @@ The service account must have **Modify** access to `%PROGRAMDATA%\ConductorOne` The setup command checks for a config file, offers to copy the binary to Program Files, optionally configures a service account, and registers the Windows service with auto-start and recovery. - **First-run behavior:** the [GUI Configuration Editor](#gui-configuration-editor) launches automatically **only on the first run, when no config file exists yet**. Fill in your domain, base DN, and C1 credentials, click **Save**, and close the editor — `setup` resumes in `cmd.exe` and finishes registering the service. On subsequent runs the editor does **not** reappear; `setup` reuses the existing config. + **First-run behavior:** the [GUI Configuration Editor](#gui-configuration-editor) launches automatically **only on the first run, when no config file exists yet**. Fill in your domain, base DN, and C1.ai credentials, click **Save**, and close the editor — `setup` resumes in `cmd.exe` and finishes registering the service. On subsequent runs the editor does **not** reappear; `setup` reuses the existing config. To review or change an existing config, either run `baton-active-directory.exe config-editor` directly, or run `baton-active-directory.exe setup --reconfigure` to open the editor and then re-register the service in one step. @@ -384,17 +384,17 @@ Secrets encrypted with DPAPI use **machine scope**, so a gMSA on the same host c - The connector syncs current data, uploads it to C1, and prints a **Task complete!** message when finished. + The connector syncs current data, uploads it to C1.ai, and prints a **Task complete!** message when finished. - 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 Active Directory connector to. Active Directory data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Active Directory connector to. Active Directory data should be found on the **Entitlements** and **Accounts** tabs. ### Validate the connector is working -A **Connected** status in C1 means the connector has registered and is sending heartbeats — it does **not** by itself confirm that the connector can reach a domain controller, bind, and sync. Use these checks to confirm it is actually functioning: +A **Connected** status in C1.ai means the connector has registered and is sending heartbeats — it does **not** by itself confirm that the connector can reach a domain controller, bind, and sync. Use these checks to confirm it is actually functioning: @@ -416,11 +416,11 @@ A **Connected** status in C1 means the connector has registered and is sending h - **Confirm data in C1.** In C1 → **Apps** → your AD app, the **Accounts** and **Entitlements** tabs should populate after the first successful sync. Counts that match your directory confirm an end-to-end working connector. + **Confirm data in C1.ai.** In C1.ai → **Apps** → your AD app, the **Accounts** and **Entitlements** tabs should populate after the first successful sync. Counts that match your directory confirm an end-to-end working connector. -**Done.** Your Active Directory connector is now pulling access data into C1. +**Done.** Your Active Directory connector is now pulling access data into C1.ai. ## Reference @@ -488,8 +488,8 @@ bind-password: "secret" | `only-ous` | list of DNs | — | OUs to include. Mutually exclusive with `skip-ous`. | | `custom-user-attributes` | list of strings | — | Extra LDAP attributes to include in the user profile (for example, `githubUserName`) | | `sync-extension-attributes` | bool | `false` | Sync `extensionAttribute1`–`extensionAttribute15` on every user profile. Equivalent to listing all 15 names in `custom-user-attributes`. | -| `use-display-name` | bool | `false` | Use the LDAP `displayName` attribute as the C1 resource label instead of `cn`. Falls back to `cn` when `displayName` is empty. Applies to user and gMSA resources. | -| `locked-account-is-disabled` | bool | `true` | Map a locked-out account to `STATUS_DISABLED` in C1. Set to `false` to keep locked accounts `STATUS_ENABLED` and report lockout solely via the `account_locked` profile field. See [Incomplete-read attributes](#incomplete-read-attributes). | +| `use-display-name` | bool | `false` | Use the LDAP `displayName` attribute as the C1.ai resource label instead of `cn`. Falls back to `cn` when `displayName` is empty. Applies to user and gMSA resources. | +| `locked-account-is-disabled` | bool | `true` | Map a locked-out account to `STATUS_DISABLED` in C1.ai. Set to `false` to keep locked accounts `STATUS_ENABLED` and report lockout solely via the `account_locked` profile field. See [Incomplete-read attributes](#incomplete-read-attributes). | **gMSA:** @@ -506,12 +506,12 @@ bind-password: "secret" | `provisioning` | bool | `false` | Enable Grant/Revoke and account provisioning. Required for any write operation. | | `powershell-actions` | map | — | Custom PowerShell-backed actions. See [Custom PowerShell actions](#custom-powershell-actions). | -**C1 credentials:** +**C1.ai credentials:** | Field | Type | Default | Description | |---|---|---|---| -| `client-id` | string | *(required)* | C1 client ID. On Windows, can be stored as `dpapi:…`. | -| `client-secret` | string (secret) | *(required)* | C1 client secret. On Windows, can be stored as `dpapi:…`. | +| `client-id` | string | *(required)* | C1.ai client ID. On Windows, can be stored as `dpapi:…`. | +| `client-secret` | string (secret) | *(required)* | C1.ai client secret. On Windows, can be stored as `dpapi:…`. | **Multi-domain:** @@ -682,11 +682,11 @@ password-config: min-count: 1 ``` -Like `additional-domains`, this setting is YAML-only — it cannot be set via CLI flags, environment variables, or the C1 connector settings UI. It can also be edited in the [GUI Configuration Editor](#gui-configuration-editor) (Advanced tab). +Like `additional-domains`, this setting is YAML-only — it cannot be set via CLI flags, environment variables, or the C1.ai connector settings UI. It can also be edited in the [GUI Configuration Editor](#gui-configuration-editor) (Advanced tab). Behavior: -- When present and C1 requests a random password, `password-config` replaces the requested password parameters. When absent, behavior is unchanged. "No password" and admin-supplied (encrypted) password flows are never altered. +- When present and C1.ai requests a random password, `password-config` replaces the requested password parameters. When absent, behavior is unchanged. "No password" and admin-supplied (encrypted) password flows are never altered. - Constraints are *minimums* — the remainder of the password is drawn from the full character set (upper/lower/digits/symbols). Making the min-counts sum to `length` leaves no remainder, so your char-sets become the entire alphabet; see the character-class rule below before doing that. - **Character-class guarantee.** Active Directory's default policy requires three of upper, lower, digit and non-alphanumeric. Without constraints the generator already guarantees one of each; with constraints it emits your minimums and fills the rest at random, which guarantees nothing. So when your char-sets cover fewer than three classes, the connector adds a `min-count: 1` constraint for missing classes until three are covered — your own minimums are never changed, and a class you already cover is never added. A symbol is never added: three classes are always reached from upper, lower and digit first, so a deliberately symbol-free policy stays symbol-free. A generated password therefore always satisfies the policy, rather than satisfying it most of the time and leaving an orphaned account object behind when it does not. - **A char-set only guarantees a class if it contains nothing else.** The connector draws each `min-count` character at random from your set, so `char-set: "ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789"` with `min-count: 10` does *not* guarantee a digit — it produces one only by chance, and emits none about 69% of the time. Only a set confined to a single class makes its `min-count` a guarantee. Write one constraint per class rather than one wide set. @@ -736,10 +736,10 @@ custom-user-attributes: - pwdLastSet ``` -Once synced, the specified attributes appear as profile fields on the user in C1 and can be configured as additional usernames for account correlation. +Once synced, the specified attributes appear as profile fields on the user in C1.ai and can be configured as additional usernames for account correlation. -**Casing:** LDAP attribute names are case-insensitive (RFC 4512 §2.5), so configuring `mail`, `Mail`, or `MAIL` all reference the same AD attribute. The connector matches the operator's configured casing case-insensitively against the entry's returned attribute names. The profile-map key preserves the operator's configured casing — so a config of `Mail` produces `profile["Mail"]`, not `profile["mail"]` — predictable for downstream consumers reading the C1 profile JSON. +**Casing:** LDAP attribute names are case-insensitive (RFC 4512 §2.5), so configuring `mail`, `Mail`, or `MAIL` all reference the same AD attribute. The connector matches the operator's configured casing case-insensitively against the entry's returned attribute names. The profile-map key preserves the operator's configured casing — so a config of `Mail` produces `profile["Mail"]`, not `profile["mail"]` — predictable for downstream consumers reading the C1.ai profile JSON. For the common case of surfacing the full Exchange-schema extension attribute range, use the convenience flag `sync-extension-attributes: true` instead of listing all 15 names manually: @@ -750,7 +750,7 @@ sync-extension-attributes: true ### Resource label (`cn` vs `displayName`) -By default, the connector uses the LDAP `cn` attribute as the C1 resource label. AD often stores `cn` in `Last, First` order while `displayName` carries the operator-curated `First Last` form. To use `displayName` as the C1 Identity Name, set: +By default, the connector uses the LDAP `cn` attribute as the C1.ai resource label. AD often stores `cn` in `Last, First` order while `displayName` carries the operator-curated `First Last` form. To use `displayName` as the C1.ai Identity Name, set: ```yaml use-display-name: true @@ -775,9 +775,9 @@ powershell-actions: is_required: true ``` -Each custom action appears alongside the built-in connector actions and can be used in C1 automations. Argument types can be `string`, `int`, or `bool`. +Each custom action appears alongside the built-in connector actions and can be used in C1.ai automations. Argument types can be `string`, `int`, or `bool`. -Arguments are delivered to the script's `param()` block with their declared types — a `bool` binds a real boolean (works for `[bool]` and `[switch]`), an `int` binds a number, and a `string` binds a literal value. String values are passed as data (not spliced into the command line), so content such as quotes, `$(...)`, or `;` is inert and cannot inject PowerShell. Write your script with a `param()` block matching the declared argument names, and signal the outcome with an explicit exit code (`exit 0` for success, a non-zero `exit N` for failure) — the connector reports that exit code back to C1. +Arguments are delivered to the script's `param()` block with their declared types — a `bool` binds a real boolean (works for `[bool]` and `[switch]`), an `int` binds a number, and a `string` binds a literal value. String values are passed as data (not spliced into the command line), so content such as quotes, `$(...)`, or `;` is inert and cannot inject PowerShell. Write your script with a `param()` block matching the declared argument names, and signal the outcome with an explicit exit code (`exit 0` for success, a non-zero `exit N` for failure) — the connector reports that exit code back to C1.ai. ### User profile attributes @@ -815,7 +815,7 @@ Three kinds of name can appear there: The object is still emitted rather than dropped, so the account remains visible instead of silently disappearing — but values derived from those attributes should be treated as partial. This matters most for `memberOf`: group memberships, and any access derived from them, may be understated, so an access review reading such a record could conclude a user has less access than they actually do. -By default, locked-out accounts also map to `STATUS_DISABLED` in C1 (backwards-compatible). To keep locked accounts as `STATUS_ENABLED` and report lockout state solely via the `account_locked` field above, set: +By default, locked-out accounts also map to `STATUS_DISABLED` in C1.ai (backwards-compatible). To keep locked accounts as `STATUS_ENABLED` and report lockout state solely via the `account_locked` field above, set: ```yaml locked-account-is-disabled: false @@ -859,7 +859,7 @@ The connector parses every well-known AD time attribute to an RFC3339 (UTC) time #### Push attributes -The `update_profile` resource action accepts 23 named string fields, each named after the **canonical AD attribute** it targets. The platform's push-rule UI shows the AD attribute name in its "App attribute" column, so the value you map to in C1 corresponds directly to the attribute AD will receive. Attributes outside this list (including `extensionAttribute1` through `extensionAttribute15`) must be set via the `custom_attributes` map field on `update_profile`, or via the `update_user_attrs` global action. +The `update_profile` resource action accepts 23 named string fields, each named after the **canonical AD attribute** it targets. The platform's push-rule UI shows the AD attribute name in its "App attribute" column, so the value you map to in C1.ai corresponds directly to the attribute AD will receive. Attributes outside this list (including `extensionAttribute1` through `extensionAttribute15`) must be set via the `custom_attributes` map field on `update_profile`, or via the `update_user_attrs` global action. | AD attribute | Category | Notes | |---|---|---| @@ -888,7 +888,7 @@ The `update_profile` resource action accepts 23 named string fields, each named | `physicalDeliveryOfficeName` | Address | Office location | -Pre-v0.5.5 push rules used snake_case field names (`first_name`, `display_name`, `email`, etc.). Those rules continue to work — the connector resolves both the canonical AD names listed above and the legacy snake_case aliases to the same target attribute. New push rules should prefer the AD-canonical names so the C1 UI's "App attribute" column matches what AD actually expects. +Pre-v0.5.5 push rules used snake_case field names (`first_name`, `display_name`, `email`, etc.). Those rules continue to work — the connector resolves both the canonical AD names listed above and the legacy snake_case aliases to the same target attribute. New push rules should prefer the AD-canonical names so the C1.ai UI's "App attribute" column matches what AD actually expects. @@ -905,7 +905,7 @@ When the connector logs `winldap_ldap_search: search returned 0 entries` at INFO 2. **The DN doesn't exist as written** — the connector logs the exact `base` string sent to AD. Copy it verbatim into `dsquery * "" -limit 1` on the DC to confirm. -3. **The bound DC isn't authoritative for the search base** — when you narrow `user-search-dn` or `group-search-dn` into a delegated OU, a child-domain OU, or a Read-Only DC subtree, the bound DC may answer with `LDAP_REFERRAL` (result code 10) or `LDAP_PARTIAL_RESULTS` (9) instead of entries. The connector surfaces this case explicitly: alongside the zero-entries INFO, look for a WARN log of the form `ldap_ext_search: non-success result code_name=LDAP_REFERRAL r1=10`. The same condition surfaces in the C1 sync-failure panel as `LDAP error: LDAP_REFERRAL`, so it's identifiable from the platform side too without needing log access. +3. **The bound DC isn't authoritative for the search base** — when you narrow `user-search-dn` or `group-search-dn` into a delegated OU, a child-domain OU, or a Read-Only DC subtree, the bound DC may answer with `LDAP_REFERRAL` (result code 10) or `LDAP_PARTIAL_RESULTS` (9) instead of entries. The connector surfaces this case explicitly: alongside the zero-entries INFO, look for a WARN log of the form `ldap_ext_search: non-success result code_name=LDAP_REFERRAL r1=10`. The same condition surfaces in the C1.ai sync-failure panel as `LDAP error: LDAP_REFERRAL`, so it's identifiable from the platform side too without needing log access. **The connector does not chase referrals.** WinLDAP's referral-chasing option (`LDAP_OPT_REFERRALS`) is explicitly disabled — it has to be, to work around an [AD pagination bug](https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/ldap-paged-queries-subordinate-referrals-not-chased) where chased subordinate referrals confuse the paging control and corrupt the page cookie. Re-enabling chasing would also introduce an authentication-security risk (chased referrals can authenticate against arbitrary servers). The remediation is to **adjust the search configuration so the bound DC is authoritative for the subtree**: @@ -935,7 +935,7 @@ The connector performs both directory **reads** (sync) and **writes** (provision The selection is logged with `writable=true`/`writable=false`. The practical upshot: a **write-capable** connection whose site has only RODCs trades read locality for working provisioning (reads move to the covering writable DC); a **read-only** connection always keeps reads on the in-site DC. -**Symptom this prevents.** Before this behavior, a site containing an RODC could cause the connector to bind that RODC: sync succeeded (reads work against an RODC) but every write action later failed with `LDAP error: LDAP_REFERRAL` in the C1 action-failure panel, and `ldap_modify: ret code_name=LDAP_REFERRAL r1=10` in the connector log. +**Symptom this prevents.** Before this behavior, a site containing an RODC could cause the connector to bind that RODC: sync succeeded (reads work against an RODC) but every write action later failed with `LDAP error: LDAP_REFERRAL` in the C1.ai action-failure panel, and `ldap_modify: ret code_name=LDAP_REFERRAL r1=10` in the connector log. **If no writable DC is reachable at all** (a genuine outage, or a network segment that can only reach RODCs), native discovery fails and the connector falls back to DNS SRV, which cannot distinguish an RODC from a writable DC. The connector logs a prominent warning in this case (`native writable-DC discovery failed; falling back to DNS SRV which cannot guarantee a writable DC …`). If an RODC is then bound, sync works but provisioning will fail with `LDAP_REFERRAL` until a writable DC is reachable in or covering the configured site. @@ -993,7 +993,7 @@ It is idempotent — already-encrypted values are skipped — so it is safe to r DPAPI here is **machine-scoped** (`CRYPTPROTECT_LOCAL_MACHINE`). Any process on the same host can decrypt these values, which is what lets the service — including one running as a gMSA — read them without a per-user key. It protects the secrets if the file leaves the machine (backups, file shares, support bundles), **not** from other accounts on the machine. The file's permissions are what restrict local access: `setup` applies those automatically, and `encrypt-config` warns if the file is readable by ordinary users. -If a host's `config.yaml` has been readable by `BUILTIN\Users` — check with `icacls "C:\ProgramData\ConductorOne\baton-active-directory\config.yaml"` — then every local account on that server could read *and* decrypt its secrets. Encrypting or locking the file now does not undo that: **rotate the C1 client credentials and the AD bind password**, then store the new values with `setup` or `encrypt-config`. +If a host's `config.yaml` has been readable by `BUILTIN\Users` — check with `icacls "C:\ProgramData\ConductorOne\baton-active-directory\config.yaml"` — then every local account on that server could read *and* decrypt its secrets. Encrypting or locking the file now does not undo that: **rotate the C1.ai client credentials and the AD bind password**, then store the new values with `setup` or `encrypt-config`. Machine scope also means **an encrypted config is not portable**. Do not copy a config that has been through `setup` or `encrypt-config` to another server, or capture it into a golden image or a config repository that redeploys it — the connector cannot decrypt it there and will fail at startup. Distribute the plaintext config and let each host encrypt its own copy. @@ -1035,4 +1035,4 @@ The editor exposes every YAML config field across a tabbed layout (Connection, A ## What's next? -Once your Active Directory connector is synced, you can use C1 to run user access reviews on AD group memberships, enable just-in-time access requests for AD groups and gMSAs, and automate provisioning workflows using connector actions. +Once your Active Directory connector is synced, you can use C1.ai to run user access reviews on AD group memberships, enable just-in-time access requests for AD groups and gMSAs, and automate provisioning workflows using connector actions. diff --git a/baton/activecampaign.mdx b/baton/activecampaign.mdx index 0991c5ab..41daf59d 100644 --- a/baton/activecampaign.mdx +++ b/baton/activecampaign.mdx @@ -1,13 +1,13 @@ --- title: "Set up an ActiveCampaign connector" og:title: "Set up an ActiveCampaign connector" -description: "C1 provides identity governance for ActiveCampaign. Integrate your ActiveCampaign account with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for ActiveCampaign. Integrate your ActiveCampaign account with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for ActiveCampaign. Integrate your ActiveCampaign account with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for ActiveCampaign. Integrate your ActiveCampaign account with C1.ai for unified visibility and governance over user access." sidebarTitle: "ActiveCampaign" --- -C1 provides identity governance for ActiveCampaign. Integrate your -ActiveCampaign account with C1 for unified visibility and governance over your +C1.ai provides identity governance for ActiveCampaign. Integrate your +ActiveCampaign account with C1.ai for unified visibility and governance over your admin users and the permission groups they belong to. ## Capabilities @@ -62,11 +62,11 @@ API access URL. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -113,7 +113,7 @@ API access URL. - **Done.** Your ActiveCampaign connector is now pulling access data into C1. + **Done.** Your ActiveCampaign connector is now pulling access data into C1.ai. @@ -139,6 +139,6 @@ API access URL. - **Done.** Your ActiveCampaign connector is now pulling access data into C1. + **Done.** Your ActiveCampaign connector is now pulling access data into C1.ai. diff --git a/baton/adobe.mdx b/baton/adobe.mdx index e27844bd..db9c477d 100644 --- a/baton/adobe.mdx +++ b/baton/adobe.mdx @@ -1,8 +1,8 @@ --- title: "Set up Adobe connector" -description: "C1 provides identity governance and just-in-time provisioning for Adobe. Integrate your Adobe instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Adobe. Integrate your Adobe instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." og:title: "Set up Adobe connector" -og:description: "C1 provides identity governance and just-in-time provisioning for Adobe. Integrate your Adobe instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Adobe. Integrate your Adobe instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Adobe" --- @@ -31,7 +31,7 @@ Product profiles are synced with license seat data — purchased seats (from the ## Account provisioning -The Adobe connector supports creating new user accounts directly from C1. When configuring an account provisioning policy, you can map the following fields. +The Adobe connector supports creating new user accounts directly from C1.ai. When configuring an account provisioning policy, you can map the following fields. ### Required fields @@ -92,8 +92,8 @@ A user with the **System Administrator** or **Product Administrator** role in Ad Click **Add API** and select **User Management API**. - - To give C1 sync-only (READ) access, give the User Management API **read access** - - To give C1 sync and provision (READ/WRITE) access, give the User Management API **read/write access** and **Product Profile management permissions** + - To give C1.ai sync-only (READ) access, give the User Management API **read access** + - To give C1.ai sync and provision (READ/WRITE) access, give the User Management API **read/write access** and **Product Profile management permissions** Choose the **OAuth Server-to-Server** authentication type. @@ -113,17 +113,17 @@ A user with the **System Administrator** or **Product Administrator** role in Ad **To complete this task, you'll need:** -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Adobe 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Adobe** and click **Add**. @@ -156,12 +156,12 @@ A user with the **System Administrator** or **Product Administrator** role in Ad -**Done.** Your Adobe connector is now pulling access data into C1. +**Done.** Your Adobe connector is now pulling access data into C1.ai. **Follow these instructions to use the Adobe 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -171,7 +171,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -265,14 +265,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 C1.ai 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 Adobe connector to. Adobe data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Adobe connector to. Adobe data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Adobe connector is now pulling access data into C1. +**Done.** Your Adobe connector is now pulling access data into C1.ai. diff --git a/baton/adp-workforce-now.mdx b/baton/adp-workforce-now.mdx index 6e4885dd..44f0c04d 100644 --- a/baton/adp-workforce-now.mdx +++ b/baton/adp-workforce-now.mdx @@ -1,8 +1,8 @@ --- title: "Set up an ADP Workforce Now connector" og:title: "Set up an ADP Workforce Now connector" -description: "C1 provides identity governance for ADP Workforce Now. Integrate your ADP Workforce Now instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for ADP Workforce Now. Integrate your ADP Workforce Now instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for ADP Workforce Now. Integrate your ADP Workforce Now instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for ADP Workforce Now. Integrate your ADP Workforce Now instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "ADP Workforce Now" --- @@ -37,7 +37,7 @@ Each synced worker is exposed as a user resource. The following keys are written | `adjusted_service_date` | `worker.workerDates.adjustedServiceDate` | | | `raw_status` | `worker.workerStatus.statusCode.codeValue` | Literal status (`Active`, `Inactive`, `Terminated`). The SDK enabled/disabled mapping collapses `Inactive` and `Terminated` together; this field preserves the distinction. | | `reports_to_worker_id` | `workAssignments[].reportsTo[0].workerID.idValue` | Manager's worker number. | -| `manager_id` | `workAssignments[].reportsTo[0].associateOID` | Manager's ADP `associateOID`. C1's directory manager mapper resolves this against the manager user's `ExternalID`, so the manager relationship is automatically populated in the C1 user graph. Both this field and `reports_to_worker_id` are derived from the same `reportsTo` entry. | +| `manager_id` | `workAssignments[].reportsTo[0].associateOID` | Manager's ADP `associateOID`. C1.ai's directory manager mapper resolves this against the manager user's `ExternalID`, so the manager relationship is automatically populated in the C1.ai user graph. Both this field and `reports_to_worker_id` are derived from the same `reportsTo` entry. | | `job_title` | `workAssignments[].jobTitle` | | | `job_title_code` | `workAssignments[].jobCode` | Prefers `codeValue`, falls back to `shortName`. | | `department` | `workAssignments[].homeOrganizationalUnits[].nameCode` | | @@ -133,11 +133,11 @@ To configure the ADP Workforce Now connector, you need administrator permissions - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -191,13 +191,13 @@ To configure the ADP Workforce Now connector, you need administrator permissions - **Done.** Your ADP Workforce Now connector is now pulling access data into C1. + **Done.** Your ADP Workforce Now connector is now pulling access data into C1.ai. Follow these instructions to use the [ADP Workforce Now](https://dist.conductorone.com/ConductorOne/baton-adp-workforce-now) 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. + When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1.ai, automatically syncing and uploading data at regular intervals. ### Resources @@ -210,7 +210,7 @@ To configure the ADP Workforce Now connector, you need administrator permissions - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -310,15 +310,15 @@ To configure the ADP Workforce Now connector, you need administrator permissions - 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 C1.ai 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 ADP Workforce Now connector to. ADP Workforce Now data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the ADP Workforce Now connector to. ADP Workforce Now data should be found on the **Entitlements** and **Accounts** tabs. - **Done.** Your ADP Workforce Now connector is now pulling access data into C1. + **Done.** Your ADP Workforce Now connector is now pulling access data into C1.ai. diff --git a/baton/aha.mdx b/baton/aha.mdx index 4ef8a7f7..7198795c 100644 --- a/baton/aha.mdx +++ b/baton/aha.mdx @@ -1,12 +1,12 @@ --- title: "Set up an Aha! connector" og:title: "Set up an Aha! connector" -description: "C1 provides identity governance for Aha!. Integrate your Aha! account with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Aha!. Integrate your Aha! account with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Aha!. Integrate your Aha! account with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Aha!. Integrate your Aha! account with C1.ai for unified visibility and governance over user access." sidebarTitle: "Aha!" --- -C1 provides identity governance for Aha!. Integrate your Aha! account with C1 +C1.ai provides identity governance for Aha!. Integrate your Aha! account with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -70,11 +70,11 @@ users and teams. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -121,7 +121,7 @@ users and teams. - **Done.** Your Aha! connector is now pulling access data into C1. + **Done.** Your Aha! connector is now pulling access data into C1.ai. @@ -129,7 +129,7 @@ users and teams. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -147,7 +147,7 @@ users and teams. - Configure C1 credentials and Aha! credentials as environment variables: + Configure C1.ai credentials and Aha! credentials as environment variables: ```bash BATON_CLIENT_ID= @@ -159,6 +159,6 @@ users and teams. - **Done.** Your Aha! connector is now pulling access data into C1. + **Done.** Your Aha! connector is now pulling access data into C1.ai. diff --git a/baton/airbyte.mdx b/baton/airbyte.mdx index e6ae3ac0..a021648a 100644 --- a/baton/airbyte.mdx +++ b/baton/airbyte.mdx @@ -1,8 +1,8 @@ --- title: "Set up Airbyte connector" -description: "C1 provides identity governance for Airbyte. Integrate your Airbyte instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Airbyte. Integrate your Airbyte instance with C1.ai for unified visibility and governance over user access." og:title: "Set up Airbyte connector" -og:description: "C1 provides identity governance for Airbyte. Integrate your Airbyte instance with C1 for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Airbyte. Integrate your Airbyte instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Airbyte" --- @@ -26,7 +26,7 @@ Each setup method requires you to pass in credentials generated in Airbyte. Gath In the Airbyte UI, navigate to **Settings** > **Account** > **Applications** and click **Create an application**. - Give your application a name, such as "C1", then click **Submit**. + Give your application a name, such as "C1.ai", then click **Submit**. The application is created. Carefully copy and save the application client ID and client secret. @@ -40,17 +40,17 @@ Each setup method requires you to pass in credentials generated in Airbyte. Gath **To complete this task, you'll need:** -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Airbyte 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Airbyte** and click **Add**. @@ -86,12 +86,12 @@ Each setup method requires you to pass in credentials generated in Airbyte. Gath -**Done.** Your Airbyte connector is now pulling access data into C1. +**Done.** Your Airbyte connector is now pulling access data into C1.ai. **Follow these instructions to use the Airbyte 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -101,7 +101,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -192,14 +192,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 C1.ai 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 Airbyte connector to. Airbyte data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Airbyte connector to. Airbyte data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Airbyte connector is now pulling access data into C1. +**Done.** Your Airbyte connector is now pulling access data into C1.ai. diff --git a/baton/aircall.mdx b/baton/aircall.mdx index 31671678..0e63ba21 100644 --- a/baton/aircall.mdx +++ b/baton/aircall.mdx @@ -1,8 +1,8 @@ --- title: "Set up Aircall connector" -description: "C1 provides identity governance for Aircall. Integrate your Aircall instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Aircall. Integrate your Aircall instance with C1.ai for unified visibility and governance over user access." og:title: "Set up Aircall connector" -og:description: "C1 provides identity governance for Aircall. Integrate your Aircall instance with C1 for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Aircall. Integrate your Aircall instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Aircall" --- @@ -41,17 +41,17 @@ See the Aircall docs for information on how to acquire credentials: [View the do **To complete this task, you'll need:** -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Aircall 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Aircall** and click **Add**. @@ -84,22 +84,22 @@ See the Aircall docs for information on how to acquire credentials: [View the do -**Done.** Your Aircall connector is now pulling access data into C1. +**Done.** Your Aircall connector is now pulling access data into C1.ai. **Follow these instructions to use the Aircall 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources -[Contact C1's support team](mailto:support@c1.ai) to download the latest version of the connector. +[Contact C1.ai's support team](mailto:support@c1.ai) to download the latest version of the connector. ### Step 1: Set up a new Aircall connector - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -189,14 +189,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 C1.ai 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 Aircall connector to. Aircall data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Aircall connector to. Aircall data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Aircall connector is now pulling access data into C1. +**Done.** Your Aircall connector is now pulling access data into C1.ai. diff --git a/baton/airflow.mdx b/baton/airflow.mdx index 81307b68..f813ba38 100644 --- a/baton/airflow.mdx +++ b/baton/airflow.mdx @@ -1,8 +1,8 @@ --- title: "Set up an Airflow connector" og:title: "Set up an Airflow connector" -description: "C1 provides identity governance and just-in-time provisioning for Apache Airflow. Integrate your Airflow instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision role assignments." -og:description: "C1 provides identity governance and just-in-time provisioning for Apache Airflow. Integrate your Airflow instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision role assignments." +description: "C1.ai provides identity governance and just-in-time provisioning for Apache Airflow. Integrate your Airflow instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision role assignments." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Apache Airflow. Integrate your Airflow instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision role assignments." sidebarTitle: "Airflow" --- @@ -46,11 +46,11 @@ Airflow uses the FAB (Flask-AppBuilder) auth manager. The connector exchanges us - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -101,19 +101,19 @@ Airflow uses the FAB (Flask-AppBuilder) auth manager. The connector exchanges us - **Done.** Your Airflow connector is now pulling access data into C1. + **Done.** Your Airflow connector is now pulling access data into C1.ai. Follow these instructions to use the [Airflow](https://github.com/conductorone/baton-airflow) 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. + When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1.ai, automatically syncing and uploading data at regular intervals. ### Step 1: Set up a new Airflow connector - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -215,15 +215,15 @@ Airflow uses the FAB (Flask-AppBuilder) auth manager. The connector exchanges us - 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 C1.ai 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 Airflow connector to. Airflow data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the Airflow connector to. Airflow data should be found on the **Entitlements** and **Accounts** tabs. - **Done.** Your Airflow connector is now pulling access data into C1. + **Done.** Your Airflow connector is now pulling access data into C1.ai. diff --git a/baton/airtable.mdx b/baton/airtable.mdx index 58941263..499c4f63 100644 --- a/baton/airtable.mdx +++ b/baton/airtable.mdx @@ -1,8 +1,8 @@ --- title: "Set up an Airtable connector" og:title: "Set up an Airtable connector" -description: "C1 provides identity governance and just-in-time provisioning for Airtable. Integrate your Airtable instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access to workspaces, bases, and groups." -og:description: "C1 provides identity governance and just-in-time provisioning for Airtable. Integrate your Airtable instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access to workspaces, bases, and groups." +description: "C1.ai provides identity governance and just-in-time provisioning for Airtable. Integrate your Airtable instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access to workspaces, bases, and groups." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Airtable. Integrate your Airtable instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access to workspaces, bases, and groups." sidebarTitle: "Airtable" --- @@ -62,11 +62,11 @@ To configure the Airtable connector, you need Enterprise Admin permissions in Ai - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -111,13 +111,13 @@ To configure the Airtable connector, you need Enterprise Admin permissions in Ai - **Done.** Your Airtable connector is now pulling access data into C1. + **Done.** Your Airtable connector is now pulling access data into C1.ai. Follow these instructions to use the [Airtable](https://github.com/conductorone/baton-airtable) 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. + When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1.ai, automatically syncing and uploading data at regular intervals. ### Resources @@ -130,7 +130,7 @@ To configure the Airtable connector, you need Enterprise Admin permissions in Ai - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -228,15 +228,15 @@ To configure the Airtable connector, you need Enterprise Admin permissions in Ai - 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 C1.ai 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 Airtable connector to. Airtable data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the Airtable connector to. Airtable data should be found on the **Entitlements** and **Accounts** tabs. - **Done.** Your Airtable connector is now pulling access data into C1. + **Done.** Your Airtable connector is now pulling access data into C1.ai. diff --git a/baton/aks.mdx b/baton/aks.mdx index 4461c1dd..fb969c08 100644 --- a/baton/aks.mdx +++ b/baton/aks.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Microsoft AKS connector" og:title: "Set up a Microsoft AKS connector" -description: "C1 provides identity governance for Azure Kubernetes Service (AKS). Integrate your AKS instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." -og:description: "C1 provides identity governance for Azure Kubernetes Service (AKS). Integrate your AKS instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance for Azure Kubernetes Service (AKS). Integrate your AKS instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance for Azure Kubernetes Service (AKS). Integrate your AKS instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Microsoft AKS" --- @@ -78,7 +78,7 @@ If desired, you can use an existing Service Principal. Follow these steps if you Click **\+ New registration**. - Give the application a name, such as "C1". + Give the application a name, such as "C1.ai". Select the supported account type appropriate for your organization. For most internal automation, "Accounts in this organizational directory only (Single tenant)" is sufficient. @@ -170,18 +170,18 @@ Be aware that propagation of this assignment may take some time (up to multiple To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of AKS 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **AKS** and click **Add**. @@ -214,24 +214,24 @@ To complete this task, you'll need: -**Done.** Your AKS connector is now pulling access data into C1. +**Done.** Your AKS connector is now pulling access data into C1.ai. **Follow these instructions to use the AKS 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources -[Contact C1's support team](mailto:support@c1.ai) to download the latest version of the connector. +[Contact C1.ai's support team](mailto:support@c1.ai) to download the latest version of the connector. ### Step 1: Set up a new AKS connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -325,14 +325,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 C1.ai 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 AKS connector to. AKS data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the AKS connector to. AKS data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your AKS connector is now pulling access data into C1. +**Done.** Your AKS connector is now pulling access data into C1.ai. diff --git a/baton/alibaba-cloud.mdx b/baton/alibaba-cloud.mdx index 3e5b9033..1a416881 100644 --- a/baton/alibaba-cloud.mdx +++ b/baton/alibaba-cloud.mdx @@ -1,8 +1,8 @@ --- title: "Set up an Alibaba Cloud connector" og:title: "Set up an Alibaba Cloud connector" -description: "C1 provides identity governance for Alibaba Cloud. Integrate your Alibaba Cloud instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Alibaba Cloud. Integrate your Alibaba Cloud instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Alibaba Cloud. Integrate your Alibaba Cloud instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Alibaba Cloud. Integrate your Alibaba Cloud instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Alibaba Cloud" --- @@ -72,7 +72,7 @@ attachment or role assumption grants. - Use one connector instance per Alibaba Cloud account. - Group membership is the only access this connector syncs. The account, user, role and policy resource types carry no entitlements or grants, and now - declare that in their capability metadata, so C1 does not enumerate + declare that in their capability metadata, so C1.ai does not enumerate entitlements or grants for them. - Policy attachment grants are not emitted in the current build. - Role assumption grants and role attached-policy grants are not emitted in @@ -84,11 +84,11 @@ attachment or role assumption grants. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -135,7 +135,7 @@ attachment or role assumption grants. - **Done.** Your Alibaba Cloud connector is now pulling access data into C1. + **Done.** Your Alibaba Cloud connector is now pulling access data into C1.ai. @@ -144,7 +144,7 @@ attachment or role assumption grants. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -176,7 +176,7 @@ attachment or role assumption grants. - Configure C1 credentials and Alibaba Cloud credentials as environment + Configure C1.ai credentials and Alibaba Cloud credentials as environment variables: ```bash @@ -199,6 +199,6 @@ attachment or role assumption grants. - **Done.** Your Alibaba Cloud connector is now pulling access data into C1. + **Done.** Your Alibaba Cloud connector is now pulling access data into C1.ai. diff --git a/baton/alloydb.mdx b/baton/alloydb.mdx index 98690ecc..dda93e25 100644 --- a/baton/alloydb.mdx +++ b/baton/alloydb.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Google AlloyDB connector" og:title: "Set up a Google AlloyDB connector" -description: "C1 provides identity governance and just-in-time provisioning for Google AlloyDB. Integrate your Google AlloyDB 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 Google AlloyDB. Integrate your Google AlloyDB instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for Google AlloyDB. Integrate your Google AlloyDB instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Google AlloyDB. Integrate your Google AlloyDB instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "Google AlloyDB" --- @@ -31,7 +31,7 @@ To configure the Google AlloyDB connector, you need administrator permissions in - Create API credentials for C1: + Create API credentials for C1.ai: 1. Create a new API key or token named `C1` 2. Grant the required scopes or permissions @@ -43,11 +43,11 @@ To configure the Google AlloyDB connector, you need administrator permissions in - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -96,19 +96,19 @@ To configure the Google AlloyDB connector, you need administrator permissions in - **Done.** Your Google AlloyDB connector is now pulling access data into C1. + **Done.** Your Google AlloyDB connector is now pulling access data into C1.ai. Follow these instructions to use the [Google AlloyDB](https://github.com/conductorone/baton-alloydb) 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. + When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1.ai, automatically syncing and uploading data at regular intervals. ### Step 1: Set up a new Google AlloyDB connector - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -205,15 +205,15 @@ To configure the Google AlloyDB connector, you need administrator permissions in - 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 C1.ai 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 Google AlloyDB connector to. Google AlloyDB data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the Google AlloyDB connector to. Google AlloyDB data should be found on the **Entitlements** and **Accounts** tabs. - **Done.** Your Google AlloyDB connector is now pulling access data into C1. + **Done.** Your Google AlloyDB connector is now pulling access data into C1.ai. diff --git a/baton/apache-ranger.mdx b/baton/apache-ranger.mdx index d3b43088..2bea3cc8 100644 --- a/baton/apache-ranger.mdx +++ b/baton/apache-ranger.mdx @@ -1,13 +1,13 @@ --- title: "Set up an Apache Ranger connector" og:title: "Set up an Apache Ranger connector" -description: "C1 provides identity governance for Apache Ranger. Integrate your Apache Ranger instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Apache Ranger. Integrate your Apache Ranger instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Apache Ranger. Integrate your Apache Ranger instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Apache Ranger. Integrate your Apache Ranger instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Apache Ranger" --- -C1 provides identity governance for Apache Ranger. Integrate your Apache Ranger -instance with C1 for unified visibility and governance over identities, policies, +C1.ai provides identity governance for Apache Ranger. Integrate your Apache Ranger +instance with C1.ai for unified visibility and governance over identities, policies, and access grants managed by Ranger Admin. ## Capabilities @@ -67,11 +67,11 @@ directory. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -117,7 +117,7 @@ directory. - **Done.** Your Apache Ranger connector is now pulling access data into C1. + **Done.** Your Apache Ranger connector is now pulling access data into C1.ai. @@ -142,7 +142,7 @@ directory. - **Done.** Your Apache Ranger connector is now pulling access data into C1. + **Done.** Your Apache Ranger connector is now pulling access data into C1.ai. diff --git a/baton/arctic-wolf.mdx b/baton/arctic-wolf.mdx index 11c30b8d..9e6dcd7f 100644 --- a/baton/arctic-wolf.mdx +++ b/baton/arctic-wolf.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Arctic Wolf connector" og:title: "Set up a Arctic Wolf connector" -description: "C1 provides identity governance and just-in-time provisioning for Arctic Wolf. Integrate your Arctic Wolf 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 Arctic Wolf. Integrate your Arctic Wolf instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for Arctic Wolf. Integrate your Arctic Wolf instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Arctic Wolf. Integrate your Arctic Wolf instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "Arctic Wolf" --- @@ -33,7 +33,7 @@ To configure the Arctic Wolf connector, you need administrator permissions in th - In the Aurora console, go to **Settings** > **Integrations** and add a new application (integration) for C1. + In the Aurora console, go to **Settings** > **Integrations** and add a new application (integration) for C1.ai. @@ -49,11 +49,11 @@ To configure the Arctic Wolf connector, you need administrator permissions in th - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -105,13 +105,13 @@ To configure the Arctic Wolf connector, you need administrator permissions in th - **Done.** Your Arctic Wolf connector is now pulling access data into C1. + **Done.** Your Arctic Wolf connector is now pulling access data into C1.ai. Follow these instructions to use the [Arctic Wolf](https://github.com/conductorone/baton-arctic-wolf) 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. + When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1.ai, automatically syncing and uploading data at regular intervals. ### Resources @@ -124,7 +124,7 @@ To configure the Arctic Wolf connector, you need administrator permissions in th - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -224,15 +224,15 @@ To configure the Arctic Wolf connector, you need administrator permissions in th - 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 C1.ai 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 Arctic Wolf connector to. Arctic Wolf data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the Arctic Wolf connector to. Arctic Wolf data should be found on the **Entitlements** and **Accounts** tabs. - **Done.** Your Arctic Wolf connector is now pulling access data into C1. + **Done.** Your Arctic Wolf connector is now pulling access data into C1.ai. diff --git a/baton/argo-cd.mdx b/baton/argo-cd.mdx index c49461ca..771c1d72 100644 --- a/baton/argo-cd.mdx +++ b/baton/argo-cd.mdx @@ -1,8 +1,8 @@ --- title: "Set up an Argo CD connector" -description: "C1 provides identity governance for ArgoCD. Integrate your ArgoCD instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance for ArgoCD. Integrate your ArgoCD instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." og:title: "Set up an Argo CD connector" -og:description: "C1 provides identity governance for ArgoCD. Integrate your ArgoCD instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance for ArgoCD. Integrate your ArgoCD instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "ArgoCD" --- @@ -15,7 +15,7 @@ sidebarTitle: "ArgoCD" The ArgoCD connector supports [automatic account provisioning](/product/admin/account-provisioning). -When a new account is created by C1, the account's password will be sent to a [vault](/product/admin/vaults). +When a new account is created by C1.ai, the account's password will be sent to a [vault](/product/admin/vaults). This connector does not support account deprovisioning. You must deprovision accounts directly in ArgoCD. @@ -116,20 +116,20 @@ To set up the connector, you'll need: **To complete this task, you'll need:** -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of ArgoCD 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 C1.ai.** This connector does not support cloud hosting. **Follow these instructions to use the ArgoCD 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -139,7 +139,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -239,14 +239,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 C1.ai 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 ArgoCD connector to. ArgoCD data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the ArgoCD connector to. ArgoCD data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your ArgoCD connector is now pulling access data into C1. +**Done.** Your ArgoCD connector is now pulling access data into C1.ai. diff --git a/baton/ariba.mdx b/baton/ariba.mdx index 9096abac..a6d40bc0 100644 --- a/baton/ariba.mdx +++ b/baton/ariba.mdx @@ -1,8 +1,8 @@ --- title: "Set up an SAP Ariba connector" og:title: "Set up an SAP Ariba connector" -description: "C1 provides identity governance and just-in-time provisioning for SAP Ariba. Integrate your SAP Ariba 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 SAP Ariba. Integrate your SAP Ariba instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for SAP Ariba. Integrate your SAP Ariba instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for SAP Ariba. Integrate your SAP Ariba instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "SAP Ariba" --- @@ -45,7 +45,7 @@ The connector authenticates using **OAuth 2.0 client credentials** against the S - Create a new application for C1: + Create a new application for C1.ai: 1. Click **Create application** and name it `C1` 2. Select **Production** environment @@ -63,11 +63,11 @@ The connector authenticates using **OAuth 2.0 client credentials** against the S - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -120,19 +120,19 @@ The connector authenticates using **OAuth 2.0 client credentials** against the S - **Done.** Your Ariba connector is now pulling access data into C1. + **Done.** Your Ariba connector is now pulling access data into C1.ai. Follow these instructions to use the [Ariba](https://github.com/conductorone/baton-ariba) 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. + When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1.ai, automatically syncing and uploading data at regular intervals. ### Step 1: Set up a new Ariba connector - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -236,15 +236,15 @@ The connector authenticates using **OAuth 2.0 client credentials** against the S - 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 C1.ai 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 Ariba connector to. Ariba data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the Ariba connector to. Ariba data should be found on the **Entitlements** and **Accounts** tabs. - **Done.** Your Ariba connector is now pulling access data into C1. + **Done.** Your Ariba connector is now pulling access data into C1.ai. diff --git a/baton/artifactory.mdx b/baton/artifactory.mdx index b2297466..77163e71 100644 --- a/baton/artifactory.mdx +++ b/baton/artifactory.mdx @@ -1,8 +1,8 @@ --- title: "Set up a JFrog Artifactory connector" og:title: "Set up a JFrog 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: "C1.ai provides identity governance and just-in-time provisioning for Artifactory. Integrate your Artifactory instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Artifactory. Integrate your Artifactory instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "JFrog Artifactory" --- @@ -25,7 +25,7 @@ sidebarTitle: "JFrog Artifactory" **Known limitations:** -- 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. +- Repository permissions granted via pre-existing Artifactory permission targets (not created by C1.ai) cannot be revoked through this connector. Only permissions provisioned by C1.ai 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,18 +44,18 @@ 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 C1.ai - 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Artifactory** and click **Add**. @@ -88,24 +88,24 @@ To complete this task, you'll need: -**Done.** Your Artifactory connector is now pulling access data into C1. +**Done.** Your Artifactory connector is now pulling access data into C1.ai. **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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources -[Contact C1's support team](mailto:support@c1.ai) to download the latest version of the connector. +[Contact C1.ai's support team](mailto:support@c1.ai) to download the latest version of the connector. ### Step 1: Set up a new Artifactory connector - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -198,14 +198,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 C1.ai 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 C1.ai, 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. -**Done.** Your Artifactory connector is now pulling access data into C1. +**Done.** Your Artifactory connector is now pulling access data into C1.ai. diff --git a/baton/asana.mdx b/baton/asana.mdx index 577d2e16..50019ff0 100644 --- a/baton/asana.mdx +++ b/baton/asana.mdx @@ -1,8 +1,8 @@ --- title: "Set up an Asana connector" -description: "C1 provides identity governance and just-in-time provisioning for Asana. Integrate your Asana instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Asana. Integrate your Asana instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." og:title: "Set up an Asana connector" -og:description: "C1 provides identity governance and just-in-time provisioning for Asana. Integrate your Asana instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Asana. Integrate your Asana instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Asana" --- @@ -65,9 +65,9 @@ An Asana super admin using an Asana Enterprise plan must complete this task. - If you haven't already done so, create or identify a service account in Asana that will be used for the C1 integration. + If you haven't already done so, create or identify a service account in Asana that will be used for the C1.ai integration. - The service account needs, at minimum, the **Users: Read** and **Teams: Read** permissions in order to sync user data. To provision accounts and other access with C1, give the service account full permissions. + The service account needs, at minimum, the **Users: Read** and **Teams: Read** permissions in order to sync user data. To provision accounts and other access with C1.ai, give the service account full permissions. Click the three-dots icon next to the name of your service account and select **Edit service account**. @@ -87,17 +87,17 @@ An Asana super admin using an Asana Enterprise plan must complete this task. **To complete this task, you'll need:** -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Asana 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Asana** and click **Add**. @@ -125,11 +125,11 @@ An Asana super admin using an Asana Enterprise plan must complete this task. **Service account users:** Click to enable **Is service account** and enter your service account token in the **Personal access token** field. - **Optional.** If you want C1 to provision new Asana accounts, enter the ID of the workspace new accounts should be added to in the **Default workspace** field. + **Optional.** If you want C1.ai to provision new Asana accounts, enter the ID of the workspace new accounts should be added to in the **Default workspace** field. If you do not set the default workspace ID here, you can set it when [configuring account provisioning](/product/admin/account-provisioning#part-2-cel-expressions-pull-in-the-required-information). The workspace ID must be set in at least one of these places, or account provisioning will fail. - **Optional.** If want to use C1 to sync and provision Asana licenses, click to enable **Use SCIM API**. + **Optional.** If want to use C1.ai to sync and provision Asana licenses, click to enable **Use SCIM API**. Click **Save**. @@ -139,12 +139,12 @@ An Asana super admin using an Asana Enterprise plan must complete this task. -**Done.** Your Asana connector is now pulling access data into C1. +**Done.** Your Asana connector is now pulling access data into C1.ai. **Follow these instructions to use the Asana 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -154,7 +154,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -255,14 +255,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 C1.ai 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 Asana connector to. Asana data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Asana connector to. Asana data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Asana connector is now pulling access data into C1. +**Done.** Your Asana connector is now pulling access data into C1.ai. diff --git a/baton/atlassian.mdx b/baton/atlassian.mdx index 4a62def5..ab66b84c 100644 --- a/baton/atlassian.mdx +++ b/baton/atlassian.mdx @@ -1,8 +1,8 @@ --- title: "Set up an Atlassian connector" -description: "C1 provides identity governance and just-in-time provisioning for Atlassian. Integrate your Atlassian instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Atlassian. Integrate your Atlassian instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." og:title: "Set up an Atlassian connector" -og:description: "C1 provides identity governance and just-in-time provisioning for Atlassian. Integrate your Atlassian instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Atlassian. Integrate your Atlassian instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Atlassian" --- @@ -23,7 +23,7 @@ The Atlassian connector supports [automatic account provisioning](/product/admin ### 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 C1.ai 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 | |-------------|-------------------|-------------| @@ -134,17 +134,17 @@ If you want to provision workspace roles with the connector, you must raise an A **To complete this task, you'll need:** -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Atlassian 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Atlassian** and click **Add**. @@ -183,12 +183,12 @@ If you want to provision workspace roles with the connector, you must raise an A -**Done.** Your Atlassian connector is now pulling access data into C1. +**Done.** Your Atlassian connector is now pulling access data into C1.ai. **Follow these instructions to use the Atlassian 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -200,7 +200,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -297,14 +297,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 C1.ai 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 Atlassian connector to. Atlassian data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Atlassian connector to. Atlassian data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Atlassian connector is now pulling access data into C1. +**Done.** Your Atlassian connector is now pulling access data into C1.ai. diff --git a/baton/auth0.mdx b/baton/auth0.mdx index caba63f7..a8405491 100644 --- a/baton/auth0.mdx +++ b/baton/auth0.mdx @@ -1,8 +1,8 @@ --- title: "Set up an Okta Auth0 connector" -description: "C1 provides identity governance and just-in-time provisioning for Okta Auth0. Integrate your Okta Auth0 instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Okta Auth0. Integrate your Okta Auth0 instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." og:title: "Set up an Okta Auth0 connector" -og:description: "C1 provides identity governance and just-in-time provisioning for Okta Auth0. Integrate your Okta Auth0 instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Okta Auth0. Integrate your Okta Auth0 instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Okta Auth0" --- @@ -33,7 +33,7 @@ A user with the ability to create a new application in Auth0 must perform this t In Auth0, navigate to **Dashboard** > **Applications** > **Applications** and click **Create Application**. - Give the new application a name, such as "C1". + Give the new application a name, such as "C1.ai". Select the **Machine to Machine Applications** option and click **Create**. @@ -44,7 +44,7 @@ A user with the ability to create a new application in Auth0 must perform this t Give the application's access token permissions: - **You'll need these permissions to give C1 **READ** access (syncing access data):** + **You'll need these permissions to give C1.ai **READ** access (syncing access data):** - read:users - read:grants - read:organizations @@ -53,7 +53,7 @@ A user with the ability to create a new application in Auth0 must perform this t - read:role\_members - read:resource\_servers (required only if you configure the connector to sync role permissions) - **You'll need these permissions to give C1 **READ/WRITE** access (syncing access data and provisioning access):** + **You'll need these permissions to give C1.ai **READ/WRITE** access (syncing access data and provisioning access):** - read:users - read:grants - read:organizations @@ -82,17 +82,17 @@ A user with the ability to create a new application in Auth0 must perform this t **To complete this task, you'll need:** -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Auth0 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Auth0** and click **Add**. @@ -131,12 +131,12 @@ A user with the ability to create a new application in Auth0 must perform this t -**Done.** Your Auth0 connector is now pulling access data into C1. +**Done.** Your Auth0 connector is now pulling access data into C1.ai. **Follow these instructions to use the Auth0 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -148,7 +148,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -245,14 +245,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 C1.ai 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 Auth0 connector to. Auth0 data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Auth0 connector to. Auth0 data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Auth0 connector is now pulling access data into C1. +**Done.** Your Auth0 connector is now pulling access data into C1.ai. diff --git a/baton/autotask.mdx b/baton/autotask.mdx index a62e8df5..321e4db0 100644 --- a/baton/autotask.mdx +++ b/baton/autotask.mdx @@ -1,13 +1,13 @@ --- title: "Set up an Autotask connector" og:title: "Set up an Autotask connector" -description: "C1 provides identity governance for Autotask. Integrate your Autotask instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Autotask. Integrate your Autotask instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Autotask. Integrate your Autotask instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Autotask. Integrate your Autotask instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Autotask" --- -C1 provides identity governance for Autotask PSA (by Datto/Kaseya). Integrate -your Autotask instance with C1 for unified visibility and governance over +C1.ai provides identity governance for Autotask PSA (by Datto/Kaseya). Integrate +your Autotask instance with C1.ai for unified visibility and governance over resource and contact access. This connector can also be configured to automatically create Autotask tickets @@ -25,7 +25,7 @@ provider](/product/admin/external-ticketing) to learn more. |Security levels||| External ticket provisioning is also supported. When enabled, the connector -creates Autotask `Tickets` records for C1 provisioning tasks. +creates Autotask `Tickets` records for C1.ai provisioning tasks. The connector also emits the following access grants: @@ -104,11 +104,11 @@ identifiers. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -147,7 +147,7 @@ identifiers. - **Optional.** If you want C1 to create Autotask tickets for manual + **Optional.** If you want C1.ai to create Autotask tickets for manual provisioning tasks, click **Enable external ticket provisioning**. @@ -160,7 +160,7 @@ identifiers. - **Done.** Your Autotask connector is now pulling access data into C1. + **Done.** Your Autotask connector is now pulling access data into C1.ai. @@ -182,18 +182,18 @@ identifiers. - **Done.** Your Autotask connector is now pulling access data into C1. + **Done.** Your Autotask connector is now pulling access data into C1.ai. ## Configure external ticketing After enabling external ticket provisioning on the connector, configure Autotask -as an external ticketing provider in C1. +as an external ticketing provider in C1.ai. - In C1, navigate to **Platform** > **External ticketing**. + In C1.ai, navigate to **Platform** > **External ticketing**. @@ -202,7 +202,7 @@ as an external ticketing provider in C1. Map the required **Company ID** field to the Autotask company that should own - tickets created by C1. + tickets created by C1.ai. @@ -236,7 +236,7 @@ as an external ticketing provider in C1. request referred to this field as `securityLevelID`; the official REST field name is `userType`.) - **Ticket creation.** External ticket provisioning creates Autotask `Tickets` - records. The connector does not update or close Autotask tickets directly; C1 + records. The connector does not update or close Autotask tickets directly; C1.ai tracks provider state through the configured external-ticketing status mappings. - **Read-only access sync.** This connector syncs identity and access data and diff --git a/baton/avalara.mdx b/baton/avalara.mdx index 0f11cc21..c24c31c2 100644 --- a/baton/avalara.mdx +++ b/baton/avalara.mdx @@ -1,8 +1,8 @@ --- title: "Set up an Avalara connector" -description: "C1 provides identity governance for Avalara. Integrate your Avalara instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Avalara. Integrate your Avalara instance with C1.ai for unified visibility and governance over user access." og:title: "Set up an Avalara connector" -og:description: "C1 provides identity governance for Avalara. Integrate your Avalara instance with C1 for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Avalara. Integrate your Avalara instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Avalara" --- @@ -33,17 +33,17 @@ Configuring the connector requires you to pass in credentials generated in Avala **To complete this task, you'll need:** -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Avalara 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Avalara** and click **Add**. @@ -79,12 +79,12 @@ Configuring the connector requires you to pass in credentials generated in Avala -**Done.** Your Avalara connector is now pulling access data into C1. +**Done.** Your Avalara connector is now pulling access data into C1.ai. **Follow these instructions to use the Avalara 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -94,7 +94,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -185,14 +185,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 C1.ai 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 Avalara connector to. Avalara data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Avalara connector to. Avalara data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Avalara connector is now pulling access data into C1. +**Done.** Your Avalara connector is now pulling access data into C1.ai. diff --git a/baton/avatax.mdx b/baton/avatax.mdx index bf4c0e85..79530141 100644 --- a/baton/avatax.mdx +++ b/baton/avatax.mdx @@ -1,13 +1,13 @@ --- title: "Set up an AvaTax connector" og:title: "Set up an AvaTax connector" -description: "C1 provides identity governance for Avalara AvaTax. Integrate your AvaTax account with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Avalara AvaTax. Integrate your AvaTax account with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Avalara AvaTax. Integrate your AvaTax account with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Avalara AvaTax. Integrate your AvaTax account with C1.ai for unified visibility and governance over user access." sidebarTitle: "AvaTax" --- -C1 provides identity governance for Avalara AvaTax. Integrate your AvaTax -account with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Avalara AvaTax. Integrate your AvaTax +account with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -32,10 +32,10 @@ access grants. 1. In the AvaTax portal, go to **Settings → License and API keys** and copy your **Account ID** and generate (or copy) a **License key**. -2. In C1, create a new AvaTax connector. +2. In C1.ai, create a new AvaTax connector. 3. Enter the **Account ID** and **License key**, and choose the **Environment** (`production` or `sandbox`, defaulting to `production`). -4. Save the connector. C1 verifies the credentials and begins the first sync. +4. Save the connector. C1.ai verifies the credentials and begins the first sync. ## Authentication diff --git a/baton/aws-bedrock-agentcore.mdx b/baton/aws-bedrock-agentcore.mdx index 93353330..041ac45f 100644 --- a/baton/aws-bedrock-agentcore.mdx +++ b/baton/aws-bedrock-agentcore.mdx @@ -1,8 +1,8 @@ --- title: "Set up an AWS Bedrock AgentCore connector" og:title: "Set up an AWS Bedrock AgentCore connector" -description: "C1 provides identity governance for AWS Bedrock AgentCore. Integrate Bedrock AgentCore with C1 to manage non-human identities (AI agents), audit credential provider access, and track gateway associations." -og:description: "C1 provides identity governance for AWS Bedrock AgentCore. Integrate Bedrock AgentCore with C1 to manage non-human identities (AI agents), audit credential provider access, and track gateway associations." +description: "C1.ai provides identity governance for AWS Bedrock AgentCore. Integrate Bedrock AgentCore with C1.ai to manage non-human identities (AI agents), audit credential provider access, and track gateway associations." +og:description: "C1.ai provides identity governance for AWS Bedrock AgentCore. Integrate Bedrock AgentCore with C1.ai to manage non-human identities (AI agents), audit credential provider access, and track gateway associations." sidebarTitle: "AWS Bedrock AgentCore" --- @@ -33,7 +33,7 @@ The AWS Bedrock AgentCore connector syncs the following resources: The connector exposes the following Baton actions: -- **`provision_oauth_credential`**: Create or update an AgentCore OAuth2 credential provider (e.g. from a C1 Personal Client Credential) and point an existing gateway target at it. +- **`provision_oauth_credential`**: Create or update an AgentCore OAuth2 credential provider (e.g. from a C1.ai Personal Client Credential) and point an existing gateway target at it. ## Gather AWS credentials @@ -80,11 +80,11 @@ The connector exposes the following Baton actions: - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -136,20 +136,20 @@ The connector exposes the following Baton actions: - **Done.** Your AWS Bedrock AgentCore connector is now pulling access data into C1. + **Done.** Your AWS Bedrock AgentCore connector is now pulling access data into C1.ai. Follow these instructions to use the [AWS Bedrock AgentCore](https://github.com/conductorone/baton-aws-bedrock-agentcore) 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. + When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1.ai, automatically syncing and uploading data at regular intervals. ### Step 1: Set up a new connector - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -237,14 +237,14 @@ The connector exposes the following Baton actions: - 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 C1.ai 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 connector to. Data should be found on the **Entitlements**, **Accounts**, and **Secrets** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the connector to. Data should be found on the **Entitlements**, **Accounts**, and **Secrets** tabs. - **Done.** Your AWS Bedrock AgentCore connector is now pulling access data into C1. + **Done.** Your AWS Bedrock AgentCore connector is now pulling access data into C1.ai. diff --git a/baton/aws-cognito.mdx b/baton/aws-cognito.mdx index e0439ce8..4cbcb8e8 100644 --- a/baton/aws-cognito.mdx +++ b/baton/aws-cognito.mdx @@ -1,8 +1,8 @@ --- title: "Set up an AWS Cognito connector" og:title: "Set up an AWS Cognito connector" -description: "C1 provides identity governance and just-in-time provisioning for AWS Cognito. Integrate your AWS Cognito User Pools 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 AWS Cognito. Integrate your AWS Cognito User Pools with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for AWS Cognito. Integrate your AWS Cognito User Pools with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for AWS Cognito. Integrate your AWS Cognito User Pools with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "AWS Cognito" --- @@ -52,7 +52,7 @@ To configure the AWS Cognito connector, your IAM identity must have permission t - Create or identify an IAM user with the required permissions listed above. C1 recommends scoping the policy to the specific User Pool ARN(s): + Create or identify an IAM user with the required permissions listed above. C1.ai recommends scoping the policy to the specific User Pool ARN(s): ```json { @@ -91,13 +91,13 @@ To configure the AWS Cognito connector, your IAM identity must have permission t - **Last login date not available on Essentials tier.** The Cognito `UserLastAuthenticationDate` field is only populated on User Pools using the **Plus** feature plan. If your pool is on the Essentials plan, last login data will not appear in ConductorOne. - **Cognito is rate-limited.** The `ListUsers` API is rate-limited to approximately 5 requests per second. For large User Pools (tens of thousands of users), syncs will be slow. This is expected behavior and not a connector defect. - **One connector per User Pool.** Each connector instance syncs exactly one Cognito User Pool. To manage multiple pools, deploy one connector per pool. -- **Group names are immutable.** Cognito does not allow renaming groups after creation. Group names are used as stable resource IDs. If a group is deleted and re-created with the same name, C1 will treat it as the same group. -- **Invite email is optional and defaults to off.** When provisioning a new user, you can choose whether Cognito sends a temporary password to the user's email via the **Send Invite Email** field. The default is `false` (no email sent). To send the invite, add an explicit mapping for `sendInviteEmail` set to `true` in the provisioning flow. C1 never handles the credential directly. +- **Group names are immutable.** Cognito does not allow renaming groups after creation. Group names are used as stable resource IDs. If a group is deleted and re-created with the same name, C1.ai will treat it as the same group. +- **Invite email is optional and defaults to off.** When provisioning a new user, you can choose whether Cognito sends a temporary password to the user's email via the **Send Invite Email** field. The default is `false` (no email sent). To send the invite, add an explicit mapping for `sendInviteEmail` set to `true` in the provisioning flow. C1.ai never handles the credential directly. - **Additional required attributes must use exact Cognito attribute names.** If your User Pool requires attributes beyond `given_name` and `family_name` (for example `nickname`, `preferred_username`, or a custom attribute like `custom:department`), add them as optional mappings in the provisioning flow using the exact Cognito attribute name as the destination key. The connector forwards any unrecognized profile fields directly to Cognito. ## Actions -The AWS Cognito connector supports the following account lifecycle actions, which can be triggered manually or via C1 automations: +The AWS Cognito connector supports the following account lifecycle actions, which can be triggered manually or via C1.ai automations: | Action | Description | | :--- | :--- | @@ -110,7 +110,7 @@ To trigger an enable or disable action automatically: 1. In ConductorOne, navigate to **Automations** and create or edit an automation. 2. Add an action step and select **Enable User** or **Disable User** from the AWS Cognito connector. -3. C1 will pass the user's resource ID automatically — no manual input required. +3. C1.ai will pass the user's resource ID automatically — no manual input required. You can also trigger actions manually from a user's profile page under **Actions**. @@ -287,7 +287,7 @@ You can also trigger actions manually from a user's profile page under **Actions - 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 C1.ai connectors (if desired), then apply the secret config and deployment config files. diff --git a/baton/aws.mdx b/baton/aws.mdx index d2b1122f..559e73e0 100644 --- a/baton/aws.mdx +++ b/baton/aws.mdx @@ -1,15 +1,15 @@ --- title: "Set up an AWS connector" -description: "C1 provides identity governance for AWS. Integrate your AWS instance with C1 to run user access reviews (UARs) and enable just-in-time (JIT) access requests." +description: "C1.ai provides identity governance for AWS. Integrate your AWS instance with C1.ai to run user access reviews (UARs) and enable just-in-time (JIT) access requests." og:title: "Set up an AWS connector" -og:description: "C1 provides identity governance for AWS. Integrate your AWS instance with C1 to run user access reviews (UARs) and enable just-in-time (JIT) access requests." +og:description: "C1.ai provides identity governance for AWS. Integrate your AWS instance with C1.ai to run user access reviews (UARs) and enable just-in-time (JIT) access requests." sidebarTitle: "AWS" --- **This is an updated and improved version of the AWS connector!** -If you're setting up AWS with C1 for the first time, you're in the right place. +If you're setting up AWS with C1.ai for the first time, you're in the right place. ## Capabilities @@ -41,7 +41,7 @@ The AWS connector supports [automatic account provisioning and deprovisioning](/ ## AWS STS web identity action The connector exposes the global `assume_role_with_web_identity` action for -approved, short-lived AWS credential vending. C1 supplies a request-scoped OIDC +approved, short-lived AWS credential vending. C1.ai supplies a request-scoped OIDC token and age encryption recipient. The connector exchanges the token with AWS STS, encrypts the returned credential envelope before it crosses the connector boundary, and returns ciphertext plus expiration and assumed-role audit @@ -50,24 +50,24 @@ metadata. The action accepts: - `role_arn`: the target customer IAM role; -- `web_identity_token`: a short-lived C1-issued OIDC token; +- `web_identity_token`: a short-lived C1.ai-issued OIDC token; - `age_recipient`: the request-scoped public encryption recipient; - `session_name`: the AWS audit/session name; - `duration_seconds`: 900 through 43,200, also limited by the IAM role; and - `policy_json`: an optional restrictive inline session policy. -Before enabling the action, create an IAM OIDC provider for the C1 issuer and a +Before enabling the action, create an IAM OIDC provider for the C1.ai issuer and a role trust policy allowing `sts:AssumeRoleWithWebIdentity`. Restrict the trust -policy to the documented C1 issuer, intended audience, and tenant/requestor +policy to the documented C1.ai issuer, intended audience, and tenant/requestor subject profile. Do not use a wildcard issuer, audience, or subject. The role's permissions policy defines the maximum AWS access; the optional session policy can only narrow it further. Synced IAM role profiles include `aws_max_session_duration_seconds`, the -provider-observed `MaxSessionDuration` ceiling returned by IAM. C1 must combine +provider-observed `MaxSessionDuration` ceiling returned by IAM. C1.ai must combine that ceiling with its own access policy when choosing `duration_seconds`. AWS does not expose an authoritative role property that says whether a future -session will be issued directly or through role chaining; C1 must derive that +session will be issued directly or through role chaining; C1.ai must derive that topology from its configured issuance mode and apply the corresponding AWS limit. @@ -81,7 +81,7 @@ When both **Enable support for AWS Organizations** and **Enable support for AWS Instead of one row per (account, permission set, user) combination, reviewers see "Permission Set X on Account Y" as a single item, with the account's place in the AWS Organizations hierarchy shown for context. -These four resource types are **opt-in** on the C1 platform: even with both checkboxes enabled above, you must separately opt in to each resource type before C1 begins syncing it. Until you opt in, the connector keeps syncing the existing flat account/permission-set entitlement model unchanged. +These four resource types are **opt-in** on the C1.ai platform: even with both checkboxes enabled above, you must separately opt in to each resource type before C1.ai begins syncing it. Until you opt in, the connector keeps syncing the existing flat account/permission-set entitlement model unchanged. Syncing the Organization Root / Organizational Unit hierarchy also requires the `organizations:ListRoots` and `organizations:ListOrganizationalUnitsForParent` permissions (see the IAM policy in the Identity Center setup tab below). If these permissions are missing, the connector logs a warning and skips the OU hierarchy rather than failing the sync — accounts continue to sync without OU grouping. @@ -105,7 +105,7 @@ For an IAM user, **Last Login** is the most recent of password-based AWS sign-in Populating `access_key_last_used` requires `iam:ListAccessKeys` and `iam:GetAccessKeyLastUsed`; it does not require **Sync secrets**. -When AWS returns neither `PasswordLastUsed` nor any access-key last-used date, C1 leaves **Last Login** unset. A missing password date does not mean the user has no console password; use `console_access_enabled` for that distinction. +When AWS returns neither `PasswordLastUsed` nor any access-key last-used date, C1.ai leaves **Last Login** unset. A missing password date does not mean the user has no console password; use `console_access_enabled` for that distinction. Per-key detail lives on the access key itself, on the [Inventory page](/product/admin/inventory): @@ -128,9 +128,9 @@ Configuring the connector requires you to pass in credentials generated in AWS. **Important** -A user with the **Connector Administrator** or **Super Administrator** role in C1 and the **ability to create an IAM Role** in AWS must perform this task. +A user with the **Connector Administrator** or **Super Administrator** role in C1.ai and the **ability to create an IAM Role** in AWS must perform this task. -C1 uses an IAM Trust relationship between your AWS Account and C1's Service AWS Account. This is the [AWS recommended method of sharing access to AWS Accounts](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_third-party.html). C1 has a specially created and isolated AWS Account dedicated to the AWS integration. For advanced configurations, the only trusted entity should be the following ARN: `arn:aws:iam::765656841499:role/ConductorOneService` +C1.ai uses an IAM Trust relationship between your AWS Account and C1.ai's Service AWS Account. This is the [AWS recommended method of sharing access to AWS Accounts](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_third-party.html). C1.ai has a specially created and isolated AWS Account dedicated to the AWS integration. For advanced configurations, the only trusted entity should be the following ARN: `arn:aws:iam::765656841499:role/ConductorOneService` Follow the relevant set of instructions below to set up the AWS connector for IAM or SSO, as your configuration dictates. @@ -139,9 +139,9 @@ Follow the relevant set of instructions below to set up the AWS connector for IA ### IAM setup: Gather credentials that support syncing child account data -To sync IAM data (like users, roles, and groups) from multiple AWS child accounts, C1 uses a secure, read-only mechanism called **cross-account access**. This setup works by allowing a central role in your root account to temporarily assume a specific role in each child account. This method ensures that the connector can gather the necessary data without storing credentials or requiring permanent access. +To sync IAM data (like users, roles, and groups) from multiple AWS child accounts, C1.ai uses a secure, read-only mechanism called **cross-account access**. This setup works by allowing a central role in your root account to temporarily assume a specific role in each child account. This method ensures that the connector can gather the necessary data without storing credentials or requiring permanent access. -If you're using this setup, make sure to click **Enable support for AWS Organizations** when setting up the connector in the C1 web UI. You may also enable **Enable support for AWS IAM Identity Center** at the same time. By default, enabling Identity Center alongside Organizations syncs only Identity Center data (users, groups, permission sets, account assignments) and skips cross-account IAM. To also sync IAM users, roles, and groups from every child account in this combined mode, additionally enable **Also sync cross-account IAM when Identity Center is enabled**. This flag is off by default so existing Identity Center deployments don't suddenly require child-account `sts:AssumeRole` access. +If you're using this setup, make sure to click **Enable support for AWS Organizations** when setting up the connector in the C1.ai web UI. You may also enable **Enable support for AWS IAM Identity Center** at the same time. By default, enabling Identity Center alongside Organizations syncs only Identity Center data (users, groups, permission sets, account assignments) and skips cross-account IAM. To also sync IAM users, roles, and groups from every child account in this combined mode, additionally enable **Also sync cross-account IAM when Identity Center is enabled**. This flag is off by default so existing Identity Center deployments don't suddenly require child-account `sts:AssumeRole` access. **In order to use the connector to gather IAM AWS data, you'll need to configure each sub-account to have a role with a trust policy.** There are two options here: @@ -149,13 +149,13 @@ If you're using this setup, make sure to click **Enable support for AWS Organiza `{ "Effect": "Allow", "Action": "sts:AssumeRole", "Resource": "arn:aws:iam::*:role/OrganizationAccountAccessRole" }` - Create a new custom role by following the steps below -#### Get a C1-provided External ID +#### Get a C1.ai-provided External ID AWS [requires the use of External IDs](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-user_externalid.html) when granting third-party access to your AWS account. This security measure prevents the "confused deputy" problem and ensures that only authorized parties can assume the role. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **AWS v2** and click **Add**. @@ -184,14 +184,14 @@ AWS [requires the use of External IDs](https://docs.aws.amazon.com/IAM/latest/Us #### Create a custom IAM role -This custom role acts as a bridge, allowing C1 to securely access your child account. The trust policy you're about to create is the key to this connection. +This custom role acts as a bridge, allowing C1.ai to securely access your child account. The trust policy you're about to create is the key to this connection. Navigate to the [IAM Dashboard](https://us-east-1.console.aws.amazon.com/iamv2/home?) and select **Roles** > **Create Role**. - Select **Custom Trust Policy** and paste the following into the Trust Policy JSON editor, replacing `{ROOT_ID}` with the root ID from the main account and `EXTERNAL_ID_FROM_C1_INTEGRATIONS_PAGE` with the External ID you copied from C1. + Select **Custom Trust Policy** and paste the following into the Trust Policy JSON editor, replacing `{ROOT_ID}` with the root ID from the main account and `EXTERNAL_ID_FROM_C1_INTEGRATIONS_PAGE` with the External ID you copied from C1.ai. ```json { @@ -215,9 +215,9 @@ This custom role acts as a bridge, allowing C1 to securely access your child acc ``` **Notes on the Trust Policy:** - **"Action": "sts:AssumeRole"**: This is the core permission. It's the only action allowed by this policy, and it specifically allows the C1 role in your root account to temporarily assume this role in the child account. Think of it like a temporary key that only the main account can use. - **"Principal": "arn:aws:iam::`{ROOT\_ID}`:role/ConductorOneService"**: This is the trusted entity. It specifies that only the C1 role in your main root account is allowed to assume this role. This ensures that no other account can use this trust policy. - **"Condition": "sts:ExternalId"**: The External ID acts as a shared identifier between you and C1, confirming which trust relationship is being used. This helps prevent the "confused deputy" problem by ensuring the request is coming from the expected context. Learn more about [granting access using External IDs](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-user_externalid.html). + **"Action": "sts:AssumeRole"**: This is the core permission. It's the only action allowed by this policy, and it specifically allows the C1.ai role in your root account to temporarily assume this role in the child account. Think of it like a temporary key that only the main account can use. + **"Principal": "arn:aws:iam::`{ROOT\_ID}`:role/ConductorOneService"**: This is the trusted entity. It specifies that only the C1.ai role in your main root account is allowed to assume this role. This ensures that no other account can use this trust policy. + **"Condition": "sts:ExternalId"**: The External ID acts as a shared identifier between you and C1.ai, confirming which trust relationship is being used. This helps prevent the "confused deputy" problem by ensuring the request is coming from the expected context. Learn more about [granting access using External IDs](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-user_externalid.html). Click **Next**. @@ -238,7 +238,7 @@ This custom role acts as a bridge, allowing C1 to securely access your child acc #### Grant permission for data sync -Next, you will create an inline policy to define the specific data this role can gather from the child account. These are read-only permissions that enable C1 to securely sync your IAM data. +Next, you will create an inline policy to define the specific data this role can gather from the child account. These are read-only permissions that enable C1.ai to securely sync your IAM data. @@ -308,39 +308,39 @@ Next, you will create an inline policy to define the specific data this role can **Explanation of permissions** - **Core IAM Permissions** These permissions allow C1 to sync your basic identity structure. + **Core IAM Permissions** These permissions allow C1.ai to sync your basic identity structure. - * iam:ListUsers: Allows C1 to retrieve a list of all IAM user accounts. - * iam:ListGroups: Allows C1 to retrieve a list of all IAM groups. - * iam:ListRoles: Allows C1 to retrieve a list of all IAM roles. + * iam:ListUsers: Allows C1.ai to retrieve a list of all IAM user accounts. + * iam:ListGroups: Allows C1.ai to retrieve a list of all IAM groups. + * iam:ListRoles: Allows C1.ai to retrieve a list of all IAM roles. * iam:GetGroup: Required to see which users belong to which groups. ListGroups only provides the group names, while GetGroup identifies the specific members. - * iam:GetRole: Allows C1 to retrieve detailed information about specific roles, including their trust relationships. + * iam:GetRole: Allows C1.ai to retrieve detailed information about specific roles, including their trust relationships. **Access key activity** These permissions populate `access_key_last_used` on each IAM user. Enable **Sync secrets** to also sync each key as its own secret resource with status and per-key activity. - * iam:ListAccessKeys and iam:GetAccessKeyLastUsed: These allow C1 to gather access key metadata, including when each key was last used. This is useful for identifying unused or stale credentials. + * iam:ListAccessKeys and iam:GetAccessKeyLastUsed: These allow C1.ai to gather access key metadata, including when each key was last used. This is useful for identifying unused or stale credentials. - Note that C1 only retrieves metadata for auditing; it does not store or access the secret access keys themselves. + Note that C1.ai only retrieves metadata for auditing; it does not store or access the secret access keys themselves. **Optional: IAM User Console Access** The JSON above includes this permission. It is used only when **Sync IAM User Console Access** (`BATON_SYNC_IAM_USER_CONSOLE_ACCESS`) is enabled. The flag is off by default because it makes one `iam:GetLoginProfile` call per IAM user. - * iam:GetLoginProfile: Allows C1 to see whether each IAM user has a console login profile, and whether a password reset is required. + * iam:GetLoginProfile: Allows C1.ai to see whether each IAM user has a console login profile, and whether a password reset is required. - **Optional: AWS Organizations Support** Include these permissions if you enable the "Enable support for AWS Organizations" checkbox in the C1 UI. + **Optional: AWS Organizations Support** Include these permissions if you enable the "Enable support for AWS Organizations" checkbox in the C1.ai UI. * organizations:ListAccounts: Allows the connector to discover all accounts within your AWS Organization. * organizations:DescribeOrganization: Provides high-level details about your organization to ensure proper mapping. **Optional: Descriptive Account Aliases** - * iam:ListAccountAliases: Include this if you prefer to use human-readable account aliases (for example, "Production-Environment") in the C1 UI instead of 12-digit numeric AWS account IDs. + * iam:ListAccountAliases: Include this if you prefer to use human-readable account aliases (for example, "Production-Environment") in the C1.ai UI instead of 12-digit numeric AWS account IDs. - **Optional: IAM Policies as Resources** Include these permissions if you want C1 to sync IAM managed policies and inline policies as resources, along with their policy documents. See [IAM policies as resources](#iam-policies-as-resources) above. + **Optional: IAM Policies as Resources** Include these permissions if you want C1.ai to sync IAM managed policies and inline policies as resources, along with their policy documents. See [IAM policies as resources](#iam-policies-as-resources) above. - * iam:ListPolicies, iam:GetPolicy, and iam:GetPolicyVersion: Allow C1 to discover managed policies and read the JSON document of each policy's default version. - * iam:ListUserPolicies, iam:ListRolePolicies, and iam:ListGroupPolicies: Allow C1 to discover the inline policies embedded in each IAM user, role, and group. - * iam:GetUserPolicy, iam:GetRolePolicy, and iam:GetGroupPolicy: Allow C1 to read the JSON document of each inline policy. - * iam:ListAttachedUserPolicies, iam:ListAttachedRolePolicies, and iam:ListAttachedGroupPolicies: Allow C1 to see which managed policies are attached to which users, roles, and groups. + * iam:ListPolicies, iam:GetPolicy, and iam:GetPolicyVersion: Allow C1.ai to discover managed policies and read the JSON document of each policy's default version. + * iam:ListUserPolicies, iam:ListRolePolicies, and iam:ListGroupPolicies: Allow C1.ai to discover the inline policies embedded in each IAM user, role, and group. + * iam:GetUserPolicy, iam:GetRolePolicy, and iam:GetGroupPolicy: Allow C1.ai to read the JSON document of each inline policy. + * iam:ListAttachedUserPolicies, iam:ListAttachedRolePolicies, and iam:ListAttachedGroupPolicies: Allow C1.ai to see which managed policies are attached to which users, roles, and groups. If these permissions are omitted, the connector still syncs successfully — policy resources are either skipped or synced without their document contents. @@ -363,13 +363,13 @@ Next, you will create an inline policy to define the specific data this role can Follow these steps to gather the credentials needed for an AWS IAM Identity Center setup of the AWS connector. -#### Get a C1-provided External ID +#### Get a C1.ai-provided External ID AWS [requires the use of External IDs](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-user_externalid.html) when granting third-party access to your AWS account. This security measure prevents the "confused deputy" problem and ensures that only authorized parties can assume the role. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **AWS v2** and click **Add**. @@ -398,7 +398,7 @@ AWS [requires the use of External IDs](https://docs.aws.amazon.com/IAM/latest/Us #### Create a custom IAM role -This setup allows C1 to integrate with AWS IAM Identity Center (formerly SSO). It requires permissions to both read existing user, group, and permission set data, and optionally, to provision new assignments and manage related resources. +This setup allows C1.ai to integrate with AWS IAM Identity Center (formerly SSO). It requires permissions to both read existing user, group, and permission set data, and optionally, to provision new assignments and manage related resources. The permissions policy below is broken into several sections to align with these functions. This allows you to grant only the permissions you need for your use case, following the principle of least privilege. @@ -411,7 +411,7 @@ The permissions policy below is broken into several sections to align with these Navigate to the [IAM Dashboard](https://us-east-1.console.aws.amazon.com/iamv2/home?) and select **Roles** > **Create Role**. - Select **Custom Trust Policy** and paste the following into the Trust Policy JSON editor, replacing `EXTERNAL_ID_FROM_C1_INTEGRATIONS_PAGE` with the External ID from C1. + Select **Custom Trust Policy** and paste the following into the Trust Policy JSON editor, replacing `EXTERNAL_ID_FROM_C1_INTEGRATIONS_PAGE` with the External ID from C1.ai. ```json expandable { @@ -450,7 +450,7 @@ The permissions policy below is broken into several sections to align with these Under **Permissions Policies**, click **Add Permissions** and select **Create Inline Policy**. - This policy provides the necessary permissions for C1 to securely integrate with your AWS IAM Identity Center setup. Below is the full policy, followed by a detailed breakdown of each section. + This policy provides the necessary permissions for C1.ai to securely integrate with your AWS IAM Identity Center setup. Below is the full policy, followed by a detailed breakdown of each section. Switch to the **JSON Editor** tab and paste the following policy into the editor: @@ -600,38 +600,38 @@ The permissions policy below is broken into several sections to align with these ``` **Notes about permissions:** **Section 1: Read-only access (“C1ReadAccess”)** - This group of permissions is the minimum required for C1 to discover and sync your Identity Center users, groups, and permission sets. These are strictly read-only permissions. + This group of permissions is the minimum required for C1.ai to discover and sync your Identity Center users, groups, and permission sets. These are strictly read-only permissions. - `iam:CreateUser`: This permission is required to provision IAM user accounts. - `iam:List..., iam:GetGroup`: These are standard IAM permissions for listing and retrieving users, groups, and roles. They are necessary to identify resources within your AWS account. `iam:GetGroup` provides the members of a group. - `iam:GetRole`: **Recommended**, used to read a role's trust policy when syncing grants for that role. If omitted, the connector logs a warning and skips trust-policy grants for that role instead of failing. - - `identitystore:List...`: These permissions are specific to AWS IAM Identity Center. They allow C1 to list and read information about your users and groups as they are defined within the Identity Center. - - `organizations:ListAccounts`: This permission allows C1 to list all accounts within your AWS Organization. + - `identitystore:List...`: These permissions are specific to AWS IAM Identity Center. They allow C1.ai to list and read information about your users and groups as they are defined within the Identity Center. + - `organizations:ListAccounts`: This permission allows C1.ai to list all accounts within your AWS Organization. - `organizations:DescribeOrganization`: Not currently used by the connector; included for parity with the rest of this policy and to reserve it in case it's needed in the future. - `organizations:ListParents`: **Recommended**, only needed to re-parent accounts onto their Organizational Unit for the Sparse ACLs by-inheritance hierarchy. If omitted, accounts sync flat without OU grouping instead of failing. - `organizations:DescribeAccount`: **Recommended**, enables proactive validation of account status before creating assignments. If omitted, the connector proceeds anyway and surfaces a less clear error for suspended accounts. - - `sso:List..., sso:Describe..., sso:Get...`: These permissions allow C1 to list your permission sets, see how they are assigned to accounts and users, and read the inline and managed IAM policies attached to each permission set. + - `sso:List..., sso:Describe..., sso:Get...`: These permissions allow C1.ai to list your permission sets, see how they are assigned to accounts and users, and read the inline and managed IAM policies attached to each permission set. - `cloudtrail:LookupEvents`: **Optional**, only needed when Organizations support, Identity Center support, and **Sync SSO User Last Login** are all enabled. The JSON above includes it so the connector can read Identity Center sign-in events in that configuration. - `organizations:ListRoots, organizations:ListOrganizationalUnitsForParent`: **Optional**, only needed for the Sparse ACLs Organization Root / Organizational Unit hierarchy (see [Sparse ACLs](#sparse-acls-organizations-and-permission-sets-as-scoped-bindings) above). If omitted, the connector logs a warning and skips the OU hierarchy instead of failing. - - `iam:GetUser, and various iam:List... permissions`: These permissions are necessary for C1 to first retrieve all associated credentials and metadata for an IAM user before a complete deletion can be performed. + - `iam:GetUser, and various iam:List... permissions`: These permissions are necessary for C1.ai to first retrieve all associated credentials and metadata for an IAM user before a complete deletion can be performed. **Section 2: Provisioning access (“C1ProvisionAccess”)** - This group of permissions is only required if you want to provision (create or delete) user assignments in AWS, including managing IAM users directly. For example, if you plan to use C1 to add a user to a group, assign a permission set to a user, create an IAM user, or fully delete an IAM user, you will need to include these permissions. + This group of permissions is only required if you want to provision (create or delete) user assignments in AWS, including managing IAM users directly. For example, if you plan to use C1.ai to add a user to a group, assign a permission set to a user, create an IAM user, or fully delete an IAM user, you will need to include these permissions. - `iam:AddUserToGroup, iam:RemoveUserFromGroup`: These permissions are used to manage IAM group memberships directly. - - `sso:CreateAccountAssignment, sso:DeleteAccountAssignment`: These are the core permissions for provisioning. They allow C1 to add or remove assignments of permission sets to users within your organization. + - `sso:CreateAccountAssignment, sso:DeleteAccountAssignment`: These are the core permissions for provisioning. They allow C1.ai to add or remove assignments of permission sets to users within your organization. - `identitystore:CreateGroupMembership, identitystore:DeleteGroupMembership`: These permissions manage group membership for users and groups defined within the Identity Center. - `identitystore:CreateUser, identitystore:DeleteUser`: Required to provision and deprovision Identity Center user accounts (separate from IAM users). Identity Store has no disable/deactivate operation, so deprovisioning is a hard delete. - `iam:DeleteLoginProfile, iam:DeleteAccessKey, iam:DeleteUser, and other iam:Delete... and iam:Deactivate... actions`: These permissions are required to clean up all credentials and associated policies for an IAM user before the final `iam:DeleteUser` action can be successful. These are required for full user deprovisioning functionality. - `iam:TagUser`: This permission is required to add tags to a newly created IAM user. **Section 3: Access to IAM Identity Center-provisioned roles (“AccessToSSOProvisionedRoles”)** - This group of permissions allows C1 to inspect and manage the AWS-managed roles created by IAM Identity Center in your accounts. This is crucial for understanding how permission sets are being applied. - - `iam:AttachRolePolicy, iam:DeleteRole, etc.`: These are permissions to manage IAM roles. The key detail is the Resource constraint: `arn:aws:iam::*:role/aws-reserved/sso.amazonaws.com/*`. This ensures that C1 can only modify roles created and managed by the AWS IAM Identity Center service itself, preventing it from modifying other roles in your account. Note that read-only access (`iam:GetRole`) is granted separately in Section 1 for all roles. + This group of permissions allows C1.ai to inspect and manage the AWS-managed roles created by IAM Identity Center in your accounts. This is crucial for understanding how permission sets are being applied. + - `iam:AttachRolePolicy, iam:DeleteRole, etc.`: These are permissions to manage IAM roles. The key detail is the Resource constraint: `arn:aws:iam::*:role/aws-reserved/sso.amazonaws.com/*`. This ensures that C1.ai can only modify roles created and managed by the AWS IAM Identity Center service itself, preventing it from modifying other roles in your account. Note that read-only access (`iam:GetRole`) is granted separately in Section 1 for all roles. **Section 4: Other permissions** - These are supporting permissions that enable specific features or functionality. Some of the permissions listed here can be omitted if your particular use case doesn’t require the data they pull in to C1. + These are supporting permissions that enable specific features or functionality. Some of the permissions listed here can be omitted if your particular use case doesn’t require the data they pull in to C1.ai. - `IAMListPermissions`: This section adds supplementary IAM role and managed-policy listing in the management account. Access key activity is provided by `iam:ListAccessKeys` and `iam:GetAccessKeyLastUsed` in the `ConductorOneReadAccess` statement above. - - `sts:AssumeRole`: **This permission is required when AWS Organizations support is enabled and the connector is doing cross-account IAM sync.** That covers two cases: Organizations on with Identity Center off, and Organizations on with Identity Center on plus the "Also sync cross-account IAM" flag turned on. It lets C1 assume the `OrganizationAccountAccessRole` in your child accounts so it can discover and sync resources across your AWS Organization. It can be omitted if AWS Organizations support is disabled, or if Identity Center is on without the cross-account IAM flag. + - `sts:AssumeRole`: **This permission is required when AWS Organizations support is enabled and the connector is doing cross-account IAM sync.** That covers two cases: Organizations on with Identity Center off, and Organizations on with Identity Center on plus the "Also sync cross-account IAM" flag turned on. It lets C1.ai assume the `OrganizationAccountAccessRole` in your child accounts so it can discover and sync resources across your AWS Organization. It can be omitted if AWS Organizations support is disabled, or if Identity Center is on without the cross-account IAM flag. - `iam:GetSAMLProvider`: This is a necessary permission to read the configuration of the SAML provider that AWS IAM Identity Center uses for single sign-on. - - The permissions listed in the `"Sid": "IAMListPermissions"` and `"Sid": "AccessToSSOProvisiondRoles"` sections are required only if you want to use C1 to create assignments in the AWS Organization’s management account. In certain cases, you may also need to add `iam:UpdateSAMLProvider` to these sections. - - `iam:ListAccessKeys` and `iam:GetAccessKeyLastUsed` let C1 report the most recent access key activity on each IAM user. Enable **Sync secrets** to also sync each key as its own secret resource with per-key activity. - - `iam:GetLoginProfile` is only needed when **Sync IAM User Console Access** is enabled. It lets C1 report whether an IAM user has a console password. + - The permissions listed in the `"Sid": "IAMListPermissions"` and `"Sid": "AccessToSSOProvisiondRoles"` sections are required only if you want to use C1.ai to create assignments in the AWS Organization’s management account. In certain cases, you may also need to add `iam:UpdateSAMLProvider` to these sections. + - `iam:ListAccessKeys` and `iam:GetAccessKeyLastUsed` let C1.ai report the most recent access key activity on each IAM user. Enable **Sync secrets** to also sync each key as its own secret resource with per-key activity. + - `iam:GetLoginProfile` is only needed when **Sync IAM User Console Access** is enabled. It lets C1.ai report whether an IAM user has a console password. Click **Review Policy**. @@ -653,17 +653,17 @@ The permissions policy below is broken into several sections to align with these **To complete this task, you'll need:** -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of AWS 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 C1.ai.** - Return to the AWS v2 connector setup page in C1. + Return to the AWS v2 connector setup page in C1.ai. Find the **Settings** area of the page and click **Edit**. @@ -695,12 +695,12 @@ The permissions policy below is broken into several sections to align with these -**Done.** Your AWS connector is now pulling access data into C1. +**Done.** Your AWS connector is now pulling access data into C1.ai. **Follow these instructions to use the Amazon Web Services 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -712,7 +712,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -833,25 +833,25 @@ 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 C1.ai 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 AWS connector to. AWS data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the AWS connector to. AWS data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your AWS connector is now pulling access data into C1. +**Done.** Your AWS connector is now pulling access data into C1.ai. ## Configure the AWS connector using Terraform -**Use the following Terraform script to integrate your AWS instance with C1.** +**Use the following Terraform script to integrate your AWS instance with C1.ai.** -### Step 1: Get C1-provided External ID for AWS IAM Role +### Step 1: Get C1.ai-provided External ID for AWS IAM Role - In C1, click **Connectors** > **AWS Connector**. + In C1.ai, click **Connectors** > **AWS Connector**. Copy and save the **External ID** populated in the **External ID** field. We'll use this in Step 2. diff --git a/baton/azure-devops.mdx b/baton/azure-devops.mdx index 27860baf..e50b8846 100644 --- a/baton/azure-devops.mdx +++ b/baton/azure-devops.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Microsoft Azure DevOps connector" og:title: "Set up a Microsoft Azure DevOps connector" -description: "C1 provides identity governance and just-in-time provisioning for Microsoft Azure DevOps. Integrate your Azure DevOps 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 Microsoft Azure DevOps. Integrate your Azure DevOps instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Microsoft Azure DevOps. Integrate your Azure DevOps instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Microsoft Azure DevOps. Integrate your Azure DevOps instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Microsoft Azure DevOps" --- @@ -33,12 +33,12 @@ visible, but membership changes are made in Entra. For Entra-managed groups, the connector accepts add and remove requests and reports them as successful without changing membership in Azure DevOps or Entra. These groups are assumed to be managed elsewhere — in the Entra admin -center, through another C1 connector that integrates with Entra, or by another +center, through another C1.ai connector that integrates with Entra, or by another process. Reporting requests as successful prevents access reviews and just-in-time access requests from stalling on changes the connector does not perform. -To have C1 manage Entra group membership through this connector, enable +To have C1.ai manage Entra group membership through this connector, enable **Entra group membership provisioning** during setup. Requirements: - OAuth or client secret authentication. Personal Access Tokens do not support @@ -54,7 +54,7 @@ By default, Azure DevOps project-scoped security groups (such as "Contributors" When you enable **Use project RBAC roles**, project-scoped groups are also represented as structured **Project Role Assignment** resources — for example, "Contributor on Project X." This provides a clearer view of project-level access during access reviews and just-in-time requests, with the role and project scope visible directly on the entitlement. -Enabling this option also enables provisioning: C1 can grant and revoke project role assignments, adding or removing members from the underlying Azure DevOps security group. +Enabling this option also enables provisioning: C1.ai can grant and revoke project role assignments, adding or removing members from the underlying Azure DevOps security group. When **Use project RBAC roles** is enabled, project-scoped groups continue to sync as flat group resources as well, alongside the new Project Role Assignment resources. Org-level groups are unaffected and continue to sync as normal group resources. No additional Azure DevOps permissions are required beyond those already configured for group sync and provisioning. @@ -97,7 +97,7 @@ You can authenticate the Azure DevOps connector in three ways: OAuth (interactiv Give the new app a name and select the **Accounts in any organizational directory** option. - Enter whichever redirect URI matches your C1 tenant's domain as a **Web** redirect URI: + Enter whichever redirect URI matches your C1.ai tenant's domain as a **Web** redirect URI: - Default instance: `https://accounts.conductor.one/oauth/callback` - EU data residency instance: `https://accounts.c1eu.ai/oauth/callback` @@ -143,7 +143,7 @@ You can authenticate the Azure DevOps connector in three ways: OAuth (interactiv **Optional — only required for Entra group membership provisioning.** - If you want C1 to grant and revoke memberships on Entra-sourced Azure DevOps + If you want C1.ai to grant and revoke memberships on Entra-sourced Azure DevOps groups (descriptor prefix `aadgp.`), grant this same Entra app the **Microsoft Graph** application permission **`GroupMember.ReadWrite.All`** with admin consent. @@ -217,7 +217,7 @@ Personal Access Token authentication does **not** support Entra group membership provisioning. With PAT auth, grant and revoke requests against Entra-sourced groups (descriptor prefix `aadgp.`) are silent no-ops — the connector accepts the request and returns success without making any API -call. If you need C1 to actually grant or revoke memberships on Entra-sourced +call. If you need C1.ai to actually grant or revoke memberships on Entra-sourced Azure DevOps groups, configure the connector with OAuth ([Option 1](#option-1-register-a-web-application)) or a client secret ([Option 2](#option-2-register-a-service-principal-client-secret)) instead. @@ -231,7 +231,7 @@ Azure DevOps groups, configure the connector with OAuth Click **\+ New Token**. - Give the new token a name, such as "C1", then select the relevant organization and set an expiration date. + Give the new token a name, such as "C1.ai", then select the relevant organization and set an expiration date. Under **Scopes**, select **Custom defined** and set the relevant set of scopes: @@ -263,18 +263,18 @@ Azure DevOps groups, configure the connector with OAuth To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Azure DevOps 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Azure DevOps** and click **Add**. @@ -307,8 +307,8 @@ To complete this task, you'll need: 6. **Optional.** Check **Use project RBAC roles** to enable the Sparse ACL model for project access. Project-scoped groups are also synced as structured Project Role Assignment resources, with role and project context visible on each entitlement. See [Project RBAC](#project-rbac) for details. 7. Click **Save**. 8. Click **Login with OAuth**. - 9. Log in and authorize C1 with your Azure DevOps instance. - 10. You will then be redirected back to the Azure DevOps setup page in C1, where you'll see an authorization message. + 9. Log in and authorize C1.ai with your Azure DevOps instance. + 10. You will then be redirected back to the Azure DevOps setup page in C1.ai, where you'll see an authorization message. If you chose **Client secret**: 1. Enter your Azure DevOps organization URL, tenant ID, client ID, and client secret from [Option 2](#option-2-register-a-service-principal-client-secret). 2. **Optional.** Check the boxes if you want to **Sync teams** or **Sync organizations**. @@ -331,14 +331,14 @@ To complete this task, you'll need: -**Done.** Your Azure DevOps connector is now pulling access data into C1. +**Done.** Your Azure DevOps connector is now pulling access data into C1.ai. **Follow these instructions to use the Azure DevOps 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -348,7 +348,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -547,14 +547,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 C1.ai 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 Azure DevOps connector to. Azure DevOps data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Azure DevOps connector to. Azure DevOps data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Azure DevOps connector is now pulling access data into C1. +**Done.** Your Azure DevOps connector is now pulling access data into C1.ai. diff --git a/baton/azure-infrastructure.mdx b/baton/azure-infrastructure.mdx index d27906f7..d220d12a 100644 --- a/baton/azure-infrastructure.mdx +++ b/baton/azure-infrastructure.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Microsoft Azure Infrastructure connector" -description: "C1 provides identity governance and just-in-time provisioning for Microsoft Azure Infrastructure. Integrate your Azure Infrastructure instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Microsoft Azure Infrastructure. Integrate your Azure Infrastructure instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." og:title: "Set up a Microsoft Azure Infrastructure connector" -og:description: "C1 provides identity governance and just-in-time provisioning for Microsoft Azure Infrastructure. Integrate your Azure Infrastructure instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Microsoft Azure Infrastructure. Integrate your Azure Infrastructure instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Microsoft Azure Infrastructure" --- -**A newer version of this connector is available.** This version of the connector is no longer available for installation. If you're setting up Azure connector with C1 for the first time, go to [Azure](/baton/azure). +**A newer version of this connector is available.** This version of the connector is no longer available for installation. If you're setting up Azure connector with C1.ai for the first time, go to [Azure](/baton/azure). ## Capabilities @@ -48,7 +48,7 @@ A user with at least the **Cloud Application Administrator** permission in Azure Click **New registration**. - Give the application a name, such as "C1", and select the relevant supported account type. You do not need to set a redirect URI. + Give the application a name, such as "C1.ai", and select the relevant supported account type. You do not need to set a redirect URI. Click **Register**. @@ -151,18 +151,18 @@ A user with at least the **Cloud Application Administrator** permission in Azure To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Azure Infrastructure 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Azure Infrastructure** and click **Add**. @@ -229,14 +229,14 @@ To complete this task, you'll need: -**Done.** Your Azure Infrastructure connector is now pulling access data into C1. +**Done.** Your Azure Infrastructure connector is now pulling access data into C1.ai. **Follow these instructions to use the Azure Infrastructure 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -246,7 +246,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -360,14 +360,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 C1.ai 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 Azure Infrastructure connector to. Azure Infrastructure data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Azure Infrastructure connector to. Azure Infrastructure data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Azure Infrastructure connector is now pulling access data into C1. +**Done.** Your Azure Infrastructure connector is now pulling access data into C1.ai. diff --git a/baton/azure.mdx b/baton/azure.mdx index 2ff8a039..3dabd47d 100644 --- a/baton/azure.mdx +++ b/baton/azure.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Microsoft Azure connector" -description: "C1 provides identity governance and just-in-time provisioning for Azure. Integrate your Azure instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for Azure. Integrate your Azure instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." og:title: "Set up a Microsoft Azure connector" -og:description: "C1 provides identity governance and just-in-time provisioning for Azure. Integrate your Azure instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Azure. Integrate your Azure instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "Microsoft Azure" --- @@ -42,7 +42,7 @@ In the Entra admin center, navigate to **App registrations**. Click **\+ New registration**. -Give the application a name, such as "C1", and select the supported account type relevant to your Entra installation. You do not need to set a redirect URL. +Give the application a name, such as "C1.ai", and select the supported account type relevant to your Entra installation. You do not need to set a redirect URL. Click **Register**. @@ -69,7 +69,7 @@ The client secret is generated. Carefully copy and save the **Secret Value**. ### Assign Azure RBAC permissions to the application -Repeat this process for each subscription you want to sync to C1. Alternately, you can grant a Management Group scope encompassing all the desired subscriptions. +Repeat this process for each subscription you want to sync to C1.ai. Alternately, you can grant a Management Group scope encompassing all the desired subscriptions. Management groups are listed on every sync run, regardless of whether any role assignment references one. If the connector's credentials only have **Reader** at the subscription level, that listing is denied and the whole sync fails -- it does not degrade gracefully. Grant **Reader** at the Management Group scope too (instead of, or in addition to, at each subscription below it). @@ -87,7 +87,7 @@ Click **\+ Add** > **Add role assignment**. On the **Role** tab, search for and select the **Reader** role. - If you want to use the C1 connector to provision Azure roles, also grant the **User Access Administrator** role. Then, on the **Conditions** tab, select **Allow user to assign all roles**. + If you want to use the C1.ai connector to provision Azure roles, also grant the **User Access Administrator** role. Then, on the **Conditions** tab, select **Allow user to assign all roles**. Click **Next**. @@ -112,7 +112,7 @@ Click **Review + assign** at the bottom. ### Grant access to provision tenant root scoped role assignments (optional) -If you need C1 to provision role assignments at the Azure **tenant root scope** (`/`) — that is, role assignments that appear as **"Root (inherited)"** throughout your Azure hierarchy — the app requires an additional **User Access Administrator** assignment at that scope. +If you need C1.ai to provision role assignments at the Azure **tenant root scope** (`/`) — that is, role assignments that appear as **"Root (inherited)"** throughout your Azure hierarchy — the app requires an additional **User Access Administrator** assignment at that scope. The **Tenant Root Group** visible in the Azure Portal is a management group, not the actual tenant root scope. Role assignments made there will not grant the necessary permission. This setup must be done using the Azure CLI. @@ -178,18 +178,18 @@ Two additional settings are available in the connector's configuration form: To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Azure 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Azure** and click **Add**. @@ -224,7 +224,7 @@ Paste the directory (tenant) ID into the **Azure tenant ID** field. Click **Save**. -Finally, tell the connector where to find the identities that will be used for this app in C1. +Finally, tell the connector where to find the identities that will be used for this app in C1.ai. 1. In the **Shared identity source** area of the page, click **Edit**. 2. Select your Entra connector. 3. **Optional.** Limit the identities pulled from the connector you selected to only those with a certain entitlement by setting the entitlement. @@ -235,14 +235,14 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Azure connector is now pulling access data into C1. +**Done.** Your Azure connector is now pulling access data into C1.ai. **Follow these instructions to use the Azure 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -252,7 +252,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -350,14 +350,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 C1.ai 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 Azure connector to. Azure data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Azure connector to. Azure data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Azure connector is now pulling access data into C1. +**Done.** Your Azure connector is now pulling access data into C1.ai. diff --git a/baton/bamboo.mdx b/baton/bamboo.mdx index 30fed120..9c9849a9 100644 --- a/baton/bamboo.mdx +++ b/baton/bamboo.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Bamboo connector" og:title: "Set up a Bamboo connector" -description: "C1 provides identity governance for Atlassian Bamboo. Integrate your Bamboo Data Center instance with C1 for unified visibility and governance over administrative and privileged access." -og:description: "C1 provides identity governance for Atlassian Bamboo. Integrate your Bamboo Data Center instance with C1 for unified visibility and governance over administrative and privileged access." +description: "C1.ai provides identity governance for Atlassian Bamboo. Integrate your Bamboo Data Center instance with C1.ai for unified visibility and governance over administrative and privileged access." +og:description: "C1.ai provides identity governance for Atlassian Bamboo. Integrate your Bamboo Data Center instance with C1.ai for unified visibility and governance over administrative and privileged access." sidebarTitle: "Atlassian Bamboo" --- -C1 provides identity governance for Atlassian Bamboo (Data Center / -self-hosted). Integrate your Bamboo instance with C1 for unified visibility and +C1.ai provides identity governance for Atlassian Bamboo (Data Center / +self-hosted). Integrate your Bamboo instance with C1.ai for unified visibility and governance over administrative and privileged access. ## Capabilities diff --git a/baton/bamboohr.mdx b/baton/bamboohr.mdx index 24da91bd..4ef0b5f5 100644 --- a/baton/bamboohr.mdx +++ b/baton/bamboohr.mdx @@ -1,15 +1,15 @@ --- title: "Set up a BambooHR connector" -description: "C1 provides identity governance for BambooHR. Integrate your BambooHR instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance for BambooHR. Integrate your BambooHR instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." og:title: "Set up a BambooHR connector" -og:description: "C1 provides identity governance for BambooHR. Integrate your BambooHR instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance for BambooHR. Integrate your BambooHR instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "BambooHR" --- **This is an updated and improved version of the BambooHR connector!** -If you're setting up BambooHR with C1 for the first time, you're in the right place. +If you're setting up BambooHR with C1.ai for the first time, you're in the right place. ## Capabilities @@ -59,17 +59,17 @@ Configuring the connector requires you to pass in credentials generated in Bambo **To complete this task, you'll need:** -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of BambooHR 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **BambooHR v2** and click **Add**. @@ -98,7 +98,7 @@ Configuring the connector requires you to pass in credentials generated in Bambo Paste the API key into the **API key** field. - (Optional) In the **Custom fields** setting, list any additional BambooHR field names you want synced onto C1 user profiles, beyond the standard set. Use the field aliases from the [BambooHR field-name reference](https://documentation.bamboohr.com/docs/list-of-field-names) (for example, a custom field alias such as `customField4444`). Separate multiple field names with commas. Each custom field is written to the user profile under a `custom_` prefix — for example, a field configured as `customField4444` appears as `custom_customField4444` — so it can never collide with a standard profile attribute. + (Optional) In the **Custom fields** setting, list any additional BambooHR field names you want synced onto C1.ai user profiles, beyond the standard set. Use the field aliases from the [BambooHR field-name reference](https://documentation.bamboohr.com/docs/list-of-field-names) (for example, a custom field alias such as `customField4444`). Separate multiple field names with commas. Each custom field is written to the user profile under a `custom_` prefix — for example, a field configured as `customField4444` appears as `custom_customField4444` — so it can never collide with a standard profile attribute. Click **Save**. @@ -108,12 +108,12 @@ Configuring the connector requires you to pass in credentials generated in Bambo -**Done.** Your BambooHR connector is now pulling access data into C1. +**Done.** Your BambooHR connector is now pulling access data into C1.ai. **Follow these instructions to use the BambooHR 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -125,7 +125,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -215,14 +215,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 C1.ai 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 BambooHR connector to. BambooHR data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the BambooHR connector to. BambooHR data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your BambooHR connector is now pulling access data into C1. +**Done.** Your BambooHR connector is now pulling access data into C1.ai. diff --git a/baton/basecamp.mdx b/baton/basecamp.mdx index 1dcfe754..ea92f361 100644 --- a/baton/basecamp.mdx +++ b/baton/basecamp.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Basecamp connector" og:title: "Set up a Basecamp connector" -description: "C1 provides identity governance for Basecamp. Integrate your Basecamp instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Basecamp. Integrate your Basecamp instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Basecamp. Integrate your Basecamp instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Basecamp. Integrate your Basecamp instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Basecamp" --- -C1 provides identity governance for Basecamp. Integrate your Basecamp -account with C1 for unified visibility and governance over who can access +C1.ai provides identity governance for Basecamp. Integrate your Basecamp +account with C1.ai for unified visibility and governance over who can access your projects. ## Capabilities @@ -61,11 +61,11 @@ The connector exchanges it for short-lived access tokens automatically. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -112,7 +112,7 @@ The connector exchanges it for short-lived access tokens automatically. - **Done.** Your Basecamp connector is now pulling access data into C1. + **Done.** Your Basecamp connector is now pulling access data into C1.ai. @@ -138,6 +138,6 @@ The connector exchanges it for short-lived access tokens automatically. - **Done.** Your Basecamp connector is now pulling access data into C1. + **Done.** Your Basecamp connector is now pulling access data into C1.ai. diff --git a/baton/baton-runner-windows.mdx b/baton/baton-runner-windows.mdx index 9720d03b..0bb7f181 100644 --- a/baton/baton-runner-windows.mdx +++ b/baton/baton-runner-windows.mdx @@ -1,6 +1,6 @@ --- title: Run multiple connectors as a Windows service -og:title: Run multiple connectors as a Windows service - C1 docs +og:title: Run multiple connectors as a Windows service - C1.ai docs og:description: Install and configure baton-runner as a Windows service to run multiple Baton connectors from a single process on Windows Server. description: Install and configure baton-runner as a Windows service to run multiple Baton connectors from a single process on Windows Server. sidebarTitle: Run multiple connectors on Windows @@ -18,7 +18,7 @@ You'll need: - Usernames and passwords for each SQL Server instance you want to sync - The [baton-sql-server](https://github.com/conductorone/baton-sql-server) executable downloaded - The baton-runner installer downloaded -- A C1 connector created for each SQL Server instance — see [Deploy self-hosted connectors](/baton/deploy) +- A C1.ai connector created for each SQL Server instance — see [Deploy self-hosted connectors](/baton/deploy) - A client ID and secret for each connector ## Install baton-runner @@ -59,7 +59,7 @@ For this example, we'll use `sql1.yaml` and `sql2.yaml` for two SQL Server insta -Open each connector YAML file in Notepad and add the following, replacing the values with the connection string and C1 credentials for that instance: +Open each connector YAML file in Notepad and add the following, replacing the values with the connection string and C1.ai credentials for that instance: ```yaml BATON_DSN: server=192.168.1.40;user id=sa;password=YOUR_PASSWORD;port=1434 @@ -188,7 +188,7 @@ C:\ProgramData\ConductorOne\baton-runner\baton-runner.log ``` -In C1, confirm the connectors are syncing. Navigate to each connector and verify data is appearing. +In C1.ai, confirm the connectors are syncing. Navigate to each connector and verify data is appearing. Once syncing is confirmed, change the baton-runner service startup type to **Automatic**. diff --git a/baton/baton-runner.mdx b/baton/baton-runner.mdx index 4dd6e0a5..e12ed28e 100644 --- a/baton/baton-runner.mdx +++ b/baton/baton-runner.mdx @@ -1,6 +1,6 @@ --- title: Baton-runner configuration reference -og:title: Baton-runner configuration reference - C1 docs +og:title: Baton-runner configuration reference - C1.ai docs og:description: Configure baton-runner to run multiple Baton connectors from a single process, with support for multiple secret backends. description: Configure baton-runner to run multiple Baton connectors from a single process, with support for multiple secret backends. sidebarTitle: Baton-runner reference @@ -12,7 +12,7 @@ sidebarTitle: Baton-runner reference ## Download -Download baton-runner from [dist.conductorone.com/C1/baton-runner](https://dist.conductorone.com/ConductorOne/baton-runner). Builds are available for Windows (amd64), macOS (amd64 and arm64), and Linux (amd64 and arm64). +Download baton-runner from [dist.conductorone.com/C1.ai/baton-runner](https://dist.conductorone.com/ConductorOne/baton-runner). Builds are available for Windows (amd64), macOS (amd64 and arm64), and Linux (amd64 and arm64). For step-by-step setup instructions on Windows Server, see [Run multiple connectors as a Windows service](/baton/baton-runner-windows). diff --git a/baton/baton-scim.mdx b/baton/baton-scim.mdx index 7474cdf6..dcd2242d 100644 --- a/baton/baton-scim.mdx +++ b/baton/baton-scim.mdx @@ -264,7 +264,7 @@ After configuring your SCIM connector, you can run it with one of these methods: ### Using command line arguments -Providing your C1 tenant client ID and client secret via flags automatically triggers Continuous Service Mode. This mode is recommended for production deployments. +Providing your C1.ai tenant client ID and client secret via flags automatically triggers Continuous Service Mode. This mode is recommended for production deployments. ```bash # With a built-in service provider diff --git a/baton/baton-sql.mdx b/baton/baton-sql.mdx index 4feea206..09f6669c 100644 --- a/baton/baton-sql.mdx +++ b/baton/baton-sql.mdx @@ -17,7 +17,7 @@ Baton-SQL is a configuration-only connector for SQL databases. Use it for intern - SAP HANA - SQLite - Amazon Redshift -- IBM DB2 (available on request — [contact C1's support team](mailto:support@conductorone.com) for a binary) +- IBM DB2 (available on request — [contact C1.ai's support team](mailto:support@conductorone.com) for a binary) ## Resources @@ -76,7 +76,7 @@ connect: | IBM DB2 | `db2://user:pass@host:50000/dbname` | -IBM DB2 requires a separate binary bundled with IBM's client driver and isn't available from the standard download center. [Contact C1's support team](mailto:support@conductorone.com) to request a DB2-enabled binary. Customers connecting to DB2 are responsible for providing their own IBM Db2 Connect license where required. +IBM DB2 requires a separate binary bundled with IBM's client driver and isn't available from the standard download center. [Contact C1.ai's support team](mailto:support@conductorone.com) to request a DB2-enabled binary. Customers connecting to DB2 are responsible for providing their own IBM Db2 Connect license where required. ## Listing resources @@ -144,7 +144,7 @@ Entitlements define permissions that can be granted to resources. ### Entitlement purpose -The `purpose` field tells C1 how to interpret an entitlement: +The `purpose` field tells C1.ai how to interpret an entitlement: | Purpose | Use for | Example | |---------|---------|---------| @@ -264,7 +264,7 @@ static_entitlements: ### Account provisioning -Create new accounts through C1: +Create new accounts through C1.ai: ```yaml resource_types: @@ -385,7 +385,7 @@ baton resources -f sync.c1z baton grants -f sync.c1z ``` -### Service mode with C1 +### Service mode with C1.ai ```bash baton-sql --config-path ./config.yaml \ @@ -399,8 +399,8 @@ baton-sql --config-path ./config.yaml \ | Flag | Description | |------|-------------| | `--config-path` | Path to YAML configuration file | -| `--client-id` | C1 client ID | -| `--client-secret` | C1 client secret | +| `--client-id` | C1.ai client ID | +| `--client-secret` | C1.ai client secret | | `-f`, `--file` | Path to save sync data (one-shot mode) | | `-p`, `--provisioning` | Enable provisioning actions | | `--log-level` | Logging verbosity (debug, info, warn, error) | diff --git a/baton/beeline.mdx b/baton/beeline.mdx index 516ec95a..eff3ab39 100644 --- a/baton/beeline.mdx +++ b/baton/beeline.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Beeline connector" -description: "C1 provides identity governance for Beeline. Integrate your Beeline instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance for Beeline. Integrate your Beeline instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." og:title: "Set up a Beeline connector" -og:description: "C1 provides identity governance for Beeline. Integrate your Beeline instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance for Beeline. Integrate your Beeline instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Beeline" --- @@ -43,17 +43,17 @@ To set up the Beeline connector, you'll need: **To complete this task, you'll need:** -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Beeline 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Beeline** and click **Add**. @@ -95,12 +95,12 @@ To set up the Beeline connector, you'll need: -**Done.** Your Beeline connector is now pulling access data into C1. +**Done.** Your Beeline connector is now pulling access data into C1.ai. **Follow these instructions to use the Beeline 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -110,7 +110,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -206,14 +206,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 C1.ai 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 Beeline connector to. Beeline data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Beeline connector to. Beeline data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Beeline connector is now pulling access data into C1. +**Done.** Your Beeline connector is now pulling access data into C1.ai. diff --git a/baton/betterstack.mdx b/baton/betterstack.mdx index 5e304eed..0a9fe600 100644 --- a/baton/betterstack.mdx +++ b/baton/betterstack.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Better Stack connector" og:title: "Set up a Better Stack connector" -description: "C1 provides identity governance for Better Stack. Integrate your Better Stack team with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Better Stack. Integrate your Better Stack team with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Better Stack. Integrate your Better Stack team with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Better Stack. Integrate your Better Stack team with C1.ai for unified visibility and governance over user access." sidebarTitle: "Better Stack" --- -C1 provides identity governance for Better Stack. Integrate your Better Stack -team with C1 for unified visibility and governance over who belongs to the team +C1.ai provides identity governance for Better Stack. Integrate your Better Stack +team with C1.ai for unified visibility and governance over who belongs to the team and which roles they hold. ## Capabilities @@ -53,11 +53,11 @@ one team. If you manage more than one team, set up one connector per team. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -102,7 +102,7 @@ one team. If you manage more than one team, set up one connector per team. - **Done.** Your Better Stack connector is now pulling access data into C1. + **Done.** Your Better Stack connector is now pulling access data into C1.ai. @@ -126,6 +126,6 @@ one team. If you manage more than one team, set up one connector per team. - **Done.** Your Better Stack connector is now pulling access data into C1. + **Done.** Your Better Stack connector is now pulling access data into C1.ai. diff --git a/baton/beyondtrust-password-safe.mdx b/baton/beyondtrust-password-safe.mdx index f374af85..25ab3a45 100644 --- a/baton/beyondtrust-password-safe.mdx +++ b/baton/beyondtrust-password-safe.mdx @@ -1,12 +1,12 @@ --- title: "Set up a BeyondTrust Password Safe connector" og:title: "Set up a BeyondTrust Password Safe connector" -description: "C1 provides identity governance for BeyondTrust BeyondInsight + Password Safe. Integrate your Password Safe instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for BeyondTrust BeyondInsight + Password Safe. Integrate your Password Safe instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for BeyondTrust BeyondInsight + Password Safe. Integrate your Password Safe instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for BeyondTrust BeyondInsight + Password Safe. Integrate your Password Safe instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "BeyondTrust Password Safe" --- -C1 provides identity governance for BeyondTrust BeyondInsight + Password Safe (BIPS). Integrate your BIPS instance with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for BeyondTrust BeyondInsight + Password Safe (BIPS). Integrate your BIPS instance with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -28,7 +28,7 @@ Managed accounts are **not API-accessible by default**. A BeyondInsight administ - In BeyondInsight, create an **Application** user dedicated to C1. + In BeyondInsight, create an **Application** user dedicated to C1.ai. @@ -36,11 +36,11 @@ Managed accounts are **not API-accessible by default**. A BeyondInsight administ - Attach an **API Access Policy** to the registration that allows access from the IP range C1 will connect from. If the policy requires a run-as user password, capture it as well. + Attach an **API Access Policy** to the registration that allows access from the IP range C1.ai will connect from. If the policy requires a run-as user password, capture it as well. - Grant the C1 application user the BeyondInsight permissions: **User Accounts Management (Read/Write)**, **Smart Rule Management (Read)**, **Asset Management (Read)**, and Read access to the Smart Rules that scope the managed accounts you want synced. + Grant the C1.ai application user the BeyondInsight permissions: **User Accounts Management (Read/Write)**, **Smart Rule Management (Read)**, **Asset Management (Read)**, and Read access to the Smart Rules that scope the managed accounts you want synced. @@ -68,11 +68,11 @@ Managed accounts are **not API-accessible by default**. A BeyondInsight administ - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -117,7 +117,7 @@ Managed accounts are **not API-accessible by default**. A BeyondInsight administ - **Done.** Your BeyondTrust Password Safe connector is now pulling access data into C1. + **Done.** Your BeyondTrust Password Safe connector is now pulling access data into C1.ai. @@ -140,6 +140,6 @@ Managed accounts are **not API-accessible by default**. A BeyondInsight administ - **Done.** Your BeyondTrust Password Safe connector is now pulling access data into C1. + **Done.** Your BeyondTrust Password Safe connector is now pulling access data into C1.ai. diff --git a/baton/bitbucket-datacenter.mdx b/baton/bitbucket-datacenter.mdx index ff20a03b..f6a0ff79 100644 --- a/baton/bitbucket-datacenter.mdx +++ b/baton/bitbucket-datacenter.mdx @@ -1,8 +1,8 @@ --- title: "Set up an Atlassian Bitbucket Data Center connector" -description: "C1 provides identity governance and just-in-time provisioning for Bitbucket Data Center. Integrate your Bitbucket Data Center instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Bitbucket Data Center. Integrate your Bitbucket Data Center instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." og:title: "Set up an Atlassian Bitbucket Data Center connector" -og:description: "C1 provides identity governance and just-in-time provisioning for Bitbucket Data Center. Integrate your Bitbucket Data Center instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Bitbucket Data Center. Integrate your Bitbucket Data Center instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Atlassian Bitbucket Data Center" --- @@ -30,7 +30,7 @@ Configuring the connector requires you to pass in credentials generated in Bitbu Click **Create token**. - Give the token a name, such as "C1". + Give the token a name, such as "C1.ai". In the **Permissions** section of the page, select these permissions: @@ -52,20 +52,20 @@ Configuring the connector requires you to pass in credentials generated in Bitbu **To complete this task, you'll need:** -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Bitbucket Data Center 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 C1.ai.** Cloud-hosted connector not currently available. **Follow these instructions to use the Bitbucket Data Center](https://github.com/conductorone/baton-bitbucket-datacenter), 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -75,7 +75,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -169,14 +169,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 C1.ai 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 Bitbucket Data Center connector to. Bitbucket Data Center data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Bitbucket Data Center connector to. Bitbucket Data Center data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Bitbucket Data Center connector is now pulling access data into C1. +**Done.** Your Bitbucket Data Center connector is now pulling access data into C1.ai. diff --git a/baton/bitbucket.mdx b/baton/bitbucket.mdx index 1bee30a7..026a8987 100644 --- a/baton/bitbucket.mdx +++ b/baton/bitbucket.mdx @@ -1,8 +1,8 @@ --- title: "Set up an Atlassian Bitbucket connector" -description: "C1 provides identity governance for Bitbucket. Integrate your Bitbucket instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance for Bitbucket. Integrate your Bitbucket instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." og:title: "Set up an Atlassian Bitbucket connector" -og:description: "C1 provides identity governance for Bitbucket. Integrate your Bitbucket instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance for Bitbucket. Integrate your Bitbucket instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Atlassian Bitbucket" --- @@ -30,7 +30,7 @@ Configuring the connector requires you to pass in credentials generated in Bitbu Click **Create API token with scopes**. - Give the API token a name, such as "C1", and set its expiration date. + Give the API token a name, such as "C1.ai", and set its expiration date. Select **Bitbucket** from the list of apps. @@ -67,17 +67,17 @@ Configuring the connector requires you to pass in credentials generated in Bitbu **To complete this task, you'll need:** -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Bitbucket 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Bitbucket** and click **Add**. @@ -116,12 +116,12 @@ Configuring the connector requires you to pass in credentials generated in Bitbu -**Done.** Your Bitbucket connector is now pulling access data into C1. +**Done.** Your Bitbucket connector is now pulling access data into C1.ai. **Follow these instructions to use the Bitbucket 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -131,7 +131,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -225,14 +225,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 C1.ai 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 Bitbucket connector to. Bitbucket data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Bitbucket connector to. Bitbucket data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Bitbucket connector is now pulling access data into C1. +**Done.** Your Bitbucket connector is now pulling access data into C1.ai. diff --git a/baton/bitrise.mdx b/baton/bitrise.mdx index 307ad772..bd6a4bf8 100644 --- a/baton/bitrise.mdx +++ b/baton/bitrise.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Bitrise connector" -description: "C1 provides identity governance for Bitrise. Integrate your Bitrise instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Bitrise. Integrate your Bitrise instance with C1.ai for unified visibility and governance over user access." og:title: "Set up a Bitrise connector" -og:description: "C1 provides identity governance for Bitrise. Integrate your Bitrise instance with C1 for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Bitrise. Integrate your Bitrise instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Bitrise" --- @@ -39,17 +39,17 @@ This connector requires the following scopes: **To complete this task, you'll need:** -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Bitrise 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Bitrise** and click **Add**. @@ -82,22 +82,22 @@ This connector requires the following scopes: -**Done.** Your Bitrise connector is now pulling access data into C1. +**Done.** Your Bitrise connector is now pulling access data into C1.ai. **Follow these instructions to use the Bitrise 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources -[Contact C1's support team](mailto:support@c1.ai) to download the latest version of the connector. +[Contact C1.ai's support team](mailto:support@c1.ai) to download the latest version of the connector. ### Step 1: Set up a new Bitrise connector - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -186,14 +186,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 C1.ai 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 Bitrise connector to. Bitrise data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Bitrise connector to. Bitrise data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Bitrise connector is now pulling access data into C1. +**Done.** Your Bitrise connector is now pulling access data into C1.ai. diff --git a/baton/bitwarden.mdx b/baton/bitwarden.mdx index 7a1b7f5d..5e42de4d 100644 --- a/baton/bitwarden.mdx +++ b/baton/bitwarden.mdx @@ -1,15 +1,15 @@ --- title: "Set up a Bitwarden connector" og:title: "Set up a Bitwarden connector" -description: "C1 provides identity governance for Bitwarden. Integrate your Bitwarden organization with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Bitwarden. Integrate your Bitwarden organization with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Bitwarden. Integrate your Bitwarden organization with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Bitwarden. Integrate your Bitwarden organization with C1.ai for unified visibility and governance over user access." sidebarTitle: "Bitwarden" --- {/* stargate: cf-bitwarden-fullimpl-20260605 */} -C1 provides identity governance for Bitwarden. Integrate your Bitwarden -organization with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Bitwarden. Integrate your Bitwarden +organization with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -60,11 +60,11 @@ groups, and collections, so treat the secret as sensitive. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -111,7 +111,7 @@ groups, and collections, so treat the secret as sensitive. - **Done.** Your Bitwarden connector is now pulling access data into C1. + **Done.** Your Bitwarden connector is now pulling access data into C1.ai. @@ -137,6 +137,6 @@ groups, and collections, so treat the secret as sensitive. - **Done.** Your Bitwarden connector is now pulling access data into C1. + **Done.** Your Bitwarden connector is now pulling access data into C1.ai. diff --git a/baton/blackline.mdx b/baton/blackline.mdx index e03724aa..8ae4e31a 100644 --- a/baton/blackline.mdx +++ b/baton/blackline.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Blackline connector" -description: "C1 provides identity governance for Blackline. Integrate your Blackline instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Blackline. Integrate your Blackline instance with C1.ai for unified visibility and governance over user access." og:title: "Set up a Blackline connector" -og:description: "C1 provides identity governance for Blackline. Integrate your Blackline instance with C1 for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Blackline. Integrate your Blackline instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Blackline" --- @@ -67,17 +67,17 @@ The connector uses the following endpoints: **To complete this task, you'll need:** -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Blackline 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Blackline** and click **Add**. @@ -110,22 +110,22 @@ The connector uses the following endpoints: -**Done.** Your Blackline connector is now pulling access data into C1. +**Done.** Your Blackline connector is now pulling access data into C1.ai. **Follow these instructions to use the Blackline 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources -[Contact C1's support team](mailto:support@c1.ai) to download the latest version of the connector. +[Contact C1.ai's support team](mailto:support@c1.ai) to download the latest version of the connector. ### Step 1: Set up a new Blackline connector - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -219,13 +219,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 C1.ai 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 Blackline connector to. Blackline data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Blackline connector to. Blackline data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Blackline connector is now pulling access data into C1. +**Done.** Your Blackline connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/blueworks-live.mdx b/baton/blueworks-live.mdx index 34881d26..cdde5f15 100644 --- a/baton/blueworks-live.mdx +++ b/baton/blueworks-live.mdx @@ -1,8 +1,8 @@ --- title: "Set up IBM Blueworks Live connector" og:title: "Set up IBM Blueworks Live connector" -description: "C1 provides identity governance and just-in-time provisioning for IBM Blueworks Live. Integrate your Blueworks Live 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 IBM Blueworks Live. Integrate your Blueworks Live instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for IBM Blueworks Live. Integrate your Blueworks Live instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for IBM Blueworks Live. Integrate your Blueworks Live instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "IBM Blueworks Live" --- @@ -50,18 +50,18 @@ This connector requires the following scopes: To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Blueworks Live 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Blueworks Live** and click **Add**. @@ -94,24 +94,24 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Blueworks Live connector is now pulling access data into C1. +**Done.** Your Blueworks Live connector is now pulling access data into C1.ai. **Follow these instructions to use the Blueworks Live 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources -[Contact C1's support team](mailto:support@c1.ai) to download the latest version of the connector. +[Contact C1.ai's support team](mailto:support@c1.ai) to download the latest version of the connector. ### Step 1: Set up a new Blueworks Live connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -207,14 +207,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 C1.ai 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 Blueworks Live connector to. Blueworks Live data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Blueworks Live connector to. Blueworks Live data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Blueworks Live connector is now pulling access data into C1. +**Done.** Your Blueworks Live connector is now pulling access data into C1.ai. diff --git a/baton/bonusly.mdx b/baton/bonusly.mdx index 9bd75b8a..fb93f8c1 100644 --- a/baton/bonusly.mdx +++ b/baton/bonusly.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Bonusly connector" og:title: "Set up a Bonusly connector" -description: "C1 provides identity governance for Bonusly. Integrate your Bonusly instance with C1 for unified visibility and governance over employee identities." -og:description: "C1 provides identity governance for Bonusly. Integrate your Bonusly instance with C1 for unified visibility and governance over employee identities." +description: "C1.ai provides identity governance for Bonusly. Integrate your Bonusly instance with C1.ai for unified visibility and governance over employee identities." +og:description: "C1.ai provides identity governance for Bonusly. Integrate your Bonusly instance with C1.ai for unified visibility and governance over employee identities." sidebarTitle: "Bonusly" --- -C1 provides identity governance for Bonusly. Integrate your Bonusly instance -with C1 for unified visibility over the people in your Bonusly workspace. +C1.ai provides identity governance for Bonusly. Integrate your Bonusly instance +with C1.ai for unified visibility over the people in your Bonusly workspace. ## Capabilities @@ -46,11 +46,11 @@ access token. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -94,7 +94,7 @@ access token. - **Done.** Your Bonusly connector is now pulling identity data into C1. + **Done.** Your Bonusly connector is now pulling identity data into C1.ai. @@ -117,6 +117,6 @@ access token. - **Done.** Your Bonusly connector is now pulling identity data into C1. + **Done.** Your Bonusly connector is now pulling identity data into C1.ai. diff --git a/baton/bookstack.mdx b/baton/bookstack.mdx index 65c695cd..c24968d3 100644 --- a/baton/bookstack.mdx +++ b/baton/bookstack.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Bookstack connector" og:title: "Set up a Bookstack connector" -description: "C1 provides identity governance for Bookstack. Integrate your Bookstack instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Bookstack. Integrate your Bookstack instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Bookstack. Integrate your Bookstack instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Bookstack. Integrate your Bookstack instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Bookstack" --- -C1 provides identity governance for Bookstack. Integrate your Bookstack -instance with C1 for unified visibility and governance over who can access your +C1.ai provides identity governance for Bookstack. Integrate your Bookstack +instance with C1.ai for unified visibility and governance over who can access your knowledge base and the roles they hold. ## Capabilities @@ -29,7 +29,7 @@ the connector cannot read users or roles and the sync fails. Bookstack authenticates the REST API with a token pair: a public **Token ID** -and a secret **Token Secret**. C1 takes these as a single value, joined with a +and a secret **Token Secret**. C1.ai takes these as a single value, joined with a colon. @@ -53,7 +53,7 @@ colon. Join the two halves with a single colon, in the order `TokenID:TokenSecret` — for example `aBcDeFgHiJkLmNoPqRsTuVwX:YzAxMjM0NTY3ODlhYmNkZWZnaGlqa2w`. This joined - string is the value C1 needs. + string is the value C1.ai needs. @@ -61,11 +61,11 @@ colon. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -109,7 +109,7 @@ colon. - **Done.** Your Bookstack connector is now pulling access data into C1. + **Done.** Your Bookstack connector is now pulling access data into C1.ai. @@ -136,6 +136,6 @@ colon. - **Done.** Your Bookstack connector is now pulling access data into C1. + **Done.** Your Bookstack connector is now pulling access data into C1.ai. diff --git a/baton/boomi.mdx b/baton/boomi.mdx index f3463643..cc6d80f8 100644 --- a/baton/boomi.mdx +++ b/baton/boomi.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Boomi connector" og:title: "Set up a Boomi connector" -description: "C1 provides identity governance and just-in-time provisioning for Boomi. Integrate your Boomi 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 Boomi. Integrate your Boomi instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for Boomi. Integrate your Boomi instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Boomi. Integrate your Boomi instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "Boomi" --- @@ -28,9 +28,9 @@ The Boomi connector supports [automatic account provisioning](/product/admin/acc Boomi uses two types of role assignments: -**Global Roles**: Assigned to users at the account level, granting permissions across the entire Boomi account. These are managed through the **Roles** resource in C1. +**Global Roles**: Assigned to users at the account level, granting permissions across the entire Boomi account. These are managed through the **Roles** resource in C1.ai. -**Group Roles**: When a user is added to an Account Group, they are assigned one or more specific roles within that group context. These are not roles that belong to the group itself, but rather roles that a specific user has within the context of that group. A single user can have multiple different roles within the same group. Each user-group-role combination is represented as a separate grant in C1 under the **Account Groups** resource type. +**Group Roles**: When a user is added to an Account Group, they are assigned one or more specific roles within that group context. These are not roles that belong to the group itself, but rather roles that a specific user has within the context of that group. A single user can have multiple different roles within the same group. Each user-group-role combination is represented as a separate grant in C1.ai under the **Account Groups** resource type. ## Gather Boomi credentials @@ -82,11 +82,11 @@ For more information about Boomi API tokens, see the [Platform API Tokens docume - 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 C1.ai. - In C1, navigate to **Admin** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Admin** > **Connectors** and click **Add connector**. @@ -129,14 +129,14 @@ For more information about Boomi API tokens, see the [Platform API Tokens docume - **Done.** Your Boomi connector is now pulling access data into C1. + **Done.** Your Boomi connector is now pulling access data into C1.ai. **Follow these instructions to use the Boomi 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -146,7 +146,7 @@ For more information about Boomi API tokens, see the [Platform API Tokens docume - In C1, navigate to **Connectors** > **Add connector**. + In C1.ai, navigate to **Connectors** > **Add connector**. @@ -245,15 +245,15 @@ For more information about Boomi API tokens, see the [Platform API Tokens docume - 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 C1.ai 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 Boomi connector to. Boomi data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the Boomi connector to. Boomi data should be found on the **Entitlements** and **Accounts** tabs. - **Done.** Your Boomi connector is now pulling access data into C1. + **Done.** Your Boomi connector is now pulling access data into C1.ai. diff --git a/baton/box.mdx b/baton/box.mdx index fc730274..6c316c48 100644 --- a/baton/box.mdx +++ b/baton/box.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Box connector" -description: "C1 provides identity governance for Box. Integrate your Box instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance for Box. Integrate your Box instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." og:title: "Set up a Box connector" -og:description: "C1 provides identity governance for Box. Integrate your Box instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance for Box. Integrate your Box instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Box" --- @@ -40,7 +40,7 @@ A user with an administrator role in Box and two-factor authentication set on th Click **Create New App** and select **Custom App**. - Enter a name for your new app, such as "C1", and choose how to categorize the new app. + Enter a name for your new app, such as "C1.ai", and choose how to categorize the new app. When prompted to choose an authentication method for your new app, select **Server Authentication (Client Credentials Grant)**. @@ -133,17 +133,17 @@ A user with an administrator role in Box and two-factor authentication set on 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 C1.ai - Access to the set of Box 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Box** and click **Add**. @@ -179,12 +179,12 @@ A user with an administrator role in Box and two-factor authentication set on th -**That's it!** Your Box connector is now pulling access data into C1. +**That's it!** Your Box connector is now pulling access data into C1.ai. **Follow these instructions to use the Box 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -194,7 +194,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -285,13 +285,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 C1.ai 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 Box connector to. Box data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Box connector to. Box data should be found on the **Entitlements** and **Accounts** tabs. -**That's it!** Your Box connector is now pulling access data into C1. +**That's it!** Your Box connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/breathehr.mdx b/baton/breathehr.mdx index f4b59db4..059438bf 100644 --- a/baton/breathehr.mdx +++ b/baton/breathehr.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Breathe connector" og:title: "Set up a Breathe connector" -description: "C1 provides identity governance for Breathe. Integrate your Breathe instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Breathe. Integrate your Breathe instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Breathe. Integrate your Breathe instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Breathe. Integrate your Breathe instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Breathe" --- -C1 provides identity governance for Breathe. Integrate your Breathe instance -with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Breathe. Integrate your Breathe instance +with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -76,11 +76,11 @@ employee and department directory. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -124,7 +124,7 @@ employee and department directory. - **Done.** Your Breathe connector is now pulling access data into C1. + **Done.** Your Breathe connector is now pulling access data into C1.ai. @@ -133,7 +133,7 @@ employee and department directory. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -151,7 +151,7 @@ employee and department directory. - Configure C1 credentials and Breathe credentials as environment + Configure C1.ai credentials and Breathe credentials as environment variables: ```bash @@ -174,6 +174,6 @@ employee and department directory. - **Done.** Your Breathe connector is now pulling access data into C1. + **Done.** Your Breathe connector is now pulling access data into C1.ai. diff --git a/baton/brevo.mdx b/baton/brevo.mdx index e03514dc..897a41f4 100644 --- a/baton/brevo.mdx +++ b/baton/brevo.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Brevo connector" og:title: "Set up a Brevo connector" -description: "C1 provides identity governance for Brevo. Integrate your Brevo instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Brevo. Integrate your Brevo instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Brevo. Integrate your Brevo instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Brevo. Integrate your Brevo instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Brevo" --- -C1 provides identity governance for Brevo (formerly Sendinblue). Integrate your -Brevo corporate account with C1 for unified visibility over the people in your +C1.ai provides identity governance for Brevo (formerly Sendinblue). Integrate your +Brevo corporate account with C1.ai for unified visibility over the people in your account, the groups they belong to, and group membership. ## Capabilities @@ -56,11 +56,11 @@ tier to generate an API key with access to the corporate endpoints. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -101,7 +101,7 @@ tier to generate an API key with access to the corporate endpoints. - **Done.** Your Brevo connector is now pulling access data into C1. + **Done.** Your Brevo connector is now pulling access data into C1.ai. @@ -124,6 +124,6 @@ tier to generate an API key with access to the corporate endpoints. - **Done.** Your Brevo connector is now pulling access data into C1. + **Done.** Your Brevo connector is now pulling access data into C1.ai. diff --git a/baton/brex.mdx b/baton/brex.mdx index 34105d87..1326c6be 100644 --- a/baton/brex.mdx +++ b/baton/brex.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Brex connector" og:title: "Set up a Brex connector" -description: "C1 provides identity governance and just-in-time provisioning for Brex. Integrate your Brex 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 Brex. Integrate your Brex instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for Brex. Integrate your Brex instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Brex. Integrate your Brex instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "Brex" --- @@ -43,7 +43,7 @@ To configure the Brex connector, you need administrator permissions in Brex. - Create API credentials for C1: + Create API credentials for C1.ai: 1. Create a new API key or token named `C1` 2. Grant the required scopes or permissions @@ -55,11 +55,11 @@ To configure the Brex connector, you need administrator permissions in Brex. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -105,13 +105,13 @@ To configure the Brex connector, you need administrator permissions in Brex. - **Done.** Your Brex connector is now pulling access data into C1. + **Done.** Your Brex connector is now pulling access data into C1.ai. Follow these instructions to use the [Brex](https://github.com/conductorone/baton-brex) 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. + When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1.ai, automatically syncing and uploading data at regular intervals. ### Resources @@ -124,7 +124,7 @@ To configure the Brex connector, you need administrator permissions in Brex. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -218,15 +218,15 @@ To configure the Brex connector, you need administrator permissions in Brex. - 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 C1.ai 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 Brex connector to. Brex data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the Brex connector to. Brex data should be found on the **Entitlements** and **Accounts** tabs. - **Done.** Your Brex connector is now pulling access data into C1. + **Done.** Your Brex connector is now pulling access data into C1.ai. diff --git a/baton/bridge-client.mdx b/baton/bridge-client.mdx index fcade5a9..e5625766 100644 --- a/baton/bridge-client.mdx +++ b/baton/bridge-client.mdx @@ -1,47 +1,47 @@ --- -title: "Set up a C1 bridge" -og:title: "Set up a C1 bridge" -description: "Connect on-prem appliances to C1 over a secure tunnel. The bridge agent dials out from your environment to C1 and forwards incoming connections to local TCP backends, so self-hosted services can be reached without inbound network exposure." -og:description: "Connect on-prem appliances to C1 over a secure tunnel. The bridge agent dials out from your environment to C1 and forwards incoming connections to local TCP backends, so self-hosted services can be reached without inbound network exposure." +title: "Set up a C1.ai bridge" +og:title: "Set up a C1.ai bridge" +description: "Connect on-prem appliances to C1.ai over a secure tunnel. The bridge agent dials out from your environment to C1.ai and forwards incoming connections to local TCP backends, so self-hosted services can be reached without inbound network exposure." +og:description: "Connect on-prem appliances to C1.ai over a secure tunnel. The bridge agent dials out from your environment to C1.ai and forwards incoming connections to local TCP backends, so self-hosted services can be reached without inbound network exposure." sidebarTitle: "Bridge" --- The bridge is a long-running agent, not a sync connector. It dials *out* -from your environment to C1 and relays incoming connections -from C1 to one or more local TCP backends. Use it when a self-hosted -service needs to be reachable from C1 without opening inbound firewall +from your environment to C1.ai and relays incoming connections +from C1.ai to one or more local TCP backends. Use it when a self-hosted +service needs to be reachable from C1.ai without opening inbound firewall rules or publishing the service to the public internet. -Bridges are configured in C1 under **Settings > Bridges**. +Bridges are configured in C1.ai under **Settings > Bridges**. ## Capabilities | Capability | Supported | | :--- | :--- | -| Outbound tunnel from your network to C1 | | +| Outbound tunnel from your network to C1.ai | | | OAuth 2.0 Client Credentials (`private_key_jwt`) authentication | | | Multiple local services per bridge (up to 32) | | | External secrets via HashiCorp Vault (KV v1 / v2) | | | YAML or env-only configuration | | -The bridge authenticates to C1 via OAuth 2.0 Client Credentials +The bridge authenticates to C1.ai via OAuth 2.0 Client Credentials with `private_key_jwt`. It periodically refreshes the bearer token and pushes the new token into the tunnel's keepalive metadata so the -C1 relay re-authenticates on every ping. Services advertised -by the bridge appear on the bridge's detail page in the C1 UI +C1.ai relay re-authenticates on every ping. Services advertised +by the bridge appear on the bridge's detail page in the C1.ai UI once the agent connects. -## Create a bridge in C1 +## Create a bridge in C1.ai -To complete this task, you'll need the **Connector Administrator** or **Super Administrator** role in C1 (specifically the `IamV1TunnelCredentialsServiceCreateBridge` and `IamV1TunnelCredentialsServiceCreateBridgeCredential` capabilities — the first creates the bridge, the second issues its credentials). +To complete this task, you'll need the **Connector Administrator** or **Super Administrator** role in C1.ai (specifically the `IamV1TunnelCredentialsServiceCreateBridge` and `IamV1TunnelCredentialsServiceCreateBridgeCredential` capabilities — the first creates the bridge, the second issues its credentials). -In C1, navigate to **Platform** > **Bridges**. +In C1.ai, navigate to **Platform** > **Bridges**. Click **Create bridge**. @@ -58,7 +58,7 @@ On the bridge detail page, find the **Credentials** card and click **Create cred A **Credential created** dialog opens with the **Client ID** and **Client secret**. **Copy and save the client secret immediately — it is only visible once.** Click **Done** to close the dialog. - These credentials are what the bridge agent uses to authenticate back to C1. You'll paste them into the agent's configuration in the next section. + These credentials are what the bridge agent uses to authenticate back to C1.ai. You'll paste them into the agent's configuration in the next section. @@ -83,7 +83,7 @@ To complete this task, you'll need: **Follow these instructions to run the bridge as a Deployment on Kubernetes.** -When running on Kubernetes, the bridge maintains an ongoing connection with C1. The YAML is supplied at runtime via a `Secret` volume (use a `Secret` rather than a `ConfigMap` so the client secret stays encrypted at rest). +When running on Kubernetes, the bridge maintains an ongoing connection with C1.ai. The YAML is supplied at runtime via a `Secret` volume (use a `Secret` rather than a `ConfigMap` so the client secret stays encrypted at rest). #### Step 1: Create the Secret @@ -116,14 +116,14 @@ Each entry under `ports:` accepts the following fields: | :--------------- | :------- | :---------------------------------------------------------------------------------------------------------------------------- | | `listen_port` | yes | Port advertised on the bridge (1–65535). Must be unique within the config. | | `backend` | yes | Local `host:port` the bridge dials for this service. | -| `name` | no | Service name shown in C1. Must be unique when set. | -| `service_type` | metadata | Describes the kind of service so C1 can identify and classify it: `MCP_NATIVE` (a native MCP server), `HOSTED` (a hosted MCP server or other hosted HTTP service), or `RAW` (an opaque TCP service). | +| `name` | no | Service name shown in C1.ai. Must be unique when set. | +| `service_type` | metadata | Describes the kind of service so C1.ai can identify and classify it: `MCP_NATIVE` (a native MCP server), `HOSTED` (a hosted MCP server or other hosted HTTP service), or `RAW` (an opaque TCP service). | | `service_path` | metadata | The service's URL path — for example, `/mcp` for an MCP server. | | `transport_type` | metadata | The service transport — for example, `streamable-http` or `sse` for an MCP server, or `http` for a plain hosted HTTP service. | -`service_type`, `service_path`, and `transport_type` are descriptive metadata: C1 records them and uses them to identify and classify the service you advertise — for example, to recognize an MCP server and its endpoint when you connect it in C1. Set them to match the service you're exposing. +`service_type`, `service_path`, and `transport_type` are descriptive metadata: C1.ai records them and uses them to identify and classify the service you advertise — for example, to recognize an MCP server and its endpoint when you connect it in C1.ai. Set them to match the service you're exposing. -`api_host` is derived automatically from `client_id` and does not need to be set; specify it only for a non-standard C1 host or port. +`api_host` is derived automatically from `client_id` and does not need to be set; specify it only for a non-standard C1.ai host or port. #### Step 2: Create the Deployment @@ -175,7 +175,7 @@ kubectl apply -f bridge.yaml ``` -Back in C1, refresh the bridge's detail page under **Settings** > **Bridges**. The bridge's status changes to **Connected** within a few seconds of the pod starting, and any services it advertises appear in the **Services** section. +Back in C1.ai, refresh the bridge's detail page under **Settings** > **Bridges**. The bridge's status changes to **Connected** within a few seconds of the pod starting, and any services it advertises appear in the **Services** section. You can also tail the bridge's logs locally: @@ -185,7 +185,7 @@ kubectl logs -l app=bridge-client -f -**That's it!** Your bridge is now relaying traffic between C1 and your local services. +**That's it!** Your bridge is now relaying traffic between C1.ai and your local services. @@ -222,9 +222,9 @@ docker run --rm \ For pure env-only mode (no YAML on disk), drop the `-v` bind mount and pass the equivalent `C1_BRIDGE_*` vars with `-e`. See the [Environment variables](#environment-variables) section below for the full list. -Back in C1, refresh the bridge's detail page under **Settings** > **Bridges**. The bridge's status changes to **Connected** within a few seconds of the container starting. +Back in C1.ai, refresh the bridge's detail page under **Settings** > **Bridges**. The bridge's status changes to **Connected** within a few seconds of the container starting. -**That's it!** Your bridge is now relaying traffic between C1 and your local services. +**That's it!** Your bridge is now relaying traffic between C1.ai and your local services. @@ -315,7 +315,7 @@ To rotate or revoke a bridge's credentials later: -In C1, navigate to **Platform** > **Bridges** and click the bridge. +In C1.ai, navigate to **Platform** > **Bridges** and click the bridge. On the bridge's detail page, find the **Credentials** card. @@ -327,4 +327,4 @@ On the bridge's detail page, find the **Credentials** card. ## MCP servers: tool-call access -When the bridge fronts an MCP server, you register that server in C1 separately — selecting this bridge and its advertised service — so C1 can discover and govern its tools. C1 records each tool's name, description, and input schema exactly as your server advertises them and surfaces that text to AI clients during discovery, so clear tool descriptions and schemas on your server determine how reliably an agent finds and calls them. Reaching those tools through C1 then has one more requirement beyond connectivity: the requesting user must be an **app user** of the app the server is registered under, and must hold a grant for the tool. New external apps start with no app users, so a call from an identity that isn't an app user opens an access request instead of executing. App users come from the destination app's account sources. Populate them by linking an entitlement from another app (during registration, or via linked entitlements later in the app's settings), by importing a CSV of app users, or — if the app is backed by a connector — by syncing them from the connector. +When the bridge fronts an MCP server, you register that server in C1.ai separately — selecting this bridge and its advertised service — so C1.ai can discover and govern its tools. C1.ai records each tool's name, description, and input schema exactly as your server advertises them and surfaces that text to AI clients during discovery, so clear tool descriptions and schemas on your server determine how reliably an agent finds and calls them. Reaching those tools through C1.ai then has one more requirement beyond connectivity: the requesting user must be an **app user** of the app the server is registered under, and must hold a grant for the tool. New external apps start with no app users, so a call from an identity that isn't an app user opens an access request instead of executing. App users come from the destination app's account sources. Populate them by linking an entitlement from another app (during registration, or via linked entitlements later in the app's settings), by importing a CSV of app users, or — if the app is backed by a connector — by syncing them from the connector. diff --git a/baton/broadcom-sac.mdx b/baton/broadcom-sac.mdx index bc467242..5c7e39fd 100644 --- a/baton/broadcom-sac.mdx +++ b/baton/broadcom-sac.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Broadcom SAC connector" -description: "C1 provides identity governance for Broadcom SAC. Integrate your Broadcom SAC instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Broadcom SAC. Integrate your Broadcom SAC instance with C1.ai for unified visibility and governance over user access." og:title: "Set up a Broadcom SAC connector" -og:description: "C1 provides identity governance for Broadcom SAC. Integrate your Broadcom SAC instance with C1 for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Broadcom SAC. Integrate your Broadcom SAC instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Broadcom SAC" --- @@ -36,7 +36,7 @@ A user with administrative privileges in the Broadcom SAC tenant must perform th Click **New**. - In the **New API Client** dialog, give the new API client a name (such as "C1") and enter a description, then check **Allow access to Secure Access Cloud management API**. + In the **New API Client** dialog, give the new API client a name (such as "C1.ai") and enter a description, then check **Allow access to Secure Access Cloud management API**. Click **Save**. @@ -53,17 +53,17 @@ A user with administrative privileges in the Broadcom SAC tenant must perform 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 C1.ai - Access to the set of Broadcom SAC 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Broadcom SAC** and click **Add**. @@ -99,12 +99,12 @@ A user with administrative privileges in the Broadcom SAC tenant must perform th -**Done.** Your Broadcom SAC connector is now pulling access data into C1. +**Done.** Your Broadcom SAC connector is now pulling access data into C1.ai. **Follow these instructions to use the Broadcom SAC 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -114,7 +114,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -205,14 +205,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 C1.ai 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 Broadcom SAC connector to. Broadcom SAC data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Broadcom SAC connector to. Broadcom SAC data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Broadcom SAC connector is now pulling access data into C1. +**Done.** Your Broadcom SAC connector is now pulling access data into C1.ai. diff --git a/baton/buddy.mdx b/baton/buddy.mdx index 62ac63d4..2f2af5fe 100644 --- a/baton/buddy.mdx +++ b/baton/buddy.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Buddy connector" og:title: "Set up a Buddy connector" -description: "C1 provides identity governance for Buddy. Integrate your Buddy instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Buddy. Integrate your Buddy instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Buddy. Integrate your Buddy instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Buddy. Integrate your Buddy instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Buddy" --- -C1 provides identity governance for Buddy. Integrate your Buddy -workspace with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Buddy. Integrate your Buddy +workspace with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -56,11 +56,11 @@ turned on before any token can call the API. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -106,7 +106,7 @@ turned on before any token can call the API. - **Done.** Your Buddy connector is now pulling access data into C1. + **Done.** Your Buddy connector is now pulling access data into C1.ai. @@ -133,6 +133,6 @@ turned on before any token can call the API. - **Done.** Your Buddy connector is now pulling access data into C1. + **Done.** Your Buddy connector is now pulling access data into C1.ai. diff --git a/baton/bugsnag.mdx b/baton/bugsnag.mdx index 10c9d109..7c500143 100644 --- a/baton/bugsnag.mdx +++ b/baton/bugsnag.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Bugsnag connector" og:title: "Set up a Bugsnag connector" -description: "C1 provides identity governance for Bugsnag. Integrate your Bugsnag instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Bugsnag. Integrate your Bugsnag instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Bugsnag. Integrate your Bugsnag instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Bugsnag. Integrate your Bugsnag instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Bugsnag" --- -C1 provides identity governance for Bugsnag. Integrate your Bugsnag -organization with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Bugsnag. Integrate your Bugsnag +organization with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -73,11 +73,11 @@ collaborators and teams. The token is sent on every request as - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -119,7 +119,7 @@ collaborators and teams. The token is sent on every request as - **Done.** Your Bugsnag connector is now pulling access data into C1. + **Done.** Your Bugsnag connector is now pulling access data into C1.ai. @@ -145,6 +145,6 @@ collaborators and teams. The token is sent on every request as - **Done.** Your Bugsnag connector is now pulling access data into C1. + **Done.** Your Bugsnag connector is now pulling access data into C1.ai. diff --git a/baton/buildkite.mdx b/baton/buildkite.mdx index e6517e57..30ec2437 100644 --- a/baton/buildkite.mdx +++ b/baton/buildkite.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Buildkite connector" -description: "C1 provides identity governance for Buildkite. Integrate your Buildkite instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance for Buildkite. Integrate your Buildkite instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." og:title: "Set up a Buildkite connector" -og:description: "C1 provides identity governance for Buildkite. Integrate your Buildkite instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance for Buildkite. Integrate your Buildkite instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Buildkite" --- @@ -55,17 +55,17 @@ Next, move on to the instructions for your chosen setup method. **To complete this task, you'll need:** -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Buildkite 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Buildkite** and click **Add**. @@ -107,18 +107,18 @@ Next, move on to the instructions for your chosen setup method. -**Done.** Your Buildkite connector is now pulling access data into C1. +**Done.** Your Buildkite connector is now pulling access data into C1.ai. Follow these instructions to use the [Buildkite](https://github.com/conductorone/baton-buildkite) 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Step 1: Set up a new Buildkite connector - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -209,14 +209,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 C1.ai 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 Buildkite connector to. Buildkite data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the Buildkite connector to. Buildkite data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Buildkite connector is now pulling access data into C1. +**Done.** Your Buildkite connector is now pulling access data into C1.ai. diff --git a/baton/calendly.mdx b/baton/calendly.mdx index 48cdab4f..7330d49d 100644 --- a/baton/calendly.mdx +++ b/baton/calendly.mdx @@ -1,8 +1,8 @@ --- title: "Set up Calendly connector" og:title: "Set up Calendly connector" -description: "C1 provides identity governance and just-in-time provisioning for Calendly. Integrate your Calendly 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 Calendly. Integrate your Calendly instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Calendly. Integrate your Calendly instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Calendly. Integrate your Calendly instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Calendly" --- @@ -34,7 +34,7 @@ Navigate to the **Integrations** page and click **API & Webhooks**. In the **Your personal access tokens** area of the page, click **Generate new token**. -Give the new token a name, such as "C1" and click **Create token**. +Give the new token a name, such as "C1.ai" and click **Create token**. Carefully copy and save the personal access token. @@ -48,18 +48,18 @@ Carefully copy and save the personal access 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 C1.ai - Access to the set of Calendly 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Calendly** and click **Add**. @@ -92,14 +92,14 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Calendly connector is now pulling access data into C1. +**Done.** Your Calendly connector is now pulling access data into C1.ai. **Follow these instructions to use the Calendly 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -109,7 +109,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -202,14 +202,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 C1.ai 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 Calendly connector to. Calendly data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Calendly connector to. Calendly data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Calendly connector is now pulling access data into C1. +**Done.** Your Calendly connector is now pulling access data into C1.ai. diff --git a/baton/canva.mdx b/baton/canva.mdx index 95e0cd3e..a0dfc5a6 100644 --- a/baton/canva.mdx +++ b/baton/canva.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Canva connector" og:title: "Set up a Canva connector" -description: "C1 provides identity governance and just-in-time provisioning for Canva. Integrate your Canva tenant with C1 to run user access reviews, enable access requests, and provision accounts and group memberships." -og:description: "C1 provides identity governance and just-in-time provisioning for Canva. Integrate your Canva tenant with C1 to run user access reviews, enable access requests, and provision accounts and group memberships." +description: "C1.ai provides identity governance and just-in-time provisioning for Canva. Integrate your Canva tenant with C1.ai to run user access reviews, enable access requests, and provision accounts and group memberships." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Canva. Integrate your Canva tenant with C1.ai to run user access reviews, enable access requests, and provision accounts and group memberships." sidebarTitle: "Canva" --- @@ -69,11 +69,11 @@ Admin API is optional and is only required for the `team` resource type. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -121,7 +121,7 @@ Admin API is optional and is only required for the `team` resource type. - **Done.** Your Canva connector is now pulling access data into C1. + **Done.** Your Canva connector is now pulling access data into C1.ai. @@ -146,7 +146,7 @@ Admin API is optional and is only required for the `team` resource type. - **Done.** Your Canva connector is now pulling access data into C1. + **Done.** Your Canva connector is now pulling access data into C1.ai. diff --git a/baton/canvas.mdx b/baton/canvas.mdx index f6bb7dd0..3340741e 100644 --- a/baton/canvas.mdx +++ b/baton/canvas.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Canvas connector" og:title: "Set up a Canvas connector" -description: "C1 provides identity governance for Canvas LMS. Integrate your Canvas instance with C1 for unified visibility and governance over user access to accounts, courses, and enrollments." -og:description: "C1 provides identity governance for Canvas LMS. Integrate your Canvas instance with C1 for unified visibility and governance over user access to accounts, courses, and enrollments." +description: "C1.ai provides identity governance for Canvas LMS. Integrate your Canvas instance with C1.ai for unified visibility and governance over user access to accounts, courses, and enrollments." +og:description: "C1.ai provides identity governance for Canvas LMS. Integrate your Canvas instance with C1.ai for unified visibility and governance over user access to accounts, courses, and enrollments." sidebarTitle: "Canvas" --- -C1 provides identity governance for Canvas LMS by Instructure. Integrate your -Canvas instance with C1 for unified visibility and governance over who has +C1.ai provides identity governance for Canvas LMS by Instructure. Integrate your +Canvas instance with C1.ai for unified visibility and governance over who has access to which accounts, courses, and enrollments. ## Capabilities @@ -23,7 +23,7 @@ The connector reads the users in your Canvas instance, the account hierarchy those users belong to, the courses defined under those accounts, and the enrollments that tie a user to a course. Each course exposes its enrollment roles — for example **Teacher**, **TA**, **Student**, and **Observer** — as -entitlements, and C1 records a grant for every user enrolled in that course +entitlements, and C1.ai records a grant for every user enrolled in that course under a given role. This lets you see which users hold instructor or administrative access through their course and account memberships. @@ -71,11 +71,11 @@ scoped to a single user only sees that user's own data. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -117,7 +117,7 @@ scoped to a single user only sees that user's own data. - **Done.** Your Canvas connector is now pulling access data into C1. + **Done.** Your Canvas connector is now pulling access data into C1.ai. @@ -141,7 +141,7 @@ scoped to a single user only sees that user's own data. - **Done.** Your Canvas connector is now pulling access data into C1. + **Done.** Your Canvas connector is now pulling access data into C1.ai. @@ -157,6 +157,6 @@ scoped to a single user only sees that user's own data. Browse the full catalog of ConductorOne connectors and integrations. - Learn more about identity governance and access management with C1. + Learn more about identity governance and access management with C1.ai. diff --git a/baton/casdoor.mdx b/baton/casdoor.mdx index bfd16395..b9f31aa7 100644 --- a/baton/casdoor.mdx +++ b/baton/casdoor.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Casdoor connector" og:title: "Set up a Casdoor connector" -description: "C1 provides identity governance for Casdoor. Integrate your Casdoor instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Casdoor. Integrate your Casdoor instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Casdoor. Integrate your Casdoor instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Casdoor. Integrate your Casdoor instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Casdoor" --- -C1 provides identity governance for Casdoor. Integrate your Casdoor -instance with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Casdoor. Integrate your Casdoor +instance with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -47,11 +47,11 @@ read the organization's users and groups. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -95,7 +95,7 @@ read the organization's users and groups. - **Done.** Your Casdoor connector is now pulling access data into C1. + **Done.** Your Casdoor connector is now pulling access data into C1.ai. @@ -117,6 +117,6 @@ read the organization's users and groups. - **Done.** Your Casdoor connector is now pulling access data into C1. + **Done.** Your Casdoor connector is now pulling access data into C1.ai. diff --git a/baton/catalyst-center.mdx b/baton/catalyst-center.mdx index 5a9e8224..075c9933 100644 --- a/baton/catalyst-center.mdx +++ b/baton/catalyst-center.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Cisco Catalyst Center connector" og:title: "Set up a Cisco Catalyst Center connector" -description: "C1 provides identity governance for Cisco Catalyst Center. Integrate your Catalyst Center instance with C1 for unified visibility and governance over administrator access." -og:description: "C1 provides identity governance for Cisco Catalyst Center. Integrate your Catalyst Center instance with C1 for unified visibility and governance over administrator access." +description: "C1.ai provides identity governance for Cisco Catalyst Center. Integrate your Catalyst Center instance with C1.ai for unified visibility and governance over administrator access." +og:description: "C1.ai provides identity governance for Cisco Catalyst Center. Integrate your Catalyst Center instance with C1.ai for unified visibility and governance over administrator access." sidebarTitle: "Cisco Catalyst Center" --- -C1 provides identity governance for Cisco Catalyst Center (formerly DNA Center). -Integrate your Catalyst Center instance with C1 for unified visibility and +C1.ai provides identity governance for Cisco Catalyst Center (formerly DNA Center). +Integrate your Catalyst Center instance with C1.ai for unified visibility and governance over administrator accounts and RBAC roles. ## Capabilities @@ -46,11 +46,11 @@ administration area so the connector can list administrators and roles. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -93,7 +93,7 @@ administration area so the connector can list administrators and roles. - **Done.** Your Cisco Catalyst Center connector is now pulling access data into C1. + **Done.** Your Cisco Catalyst Center connector is now pulling access data into C1.ai. @@ -115,6 +115,6 @@ administration area so the connector can list administrators and roles. - **Done.** Your Cisco Catalyst Center connector is now pulling access data into C1. + **Done.** Your Cisco Catalyst Center connector is now pulling access data into C1.ai. diff --git a/baton/celigo.mdx b/baton/celigo.mdx index 7b49bc33..f7a80c0e 100644 --- a/baton/celigo.mdx +++ b/baton/celigo.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Celigo connector" og:title: "Set up a Celigo connector" -description: "C1 provides identity governance and just-in-time provisioning for Celigo. Integrate your Celigo 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 Celigo. Integrate your Celigo instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Celigo. Integrate your Celigo instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Celigo. Integrate your Celigo instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Celigo" --- @@ -32,7 +32,7 @@ In Celigo, navigate to **Resources** > **API tokens**. Click **Create API token**. -Give the new API token a name, such as "C1 integration". +Give the new API token a name, such as "C1.ai integration". In the **Auto purge token** field, select a lifetime for the token. @@ -58,18 +58,18 @@ Carefully and copy and save the new API 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 C1.ai - Access to the set of Celigo 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Celigo** and click **Add**. @@ -105,14 +105,14 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Celigo connector is now pulling access data into C1. +**Done.** Your Celigo connector is now pulling access data into C1.ai. **Follow these instructions to use the Celigo 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -122,7 +122,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -216,14 +216,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 C1.ai 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 Celigo connector to. Celigo data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Celigo connector to. Celigo data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Celigo connector is now pulling access data into C1. +**Done.** Your Celigo connector is now pulling access data into C1.ai. diff --git a/baton/charliehr.mdx b/baton/charliehr.mdx index cbadb177..23729914 100644 --- a/baton/charliehr.mdx +++ b/baton/charliehr.mdx @@ -1,15 +1,15 @@ --- title: "Set up a CharlieHR connector" og:title: "Set up a CharlieHR connector" -description: "C1 provides identity governance for CharlieHR. Integrate your CharlieHR company with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for CharlieHR. Integrate your CharlieHR company with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for CharlieHR. Integrate your CharlieHR company with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for CharlieHR. Integrate your CharlieHR company with C1.ai for unified visibility and governance over user access." sidebarTitle: "CharlieHR" --- {/* stargate: cf-charliehr-20260605 */} -C1 provides identity governance for CharlieHR. Integrate your CharlieHR company -with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for CharlieHR. Integrate your CharlieHR company +with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -47,11 +47,11 @@ grants read access to your company's people data, so treat it as a secret. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -92,7 +92,7 @@ grants read access to your company's people data, so treat it as a secret. - **Done.** Your CharlieHR connector is now pulling access data into C1. + **Done.** Your CharlieHR connector is now pulling access data into C1.ai. @@ -115,6 +115,6 @@ grants read access to your company's people data, so treat it as a secret. - **Done.** Your CharlieHR connector is now pulling access data into C1. + **Done.** Your CharlieHR connector is now pulling access data into C1.ai. diff --git a/baton/charthop.mdx b/baton/charthop.mdx index af41fd34..7108de63 100644 --- a/baton/charthop.mdx +++ b/baton/charthop.mdx @@ -1,8 +1,8 @@ --- title: "Set up a ChartHop connector" og:title: "Set up a ChartHop connector" -description: "C1 provides identity governance and just-in-time provisioning for ChartHop. Integrate your ChartHop 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 ChartHop. Integrate your ChartHop instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for ChartHop. Integrate your ChartHop instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for ChartHop. Integrate your ChartHop instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "ChartHop" --- @@ -36,7 +36,7 @@ To configure the ChartHop connector, you need administrator permissions in Chart - Create API credentials for C1: + Create API credentials for C1.ai: 1. Create a new API key or token named `C1` 2. Grant the required scopes or permissions @@ -48,11 +48,11 @@ To configure the ChartHop connector, you need administrator permissions in Chart - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -99,19 +99,19 @@ To configure the ChartHop connector, you need administrator permissions in Chart - **Done.** Your ChartHop connector is now pulling access data into C1. + **Done.** Your ChartHop connector is now pulling access data into C1.ai. Follow these instructions to use the [ChartHop](https://github.com/conductorone/baton-charthop) 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. + When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1.ai, automatically syncing and uploading data at regular intervals. ### Step 1: Set up a new ChartHop connector - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -206,15 +206,15 @@ To configure the ChartHop connector, you need administrator permissions in Chart - 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 C1.ai 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 ChartHop connector to. ChartHop data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the ChartHop connector to. ChartHop data should be found on the **Entitlements** and **Accounts** tabs. - **Done.** Your ChartHop connector is now pulling access data into C1. + **Done.** Your ChartHop connector is now pulling access data into C1.ai. diff --git a/baton/chatwoot.mdx b/baton/chatwoot.mdx index dd63cb56..93aa83d2 100644 --- a/baton/chatwoot.mdx +++ b/baton/chatwoot.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Chatwoot connector" og:title: "Set up a Chatwoot connector" -description: "C1 provides identity governance for Chatwoot. Integrate your Chatwoot instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Chatwoot. Integrate your Chatwoot instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Chatwoot. Integrate your Chatwoot instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Chatwoot. Integrate your Chatwoot instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Chatwoot" --- -C1 provides identity governance for Chatwoot. Integrate your Chatwoot -instance with C1 for unified visibility and governance over agent access to +C1.ai provides identity governance for Chatwoot. Integrate your Chatwoot +instance with C1.ai for unified visibility and governance over agent access to teams. ## Capabilities @@ -50,11 +50,11 @@ recommended so the token can see every agent and team on the account. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -97,7 +97,7 @@ recommended so the token can see every agent and team on the account. - **Done.** Your Chatwoot connector is now pulling access data into C1. + **Done.** Your Chatwoot connector is now pulling access data into C1.ai. @@ -122,6 +122,6 @@ recommended so the token can see every agent and team on the account. - **Done.** Your Chatwoot connector is now pulling access data into C1. + **Done.** Your Chatwoot connector is now pulling access data into C1.ai. diff --git a/baton/checkly.mdx b/baton/checkly.mdx index 2f28a78c..b8425855 100644 --- a/baton/checkly.mdx +++ b/baton/checkly.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Checkly connector" og:title: "Set up a Checkly connector" -description: "C1 provides identity governance for Checkly. Integrate your Checkly account with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Checkly. Integrate your Checkly account with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Checkly. Integrate your Checkly account with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Checkly. Integrate your Checkly account with C1.ai for unified visibility and governance over user access." sidebarTitle: "Checkly" --- -C1 provides identity governance for Checkly. Integrate your Checkly account -with C1 for unified visibility and governance over the members who can access +C1.ai provides identity governance for Checkly. Integrate your Checkly account +with C1.ai for unified visibility and governance over the members who can access your Checkly monitoring account. ## Capabilities @@ -53,11 +53,11 @@ read the account ID. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -99,7 +99,7 @@ read the account ID. - **Done.** Your Checkly connector is now pulling access data into C1. + **Done.** Your Checkly connector is now pulling access data into C1.ai. @@ -123,6 +123,6 @@ read the account ID. - **Done.** Your Checkly connector is now pulling access data into C1. + **Done.** Your Checkly connector is now pulling access data into C1.ai. diff --git a/baton/circleci.mdx b/baton/circleci.mdx index 04dd0c12..391d7d6d 100644 --- a/baton/circleci.mdx +++ b/baton/circleci.mdx @@ -1,15 +1,15 @@ --- title: "Set up a CircleCI connector" og:title: "Set up a CircleCI connector" -description: "C1 provides identity governance for CircleCI. Integrate your CircleCI organization with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for CircleCI. Integrate your CircleCI organization with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for CircleCI. Integrate your CircleCI organization with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for CircleCI. Integrate your CircleCI organization with C1.ai for unified visibility and governance over user access." sidebarTitle: "CircleCI" --- {/* stargate: cf-circleci-20260605 */} -C1 provides identity governance for CircleCI. Integrate your CircleCI -organization with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for CircleCI. Integrate your CircleCI +organization with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -56,11 +56,11 @@ member list. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -102,7 +102,7 @@ member list. - **Done.** Your CircleCI connector is now pulling access data into C1. + **Done.** Your CircleCI connector is now pulling access data into C1.ai. @@ -126,6 +126,6 @@ member list. - **Done.** Your CircleCI connector is now pulling access data into C1. + **Done.** Your CircleCI connector is now pulling access data into C1.ai. diff --git a/baton/cisco-ise.mdx b/baton/cisco-ise.mdx index 8c63a715..c7ee9e0d 100644 --- a/baton/cisco-ise.mdx +++ b/baton/cisco-ise.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Cisco Ise connector" og:title: "Set up a Cisco Ise connector" -description: "C1 provides identity governance and just-in-time provisioning for Cisco Ise. Integrate your Cisco Ise 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 Cisco Ise. Integrate your Cisco Ise instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for Cisco Ise. Integrate your Cisco Ise instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Cisco Ise. Integrate your Cisco Ise instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "Cisco Ise" --- @@ -57,11 +57,11 @@ To configure the Cisco ISE connector, you need an administrator account with ERS - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -109,13 +109,13 @@ To configure the Cisco ISE connector, you need an administrator account with ERS - **That's it!** Your Cisco Ise connector is now pulling access data into C1. + **That's it!** Your Cisco Ise connector is now pulling access data into C1.ai. Follow these instructions to use the [Cisco Ise](https://github.com/conductorone/baton-cisco-ise) 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. + When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1.ai, automatically syncing and uploading data at regular intervals. ### Resources @@ -128,7 +128,7 @@ To configure the Cisco ISE connector, you need an administrator account with ERS - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -222,15 +222,15 @@ To configure the Cisco ISE connector, you need an administrator account with ERS - 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 C1.ai 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 Cisco Ise connector to. Cisco Ise data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the Cisco Ise connector to. Cisco Ise data should be found on the **Entitlements** and **Accounts** tabs. - **That's it!** Your Cisco Ise connector is now pulling access data into C1. + **That's it!** Your Cisco Ise connector is now pulling access data into C1.ai. diff --git a/baton/cisco-meraki.mdx b/baton/cisco-meraki.mdx index 77dda6c7..5155b56c 100644 --- a/baton/cisco-meraki.mdx +++ b/baton/cisco-meraki.mdx @@ -1,8 +1,8 @@ --- title: "Set up Cisco Meraki connector" og:title: "Set up Cisco Meraki connector" -description: "C1 provides identity governance and just-in-time provisioning for Cisco Meraki. Integrate your Cisco Meraki 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 Cisco Meraki. Integrate your Cisco Meraki instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for Cisco Meraki. Integrate your Cisco Meraki instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Cisco Meraki. Integrate your Cisco Meraki instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "Cisco Meraki" --- @@ -24,25 +24,25 @@ The Cisco Meraki connector supports [automatic account provisioning](/product/ad - Auth users flagged as Meraki administrators are excluded from Auth User sync, so they are not counted twice against dashboard admins. - Revoking an org-access role from an admin who holds no network or tag access deletes that administrator from the organization. Meraki requires every admin to hold organization, network, or tag access, so no-access is not a state an admin can remain in. - Granting the Enterprise Role requires an organization that supports enterprise admins. Organizations without that support reject the grant. -- Account delete is org-scoped. If Meraki still shows the same admin ID in other organizations after the target org membership is gone, C1 treats the requested delete as complete. The CLI delete path (no parent org) refuses to guess when the same admin ID appears in multiple orgs. +- Account delete is org-scoped. If Meraki still shows the same admin ID in other organizations after the target org membership is gone, C1.ai treats the requested delete as complete. The CLI delete path (no parent org) refuses to guess when the same admin ID appears in multiple orgs. ### 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 C1.ai 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 | |-------------|-------------------|-------------| | update_org_admin_profile | `admin_id` (string, required), `org_id` (string, required), `name` (string, required) | Updates the display name of an organization admin. Preserves the admin's existing access level, network access, and tag access. | -Both `admin_id` and `org_id` are Cisco Meraki native identifiers, not email addresses or C1 resource IDs. Read them from the account's profile attributes in C1. +Both `admin_id` and `org_id` are Cisco Meraki native identifiers, not email addresses or C1.ai resource IDs. Read them from the account's profile attributes in C1.ai. Cisco Meraki org admins can have an organization access level of `full`, `read-only`, `enterprise`, `none`, or `camera-sensor`. An admin with `none` access has no organization-level -permissions in Meraki, so C1 does not create a role grant for that admin — granting or revoking +permissions in Meraki, so C1.ai does not create a role grant for that admin — granting or revoking a no-access role would have no effect upstream. Admins with `none` org access show one fewer role grant than admins with real access. The `camera-sensor` level syncs as a role resource and -appears on grants for visibility, but Meraki treats it as read-only on write: C1 cannot +appears on grants for visibility, but Meraki treats it as read-only on write: C1.ai cannot grant `camera-sensor`. Revoking a synced `camera-sensor` grant still runs the normal role revoke path (demote org access to `none`, or delete the admin if they hold no network/tag scope), because revoke keys off the principal's current access rather than the role slug. @@ -50,7 +50,7 @@ scope), because revoke keys off the principal's current access rather than the r **Granting org-access roles:** When you grant the **full** org-access role to an admin who -already has network- or tag-scoped access, C1 clears that scoped access. This matches Meraki +already has network- or tag-scoped access, C1.ai clears that scoped access. This matches Meraki Dashboard: promoting an admin to full organization access replaces their network/tag scope rather than adding to it. Meraki's API rejects attempts to keep both full org access and network/tag scope at the same time. Granting **read-only** or **enterprise** org access @@ -74,7 +74,7 @@ Here is the information you need: Generate the API key from an account that does not authenticate through SAML or SSO. Meraki does not allow SAML users to generate API keys. -To create the key, navigate to **Organization** > **Configure** > **API & Webhooks**, open the **API keys and access** tab, and click **Generate API Key**. The key inherits the permissions of the administrator who generates it, so use an account with full organization access when C1 provisions access. Meraki displays the key once and allows a maximum of two keys per administrator. +To create the key, navigate to **Organization** > **Configure** > **API & Webhooks**, open the **API keys and access** tab, and click **Generate API Key**. The key inherits the permissions of the administrator who generates it, so use an account with full organization access when C1.ai provisions access. Meraki displays the key once and allows a maximum of two keys per administrator. Cisco Meraki rate-limits the API to ten requests per second per organization. @@ -85,18 +85,18 @@ See the Cisco Meraki docs for information on how to acquire credentials: [View t To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Cisco Meraki 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Cisco Meraki** and click **Add**. @@ -130,7 +130,7 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can Open the connector and find the **Resource capabilities** area. Enable **Auth User** and **Network**. - C1 disables these two resource types by default. Until you enable them, no network or auth user data syncs, and deleting an auth user is unavailable. + C1.ai disables these two resource types by default. Until you enable them, no network or auth user data syncs, and deleting an auth user is unavailable. To let users request Cisco Meraki access, open the app's **Entitlements** tab, select an entitlement, and turn on **Make requestable to standard audience** under **Access requests**. @@ -139,24 +139,24 @@ To let users request Cisco Meraki access, open the app's **Entitlements** tab, s -**Done.** Your Cisco Meraki connector is now pulling access data into C1. +**Done.** Your Cisco Meraki connector is now pulling access data into C1.ai. **Follow these instructions to use the Cisco Meraki 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai 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 C1.ai's support team](mailto:support@conductorone.com) to download the latest version of the connector. ### Step 1: Set up a new Cisco Meraki connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -249,14 +249,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 C1.ai 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 Cisco Meraki connector to. Cisco Meraki data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Cisco Meraki connector to. Cisco Meraki data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Cisco Meraki connector is now pulling access data into C1. +**Done.** Your Cisco Meraki connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/cisco-webex.mdx b/baton/cisco-webex.mdx index 581e3e5d..faf7f8ee 100644 --- a/baton/cisco-webex.mdx +++ b/baton/cisco-webex.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Cisco Webex connector" og:title: "Set up a Cisco Webex connector" -description: "C1 provides identity governance for Cisco Webex. Integrate your Cisco Webex organization with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Cisco Webex. Integrate your Cisco Webex organization with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Cisco Webex. Integrate your Cisco Webex organization with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Cisco Webex. Integrate your Cisco Webex organization with C1.ai for unified visibility and governance over user access." sidebarTitle: "Cisco Webex" --- -C1 provides identity governance for Cisco Webex. Integrate your Cisco Webex -organization with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Cisco Webex. Integrate your Cisco Webex +organization with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -55,11 +55,11 @@ token sees only itself. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -103,7 +103,7 @@ token sees only itself. - **Done.** Your Cisco Webex connector is now pulling access data into C1. + **Done.** Your Cisco Webex connector is now pulling access data into C1.ai. @@ -129,6 +129,6 @@ token sees only itself. - **Done.** Your Cisco Webex connector is now pulling access data into C1. + **Done.** Your Cisco Webex connector is now pulling access data into C1.ai. diff --git a/baton/claude-developer-platform.mdx b/baton/claude-developer-platform.mdx index 2e01b965..f0a31979 100644 --- a/baton/claude-developer-platform.mdx +++ b/baton/claude-developer-platform.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Claude Developer Platform connector" og:title: "Set up a Claude Developer Platform connector" -description: "C1 provides identity governance and just-in-time provisioning for Claude Developer Platform. Integrate your Claude Developer Platform 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 Developer Platform. Integrate your Claude Developer Platform instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for Claude Developer Platform. Integrate your Claude Developer Platform instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Claude Developer Platform. Integrate your Claude Developer Platform instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "Claude Developer Platform" --- @@ -56,11 +56,11 @@ To configure the Claude Developer Platform connector, you need administrator per - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -106,13 +106,13 @@ To configure the Claude Developer Platform connector, you need administrator per - **Done.** Your Claude Developer Platform connector is now pulling access data into C1. + **Done.** Your Claude Developer Platform connector is now pulling access data into C1.ai. Follow these instructions to use the [Claude Developer Platform](https://github.com/conductorone/baton-claude-developer-platform) 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. + When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1.ai, automatically syncing and uploading data at regular intervals. ### Resources @@ -125,7 +125,7 @@ To configure the Claude Developer Platform connector, you need administrator per - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -219,15 +219,15 @@ To configure the Claude Developer Platform connector, you need administrator per - 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 C1.ai 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 Developer Platform connector to. Claude Developer Platform data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the Claude Developer Platform connector to. Claude Developer Platform data should be found on the **Entitlements** and **Accounts** tabs. - **Done.** Your Claude Developer Platform connector is now pulling access data into C1. + **Done.** Your Claude Developer Platform connector is now pulling access data into C1.ai. diff --git a/baton/claude-enterprise.mdx b/baton/claude-enterprise.mdx index 923d5571..5ba60452 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: "C1.ai provides identity governance and just-in-time provisioning for Claude Enterprise. Integrate your Claude Enterprise instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Claude Enterprise. Integrate your Claude Enterprise instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "Claude Enterprise" --- @@ -26,13 +26,13 @@ The Claude Enterprise connector syncs the following resources: #### Account creation fields -When provisioning a new Claude Enterprise user account, C1 prompts for the following field: +When provisioning a new Claude Enterprise user account, C1.ai 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 C1 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.ai and is used as the SCIM username. No password is required — Claude Enterprise authenticates users through SSO, so accounts are created without credentials. ## How this connector connects to Claude Enterprise @@ -58,7 +58,7 @@ The connector lists and reconciles directory data entirely from the Compliance A ### Activity feed (Compliance mode) -In Compliance mode the connector also streams Anthropic's audit/activity feed (`/v1/compliance/activities`) as C1 **usage events** — each event records a user acting within an organization (for example, viewing a chat or file). These power last-active and dormant-access signals for access reviews, alongside the access state from the directory sync. The feed reads only when a Compliance Access Key is configured (it is absent in SCIM-only mode) and requires the `read:compliance_activities` scope on the key. +In Compliance mode the connector also streams Anthropic's audit/activity feed (`/v1/compliance/activities`) as C1.ai **usage events** — each event records a user acting within an organization (for example, viewing a chat or file). These power last-active and dormant-access signals for access reviews, alongside the access state from the directory sync. The feed reads only when a Compliance Access Key is configured (it is absent in SCIM-only mode) and requires the `read:compliance_activities` scope on the key. ### SCIM 2.0 (optional — provisioning) @@ -190,7 +190,7 @@ Configure these if you want provisioning in Compliance mode, or if you have no C To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - At least one of the **Compliance Access Key** (recommended) or the **SCIM credentials** generated above (both, if you want Compliance-canonical sync plus provisioning of SCIM-managed groups) - Optionally, the separate **Admin API Key** generated above, if you also want provisioning of console-created ("direct") group membership @@ -198,11 +198,11 @@ To complete this task, you'll need: - **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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -251,7 +251,7 @@ To complete this task, you'll need: - **Done.** Your Claude Enterprise connector is now pulling access data into C1. + **Done.** Your Claude Enterprise connector is now pulling access data into C1.ai. @@ -259,7 +259,7 @@ 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 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -271,7 +271,7 @@ To complete this task, you'll need: - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -375,15 +375,15 @@ To complete this task, you'll need: - 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 C1.ai 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. + Check that the connector data uploaded correctly. In C1.ai, 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. - **Done.** Your Claude Enterprise connector is now pulling access data into C1. + **Done.** Your Claude Enterprise connector is now pulling access data into C1.ai. diff --git a/baton/clerk.mdx b/baton/clerk.mdx index 5efb5207..cd0b907e 100644 --- a/baton/clerk.mdx +++ b/baton/clerk.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Clerk connector" og:title: "Set up a Clerk connector" -description: "C1 provides identity governance for Clerk. Integrate your Clerk instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Clerk. Integrate your Clerk instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Clerk. Integrate your Clerk instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Clerk. Integrate your Clerk instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Clerk" --- @@ -75,11 +75,11 @@ calls, but the key itself is not scoped to read-only access by Clerk. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -120,7 +120,7 @@ calls, but the key itself is not scoped to read-only access by Clerk. - **Done.** Your Clerk connector is now pulling access data into C1. + **Done.** Your Clerk connector is now pulling access data into C1.ai. @@ -129,7 +129,7 @@ calls, but the key itself is not scoped to read-only access by Clerk. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -147,7 +147,7 @@ calls, but the key itself is not scoped to read-only access by Clerk. - Configure C1 credentials and the Clerk Secret Key as environment + Configure C1.ai credentials and the Clerk Secret Key as environment variables: ```bash @@ -169,6 +169,6 @@ calls, but the key itself is not scoped to read-only access by Clerk. - **Done.** Your Clerk connector is now pulling access data into C1. + **Done.** Your Clerk connector is now pulling access data into C1.ai. diff --git a/baton/clickhouse-cloud.mdx b/baton/clickhouse-cloud.mdx index 1c3de3ea..5026fdec 100644 --- a/baton/clickhouse-cloud.mdx +++ b/baton/clickhouse-cloud.mdx @@ -1,8 +1,8 @@ --- title: "Set up ClickHouse connector" og:title: "Set up ClickHouse connector" -description: "C1 provides identity governance and just-in-time provisioning for ClickHouse. Integrate your ClickHouse 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 ClickHouse. Integrate your ClickHouse instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for ClickHouse. Integrate your ClickHouse instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for ClickHouse. Integrate your ClickHouse instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "ClickHouse" --- @@ -59,18 +59,18 @@ See the ClickHouse docs for information on how to acquire credentials: [View the To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of ClickHouse 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **ClickHouse** and click **Add**. @@ -100,24 +100,24 @@ To complete this task, you'll need: -**Done.** Your ClickHouse connector is now pulling access data into C1. +**Done.** Your ClickHouse connector is now pulling access data into C1.ai. **Follow these instructions to use the ClickHouse 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai 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 C1.ai's support team](mailto:support@conductorone.com) to download the latest version of the connector. ### Step 1: Set up a new ClickHouse connector - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -211,14 +211,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 C1.ai 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 ClickHouse connector to. ClickHouse data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the ClickHouse connector to. ClickHouse data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your ClickHouse connector is now pulling access data into C1. +**Done.** Your ClickHouse connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/clickup.mdx b/baton/clickup.mdx index fd14229e..38670c85 100644 --- a/baton/clickup.mdx +++ b/baton/clickup.mdx @@ -1,15 +1,15 @@ --- title: "Set up a ClickUp connector" og:title: "Set up a ClickUp connector" -description: "C1 provides identity governance for ClickUp. Integrate your ClickUp Workspace with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for ClickUp. Integrate your ClickUp Workspace with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for ClickUp. Integrate your ClickUp Workspace with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for ClickUp. Integrate your ClickUp Workspace with C1.ai for unified visibility and governance over user access." sidebarTitle: "ClickUp" --- {/* stargate: cf-clickup-20260605 */} -C1 provides identity governance for ClickUp. Integrate your ClickUp Workspace -with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for ClickUp. Integrate your ClickUp Workspace +with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -57,11 +57,11 @@ secret. The token must belong to a member of the Workspace you want to sync. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -103,7 +103,7 @@ secret. The token must belong to a member of the Workspace you want to sync. - **Done.** Your ClickUp connector is now pulling access data into C1. + **Done.** Your ClickUp connector is now pulling access data into C1.ai. @@ -127,6 +127,6 @@ secret. The token must belong to a member of the Workspace you want to sync. - **Done.** Your ClickUp connector is now pulling access data into C1. + **Done.** Your ClickUp connector is now pulling access data into C1.ai. diff --git a/baton/clockify.mdx b/baton/clockify.mdx index 90293b11..c5fa0eb7 100644 --- a/baton/clockify.mdx +++ b/baton/clockify.mdx @@ -1,15 +1,15 @@ --- title: "Set up a Clockify connector" og:title: "Set up a Clockify connector" -description: "C1 provides identity governance for Clockify. Integrate your Clockify workspace with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Clockify. Integrate your Clockify workspace with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Clockify. Integrate your Clockify workspace with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Clockify. Integrate your Clockify workspace with C1.ai for unified visibility and governance over user access." sidebarTitle: "Clockify" --- {/* stargate: cf-clockify-20260605 */} -C1 provides identity governance for Clockify. Integrate your Clockify workspace -with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Clockify. Integrate your Clockify workspace +with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -21,7 +21,7 @@ with C1 for unified visibility and governance over user access. The connector syncs the members of a Clockify workspace as user identities. Each user carries their workspace role and status, so you can see who holds administrative access. It also syncs the workspace's user groups and who belongs -to each one, so group membership is visible and reviewable in C1. +to each one, so group membership is visible and reviewable in C1.ai. ## Gather Clockify credentials @@ -52,11 +52,11 @@ your Clockify account, so treat it as a secret. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -98,7 +98,7 @@ your Clockify account, so treat it as a secret. - **Done.** Your Clockify connector is now pulling access data into C1. + **Done.** Your Clockify connector is now pulling access data into C1.ai. @@ -122,6 +122,6 @@ your Clockify account, so treat it as a secret. - **Done.** Your Clockify connector is now pulling access data into C1. + **Done.** Your Clockify connector is now pulling access data into C1.ai. diff --git a/baton/close.mdx b/baton/close.mdx index bd9ee4e1..7379ae13 100644 --- a/baton/close.mdx +++ b/baton/close.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Close connector" og:title: "Set up a Close connector" -description: "C1 provides identity governance for Close. Integrate your Close account with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Close. Integrate your Close account with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Close. Integrate your Close account with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Close. Integrate your Close account with C1.ai for unified visibility and governance over user access." sidebarTitle: "Close" --- -C1 provides identity governance for Close. Integrate your Close account with -C1 for unified visibility and governance over who has access to your customer +C1.ai provides identity governance for Close. Integrate your Close account with +C1.ai for unified visibility and governance over who has access to your customer relationship data. ## Capabilities @@ -49,11 +49,11 @@ to an administrator of your Close organization. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -94,7 +94,7 @@ to an administrator of your Close organization. - **Done.** Your Close connector is now pulling access data into C1. + **Done.** Your Close connector is now pulling access data into C1.ai. @@ -117,6 +117,6 @@ to an administrator of your Close organization. - **Done.** Your Close connector is now pulling access data into C1. + **Done.** Your Close connector is now pulling access data into C1.ai. diff --git a/baton/cloudamqp.mdx b/baton/cloudamqp.mdx index fe4992c4..5a65fd58 100644 --- a/baton/cloudamqp.mdx +++ b/baton/cloudamqp.mdx @@ -1,8 +1,8 @@ --- title: "Set up a CloudAMQP connector" og:title: "Set up a CloudAMQP connector" -description: "C1 provides identity governance and just-in-time provisioning for CloudAMQP. Integrate your CloudAMQP 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 CloudAMQP. Integrate your CloudAMQP instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for CloudAMQP. Integrate your CloudAMQP instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for CloudAMQP. Integrate your CloudAMQP instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "CloudAMQP" --- @@ -33,7 +33,7 @@ Configuring the connector requires you to pass in credentials generated in Cloud On the team page, click **API Access**. - In the **Full access keys** area of the page, enter a label for the new API key (such as "C1 integration") in the **Comment** text box. + In the **Full access keys** area of the page, enter a label for the new API key (such as "C1.ai integration") in the **Comment** text box. Click **Generate New Key**. The new key is added to the list of API keys. @@ -50,18 +50,18 @@ Configuring the connector requires you to pass in credentials generated in Cloud To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of CloudAMQP 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **CloudAMQP** and click **Add**. @@ -94,14 +94,14 @@ To complete this task, you'll need: -**Done.** Your CloudAMQP connector is now pulling access data into C1. +**Done.** Your CloudAMQP connector is now pulling access data into C1.ai. **Follow these instructions to use the CloudAMQP 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -111,7 +111,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -201,14 +201,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 C1.ai 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 CloudAMQP connector to. CloudAMQP data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the CloudAMQP connector to. CloudAMQP data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your CloudAMQP connector is now pulling access data into C1. +**Done.** Your CloudAMQP connector is now pulling access data into C1.ai. diff --git a/baton/cloudflare-zero-trust.mdx b/baton/cloudflare-zero-trust.mdx index ad0e0d2b..fd11791a 100644 --- a/baton/cloudflare-zero-trust.mdx +++ b/baton/cloudflare-zero-trust.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Cloudflare Zero Trust connector" og:title: "Set up a Cloudflare Zero Trust connector" -description: "C1 provides identity governance for Cloudflare Zero Trust. Integrate your Cloudflare Zero Trust instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." -og:description: "C1 provides identity governance for Cloudflare Zero Trust. Integrate your Cloudflare Zero Trust instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance for Cloudflare Zero Trust. Integrate your Cloudflare Zero Trust instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance for Cloudflare Zero Trust. Integrate your Cloudflare Zero Trust instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Cloudflare Zero Trust" --- @@ -62,7 +62,7 @@ A user with **Super Administrator** access in Cloudflare Zero Trust must perform 2. Set the appropriate permissions for the API token: - If you want to use C1 to provision Cloudflare Zero Trust groups and roles, set: + If you want to use C1.ai to provision Cloudflare Zero Trust groups and roles, set: - Account -> Account Settings -> Read - Account -> Access: Organizations, Identity Providers, and Groups -> Edit @@ -102,18 +102,18 @@ Next, move on to the instructions for your chosen setup method. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Cloudflare Zero Trust 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Cloudflare Zero Trust** and click **Add**. @@ -148,14 +148,14 @@ To complete this task, you'll need: -**Done.** Your Cloudflare Zero Trust connector is now pulling access data into C1. +**Done.** Your Cloudflare Zero Trust connector is now pulling access data into C1.ai. **Follow these instructions to use the Cloudflare Zero Trust 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -165,7 +165,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -264,14 +264,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 C1.ai 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 Cloudflare Zero Trust connector to. Cloudflare Zero Trust data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Cloudflare Zero Trust connector to. Cloudflare Zero Trust data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Cloudflare Zero Trust connector is now pulling access data into C1. +**Done.** Your Cloudflare Zero Trust connector is now pulling access data into C1.ai. diff --git a/baton/cloudflare.mdx b/baton/cloudflare.mdx index cd530bc9..105ce45e 100644 --- a/baton/cloudflare.mdx +++ b/baton/cloudflare.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Cloudflare connector" og:title: "Set up a Cloudflare connector" -description: "C1 provides identity governance and just-in-time provisioning for Cloudflare. Integrate your Cloudflare 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 Cloudflare. Integrate your Cloudflare instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for Cloudflare. Integrate your Cloudflare instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Cloudflare. Integrate your Cloudflare instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "Cloudflare" --- -**This is an updated and improved version of the Cloudflare connector!** If you're setting up Cloudflare with C1 for the first time, you're in the right place. +**This is an updated and improved version of the Cloudflare connector!** If you're setting up Cloudflare with C1.ai for the first time, you're in the right place. ## Capabilities @@ -68,7 +68,7 @@ If you prefer to authenticate to Cloudflare using the legacy Global API key rath 2. Set the appropriate permissions for the API token: - - To provision Cloudflare access via C1 and run access reviews on your Cloudflare users (includes inviting/removing account members and managing role assignments): + - To provision Cloudflare access via C1.ai and run access reviews on your Cloudflare users (includes inviting/removing account members and managing role assignments): - Account -> Account Settings -> Edit @@ -109,18 +109,18 @@ Next, move on to the instructions for your chosen setup method. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Cloudflare 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Cloudflare v2** and click **Add**. @@ -155,14 +155,14 @@ To complete this task, you'll need: -**Done.** Your Cloudflare connector is now pulling access data into C1. +**Done.** Your Cloudflare connector is now pulling access data into C1.ai. **Follow these instructions to use the Cloudflare 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -172,7 +172,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -271,14 +271,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 C1.ai 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 Cloudflare connector to. Cloudflare data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Cloudflare connector to. Cloudflare data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Cloudflare connector is now pulling access data into C1. +**Done.** Your Cloudflare connector is now pulling access data into C1.ai. diff --git a/baton/cloudsmith.mdx b/baton/cloudsmith.mdx index 92c09aea..e1267336 100644 --- a/baton/cloudsmith.mdx +++ b/baton/cloudsmith.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Cloudsmith connector" og:title: "Set up a Cloudsmith connector" -description: "C1 provides identity governance for Cloudsmith. Integrate your Cloudsmith organization with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Cloudsmith. Integrate your Cloudsmith organization with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Cloudsmith. Integrate your Cloudsmith organization with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Cloudsmith. Integrate your Cloudsmith organization with C1.ai for unified visibility and governance over user access." sidebarTitle: "Cloudsmith" --- -C1 provides identity governance for Cloudsmith. Integrate your Cloudsmith -organization with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Cloudsmith. Integrate your Cloudsmith +organization with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -53,11 +53,11 @@ sees only a partial roster. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -100,7 +100,7 @@ sees only a partial roster. - **Done.** Your Cloudsmith connector is now pulling access data into C1. + **Done.** Your Cloudsmith connector is now pulling access data into C1.ai. @@ -125,6 +125,6 @@ sees only a partial roster. - **Done.** Your Cloudsmith connector is now pulling access data into C1. + **Done.** Your Cloudsmith connector is now pulling access data into C1.ai. diff --git a/baton/codacy.mdx b/baton/codacy.mdx index 9d00302b..d91cdd9a 100644 --- a/baton/codacy.mdx +++ b/baton/codacy.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Codacy connector" og:title: "Set up a Codacy connector" -description: "C1 provides identity governance for Codacy. Integrate your Codacy organization with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Codacy. Integrate your Codacy organization with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Codacy. Integrate your Codacy organization with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Codacy. Integrate your Codacy organization with C1.ai for unified visibility and governance over user access." sidebarTitle: "Codacy" --- -C1 provides identity governance for Codacy. Integrate your Codacy organization -with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Codacy. Integrate your Codacy organization +with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -51,11 +51,11 @@ so treat it as a secret. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -98,7 +98,7 @@ so treat it as a secret. - **Done.** Your Codacy connector is now pulling access data into C1. + **Done.** Your Codacy connector is now pulling access data into C1.ai. @@ -123,6 +123,6 @@ so treat it as a secret. - **Done.** Your Codacy connector is now pulling access data into C1. + **Done.** Your Codacy connector is now pulling access data into C1.ai. diff --git a/baton/codecov.mdx b/baton/codecov.mdx index f1f7ac72..e1794f30 100644 --- a/baton/codecov.mdx +++ b/baton/codecov.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Codecov connector" og:title: "Set up a Codecov connector" -description: "C1 provides identity governance for Codecov. Integrate your Codecov organization with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Codecov. Integrate your Codecov organization with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Codecov. Integrate your Codecov organization with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Codecov. Integrate your Codecov organization with C1.ai for unified visibility and governance over user access." sidebarTitle: "Codecov" --- -C1 provides identity governance for Codecov. Integrate your Codecov -organization with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Codecov. Integrate your Codecov +organization with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -56,11 +56,11 @@ roster. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -107,7 +107,7 @@ roster. - **Done.** Your Codecov connector is now pulling access data into C1. + **Done.** Your Codecov connector is now pulling access data into C1.ai. @@ -136,6 +136,6 @@ roster. - **Done.** Your Codecov connector is now pulling access data into C1. + **Done.** Your Codecov connector is now pulling access data into C1.ai. diff --git a/baton/codefresh.mdx b/baton/codefresh.mdx index 23f494af..b0dd6b9a 100644 --- a/baton/codefresh.mdx +++ b/baton/codefresh.mdx @@ -1,15 +1,15 @@ --- title: "Set up a Codefresh connector" og:title: "Set up a Codefresh connector" -description: "C1 provides identity governance for Codefresh. Integrate your Codefresh account with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Codefresh. Integrate your Codefresh account with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Codefresh. Integrate your Codefresh account with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Codefresh. Integrate your Codefresh account with C1.ai for unified visibility and governance over user access." sidebarTitle: "Codefresh" --- {/* stargate: cf-codefresh-20260605 */} -C1 provides identity governance for Codefresh. Integrate your Codefresh account -with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Codefresh. Integrate your Codefresh account +with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -52,11 +52,11 @@ The connector reads the account the key belongs to automatically (from - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -97,7 +97,7 @@ The connector reads the account the key belongs to automatically (from - **Done.** Your Codefresh connector is now pulling access data into C1. + **Done.** Your Codefresh connector is now pulling access data into C1.ai. @@ -120,6 +120,6 @@ The connector reads the account the key belongs to automatically (from - **Done.** Your Codefresh connector is now pulling access data into C1. + **Done.** Your Codefresh connector is now pulling access data into C1.ai. diff --git a/baton/coder.mdx b/baton/coder.mdx index 7d476a96..be912f37 100644 --- a/baton/coder.mdx +++ b/baton/coder.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Coder connector" og:title: "Set up a Coder connector" -description: "C1 provides identity governance for Coder. Integrate your Coder deployment with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Coder. Integrate your Coder deployment with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Coder. Integrate your Coder deployment with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Coder. Integrate your Coder deployment with C1.ai for unified visibility and governance over user access." sidebarTitle: "Coder" --- -C1 provides identity governance for Coder. Integrate your Coder deployment with -C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Coder. Integrate your Coder deployment with +C1.ai for unified visibility and governance over user access. ## Capabilities @@ -51,11 +51,11 @@ the full user roster. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -98,7 +98,7 @@ the full user roster. - **Done.** Your Coder connector is now pulling access data into C1. + **Done.** Your Coder connector is now pulling access data into C1.ai. @@ -123,6 +123,6 @@ the full user roster. - **Done.** Your Coder connector is now pulling access data into C1. + **Done.** Your Coder connector is now pulling access data into C1.ai. diff --git a/baton/concur.mdx b/baton/concur.mdx index 326aacf4..bbe18d6b 100644 --- a/baton/concur.mdx +++ b/baton/concur.mdx @@ -1,8 +1,8 @@ --- title: "Set up a SAP Concur connector" og:title: "Set up a SAP Concur connector" -description: "C1 provides identity governance and just-in-time provisioning for Concur. Integrate your Concur 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 Concur. Integrate your Concur instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Concur. Integrate your Concur instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Concur. Integrate your Concur instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "SAP Concur" --- @@ -35,7 +35,7 @@ A user with Admin access in Concur must perform this task. Click **+ Create New App**. - Give the new app a name, such as "C1 integration", and add a description. + Give the new app a name, such as "C1.ai integration", and add a description. In the **Grants/Scopes** area of the page, add the following: @@ -53,7 +53,7 @@ A user with Admin access in Concur must perform this task. - `identity.user.enterprise.read` - `spend.user.general.read` - Also add these scopes to give C1 READ/WRITE (provisioning) access: + Also add these scopes to give C1.ai READ/WRITE (provisioning) access: - `user.write` - `user.provision.write` - `identity.user.coreenterprise.writeonly` @@ -96,18 +96,18 @@ A user with Admin access in Concur must perform this task. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Concur 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Concur** and click **Add**. @@ -146,24 +146,24 @@ To complete this task, you'll need: -**Done.** Your Concur connector is now pulling access data into C1. +**Done.** Your Concur connector is now pulling access data into C1.ai. **Follow these instructions to use the Concur 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources -[Contact C1's support team](mailto:support@c1.ai) to download the latest version of the connector. +[Contact C1.ai's support team](mailto:support@c1.ai) to download the latest version of the connector. ### Step 1: Set up a new Concur connector - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -259,14 +259,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 C1.ai 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 Concur connector to. Concur data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Concur connector to. Concur data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Concur connector is now pulling access data into C1. +**Done.** Your Concur connector is now pulling access data into C1.ai. diff --git a/baton/configcat.mdx b/baton/configcat.mdx index 137a28cb..185a6d8d 100644 --- a/baton/configcat.mdx +++ b/baton/configcat.mdx @@ -1,15 +1,15 @@ --- title: "Set up a ConfigCat connector" og:title: "Set up a ConfigCat connector" -description: "C1 provides identity governance for ConfigCat. Integrate your ConfigCat organization with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for ConfigCat. Integrate your ConfigCat organization with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for ConfigCat. Integrate your ConfigCat organization with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for ConfigCat. Integrate your ConfigCat organization with C1.ai for unified visibility and governance over user access." sidebarTitle: "ConfigCat" --- {/* stargate: cf-configcat-20260605 */} -C1 provides identity governance for ConfigCat. Integrate your ConfigCat -organization with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for ConfigCat. Integrate your ConfigCat +organization with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -56,11 +56,11 @@ access to your account, so treat them as secrets. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -103,7 +103,7 @@ access to your account, so treat them as secrets. - **Done.** Your ConfigCat connector is now pulling access data into C1. + **Done.** Your ConfigCat connector is now pulling access data into C1.ai. @@ -128,6 +128,6 @@ access to your account, so treat them as secrets. - **Done.** Your ConfigCat connector is now pulling access data into C1. + **Done.** Your ConfigCat connector is now pulling access data into C1.ai. diff --git a/baton/configure.mdx b/baton/configure.mdx index 2a11bd06..a7e1bd8f 100644 --- a/baton/configure.mdx +++ b/baton/configure.mdx @@ -11,10 +11,10 @@ og:description: "Tune your connector by adjusting what it syncs and how it repor **Important** -This task requires the **Super Administrator** or **Application Administrator** role in C1. +This task requires the **Super Administrator** or **Application Administrator** role in C1.ai. -You can specify which attributes each connector syncs or ignores. This allows you to customize the information that is pulled into C1. +You can specify which attributes each connector syncs or ignores. This allows you to customize the information that is pulled into C1.ai. @@ -26,8 +26,8 @@ You can specify which attributes each connector syncs or ignores. This allows yo Click the **Advanced** tab. Here you can select which attributes to ignore or build a list of specific attributes to sync: - **Sync everything:** Leave **All attributes** (the default option) selected to pull in all available attributes. - - **Blocklist option:** Select **Ignore attributes** and enter those attributes that you want C1 to ignore when syncing. All attributes not specifically listed will be synced. - - **Allowlist option:** Select **Only sync attributes** and enter those attributes that you want C1 to sync. All attributes not specifically listed will be ignored. + - **Blocklist option:** Select **Ignore attributes** and enter those attributes that you want C1.ai to ignore when syncing. All attributes not specifically listed will be synced. + - **Allowlist option:** Select **Only sync attributes** and enter those attributes that you want C1.ai to sync. All attributes not specifically listed will be ignored. Click **Save**. @@ -38,9 +38,9 @@ You can specify which attributes each connector syncs or ignores. This allows yo ## Connector sync pause -C1 automatically pauses a connector’s sync cycle and alerts the connector owner if significant data anomalies are detected (for example, if the number of resources decreases by half between one sync and the next). +C1.ai automatically pauses a connector’s sync cycle and alerts the connector owner if significant data anomalies are detected (for example, if the number of resources decreases by half between one sync and the next). -When a significant drop in resources is detected during a connector sync, C1 does not immediately apply the change as a precaution against unintentionally removing access. A banner explaining that the sync has been paused is displayed. Click **Confirm changes** in the banner on the application’s page to let C1 know that the change is expected and that it’s safe to proceed. +When a significant drop in resources is detected during a connector sync, C1.ai does not immediately apply the change as a precaution against unintentionally removing access. A banner explaining that the sync has been paused is displayed. Click **Confirm changes** in the banner on the application’s page to let C1.ai know that the change is expected and that it’s safe to proceed. ### Turn off connector sync pause diff --git a/baton/confluence-datacenter.mdx b/baton/confluence-datacenter.mdx index 0271ef44..f904443f 100644 --- a/baton/confluence-datacenter.mdx +++ b/baton/confluence-datacenter.mdx @@ -1,8 +1,8 @@ --- title: "Set up an Atlassian Confluence Data Center connector" -description: "C1 provides identity governance and just-in-time provisioning for Confluence Data Center. Integrate your Confluence Data Center instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Confluence Data Center. Integrate your Confluence Data Center instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." og:title: "Set up an Atlassian Confluence Data Center connector" -og:description: "C1 provides identity governance and just-in-time provisioning for Confluence Data Center. Integrate your Confluence Data Center instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Confluence Data Center. Integrate your Confluence Data Center instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Atlassian Confluence Data Center" --- @@ -55,20 +55,20 @@ A user with **Administrator** access in Confluence Data Center must perform this **To complete this task, you'll need:** -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Confluence Data Center 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 C1.ai.** Cloud-hosted connector not currently available. **Follow these instructions to use the Confluence Data Center 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -78,7 +78,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -173,14 +173,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 C1.ai 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 Confluence Data Center connector to. Confluence Data Center data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Confluence Data Center connector to. Confluence Data Center data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Confluence Data Center connector is now pulling access data into C1. +**Done.** Your Confluence Data Center connector is now pulling access data into C1.ai. diff --git a/baton/confluence.mdx b/baton/confluence.mdx index c101a507..9192afb8 100644 --- a/baton/confluence.mdx +++ b/baton/confluence.mdx @@ -1,13 +1,13 @@ --- title: "Set up an Atlassian Confluence connector" -description: "C1 provides identity governance for Confluence. Integrate your Confluence instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance for Confluence. Integrate your Confluence instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." og:title: "Set up an Atlassian Confluence connector" -og:description: "C1 provides identity governance for Confluence. Integrate your Confluence instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance for Confluence. Integrate your Confluence instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Atlassian Confluence" --- -**This is an updated and improved version of the Confluence connector!** If you're setting up Confluence with C1 for the first time, you're in the right place. +**This is an updated and improved version of the Confluence connector!** If you're setting up Confluence with C1.ai for the first time, you're in the right place. ## Capabilities @@ -79,17 +79,17 @@ A user with **Administrator** access in Confluence must perform this task. **To complete this task, you'll need:** -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Confluence 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Confluence v2** and click **Add**. @@ -131,12 +131,12 @@ A user with **Administrator** access in Confluence must perform this task. -**Done.** Your Confluence connector is now pulling access data into C1. +**Done.** Your Confluence connector is now pulling access data into C1.ai. Follow these instructions to use the [Confluence](https://github.com/conductorone/baton-confluence) 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -148,7 +148,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -249,14 +249,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 C1.ai 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 Confluence connector to. Confluence data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Confluence connector to. Confluence data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Confluence connector is now pulling access data into C1. +**Done.** Your Confluence connector is now pulling access data into C1.ai. @@ -267,7 +267,7 @@ Each Confluence Space has its own set of permissions and allowed actions, which The Confluence connector syncs entitlements formed by valid pairs of targets (nouns) and operators (verbs), such as `administer-space` or `read-space`. -When configuring the connector in C1, the noun and verb fields are pre-filled with a suggested subset (`space` noun and 6 common verbs). These suggested values only pre-populate the configuration form — they are **not** automatically applied. If you leave the noun and verb fields empty (or do not set `--noun` / `--verb` flags), the connector syncs **all** available nouns and verbs listed below. +When configuring the connector in C1.ai, the noun and verb fields are pre-filled with a suggested subset (`space` noun and 6 common verbs). These suggested values only pre-populate the configuration form — they are **not** automatically applied. If you leave the noun and verb fields empty (or do not set `--noun` / `--verb` flags), the connector syncs **all** available nouns and verbs listed below. All available targets (nouns): @@ -291,7 +291,7 @@ All available operators (verbs): Not all target-operator (noun-verb) pairs are valid. -To limit what the Confluence connector syncs to C1, use the `--noun` and `--verb` flags when setting up the Confluence connector in self-hosted mode, or configure the noun and verb fields in the C1 UI for cloud-hosted connectors. See the [baton-confluence repo's README](https://github.com/conductorone/baton-confluence) for more information. +To limit what the Confluence connector syncs to C1.ai, use the `--noun` and `--verb` flags when setting up the Confluence connector in self-hosted mode, or configure the noun and verb fields in the C1.ai UI for cloud-hosted connectors. See the [baton-confluence repo's README](https://github.com/conductorone/baton-confluence) for more information. Space permission entitlements are only synced when RBAC mode is **disabled** (the default). When `--use-rbac` is enabled, the connector syncs Space Roles and Space Role Assignments instead. See [RBAC space roles](/baton/confluence#rbac-space-roles) for details. diff --git a/baton/confluent-kafka.mdx b/baton/confluent-kafka.mdx index ad60eabf..7db5916d 100644 --- a/baton/confluent-kafka.mdx +++ b/baton/confluent-kafka.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Confluent Cloud connector" og:title: "Set up a Confluent Cloud connector" -description: "C1 provides identity governance and just-in-time provisioning for Confluent Cloud. Integrate your Confluent Cloud organization 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 Confluent Cloud. Integrate your Confluent Cloud organization with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for Confluent Cloud. Integrate your Confluent Cloud organization with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Confluent Cloud. Integrate your Confluent Cloud organization with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "Confluent Cloud" --- -C1 provides identity governance and just-in-time provisioning for Confluent -Cloud. Integrate your Confluent Cloud organization with C1 to run user access +C1.ai provides identity governance and just-in-time provisioning for Confluent +Cloud. Integrate your Confluent Cloud organization with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access. @@ -47,7 +47,7 @@ already has a Kafka cluster. - **Only user and service account principals are synced.** The connector reads role bindings whose principal is a user or a service account. A binding held by any other principal, including an SSO group mapping or an identity pool, does - not appear in C1 — so access held through SSO group membership or a workload + not appear in C1.ai — so access held through SSO group membership or a workload identity is not visible here. - **API keys are not synced.** Confluent API keys, including those owned by service accounts, are outside the connector's resource model. @@ -57,7 +57,7 @@ already has a Kafka cluster. - **API key authentication only.** The connector authenticates with a Cloud API key. OAuth through Confluent STS is not supported. - **No last-login data.** Confluent's user API does not expose a last-login - timestamp, so C1 cannot report dormant Confluent accounts. + timestamp, so C1.ai cannot report dormant Confluent accounts. - **No account creation.** The connector does not create users, service accounts, or organization invitations. @@ -94,11 +94,11 @@ read access and role-binding writes the connector needs across the organization. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -140,7 +140,7 @@ read access and role-binding writes the connector needs across the organization. - **Done.** Your Confluent Cloud connector is now pulling access data into C1. + **Done.** Your Confluent Cloud connector is now pulling access data into C1.ai. @@ -169,6 +169,6 @@ read access and role-binding writes the connector needs across the organization. - **Done.** Your Confluent Cloud connector is now pulling access data into C1. + **Done.** Your Confluent Cloud connector is now pulling access data into C1.ai. diff --git a/baton/contentful.mdx b/baton/contentful.mdx index 7f70f1cc..1295a775 100644 --- a/baton/contentful.mdx +++ b/baton/contentful.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Contentful connector" og:title: "Set up a Contentful connector" -description: "C1 provides identity governance and just-in-time provisioning for Contentful. Integrate your Contentful 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 Contentful. Integrate your Contentful instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Contentful. Integrate your Contentful instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Contentful. Integrate your Contentful instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Contentful" --- @@ -48,7 +48,7 @@ A user with the **Administrator** role in Contentful must perform this task. In Contentful, navigate to **Settings** > **CMA tokens**. - Click **Create personal access token** and give the new token a name, such as "C1". + Click **Create personal access token** and give the new token a name, such as "C1.ai". Click **Generate**. Carefully copy and save the new token. @@ -62,18 +62,18 @@ A user with the **Administrator** role in Contentful must perform this task. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Contentful 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Contentful** and click **Add**. @@ -109,14 +109,14 @@ To complete this task, you'll need: -**Done.** Your Contentful connector is now pulling access data into C1. +**Done.** Your Contentful connector is now pulling access data into C1.ai. **Follow these instructions to use the Contentful 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -128,7 +128,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -222,14 +222,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 C1.ai 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 Contentful connector to. Contentful data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Contentful connector to. Contentful data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Contentful connector is now pulling access data into C1. +**Done.** Your Contentful connector is now pulling access data into C1.ai. diff --git a/baton/couchdb.mdx b/baton/couchdb.mdx index 6a7b074a..706f83fc 100644 --- a/baton/couchdb.mdx +++ b/baton/couchdb.mdx @@ -1,8 +1,8 @@ --- title: "Set up a CouchDB connector" og:title: "Set up a CouchDB connector" -description: "C1 provides identity governance for CouchDB. Integrate your CouchDB instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for CouchDB. Integrate your CouchDB instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for CouchDB. Integrate your CouchDB instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for CouchDB. Integrate your CouchDB instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "CouchDB" --- @@ -40,18 +40,18 @@ Each setup method requires you to pass in credentials generated in CouchDB. Gath To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of CouchDB 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **CouchDB** and click **Add**. @@ -87,14 +87,14 @@ To complete this task, you'll need: -**Done.** Your CouchDB connector is now pulling access data into C1. +**Done.** Your CouchDB connector is now pulling access data into C1.ai. **Follow these instructions to use the CouchDB 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -104,7 +104,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -196,14 +196,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 C1.ai 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 CouchDB connector to. CouchDB data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the CouchDB connector to. CouchDB data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your CouchDB connector is now pulling access data into C1. +**Done.** Your CouchDB connector is now pulling access data into C1.ai. diff --git a/baton/countly.mdx b/baton/countly.mdx index 3e69a430..b705914c 100644 --- a/baton/countly.mdx +++ b/baton/countly.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Countly connector" og:title: "Set up a Countly connector" -description: "C1 provides identity governance for Countly. Integrate your Countly instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Countly. Integrate your Countly instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Countly. Integrate your Countly instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Countly. Integrate your Countly instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Countly" --- -C1 provides identity governance for Countly. Integrate your Countly -instance with C1 for unified visibility and governance over the dashboard +C1.ai provides identity governance for Countly. Integrate your Countly +instance with C1.ai for unified visibility and governance over the dashboard users in your apps. ## Capabilities @@ -52,11 +52,11 @@ endpoints the connector reads are restricted to global admins. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -101,7 +101,7 @@ endpoints the connector reads are restricted to global admins. - **Done.** Your Countly connector is now pulling access data into C1. + **Done.** Your Countly connector is now pulling access data into C1.ai. @@ -127,6 +127,6 @@ endpoints the connector reads are restricted to global admins. - **Done.** Your Countly connector is now pulling access data into C1. + **Done.** Your Countly connector is now pulling access data into C1.ai. diff --git a/baton/coupa.mdx b/baton/coupa.mdx index d792eda9..8eb2bdc3 100644 --- a/baton/coupa.mdx +++ b/baton/coupa.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Coupa connector" og:title: "Set up a Coupa connector" -description: "C1 provides identity governance for Coupa. Integrate your Coupa instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." -og:description: "C1 provides identity governance for Coupa. Integrate your Coupa instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance for Coupa. Integrate your Coupa instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance for Coupa. Integrate your Coupa instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Coupa" --- -**This is an updated and improved version of the Coupa connector!** If you're setting up Coupa with C1 for the first time, you're in the right place. +**This is an updated and improved version of the Coupa connector!** If you're setting up Coupa with C1.ai for the first time, you're in the right place. ## Capabilities @@ -21,28 +21,28 @@ sidebarTitle: "Coupa" | Roles | | | | Licenses | | | -¹ Account Groups sync is opt-in. To enable it, select **Account Groups** in the resource types to sync when configuring the connector in C1, and ensure the `core.accounting.read` OAuth scope is added to your Coupa OAuth client. +¹ Account Groups sync is opt-in. To enable it, select **Account Groups** in the resource types to sync when configuring the connector in C1.ai, and ensure the `core.accounting.read` OAuth scope is added to your Coupa OAuth client. -The **Licenses** resource surfaces each user's Coupa license assignments — such as Analytics, Purchasing, Sourcing, CLM Advanced, Navi AI Agent, and Intake — as license profiles, so they can be reviewed and provisioned through C1 License Management. +The **Licenses** resource surfaces each user's Coupa license assignments — such as Analytics, Purchasing, Sourcing, CLM Advanced, Navi AI Agent, and Intake — as license profiles, so they can be reviewed and provisioned through C1.ai License Management. ### Account provisioning -C1 can create Coupa user accounts. When you configure account provisioning for the app, map these profile fields: +C1.ai can create Coupa user accounts. When you configure account provisioning for the app, map these profile fields: | Field | Description | |-------|-------------| | First name | First name of the person who will own the Coupa user. | | Last name | Last name of the person who will own the Coupa user. | -| Email | Email address of the Coupa user. Defaults to the C1 user's primary email. | -| Login | Login for the Coupa user. Defaults to the C1 user's username. | +| Email | Email address of the Coupa user. Defaults to the C1.ai user's primary email. | +| Login | Login for the Coupa user. Defaults to the C1.ai user's username. | -Every field is optional to C1. Map **First name** and **Last name** regardless — Coupa has no other source for a new user's name. +Every field is optional to C1.ai. Map **First name** and **Last name** regardless — Coupa has no other source for a new user's name. Accounts are created active. Coupa authenticates through SSO, so no password is set. ### 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 C1.ai 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 | |-------------|-------------------|-------------| @@ -85,7 +85,7 @@ A user with **Admin** access in Coupa must perform this task. - Enter the appropriate login and contact information for your organization. - Select scopes: - **You'll need these scopes to give C1 READ access (syncing access data):** + **You'll need these scopes to give C1.ai READ access (syncing access data):** - core.business_entity.read - core.common.read - core.user_group.read @@ -97,7 +97,7 @@ A user with **Admin** access in Coupa must perform this task. **If you also want to sync Account Groups, add:** - core.accounting.read - **You'll need these scopes to give C1 READ/WRITE access (syncing access data and provisioning access):** + **You'll need these scopes to give C1.ai READ/WRITE access (syncing access data and provisioning access):** - core.business_entity.read - core.common.read - core.user_group.read @@ -137,18 +137,18 @@ A user with **Admin** access in Coupa must perform this task. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Coupa 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Coupa v2** and click **Add**. @@ -187,14 +187,14 @@ To complete this task, you'll need: -**Done.** Your Coupa connector is now pulling access data into C1. +**Done.** Your Coupa connector is now pulling access data into C1.ai. **Follow these instructions to use the Coupa 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -206,7 +206,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -301,14 +301,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 C1.ai 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 Coupa connector to. Coupa data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Coupa connector to. Coupa data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Coupa connector is now pulling access data into C1. +**Done.** Your Coupa connector is now pulling access data into C1.ai. diff --git a/baton/crisp.mdx b/baton/crisp.mdx index dae35897..98976d67 100644 --- a/baton/crisp.mdx +++ b/baton/crisp.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Crisp connector" og:title: "Set up a Crisp connector" -description: "C1 provides identity governance for Crisp. Integrate your Crisp instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Crisp. Integrate your Crisp instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Crisp. Integrate your Crisp instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Crisp. Integrate your Crisp instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Crisp" --- -C1 provides identity governance for Crisp. Integrate your Crisp website with -C1 for unified visibility and governance over the operators who can access your +C1.ai provides identity governance for Crisp. Integrate your Crisp website with +C1.ai for unified visibility and governance over the operators who can access your customer conversations. ## Capabilities @@ -61,11 +61,11 @@ Crisp authenticates the REST API with a token pair — an **identifier** and a - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -110,7 +110,7 @@ Crisp authenticates the REST API with a token pair — an **identifier** and a - **Done.** Your Crisp connector is now pulling access data into C1. + **Done.** Your Crisp connector is now pulling access data into C1.ai. @@ -138,6 +138,6 @@ Crisp authenticates the REST API with a token pair — an **identifier** and a - **Done.** Your Crisp connector is now pulling access data into C1. + **Done.** Your Crisp connector is now pulling access data into C1.ai. diff --git a/baton/crowdstrike.mdx b/baton/crowdstrike.mdx index 368329ff..9845c7f3 100644 --- a/baton/crowdstrike.mdx +++ b/baton/crowdstrike.mdx @@ -1,8 +1,8 @@ --- title: "Set up a CrowdStrike connector" og:title: "Set up a CrowdStrike connector" -description: "C1 provides identity governance for CrowdStrike. Integrate your CrowdStrike 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 for CrowdStrike. Integrate your CrowdStrike instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance for CrowdStrike. Integrate your CrowdStrike instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance for CrowdStrike. Integrate your CrowdStrike instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "CrowdStrike" --- @@ -45,7 +45,7 @@ A user with the **Falcon Administrator** role in CrowdStrike must perform this t Click **+ Add new API client**. - Give the new API client a name, such as "C1 integration" and add a description. + Give the new API client a name, such as "C1.ai integration" and add a description. In the **API SCOPES** section of the page, select the appropriate **User management** scopes: @@ -67,18 +67,18 @@ A user with the **Falcon Administrator** role in CrowdStrike must perform this t To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of CrowdStrike 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **CrowdStrike** and click **Add**. @@ -114,14 +114,14 @@ To complete this task, you'll need: -**Done.** Your CrowdStrike connector is now pulling access data into C1. +**Done.** Your CrowdStrike connector is now pulling access data into C1.ai. **Follow these instructions to use the CrowdStrike 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -133,7 +133,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -228,21 +228,21 @@ 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 C1.ai 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 CrowdStrike connector to. CrowdStrike data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the CrowdStrike connector to. CrowdStrike data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your CrowdStrike connector is now pulling access data into C1. +**Done.** Your CrowdStrike connector is now pulling access data into C1.ai. ## Enable risk score ingestion -The CrowdStrike connector can ingest Falcon identity risk scores and surface them in C1 during access reviews and access request approvals. See [External insights](/product/admin/external-insights) for an overview of where risk data appears. +The CrowdStrike connector can ingest Falcon identity risk scores and surface them in C1.ai during access reviews and access request approvals. See [External insights](/product/admin/external-insights) for an overview of where risk data appears. ### Before you begin @@ -250,7 +250,7 @@ Confirm that: - Your organization has a **CrowdStrike Falcon Identity Protection** license - You have the **Falcon Administrator** role in CrowdStrike -- Your CrowdStrike connector is already set up and syncing in C1 +- Your CrowdStrike connector is already set up and syncing in C1.ai ### Add required API scopes @@ -261,7 +261,7 @@ The CrowdStrike API client you created during connector setup needs additional s Sign into the Falcon console and navigate to **Support** > **API Clients and Keys**. - Find the API client you created for the C1 integration and click to edit it. + Find the API client you created for the C1.ai integration and click to edit it. In the **API SCOPES** section, enable the following scopes: @@ -277,14 +277,14 @@ The CrowdStrike API client you created during connector setup needs additional s ### Risk score ingestion setting -Identity risk scores use the **Identity Risk Score** (`security_insight`) capability, which is opt-in in C1. Once the scopes above are in place and the capability is enabled, the connector syncs risk scores automatically. There is no connector config flag that empties this resource type. +Identity risk scores use the **Identity Risk Score** (`security_insight`) capability, which is opt-in in C1.ai. Once the scopes above are in place and the capability is enabled, the connector syncs risk scores automatically. There is no connector config flag that empties this resource type. -**Done.** Your CrowdStrike connector will now sync risk score data into C1. See [External insights](/product/admin/external-insights) for details on where to see this data in the UI. +**Done.** Your CrowdStrike connector will now sync risk score data into C1.ai. See [External insights](/product/admin/external-insights) for details on where to see this data in the UI. ## Surface identity password risk -**Early access.** This feature is in early access, which means it's undergoing ongoing testing and development while we gather feedback, validate functionality, and improve outputs. Contact the C1 Support team if you'd like to try it out or share feedback. +**Early access.** This feature is in early access, which means it's undergoing ongoing testing and development while we gather feedback, validate functionality, and improve outputs. Contact the C1.ai Support team if you'd like to try it out or share feedback. Once risk score ingestion is enabled, you can flag identities with a compromised or weak password from Falcon Identity Protection as risk factors: @@ -300,7 +300,7 @@ Confirm that: - Risk score ingestion is set up — see [Enable risk score ingestion](#enable-risk-score-ingestion). - The **Identity Risk Score** resource capability is turned on for your connector (see [Enable or disable external insights](/product/admin/external-insights#enable-or-disable-external-insights)). Password risk attaches to that insight, so it won't appear if the capability is off. -- Your CrowdStrike connector is already set up and syncing in C1. +- Your CrowdStrike connector is already set up and syncing in C1.ai. ### Turn on password risk @@ -308,7 +308,7 @@ Password risk uses the same Identity Protection scopes as risk score ingestion, - In C1, go to **Apps** > **Connectors** and select your CrowdStrike connector. + In C1.ai, go to **Apps** > **Connectors** and select your CrowdStrike connector. On the connector's **Settings**, click **Edit**. @@ -323,7 +323,7 @@ Password risk uses the same Identity Protection scopes as risk score ingestion, ## Detect shadow MCP servers -**Early access.** This feature is in early access, which means it's undergoing ongoing testing and development while we gather feedback, validate functionality, and improve outputs. Contact the C1 Support team if you'd like to try it out or share feedback. +**Early access.** This feature is in early access, which means it's undergoing ongoing testing and development while we gather feedback, validate functionality, and improve outputs. Contact the C1.ai Support team if you'd like to try it out or share feedback. The CrowdStrike connector can surface unsanctioned ("shadow") [Model Context Protocol](https://modelcontextprotocol.io) servers running on your endpoints — ungoverned AI-agent tooling that never passed through a sanctioned gateway — and correlate each to the identity that ran it. It reads CrowdStrike endpoint detections and models each shadow server as: @@ -331,7 +331,7 @@ The CrowdStrike connector can surface unsanctioned ("shadow") [Model Context Pro - an **`mcp_server`** resource describing the server (package, launcher, transport, host, sample command line, and the identity it resolved to), and - an **`endpoint_user`** account for the OS user that ran it, holding a **runner** grant on that server. -Assign the endpoint-user account to a C1 identity (or it auto-matches by email when the endpoint user resolves in Identity Protection) so the shadow MCP shows up against a real person in access reviews. +Assign the endpoint-user account to a C1.ai identity (or it auto-matches by email when the endpoint user resolves in Identity Protection) so the shadow MCP shows up against a real person in access reviews. ### Before you begin @@ -339,7 +339,7 @@ Confirm that: - Your CrowdStrike environment generates endpoint detections (the connector reads them via the Alerts API) - You have the **Falcon Administrator** role in CrowdStrike -- Your CrowdStrike connector is already set up and syncing in C1 +- Your CrowdStrike connector is already set up and syncing in C1.ai ### Add the required API scope @@ -348,7 +348,7 @@ Confirm that: Sign into the Falcon console and navigate to **Support** > **API Clients and Keys**. - Find the API client you created for the C1 integration and click to edit it. + Find the API client you created for the C1.ai integration and click to edit it. In the **API SCOPES** section, enable **Alerts: Read**. Keep the **Identity Protection Entities: Read** scope enabled (from risk score ingestion) so endpoint users can be matched to identities. @@ -383,9 +383,9 @@ CrowdStrike doesn't flag MCP servers by default, so you author a Custom IOA rule ### Turn on shadow MCP detection -In C1, enable **both** the **Shadow MCP Server** and **Endpoint User** capabilities on the connector (these resource types are opt-in via C1 capability mediation, not a connector config flag), then save and re-sync. +In C1.ai, enable **both** the **Shadow MCP Server** and **Endpoint User** capabilities on the connector (these resource types are opt-in via C1.ai capability mediation, not a connector config flag), then save and re-sync. -**Enable them together.** Shadow MCP `runner` grants use `endpoint_user` principals. If only Shadow MCP Server is enabled and Endpoint User is off, C1 will not list those principals and the runner grant graph will not fully resolve. +**Enable them together.** Shadow MCP `runner` grants use `endpoint_user` principals. If only Shadow MCP Server is enabled and Endpoint User is off, C1.ai will not list those principals and the runner grant graph will not fully resolve. ### Detection inventory window (page caps) @@ -396,17 +396,17 @@ Shadow MCP inventory is a **recent endpoint-protection (epp) alert scan window** If epp volume is high, the effective lookback shortens. Detections (and thus `mcp_server` / `endpoint_user` resources) that fall outside the scanned window can drop from a later sync **without a hard sync failure** — the connector logs a warning when a page cap is hit and continues with partial results. Re-enablement or lower epp noise restores visibility when those detections reappear in the window. -**Done.** As endpoints run MCP servers, CrowdStrike raises detections and the connector syncs them into C1 as `mcp_server` resources and `endpoint_user` accounts. Assign each endpoint-user account to a C1 identity to attribute the finding. +**Done.** As endpoints run MCP servers, CrowdStrike raises detections and the connector syncs them into C1.ai as `mcp_server` resources and `endpoint_user` accounts. Assign each endpoint-user account to a C1.ai identity to attribute the finding. ## Detect AI coding tools -**Early access.** This feature is in early access, which means it's undergoing ongoing testing and development while we gather feedback, validate functionality, and improve outputs. Contact the C1 Support team if you'd like to try it out or share feedback. +**Early access.** This feature is in early access, which means it's undergoing ongoing testing and development while we gather feedback, validate functionality, and improve outputs. Contact the C1.ai Support team if you'd like to try it out or share feedback. The CrowdStrike connector can inventory **AI coding tools** ("harnesses" — Claude Code, Claude Desktop, Cursor, Windsurf, OpenAI Codex, Gemini CLI, GitHub Copilot CLI, opencode, Aider, and similar) observed running on your endpoints, and correlate each to the identity that ran it. This gives you governance visibility into which people are using which AI tools on which hosts. It reads CrowdStrike endpoint detections and models each tool as an **`ai_tool`** resource describing the tool (name, vendor, category, host, sample command line, and the identity it resolved to), with a low-severity insight linking it to that identity. -This shares the same detection pipeline as shadow MCP detection — it reads the Alerts API and resolves endpoint users to identities the same way — but is enabled independently via the **AI Coding Tool** C1 capability. +This shares the same detection pipeline as shadow MCP detection — it reads the Alerts API and resolves endpoint users to identities the same way — but is enabled independently via the **AI Coding Tool** C1.ai capability. ### Before you begin @@ -414,7 +414,7 @@ Confirm that: - Your CrowdStrike environment generates endpoint detections (the connector reads them via the Alerts API) - You have the **Falcon Administrator** role in CrowdStrike -- Your CrowdStrike connector is already set up and syncing in C1 +- Your CrowdStrike connector is already set up and syncing in C1.ai ### Add the required API scope @@ -447,10 +447,10 @@ CrowdStrike doesn't flag AI coding tools by default, so you author a Custom IOA ### Turn on AI coding tool detection -In C1, enable the **AI Coding Tool** capability on the connector (opt-in via C1 capability mediation, not a connector config flag), then save and re-sync. +In C1.ai, enable the **AI Coding Tool** capability on the connector (opt-in via C1.ai capability mediation, not a connector config flag), then save and re-sync. ### Detection inventory window (page caps) AI coding tool inventory shares the same Alerts scan as shadow MCP detection. Inventory is a **recent epp alert scan window** bounded by `mcpAlertMaxPages` (and identity correlation by `mcpIdentityIndexMaxPages`), not full historical state. High epp volume shortens effective lookback; tools that fall outside the window can disappear from a later sync without a hard failure (a warning is logged when the page cap is hit). See [Detect shadow MCP servers](#detect-shadow-mcp-servers) for the same semantics. -**Done.** As endpoints run AI coding tools, CrowdStrike raises detections and the connector syncs them into C1 as `ai_tool` resources correlated to the identities that ran them. +**Done.** As endpoints run AI coding tools, CrowdStrike raises detections and the connector syncs them into C1.ai as `ai_tool` resources correlated to the identities that ran them. diff --git a/baton/cursor.mdx b/baton/cursor.mdx index 5370b7d2..9c6aadab 100644 --- a/baton/cursor.mdx +++ b/baton/cursor.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Cursor connector" og:title: "Set up a Cursor connector" -description: "C1 provides identity governance for Cursor. Integrate your Cursor instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." -og:description: "C1 provides identity governance for Cursor. Integrate your Cursor instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance for Cursor. Integrate your Cursor instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance for Cursor. Integrate your Cursor instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Cursor" --- @@ -76,18 +76,18 @@ For more information, see the [Cursor SCIM documentation](https://cursor.com/doc To complete this task, you need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - The Cursor API key gathered in the previous section -**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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Cursor** and click **Add**. @@ -120,21 +120,21 @@ To complete this task, you need: -**Done.** Your Cursor connector is now pulling access data into C1. +**Done.** Your Cursor connector is now pulling access data into C1.ai. **Follow these instructions to use the Cursor 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 C1.ai, automatically syncing and uploading data at regular intervals. +This data is immediately available in the C1.ai UI for access reviews and access requests. ### Step 1: Set up a new Cursor connector - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -231,14 +231,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 C1.ai 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 Cursor connector to. Cursor data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Cursor connector to. Cursor data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Cursor connector is now pulling access data into C1. +**Done.** Your Cursor connector is now pulling access data into C1.ai. diff --git a/baton/custom.mdx b/baton/custom.mdx index 8fa80935..73b6ae77 100644 --- a/baton/custom.mdx +++ b/baton/custom.mdx @@ -6,7 +6,7 @@ og:description: "Use the Baton software development kit to build your own connec sidebarTitle: "Build a new connector" --- -If you need to connect C1 to a homegrown or backoffice piece of infrastructure, you can build your own connector with the Baton software development kit (SDK). Once built, these connectors can be integrated directly with C1. +If you need to connect C1.ai to a homegrown or backoffice piece of infrastructure, you can build your own connector with the Baton software development kit (SDK). Once built, these connectors can be integrated directly with C1.ai. Check out our tutorial video to learn how to build your own connector: diff --git a/baton/databricks.mdx b/baton/databricks.mdx index bfc4d0cc..4007b52a 100644 --- a/baton/databricks.mdx +++ b/baton/databricks.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Databricks connector" og:title: "Set up a Databricks connector" -description: "C1 provides identity governance and just-in-time provisioning for Databricks. Integrate your Databricks 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 Databricks. Integrate your Databricks instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Databricks. Integrate your Databricks instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Databricks. Integrate your Databricks instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Databricks" --- @@ -47,7 +47,7 @@ A user with the **Account admin** role in each Databricks workspace you want to - Ensure that your Databricks user account has the **Account admin** role and is assigned to each Databricks workspace you want to sync to C1. + Ensure that your Databricks user account has the **Account admin** role and is assigned to each Databricks workspace you want to sync to C1.ai. In the Databricks account console, open the menu that appears next to your username in the upper right corner. @@ -89,18 +89,18 @@ Next, move on to the instructions for your chosen setup method. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Databricks 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Databricks** and click **Add**. @@ -141,14 +141,14 @@ To complete this task, you'll need: -**Done.** Your Databricks connector is now pulling access data into C1. +**Done.** Your Databricks connector is now pulling access data into C1.ai. **Follow these instructions to use the Databricks 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -160,7 +160,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -274,14 +274,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 C1.ai 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 Databricks connector to. Databricks data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Databricks connector to. Databricks data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Databricks connector is now pulling access data into C1. +**Done.** Your Databricks connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/datadog.mdx b/baton/datadog.mdx index 68664bd2..5d8cd506 100644 --- a/baton/datadog.mdx +++ b/baton/datadog.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Datadog connector" og:title: "Set up a Datadog connector" -description: "C1 provides identity governance for Datadog. Integrate your Datadog instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." -og:description: "C1 provides identity governance for Datadog. Integrate your Datadog instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance for Datadog. Integrate your Datadog instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance for Datadog. Integrate your Datadog instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Datadog" --- -**This is an updated and improved version of the Datadog connector!** If you're setting up Datadog with C1 for the first time, you're in the right place. +**This is an updated and improved version of the Datadog connector!** If you're setting up Datadog with C1.ai for the first time, you're in the right place. ## Capabilities @@ -26,7 +26,7 @@ sidebarTitle: "Datadog" ### 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 C1.ai 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 | |-------------|-------------------|-------------| @@ -39,9 +39,9 @@ Connector actions are custom capabilities that extend C1 automations with app-sp Configuring the connector requires you to pass in credentials generated in Datadog. Gather these credentials before you move on. -A user with the **Connector Administrator** or **Super Administrator** role in C1 and the **Datadog Admin** or **Datadog standard** role in Datadog must perform this task. +A user with the **Connector Administrator** or **Super Administrator** role in C1.ai and the **Datadog Admin** or **Datadog standard** role in Datadog must perform this task. -If your user has a custom Datadog role, make sure it includes the **User App Keys** and **API Keys Read** permissions, plus **User Access Invite** and **User Access Manage** to create, update, enable, and disable users from C1. +If your user has a custom Datadog role, make sure it includes the **User App Keys** and **API Keys Read** permissions, plus **User Access Invite** and **User Access Manage** to create, update, enable, and disable users from C1.ai. ### Locate your Datadog site @@ -63,7 +63,7 @@ If your user has a custom Datadog role, make sure it includes the **User App Key - Enter a name for your new key, such as "C1", and click **Create Key**. + Enter a name for your new key, such as "C1.ai", and click **Create Key**. Copy and save the newly created API key. @@ -81,7 +81,7 @@ If your user has a custom Datadog role, make sure it includes the **User App Key Click **Application Keys** and then click **+ New Key**. - Enter a name for your new key, such as "C1", and click **Create Key**. + Enter a name for your new key, such as "C1.ai", and click **Create Key**. Copy and save the newly created application key. @@ -95,18 +95,18 @@ If your user has a custom Datadog role, make sure it includes the **User App Key To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Datadog 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Datadog v2** and click **Add**. @@ -151,14 +151,14 @@ To complete this task, you'll need: -**Done.** Your Datadog connector is now pulling access data into C1. +**Done.** Your Datadog connector is now pulling access data into C1.ai. **Follow these instructions to use the Datadog 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -170,7 +170,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -271,14 +271,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 C1.ai 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 Datadog connector to. Datadog data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Datadog connector to. Datadog data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Datadog connector is now pulling access data into C1. +**Done.** Your Datadog connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/dayforce.mdx b/baton/dayforce.mdx index 99a1c613..6f8b2bed 100644 --- a/baton/dayforce.mdx +++ b/baton/dayforce.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Dayforce connector" og:title: "Set up a Dayforce connector" -description: "C1 provides identity governance for Dayforce. Integrate your Dayforce instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Dayforce. Integrate your Dayforce instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Dayforce. Integrate your Dayforce instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Dayforce. Integrate your Dayforce instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Dayforce" --- @@ -18,10 +18,10 @@ Specifically, the connector syncs Clock Device Groups, Document Security Groups, The Dayforce connector supports [automatic account provisioning](/product/admin/account-provisioning) by hiring a new employee, and grants and revokes security-role assignments on existing employees. -This connector does not support account deprovisioning. Dayforce employee records are persistent, so C1 disables access by revoking role grants rather than deleting accounts. +This connector does not support account deprovisioning. Dayforce employee records are persistent, so C1.ai disables access by revoking role grants rather than deleting accounts. -**Same-day role revokes take effect at end of day.** Dayforce ends a role assignment at 23:59 of the day it was granted, so revoking a role on the same day it was granted leaves it active until midnight. The role appears as granted in C1 until the first sync after midnight. For immediate access cut-off, disable the user in the Dayforce IAM admin UI. +**Same-day role revokes take effect at end of day.** Dayforce ends a role assignment at 23:59 of the day it was granted, so revoking a role on the same day it was granted leaves it active until midnight. The role appears as granted in C1.ai until the first sync after midnight. For immediate access cut-off, disable the user in the Dayforce IAM admin UI. ## Gather Dayforce credentials @@ -75,18 +75,18 @@ Set the following roles and permissions on the account or service account you us To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Dayforce 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Dayforce** and click **Add**. @@ -128,7 +128,7 @@ To complete this task, you'll need: -**Done.** Your Dayforce connector is now pulling access data into C1. +**Done.** Your Dayforce connector is now pulling access data into C1.ai. diff --git a/baton/dbt-cloud.mdx b/baton/dbt-cloud.mdx index 8b4cd9f0..de2ea6dc 100644 --- a/baton/dbt-cloud.mdx +++ b/baton/dbt-cloud.mdx @@ -1,15 +1,15 @@ --- title: "Set up a dbt Cloud connector" og:title: "Set up a dbt Cloud connector" -description: "C1 provides identity governance for dbt Cloud. Integrate your dbt Cloud account with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for dbt Cloud. Integrate your dbt Cloud account with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for dbt Cloud. Integrate your dbt Cloud account with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for dbt Cloud. Integrate your dbt Cloud account with C1.ai for unified visibility and governance over user access." sidebarTitle: "dbt Cloud" --- {/* stargate: cf-dbt-cloud-20260605 */} -C1 provides identity governance for dbt Cloud. Integrate your dbt Cloud account -with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for dbt Cloud. Integrate your dbt Cloud account +with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -22,7 +22,7 @@ The connector syncs the users in a dbt Cloud account as identities. Each user carries their account status and license type, so you can see who holds a paid developer seat versus read-only access. It also syncs the account's groups (permission sets) and who belongs to each one, so group membership is visible -and reviewable in C1. +and reviewable in C1.ai. ## Gather dbt Cloud credentials @@ -63,11 +63,11 @@ personal token. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -111,7 +111,7 @@ personal token. - **Done.** Your dbt Cloud connector is now pulling access data into C1. + **Done.** Your dbt Cloud connector is now pulling access data into C1.ai. @@ -136,6 +136,6 @@ personal token. - **Done.** Your dbt Cloud connector is now pulling access data into C1. + **Done.** Your dbt Cloud connector is now pulling access data into C1.ai. diff --git a/baton/deel.mdx b/baton/deel.mdx index 5a488fae..a68cad7b 100644 --- a/baton/deel.mdx +++ b/baton/deel.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Deel connector" og:title: "Set up a Deel connector" -description: "C1 provides identity governance for Deel. Integrate your Deel instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Deel. Integrate your Deel instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Deel. Integrate your Deel instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Deel. Integrate your Deel instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Deel" --- @@ -37,18 +37,18 @@ This connector requires the following scopes: To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Deel 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Deel** and click **Add**. @@ -81,24 +81,24 @@ To complete this task, you'll need: -**Done.** Your Deel connector is now pulling access data into C1. +**Done.** Your Deel connector is now pulling access data into C1.ai. **Follow these instructions to use the Deel 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources -[Contact C1's support team](mailto:support@c1.ai) to download the latest version of the connector. +[Contact C1.ai's support team](mailto:support@c1.ai) to download the latest version of the connector. ### Step 1: Set up a new Deel connector - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -189,14 +189,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 C1.ai 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 Deel connector to. Deel data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Deel connector to. Deel data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Deel connector is now pulling access data into C1. +**Done.** Your Deel connector is now pulling access data into C1.ai. diff --git a/baton/delinea.mdx b/baton/delinea.mdx index 05521dac..9386d65c 100644 --- a/baton/delinea.mdx +++ b/baton/delinea.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Delinea connector" og:title: "Set up a Delinea connector" -description: "C1 provides identity governance for Delinea. Integrate your Delinea instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Delinea. Integrate your Delinea instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Delinea. Integrate your Delinea instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Delinea. Integrate your Delinea instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Delinea" --- @@ -53,18 +53,18 @@ For more detail, see the Delinea documentation on [adding users](https://docs.de To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Delinea 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Delinea** and click **Add**. @@ -97,24 +97,24 @@ To complete this task, you'll need: -**Done.** Your Delinea connector is now pulling access data into C1. +**Done.** Your Delinea connector is now pulling access data into C1.ai. **Follow these instructions to use the Delinea 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources -[Contact C1's support team](mailto:support@c1.ai) to download the latest version of the connector. +[Contact C1.ai's support team](mailto:support@c1.ai) to download the latest version of the connector. ### Step 1: Set up a new Delinea connector - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -207,14 +207,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 C1.ai 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 Delinea connector to. Delinea data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Delinea connector to. Delinea data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Delinea connector is now pulling access data into C1. +**Done.** Your Delinea connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/deploy.mdx b/baton/deploy.mdx index 912a42a4..d6ed63ba 100644 --- a/baton/deploy.mdx +++ b/baton/deploy.mdx @@ -8,10 +8,10 @@ sidebarTitle: "Deploy self-hosted connectors" ## Self-hosted connector network architecture -The following diagram shows how a self-hosted connector runs inside your network, how it reaches the systems it syncs, and how it communicates with C1 over an outbound-only connection. +The following diagram shows how a self-hosted connector runs inside your network, how it reaches the systems it syncs, and how it communicates with C1.ai over an outbound-only connection. -Reference architecture diagram of self-hosted connector network topology. On the left, a customer network trust boundary contains a Baton connector (running as a Docker container, Kubernetes deployment, systemd unit, or Windows service, optionally supervised by baton-runner) alongside a customer secret store (env vars, Kubernetes Secret, AWS Secrets Manager, or HashiCorp Vault) and the target systems it syncs, such as Active Directory/LDAP, SQL Server or PostgreSQL, Jira/Confluence/Bitbucket, and internal HTTP APIs. The connector reaches target systems over private network protocols like LDAPS, TDS, and HTTPS, and writes an ephemeral sync.c1z file and debug log to a local working directory. On the right, the C1 cloud (multi-tenant SaaS) exposes an OAuth 2.0 token endpoint and a connector API/task queue. The only connection crossing the corporate firewall is outbound HTTPS on TCP 443 using TLS 1.2+ and gRPC to *.conductorone.com — no inbound ports, VPN, or DMZ host are required, and it works behind NAT and egress proxies. This is a pull model: the connector always initiates, calling Hello (registers host ID, version, capabilities), GetTask/GetTasks (long-polls for work), Heartbeat (keepalive during a task), UploadAsset (streams sync.c1z in 512KB chunks), and FinishTask (reports success or failure); the task assignment response rides the same outbound connection rather than a new inbound one. Task types include full sync, grant/revoke entitlement, create account, delete resource, rotate credentials, issue credential, create/get ticket, event feed, and debug. Target-system credentials are never transmitted to C1. For high availability, multiple connector replicas share one client ID and C1 distributes tasks round-robin. A separate diagram section shows the alternative periodic upload mode: a baton-<app> CLI run on a schedule (such as cron) produces a sync.c1z file with no persistent connection, which is either manually uploaded in the C1 UI or placed in a customer-owned S3 bucket that C1 polls hourly. +Reference architecture diagram of self-hosted connector network topology. On the left, a customer network trust boundary contains a Baton connector (running as a Docker container, Kubernetes deployment, systemd unit, or Windows service, optionally supervised by baton-runner) alongside a customer secret store (env vars, Kubernetes Secret, AWS Secrets Manager, or HashiCorp Vault) and the target systems it syncs, such as Active Directory/LDAP, SQL Server or PostgreSQL, Jira/Confluence/Bitbucket, and internal HTTP APIs. The connector reaches target systems over private network protocols like LDAPS, TDS, and HTTPS, and writes an ephemeral sync.c1z file and debug log to a local working directory. On the right, the C1.ai cloud (multi-tenant SaaS) exposes an OAuth 2.0 token endpoint and a connector API/task queue. The only connection crossing the corporate firewall is outbound HTTPS on TCP 443 using TLS 1.2+ and gRPC to *.conductorone.com — no inbound ports, VPN, or DMZ host are required, and it works behind NAT and egress proxies. This is a pull model: the connector always initiates, calling Hello (registers host ID, version, capabilities), GetTask/GetTasks (long-polls for work), Heartbeat (keepalive during a task), UploadAsset (streams sync.c1z in 512KB chunks), and FinishTask (reports success or failure); the task assignment response rides the same outbound connection rather than a new inbound one. Task types include full sync, grant/revoke entitlement, create account, delete resource, rotate credentials, issue credential, create/get ticket, event feed, and debug. Target-system credentials are never transmitted to C1.ai. For high availability, multiple connector replicas share one client ID and C1.ai distributes tasks round-robin. A separate diagram section shows the alternative periodic upload mode: a baton-<app> CLI run on a schedule (such as cron) produces a sync.c1z file with no persistent connection, which is either manually uploaded in the C1.ai UI or placed in a customer-owned S3 bucket that C1.ai polls hourly. ## Should I use self-hosted connectors? @@ -19,8 +19,8 @@ The following diagram shows how a self-hosted connector runs inside your network You might want to self-host and deploy connectors in your own environment if one or more of the following is true: - The technology does not expose its APIs (such as in the case of a PostgreSQL database). -- The technology or application does not have a line of sight to C1’s platform and it would be inappropriate to expose that app to the internet. -- You can’t or don’t want to provide C1 with the API keys or credentials for the technology. +- The technology or application does not have a line of sight to C1.ai’s platform and it would be inappropriate to expose that app to the internet. +- You can’t or don’t want to provide C1.ai with the API keys or credentials for the technology. - You need to control the sync schedule or some other aspect of the connector. - You wish to extend the connector’s capabilities, such as by supporting additional resources in a SaaS. @@ -28,7 +28,7 @@ In any of these scenarios, the best option is to deploy a connector in your own ## Run a self-hosted connector in service mode -Integrating your self-hosted connector with C1 creates the most seamless and fully automated method of uploading your application’s data. Once the self-hosted connector is set up, the connector’s Baton service runs in your environment. The service maintains contact with C1, syncs and uploads data at regular intervals, and passes that data to the C1 UI, where you and your colleagues can use it to run access reviews and facilitate access requests for the application. +Integrating your self-hosted connector with C1.ai creates the most seamless and fully automated method of uploading your application’s data. Once the self-hosted connector is set up, the connector’s Baton service runs in your environment. The service maintains contact with C1.ai, syncs and uploads data at regular intervals, and passes that data to the C1.ai UI, where you and your colleagues can use it to run access reviews and facilitate access requests for the application. ### Step 1: Locate or generate connector credentials @@ -63,7 +63,7 @@ Integrating your self-hosted connector with C1 creates the most seamless and ful - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -117,16 +117,16 @@ If you want to pull identities from an existing connector, complete these additi Run `baton-okta --help` to see the list of flags to be used when passing your credentials to the connector. - The connector syncs current data, uploads it to C1, and prints a `Task complete!` message when finished. + The connector syncs current data, uploads it to C1.ai, and prints a `Task complete!` message when finished. - 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 Baton connector to. The data should be found on the **Resources** and **Accounts** tabs, as appropriate. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Baton connector to. The data should be found on the **Resources** and **Accounts** tabs, as appropriate. ## Run a self-hosted connector in periodic upload mode -As an alternative to running a self-hosted connector in service mode, you can set up a self-hosted connector and periodically upload its data to C1, either manually or automatically. +As an alternative to running a self-hosted connector in service mode, you can set up a self-hosted connector and periodically upload its data to C1.ai, either manually or automatically. ### Step 1: Locate or generate connector credentials @@ -160,19 +160,19 @@ As an alternative to running a self-hosted connector in service mode, you can se Each installation method includes a `resources` command. This command runs the sync on the connector and stores the gathered data in a `sync.c1z` file. -Now that you’ve collected the connector data, you can choose to manually upload the data to C1 or to sync the data to an S3 bucket integrated with C1. The next step walks through each option. +Now that you’ve collected the connector data, you can choose to manually upload the data to C1.ai or to sync the data to an S3 bucket integrated with C1.ai. The next step walks through each option. -### Step 3: Upload data to C1 +### Step 3: Upload data to C1.ai You can upload your application’s data either manually our automatically. Follow the instructions below to set up your chosen method. ### Option 1: Manually upload connector data -Manually uploading data to C1 from an self-hosted connector is ideal when testing data ingested from the connector before automating the data upload process, or for times when you only need a single data sync. +Manually uploading data to C1.ai from an self-hosted connector is ideal when testing data ingested from the connector before automating the data upload process, or for times when you only need a single data sync. - In C1, navigate to an existing application you wish to add the connector data to, or create a new application. + In C1.ai, navigate to an existing application you wish to add the connector data to, or create a new application. - **To create a new application,** follow the steps in [Create custom applications](/product/admin/applications). - **To use an existing application,** click **Apps**. On the **Managed apps** tab, select the application’s name from the list. @@ -187,13 +187,13 @@ Manually uploading data to C1 from an self-hosted connector is ideal when testin -Once the upload is complete, C1 adds the information pulled from the connector about accounts, groups, roles, resources, and grants (as relevant) to the application. +Once the upload is complete, C1.ai adds the information pulled from the connector about accounts, groups, roles, resources, and grants (as relevant) to the application. -To update the information in C1, re-run the `resources` command and re-upload the file to C1 using the process above. +To update the information in C1.ai, re-run the `resources` command and re-upload the file to C1.ai using the process above. ### Option 2: Automatically sync connector data to an S3 bucket -The most convenient option is to automate the process of running of the sync and ingestion of the data into C1. You can automatically pull connector data into an application by using an AWS S3 bucket as a data source. +The most convenient option is to automate the process of running of the sync and ingestion of the data into C1.ai. You can automatically pull connector data into an application by using an AWS S3 bucket as a data source. **Before you begin:** @@ -203,7 +203,7 @@ Complete Steps 1-3 in [Set up an external data source](/product/admin/external-d - In C1, navigate to an existing application you wish to add the connector data to, or create a new application. + In C1.ai, navigate to an existing application you wish to add the connector data to, or create a new application. - **To create a new application,** follow the steps to [create a new app](/product/admin/applications#create-a-new-application). - **To use an existing application,** click **Apps**. On the **Managed apps** tab, select the application’s name from the list. @@ -237,11 +237,11 @@ Complete Steps 1-3 in [Set up an external data source](/product/admin/external-d baton-okta ``` - This script syncs data from the connector (in this case, Okta) and uploads it to your configured S3 bucket. Once the upload is complete, C1 adds the information pulled from the connector about accounts, groups, roles, resources, and grants (as relevant) to the application. + This script syncs data from the connector (in this case, Okta) and uploads it to your configured S3 bucket. Once the upload is complete, C1.ai adds the information pulled from the connector about accounts, groups, roles, resources, and grants (as relevant) to the application. -You can run the script on demand, or set up a scheduler to run it periodically. The S3 bucket syncs with C1 once an hour. +You can run the script on demand, or set up a scheduler to run it periodically. The S3 bucket syncs with C1.ai once an hour. ## Deployment examples @@ -316,7 +316,7 @@ spec: name: baton-yourservice-secrets ``` -For high availability, increase replicas. Multiple instances can share the same client ID and secret; C1 distributes tasks round-robin. +For high availability, increase replicas. Multiple instances can share the same client ID and secret; C1.ai distributes tasks round-robin. ### Systemd (Linux) @@ -372,11 +372,11 @@ Never commit credentials to source control. Options: ### Network requirements Service mode requires outbound HTTPS only: -- Connector initiates connections to C1 +- Connector initiates connections to C1.ai - No inbound ports required - Works behind NAT and most firewalls -If you have egress filtering, allow HTTPS to whichever domain matches your C1 tenant's hosting region — default instance: `*.conductor.one`, EU data residency instance: `*.c1eu.ai`. +If you have egress filtering, allow HTTPS to whichever domain matches your C1.ai tenant's hosting region — default instance: `*.conductor.one`, EU data residency instance: `*.c1eu.ai`. ### Resource requirements @@ -389,8 +389,8 @@ Connectors are lightweight: ### Monitoring -C1 sends email alerts after three consecutive sync failures. Monitor: -- Sync status in the C1 UI +C1.ai sends email alerts after three consecutive sync failures. Monitor: +- Sync status in the C1.ai UI - Connector logs for errors - Memory usage (should stay stable) @@ -411,7 +411,7 @@ open sync.c1z: read-only file system ``` This happens because the connector needs a writable directory for: -- **`sync.c1z`** — the sync data file uploaded to C1 +- **`sync.c1z`** — the sync data file uploaded to C1.ai - **`debug.log`** — diagnostic log output created during sync tasks #### Fix: Provide a writable working directory diff --git a/baton/deputy.mdx b/baton/deputy.mdx index 93fa8c01..3eacd8d5 100644 --- a/baton/deputy.mdx +++ b/baton/deputy.mdx @@ -1,15 +1,15 @@ --- title: "Set up a Deputy connector" og:title: "Set up a Deputy connector" -description: "C1 provides identity governance for Deputy. Integrate your Deputy instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Deputy. Integrate your Deputy instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Deputy. Integrate your Deputy instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Deputy. Integrate your Deputy instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Deputy" --- {/* stargate: cf-deputy-20260605 */} -C1 provides identity governance for Deputy. Integrate your Deputy -instance with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Deputy. Integrate your Deputy +instance with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -54,11 +54,11 @@ can read your account's employees and access levels. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -102,7 +102,7 @@ can read your account's employees and access levels. - **Done.** Your Deputy connector is now pulling access data into C1. + **Done.** Your Deputy connector is now pulling access data into C1.ai. @@ -129,6 +129,6 @@ can read your account's employees and access levels. - **Done.** Your Deputy connector is now pulling access data into C1. + **Done.** Your Deputy connector is now pulling access data into C1.ai. diff --git a/baton/deskpro.mdx b/baton/deskpro.mdx index efa41be2..809d469e 100644 --- a/baton/deskpro.mdx +++ b/baton/deskpro.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Deskpro connector" og:title: "Set up a Deskpro connector" -description: "C1 provides identity governance for Deskpro. Integrate your Deskpro instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Deskpro. Integrate your Deskpro instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Deskpro. Integrate your Deskpro instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Deskpro. Integrate your Deskpro instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Deskpro" --- -C1 provides identity governance for Deskpro. Integrate your Deskpro -instance with C1 for unified visibility and governance over agent access. +C1.ai provides identity governance for Deskpro. Integrate your Deskpro +instance with C1.ai for unified visibility and governance over agent access. ## Capabilities @@ -49,11 +49,11 @@ Deskpro account so you can create an API key. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -97,7 +97,7 @@ Deskpro account so you can create an API key. - **Done.** Your Deskpro connector is now pulling access data into C1. + **Done.** Your Deskpro connector is now pulling access data into C1.ai. @@ -124,6 +124,6 @@ Deskpro account so you can create an API key. - **Done.** Your Deskpro connector is now pulling access data into C1. + **Done.** Your Deskpro connector is now pulling access data into C1.ai. diff --git a/baton/dialpad.mdx b/baton/dialpad.mdx index 7207a7cf..02277375 100644 --- a/baton/dialpad.mdx +++ b/baton/dialpad.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Dialpad connector" og:title: "Set up a Dialpad connector" -description: "C1 provides identity governance for Dialpad. Integrate your Dialpad instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Dialpad. Integrate your Dialpad instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Dialpad. Integrate your Dialpad instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Dialpad. Integrate your Dialpad instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Dialpad" --- @@ -31,18 +31,18 @@ See the Dialpad docs for information on how to acquire credentials: [View the do To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Dialpad 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Dialpad** and click **Add**. @@ -75,24 +75,24 @@ To complete this task, you'll need: -**Done.** Your Dialpad connector is now pulling access data into C1. +**Done.** Your Dialpad connector is now pulling access data into C1.ai. **Follow these instructions to use the Dialpad 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources -[Contact C1's support team](mailto:support@c1.ai) to download the latest version of the connector. +[Contact C1.ai's support team](mailto:support@c1.ai) to download the latest version of the connector. ### Step 1: Set up a new Dialpad connector - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -182,14 +182,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 C1.ai 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 Dialpad connector to. Dialpad data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Dialpad connector to. Dialpad data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Dialpad connector is now pulling access data into C1. +**Done.** Your Dialpad connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/digicert-certcentral.mdx b/baton/digicert-certcentral.mdx index 1d850d9a..323fbb02 100644 --- a/baton/digicert-certcentral.mdx +++ b/baton/digicert-certcentral.mdx @@ -1,8 +1,8 @@ --- title: "Set up a DigiCert CertCentral connector" og:title: "Set up a DigiCert CertCentral connector" -description: "C1 provides identity governance and just-in-time provisioning for DigiCert CertCentral. Integrate your DigiCert CertCentral 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 DigiCert CertCentral. Integrate your DigiCert CertCentral instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for DigiCert CertCentral. Integrate your DigiCert CertCentral instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for DigiCert CertCentral. Integrate your DigiCert CertCentral instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "DigiCert CertCentral" --- @@ -24,7 +24,7 @@ We recommend closely monitoring workflows that use this connector and contacting Supports [automatic account provisioning and deprovisioning](/product/admin/account-provisioning) - When a new account is created by C1, the account's password will be sent to a [vault](/product/admin/vaults) + When a new account is created by C1.ai, the account's password will be sent to a [vault](/product/admin/vaults) ## Gather DigiCert CertCentral configuration information @@ -41,18 +41,18 @@ See the DigiCert CertCentral docs for information on how to acquire credentials: To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of DigiCert CertCentral 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **DigiCert CertCentral** and click **Add**. @@ -85,24 +85,24 @@ To complete this task, you'll need: -**Done.** Your DigiCert CertCentral connector is now pulling access data into C1. +**Done.** Your DigiCert CertCentral connector is now pulling access data into C1.ai. **Follow these instructions to use the DigiCert CertCentral 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources -[Contact C1's support team](mailto:support@c1.ai) to download the latest version of the connector. +[Contact C1.ai's support team](mailto:support@c1.ai) to download the latest version of the connector. ### Step 1: Set up a new DigiCert CertCentral connector - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -195,14 +195,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 C1.ai 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 DigiCert CertCentral connector to. DigiCert CertCentral data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the DigiCert CertCentral connector to. DigiCert CertCentral data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your DigiCert CertCentral connector is now pulling access data into C1. +**Done.** Your DigiCert CertCentral connector is now pulling access data into C1.ai. diff --git a/baton/discourse.mdx b/baton/discourse.mdx index e4489711..e2bbf597 100644 --- a/baton/discourse.mdx +++ b/baton/discourse.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Discourse connector" og:title: "Set up a Discourse connector" -description: "C1 provides identity governance for Discourse. Integrate your Discourse instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Discourse. Integrate your Discourse instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Discourse. Integrate your Discourse instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Discourse. Integrate your Discourse instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Discourse" --- -C1 provides identity governance for Discourse. Integrate your Discourse -instance with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Discourse. Integrate your Discourse +instance with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -50,11 +50,11 @@ every user and group. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -97,7 +97,7 @@ every user and group. - **Done.** Your Discourse connector is now pulling access data into C1. + **Done.** Your Discourse connector is now pulling access data into C1.ai. @@ -122,6 +122,6 @@ every user and group. - **Done.** Your Discourse connector is now pulling access data into C1. + **Done.** Your Discourse connector is now pulling access data into C1.ai. diff --git a/baton/dixa.mdx b/baton/dixa.mdx index 391232f3..327662d3 100644 --- a/baton/dixa.mdx +++ b/baton/dixa.mdx @@ -1,14 +1,14 @@ --- title: "Set up a Dixa connector" og:title: "Set up a Dixa connector" -description: "C1 provides identity governance for Dixa. Integrate your Dixa account with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Dixa. Integrate your Dixa account with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Dixa. Integrate your Dixa account with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Dixa. Integrate your Dixa account with C1.ai for unified visibility and governance over user access." sidebarTitle: "Dixa" --- {/* stargate */} -C1 provides identity governance for Dixa. Integrate your Dixa account with C1 +C1.ai provides identity governance for Dixa. Integrate your Dixa account with C1.ai for unified visibility and governance over who has access to your customer service workspace. @@ -50,11 +50,11 @@ to an administrator of your Dixa organization. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -95,7 +95,7 @@ to an administrator of your Dixa organization. - **Done.** Your Dixa connector is now pulling access data into C1. + **Done.** Your Dixa connector is now pulling access data into C1.ai. @@ -118,6 +118,6 @@ to an administrator of your Dixa organization. - **Done.** Your Dixa connector is now pulling access data into C1. + **Done.** Your Dixa connector is now pulling access data into C1.ai. diff --git a/baton/dockerhub.mdx b/baton/dockerhub.mdx index ef655503..ca488aa4 100644 --- a/baton/dockerhub.mdx +++ b/baton/dockerhub.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Docker Hub connector" og:title: "Set up a Docker Hub connector" -description: "C1 provides identity governance for Docker Hub. Integrate your Docker Hub instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Docker Hub. Integrate your Docker Hub instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Docker Hub. Integrate your Docker Hub instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Docker Hub. Integrate your Docker Hub instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Docker Hub" --- @@ -30,18 +30,18 @@ Here's the set of credentials you'll need when setting up the connector: To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Docker Hub 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Docker Hub** and click **Add**. @@ -74,14 +74,14 @@ To complete this task, you'll need: -**Done.** Your Docker Hub connector is now pulling access data into C1. +**Done.** Your Docker Hub connector is now pulling access data into C1.ai. **Follow these instructions to use the Docker Hub 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -91,7 +91,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -182,14 +182,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 C1.ai 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 Docker Hub connector to. Docker Hub data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Docker Hub connector to. Docker Hub data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Docker Hub connector is now pulling access data into C1. +**Done.** Your Docker Hub connector is now pulling access data into C1.ai. diff --git a/baton/document360.mdx b/baton/document360.mdx index 88c3ff9d..3562fde6 100644 --- a/baton/document360.mdx +++ b/baton/document360.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Document360 connector" og:title: "Set up a Document360 connector" -description: "C1 provides identity governance for Document360. Integrate your Document360 instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Document360. Integrate your Document360 instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Document360. Integrate your Document360 instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Document360. Integrate your Document360 instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Document360" --- -C1 provides identity governance for Document360. Integrate your Document360 -instance with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Document360. Integrate your Document360 +instance with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -72,11 +72,11 @@ scoped to a single project. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -118,7 +118,7 @@ scoped to a single project. - **Done.** Your Document360 connector is now pulling access data into C1. + **Done.** Your Document360 connector is now pulling access data into C1.ai. @@ -127,7 +127,7 @@ scoped to a single project. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -145,7 +145,7 @@ scoped to a single project. - Configure C1 credentials and Document360 credentials as environment + Configure C1.ai credentials and Document360 credentials as environment variables: ```bash @@ -168,6 +168,6 @@ scoped to a single project. - **Done.** Your Document360 connector is now pulling access data into C1. + **Done.** Your Document360 connector is now pulling access data into C1.ai. diff --git a/baton/docusign.mdx b/baton/docusign.mdx index 03180d63..9ae7d396 100644 --- a/baton/docusign.mdx +++ b/baton/docusign.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Docusign connector" og:title: "Set up a Docusign connector" -description: "C1 provides identity governance for Docusign. Integrate your Docusign instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." -og:description: "C1 provides identity governance for Docusign. Integrate your Docusign instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance for Docusign. Integrate your Docusign instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance for Docusign. Integrate your Docusign instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Docusign" --- -**This is an updated and improved version of the Docusign connector!** If you're setting up Docusign with C1 for the first time, you're in the right place. +**This is an updated and improved version of the Docusign connector!** If you're setting up Docusign with C1.ai for the first time, you're in the right place. ## Capabilities @@ -41,7 +41,7 @@ Configuring the connector requires you to pass in credentials generated in Docus The Docusign credentials requirements depend on your chosen hosting method and authentication mode: -- **Cloud-hosted (production)**: You'll use C1's managed OAuth app. No additional credentials are needed. You can **skip this section** and go straight to the cloud-hosted setup instructions below. +- **Cloud-hosted (production)**: You'll use C1.ai's managed OAuth app. No additional credentials are needed. You can **skip this section** and go straight to the cloud-hosted setup instructions below. - **Cloud-hosted (demo environment)** or **Self-hosted**: You'll need to create a Docusign developer app. Go on to the next section. @@ -56,12 +56,12 @@ A user with access to the **Docusign Admin console** must perform this task. In the Docusign Admin Console, click **Add App and Integration Key**. - Choose a name for your app, such as "C1" and click **Create App**. + Choose a name for your app, such as "C1.ai" and click **Create App**. On the app configuration screen, carefully copy and save the **Client ID** (also called an integration key). - You'll be asked to classify the integration key. This choice affects production billing and [can't be changed later](https://developers.docusign.com/platform/go-live/#ik-classifications). The key is created and used against your own DocuSign account in both hosting modes, so **Private custom integration** — DocuSign's description is *"used internally by your employees or your customers' employees"* — matches most setups. If you're going through C1's **Custom App (Demo Environment)** field group, you may instead consider **Third-party integration key** — *"using a partner integration that requires your own integration key"* — since C1 is the party invoking it on your behalf; confirm with DocuSign which classification fits your situation before proceeding, since it isn't reversible. + You'll be asked to classify the integration key. This choice affects production billing and [can't be changed later](https://developers.docusign.com/platform/go-live/#ik-classifications). The key is created and used against your own DocuSign account in both hosting modes, so **Private custom integration** — DocuSign's description is *"used internally by your employees or your customers' employees"* — matches most setups. If you're going through C1.ai's **Custom App (Demo Environment)** field group, you may instead consider **Third-party integration key** — *"using a partner integration that requires your own integration key"* — since C1.ai is the party invoking it on your behalf; confirm with DocuSign which classification fits your situation before proceeding, since it isn't reversible. Click **Add Secret Key**, then carefully copy and save the client secret. @@ -69,7 +69,7 @@ A user with access to the **Docusign Admin console** must perform this task. In the **Redirect URI** field: - If you're configuring a **self-hosted** connector, enter any URI of your choice (such as http://example.com/callback) and click **Add**. Nothing needs to be listening at that address — the `--configure` flow prints an authorization URL, and after you authorize, DocuSign redirects your browser there; copy the `code` parameter from the resulting (unreachable) URL and paste it when prompted. Whatever value you register here must also be passed as `--redirect-uri` / `BATON_REDIRECT_URI`, or the authorization and token exchange will fail. - - If you're configuring a **Cloud-hosted (demo environment)** connector, enter `https://accounts.conductor.one/oauth/callback` and click **Add**. C1 completes the OAuth flow through this URL; DocuSign rejects the authorization request if it isn't registered here. + - If you're configuring a **Cloud-hosted (demo environment)** connector, enter `https://accounts.conductor.one/oauth/callback` and click **Add**. C1.ai completes the OAuth flow through this URL; DocuSign rejects the authorization request if it isn't registered here. Under **Authentication**, enable **Authorization Code Grant**. @@ -92,7 +92,7 @@ A user with access to the **Docusign Admin console** must perform this task. ## Configure the Docusign connector -To complete this task, you'll need the **Connector Administrator** or **Super Administrator** role in C1 and the relevant set of permissions on your Docusign account: +To complete this task, you'll need the **Connector Administrator** or **Super Administrator** role in C1.ai and the relevant set of permissions on your Docusign account: - To sync access data (READ): Read users, groups, and permissions. @@ -104,11 +104,11 @@ To complete this task, you'll need the **Connector Administrator** or **Super Ad -**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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Docusign v2** and click **Add**. @@ -132,7 +132,7 @@ To complete this task, you'll need the **Connector Administrator** or **Super Ad Choose your **authentication method**: - - **OAuth Authentication** (default) — connects to DocuSign's production environment using C1's managed OAuth app. No additional credentials required. + - **OAuth Authentication** (default) — connects to DocuSign's production environment using C1.ai's managed OAuth app. No additional credentials required. - **Custom App (Demo Environment)** — connects to DocuSign's demo environment (`account-d.docusign.com`) using your own DocuSign developer app. See [Create a Docusign app](#create-a-docusign-app) above to obtain your credentials. @@ -152,10 +152,10 @@ To complete this task, you'll need the **Connector Administrator** or **Super Ad Click **Login with OAuth**. - Log in and authorize C1 with your Docusign instance. + Log in and authorize C1.ai with your Docusign instance. - After authorizing, you'll be redirected back to the C1 integrations page, where an "Authorized as" message is now printed. + After authorizing, you'll be redirected back to the C1.ai integrations page, where an "Authorized as" message is now printed. Click **Save**. @@ -165,14 +165,14 @@ To complete this task, you'll need the **Connector Administrator** or **Super Ad -**Done.** Your Docusign connector is now pulling access data into C1. +**Done.** Your Docusign connector is now pulling access data into C1.ai. **Follow these instructions to use the Docusign 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -184,7 +184,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -295,14 +295,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 C1.ai 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 Docusign connector to. Docusign data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Docusign connector to. Docusign data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Docusign connector is now pulling access data into C1. +**Done.** Your Docusign connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/doppler.mdx b/baton/doppler.mdx index 8c5691bc..12e14c1f 100644 --- a/baton/doppler.mdx +++ b/baton/doppler.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Doppler connector" og:title: "Set up a Doppler connector" -description: "C1 provides identity governance for Doppler. Integrate your Doppler workplace with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Doppler. Integrate your Doppler workplace with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Doppler. Integrate your Doppler workplace with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Doppler. Integrate your Doppler workplace with C1.ai for unified visibility and governance over user access." sidebarTitle: "Doppler" --- -C1 provides identity governance for Doppler. Integrate your Doppler -workplace with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Doppler. Integrate your Doppler +workplace with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -55,11 +55,11 @@ read workplace users or groups and do not work with this connector. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -105,7 +105,7 @@ read workplace users or groups and do not work with this connector. - **Done.** Your Doppler connector is now pulling access data into C1. + **Done.** Your Doppler connector is now pulling access data into C1.ai. @@ -132,6 +132,6 @@ read workplace users or groups and do not work with this connector. - **Done.** Your Doppler connector is now pulling access data into C1. + **Done.** Your Doppler connector is now pulling access data into C1.ai. diff --git a/baton/drata.mdx b/baton/drata.mdx index 141341b2..7d741f3f 100644 --- a/baton/drata.mdx +++ b/baton/drata.mdx @@ -1,15 +1,15 @@ --- title: "Set up a Drata connector" og:title: "Set up a Drata connector" -description: "C1 provides identity governance for Drata. Integrate your Drata workspace with C1 for unified visibility and governance over who has access and what role they hold." -og:description: "C1 provides identity governance for Drata. Integrate your Drata workspace with C1 for unified visibility and governance over who has access and what role they hold." +description: "C1.ai provides identity governance for Drata. Integrate your Drata workspace with C1.ai for unified visibility and governance over who has access and what role they hold." +og:description: "C1.ai provides identity governance for Drata. Integrate your Drata workspace with C1.ai for unified visibility and governance over who has access and what role they hold." sidebarTitle: "Drata" --- {/* stargate: cf-drata-20260606 */} -C1 provides identity governance for Drata. Integrate your Drata workspace with -C1 for unified visibility and governance over who has access and what role they +C1.ai provides identity governance for Drata. Integrate your Drata workspace with +C1.ai for unified visibility and governance over who has access and what role they hold. ## Capabilities @@ -56,11 +56,11 @@ You need a Drata **API key**. The Drata public API is available on the - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -101,7 +101,7 @@ You need a Drata **API key**. The Drata public API is available on the - **Done.** Your Drata connector is now pulling access data into C1. + **Done.** Your Drata connector is now pulling access data into C1.ai. @@ -124,6 +124,6 @@ You need a Drata **API key**. The Drata public API is available on the - **Done.** Your Drata connector is now pulling access data into C1. + **Done.** Your Drata connector is now pulling access data into C1.ai. diff --git a/baton/dropbox.mdx b/baton/dropbox.mdx index f278f456..33759028 100644 --- a/baton/dropbox.mdx +++ b/baton/dropbox.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Dropbox connector" og:title: "Set up a Dropbox connector" -description: "C1 provides identity governance and just-in-time provisioning for Dropbox. Integrate your Dropbox HCM 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 Dropbox. Integrate your Dropbox HCM instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Dropbox. Integrate your Dropbox HCM instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Dropbox. Integrate your Dropbox HCM instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Dropbox" --- @@ -30,8 +30,8 @@ the `events.read` scope (see below) and is off by default, since the event log c on active teams. - These usage events target a single **Dropbox** app resource. For last-login to appear in C1, the - **App** resource type must be enabled in the connector's **Capabilities & configuration** in C1 — + These usage events target a single **Dropbox** app resource. For last-login to appear in C1.ai, the + **App** resource type must be enabled in the connector's **Capabilities & configuration** in C1.ai — this is separate from the `sync-user-last-login` connector option. On a connector **upgraded** from an earlier version that predates the App resource type, the App resource type can default to **off**, and last-login will not surface until it is enabled. After enabling the App resource type (along with @@ -41,7 +41,7 @@ on active teams. ### 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 C1.ai 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 | |-------------|-------------------|-------------| @@ -79,7 +79,7 @@ A user with the **Team Admin** role in Dropbox must perform this task. Select **Team** as the access type. - Give the new app a name, such as "C1". + Give the new app a name, such as "C1.ai". Click **Create app**. @@ -96,7 +96,7 @@ A user with the **Team Admin** role in Dropbox must perform this task. Carefully copy and save the app key and app secret. - Under **OAuth 2**, add whichever redirect URI matches your C1 tenant's domain, and click **Add**: + Under **OAuth 2**, add whichever redirect URI matches your C1.ai tenant's domain, and click **Add**: - Default instance: `https://accounts.conductor.one/oauth/callback` - EU data residency instance: `https://accounts.c1eu.ai/oauth/callback` @@ -161,17 +161,17 @@ This section is only required if you're setting up a self-hosted Dropbox connect To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - The **Admin** role in Dropbox -**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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Dropbox** and click **Add**. @@ -203,24 +203,24 @@ To complete this task, you'll need: Click **Login with OAuth**. - Log in and authorize C1 with your Dropbox instance. + Log in and authorize C1.ai with your Dropbox instance. - After authorizing, you'll be redirected back to the C1 integrations page, where an "Authorized as" message is now printed. + After authorizing, you'll be redirected back to the C1.ai integrations page, where an "Authorized as" message is now printed. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Dropbox connector is now pulling access data into C1. +**Done.** Your Dropbox connector is now pulling access data into C1.ai. **Follow these instructions to use the Dropbox 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -232,7 +232,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -327,14 +327,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 C1.ai 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 Dropbox connector to. Dropbox data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Dropbox connector to. Dropbox data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Dropbox connector is now pulling access data into C1. +**Done.** Your Dropbox connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/duo.mdx b/baton/duo.mdx index 3842edab..0f1e32bb 100644 --- a/baton/duo.mdx +++ b/baton/duo.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Cisco Duo connector" og:title: "Set up a Cisco Duo connector" -description: "C1 provides identity governance for Duo. Integrate your Duo instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." -og:description: "C1 provides identity governance for Duo. Integrate your Duo instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance for Duo. Integrate your Duo instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance for Duo. Integrate your Duo instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Cisco Duo" --- @@ -60,17 +60,17 @@ A user with the **Owner** role in Duo must perform this task. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Duo 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Duo** and click **Add**. @@ -103,13 +103,13 @@ To complete this task, you'll need: -**Done.** Your Duo connector is now pulling access data into C1. +**Done.** Your Duo connector is now pulling access data into C1.ai. **Follow these instructions to use the Duo 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -119,7 +119,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -214,14 +214,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 C1.ai 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 Duo connector to. Duo data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Duo connector to. Duo data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Duo connector is now pulling access data into C1. +**Done.** Your Duo connector is now pulling access data into C1.ai. diff --git a/baton/eks.mdx b/baton/eks.mdx index 348a5e36..0c466f2f 100644 --- a/baton/eks.mdx +++ b/baton/eks.mdx @@ -1,8 +1,8 @@ --- title: "Set up an Amazon EKS connector" -description: "C1 provides identity governance for Elastic Kubernetes Service (EKS). Integrate your EKS instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance for Elastic Kubernetes Service (EKS). Integrate your EKS instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." og:title: "Set up an Amazon Elastic Kubernetes Service connector" -og:description: "C1 provides identity governance for Elastic Kubernetes Service (EKS). Integrate your EKS instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance for Elastic Kubernetes Service (EKS). Integrate your EKS instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Amazon EKS" --- @@ -62,7 +62,7 @@ Gather the relevant set of credentials before you move on. On the EKS dashboard, click **Clusters**. - A list of the clusters in the current region is shown. Make a note of the name of the cluster you want to integrate with C1. + A list of the clusters in the current region is shown. Make a note of the name of the cluster you want to integrate with C1.ai. @@ -92,11 +92,11 @@ If you want to integrate multiple clusters, you must set up an EKS connector for This process has several steps, and we'll walk through them together. -#### Get a C1-provided External ID +#### Get a C1.ai-provided External ID - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Amazon EKS** and click **Add**. @@ -133,7 +133,7 @@ This process has several steps, and we'll walk through them together. Navigate to the [IAM Dashboard](https://us-east-1.console.aws.amazon.com/iamv2/home?) and select **Access Management** > **Roles** > **Create Role**. - Select **Custom Trust Policy** and paste the following into the Trust Policy JSON editor, replacing `EXTERNAL_ID_FROM_C1_INTEGRATIONS_PAGE` with the External ID from C1. + Select **Custom Trust Policy** and paste the following into the Trust Policy JSON editor, replacing `EXTERNAL_ID_FROM_C1_INTEGRATIONS_PAGE` with the External ID from C1.ai. ```json expandable { @@ -518,17 +518,17 @@ Be aware that cluster role binding may take some time to propagate in the cluste **To complete this task, you'll need:** -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of EKS 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **AWS Elastic Kubernetes Service** and click **Add**. @@ -554,7 +554,7 @@ Be aware that cluster role binding may take some time to propagate in the cluste Enter the EKS credentials into the relevant fields. - Finally, tell the connector where to find the identities that will be used for this app in C1. + Finally, tell the connector where to find the identities that will be used for this app in C1.ai. 1. In the **Shared identity source** area of the page, click **Edit**. 2. Select your AWS v2 connector. @@ -569,12 +569,12 @@ Be aware that cluster role binding may take some time to propagate in the cluste -**Done.** Your EKS connector is now pulling access data into C1. +**Done.** Your EKS connector is now pulling access data into C1.ai. **Follow these instructions to use the EKS 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -584,7 +584,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -611,7 +611,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an Carefully copy and save these credentials. We'll use them in Step 2. - Finally, tell the connector where to find the identities that will be used for this app in C1. + Finally, tell the connector where to find the identities that will be used for this app in C1.ai. 1. In the **Shared identity source** area of the page, click **Edit**. 2. Select your AWS v2 connector. @@ -688,14 +688,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 C1.ai 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 EKS connector to. EKS data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the EKS connector to. EKS data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your EKS connector is now pulling access data into C1. +**Done.** Your EKS connector is now pulling access data into C1.ai. diff --git a/baton/elastic.mdx b/baton/elastic.mdx index 4328ab29..287249b4 100644 --- a/baton/elastic.mdx +++ b/baton/elastic.mdx @@ -1,8 +1,8 @@ --- title: "Set up an Elastic connector" og:title: "Set up an Elastic connector" -description: "C1 provides identity governance and just-in-time provisioning for Elastic. Integrate your Elastic 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 Elastic. Integrate your Elastic instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Elastic. Integrate your Elastic instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Elastic. Integrate your Elastic instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Elastic" --- @@ -34,7 +34,7 @@ A user with the **Organization owner** role in Elastic must perform this task. Navigate to the **API keys** tab and click **Create API key**. - Give the new API key a name, such as "C1 integration". + Give the new API key a name, such as "C1.ai integration". Select an expiration for the API key. @@ -52,7 +52,7 @@ A user with the **Organization owner** role in Elastic must perform this task. ### (Optional) Generate an Elastic deployment API key and look up the deployment's endpoint -The credentials generated in this step are required for C1 to sync information on Elastic deployment users and deployment roles, and to provision Elastic deployment role assignments. If you **do not** want to sync or provision deployment users or deployment roles, skip this section. +The credentials generated in this step are required for C1.ai to sync information on Elastic deployment users and deployment roles, and to provision Elastic deployment role assignments. If you **do not** want to sync or provision deployment users or deployment roles, skip this section. @@ -65,7 +65,7 @@ The credentials generated in this step are required for C1 to sync information o In the sidebar, click **API keys** > **Create API key**. - Give the new API key a name, such as "C1 deployment info integration". + Give the new API key a name, such as "C1.ai deployment info integration". Select the **Personal API key** option. @@ -97,17 +97,17 @@ The credentials generated in this step are required for C1 to sync information o To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Elastic 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Elastic** and click **Add**. @@ -136,7 +136,7 @@ To complete this task, you'll need: **Optional.** If you want to sync information on Elastic deployment users and deployment roles, paste the **Deployment API key** and **Deployment endpoint** into their respective fields. - **Optional.** By default, C1 will sync information about all users in all organizations. If you want to limit the sync to a single organization, paste that organization's ID into the **Organization ID** field. + **Optional.** By default, C1.ai will sync information about all users in all organizations. If you want to limit the sync to a single organization, paste that organization's ID into the **Organization ID** field. Click **Save**. @@ -146,23 +146,23 @@ To complete this task, you'll need: -**Done.** Your Elastic connector is now pulling access data into C1. +**Done.** Your Elastic connector is now pulling access data into C1.ai. **Follow these instructions to use the Elastic 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources -[Contact C1's support team](mailto:support@c1.ai) to download the latest version of the connector. +[Contact C1.ai's support team](mailto:support@c1.ai) to download the latest version of the connector. ### Step 1: Set up a new Elastic connector - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -257,14 +257,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 C1.ai 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 Elastic connector to. Elastic data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Elastic connector to. Elastic data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Elastic connector is now pulling access data into C1. +**Done.** Your Elastic connector is now pulling access data into C1.ai. diff --git a/baton/encompass.mdx b/baton/encompass.mdx index f0582d4b..b7a8ceed 100644 --- a/baton/encompass.mdx +++ b/baton/encompass.mdx @@ -1,8 +1,8 @@ --- title: "Set up an Encompass connector" og:title: "Set up an Encompass connector" -description: "C1 provides identity governance and just-in-time provisioning for Encompass. Integrate your Encompass 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 Encompass. Integrate your Encompass instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Encompass. Integrate your Encompass instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Encompass. Integrate your Encompass instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Encompass" --- @@ -23,7 +23,7 @@ We recommend closely monitoring workflows that use this connector and contacting Supports [automatic account provisioning and deprovisioning](/product/admin/account-provisioning) - When a new account is created by C1, the account's password will be sent to a [vault](/product/admin/vaults) + When a new account is created by C1.ai, the account's password will be sent to a [vault](/product/admin/vaults) ## Gather Encompass configuration information @@ -44,17 +44,17 @@ See the Encompass docs for information on how to acquire credentials: [View the To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Encompass 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Encompass** and click **Add**. @@ -87,23 +87,23 @@ To complete this task, you'll need: -**Done.** Your Encompass connector is now pulling access data into C1. +**Done.** Your Encompass connector is now pulling access data into C1.ai. **Follow these instructions to use the Encompass 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai 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 C1.ai's support team](mailto:support@conductorone.com) to download the latest version of the connector. ### Step 1: Set up a new Encompass connector - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -200,14 +200,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 C1.ai 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 Encompass connector to. Encompass data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Encompass connector to. Encompass data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Encompass connector is now pulling access data into C1. +**Done.** Your Encompass connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/env0.mdx b/baton/env0.mdx index 0afbd387..0d2f8eb1 100644 --- a/baton/env0.mdx +++ b/baton/env0.mdx @@ -1,15 +1,15 @@ --- title: "Set up an env0 connector" og:title: "Set up an env0 connector" -description: "C1 provides identity governance for env0. Integrate your env0 organization with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for env0. Integrate your env0 organization with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for env0. Integrate your env0 organization with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for env0. Integrate your env0 organization with C1.ai for unified visibility and governance over user access." sidebarTitle: "env0" --- {/* stargate: cf-env0-20260605 */} -C1 provides identity governance for env0. Integrate your env0 organization with -C1 for unified visibility and governance over who belongs to your env0 +C1.ai provides identity governance for env0. Integrate your env0 organization with +C1.ai for unified visibility and governance over who belongs to your env0 organization, their email and organization role, whether their access is active or still a pending invite, and when they last signed in. @@ -55,11 +55,11 @@ organization members. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -102,7 +102,7 @@ organization members. - **Done.** Your env0 connector is now pulling access data into C1. + **Done.** Your env0 connector is now pulling access data into C1.ai. @@ -126,6 +126,6 @@ organization members. - **Done.** Your env0 connector is now pulling access data into C1. + **Done.** Your env0 connector is now pulling access data into C1.ai. diff --git a/baton/expensify.mdx b/baton/expensify.mdx index 0a1e25a7..42fe6a55 100644 --- a/baton/expensify.mdx +++ b/baton/expensify.mdx @@ -1,8 +1,8 @@ --- title: "Set up an Expensify connector" og:title: "Set up an Expensify connector" -description: "C1 provides identity governance for Expensify. Integrate your Expensify instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Expensify. Integrate your Expensify instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Expensify. Integrate your Expensify instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Expensify. Integrate your Expensify instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Expensify" --- @@ -37,17 +37,17 @@ A user with access to the Expensify Integration Server must perform this task. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Expensify 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Expensify** and click **Add**. @@ -83,13 +83,13 @@ To complete this task, you'll need: -**Done.** Your Expensify connector is now pulling access data into C1. +**Done.** Your Expensify connector is now pulling access data into C1.ai. **Follow these instructions to use the Expensify 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -99,7 +99,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -190,14 +190,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 C1.ai 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 Expensify connector to. Expensify data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Expensify connector to. Expensify data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Expensify connector is now pulling access data into C1. +**Done.** Your Expensify connector is now pulling access data into C1.ai. diff --git a/baton/fabric.mdx b/baton/fabric.mdx index c0dddc8c..79ffef79 100644 --- a/baton/fabric.mdx +++ b/baton/fabric.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Microsoft Fabric connector" og:title: "Set up a Microsoft Fabric connector" -description: "C1 provides identity governance for Microsoft Fabric. Integrate your Fabric tenant with C1 for unified visibility and governance over workspace access." -og:description: "C1 provides identity governance for Microsoft Fabric. Integrate your Fabric tenant with C1 for unified visibility and governance over workspace access." +description: "C1.ai provides identity governance for Microsoft Fabric. Integrate your Fabric tenant with C1.ai for unified visibility and governance over workspace access." +og:description: "C1.ai provides identity governance for Microsoft Fabric. Integrate your Fabric tenant with C1.ai for unified visibility and governance over workspace access." sidebarTitle: "Microsoft Fabric" --- -C1 provides identity governance for Microsoft Fabric. Integrate your Fabric -tenant with C1 for unified visibility and governance over who has access to each +C1.ai provides identity governance for Microsoft Fabric. Integrate your Fabric +tenant with C1.ai for unified visibility and governance over who has access to each workspace. ## Capabilities @@ -47,7 +47,7 @@ and a Fabric administrator to allow service principals to use the Fabric APIs. In the **Fabric admin portal** > **Tenant settings**, enable **Service principals can use Fabric APIs** and add the application (or a security group that contains it) to the allowed list. Grant the service principal at least - Viewer access on the workspaces you want C1 to see. + Viewer access on the workspaces you want C1.ai to see. @@ -55,11 +55,11 @@ and a Fabric administrator to allow service principals to use the Fabric APIs. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -104,7 +104,7 @@ and a Fabric administrator to allow service principals to use the Fabric APIs. - **Done.** Your Microsoft Fabric connector is now pulling access data into C1. + **Done.** Your Microsoft Fabric connector is now pulling access data into C1.ai. @@ -127,6 +127,6 @@ and a Fabric administrator to allow service principals to use the Fabric APIs. - **Done.** Your Microsoft Fabric connector is now pulling access data into C1. + **Done.** Your Microsoft Fabric connector is now pulling access data into C1.ai. diff --git a/baton/factorial.mdx b/baton/factorial.mdx index e3a416dd..efc24ffb 100644 --- a/baton/factorial.mdx +++ b/baton/factorial.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Factorial connector" og:title: "Set up a Factorial connector" -description: "C1 provides identity governance for Factorial. Integrate your Factorial instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Factorial. Integrate your Factorial instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Factorial. Integrate your Factorial instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Factorial. Integrate your Factorial instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Factorial" --- -C1 provides identity governance for Factorial. Integrate your Factorial -instance with C1 for unified visibility and governance over employee access to +C1.ai provides identity governance for Factorial. Integrate your Factorial +instance with C1.ai for unified visibility and governance over employee access to departments. ## Capabilities @@ -50,11 +50,11 @@ You need administrator access in Factorial to create an API key. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -98,7 +98,7 @@ You need administrator access in Factorial to create an API key. - **Done.** Your Factorial connector is now pulling access data into C1. + **Done.** Your Factorial connector is now pulling access data into C1.ai. @@ -123,6 +123,6 @@ You need administrator access in Factorial to create an API key. - **Done.** Your Factorial connector is now pulling access data into C1. + **Done.** Your Factorial connector is now pulling access data into C1.ai. diff --git a/baton/faq.mdx b/baton/faq.mdx index be813d51..4e36fd41 100644 --- a/baton/faq.mdx +++ b/baton/faq.mdx @@ -4,19 +4,19 @@ sidebarTitle: "FAQ" description: "Learn how connectors work under the hood and get answers to frequently asked questions." --- -## Which IP addresses does C1 use for connectors? +## Which IP addresses does C1.ai use for connectors? -See [C1 egress IP addresses](/product/admin/egress-ips) for the full list of IPs to add to your allowlist for outbound connector and function traffic. +See [C1.ai egress IP addresses](/product/admin/egress-ips) for the full list of IPs to add to your allowlist for outbound connector and function traffic. ## What are connectors? -Connectors allow the C1 platform to connect to any SaaS, IaaS, on-prem, or infrastructure tool for the purposes of managing and automating access control. Connectors synchronize data for identities, resources, and access rights, and can orchestrate access changes (such as provisioning accounts) back to the system. +Connectors allow the C1.ai platform to connect to any SaaS, IaaS, on-prem, or infrastructure tool for the purposes of managing and automating access control. Connectors synchronize data for identities, resources, and access rights, and can orchestrate access changes (such as provisioning accounts) back to the system. Connectors are also designed to integrate with any software stack. This includes software-as-a-service applications, infrastructure-as-a-service environments, on-premises apps and directories, cloud directories, and infrastructure such as databases. ## How do connectors work? -Connectors are the connective tissue between a SaaS, IaaS, database, or other technology, and the C1 access control plane. Connectors work by “talking” to a technology stack and extracting identity, resources, entitlements, and grants into a format that can be ingested into the C1 platform. While extracting those different objects, a graph is built of the relationship between resources (parent-child relationship) and between identities and entitlements (grants). This provides a full picture of the current state of identity and access within the boundaries of an application or technology stack. +Connectors are the connective tissue between a SaaS, IaaS, database, or other technology, and the C1.ai access control plane. Connectors work by “talking” to a technology stack and extracting identity, resources, entitlements, and grants into a format that can be ingested into the C1.ai platform. While extracting those different objects, a graph is built of the relationship between resources (parent-child relationship) and between identities and entitlements (grants). This provides a full picture of the current state of identity and access within the boundaries of an application or technology stack. ## Connector capabilities @@ -24,9 +24,9 @@ Connectors can perform a variety of actions based on how they’re structured. R ### Syncing -Syncing keeps data consistent between C1 and your integrated systems. Once set up, a connector regularly retrieves access data (such as accounts, groups, roles, and orgs) from the integrated system and updates the records in the corresponding application in C1. Syncing ensures C1 has an accurate and up-to-date view of user identities and their assigned permissions. All connectors can sync. +Syncing keeps data consistent between C1.ai and your integrated systems. Once set up, a connector regularly retrieves access data (such as accounts, groups, roles, and orgs) from the integrated system and updates the records in the corresponding application in C1.ai. Syncing ensures C1.ai has an accurate and up-to-date view of user identities and their assigned permissions. All connectors can sync. -Specifically, C1 syncs: +Specifically, C1.ai syncs: - **Accounts**, or the user accounts within the integrated system. - **Resources**, or the specific pieces of access (such as group membership or role assignment) in the integrated system and which accounts they’re assigned to. @@ -41,22 +41,22 @@ We’ll also automatically pause a connector’s sync cycle and alert you if sig ### Provisioning -Provisioning automates the process of granting or revoking user access in your connected systems. Once an access change is approved in C1, a connector with provisioning capabilities makes access changes in the integrated system. +Provisioning automates the process of granting or revoking user access in your connected systems. Once an access change is approved in C1.ai, a connector with provisioning capabilities makes access changes in the integrated system. -For example, upon approval in C1, provisioning can automatically create a new employee’s user account in Active Directory and assign them to the relevant Active Directory groups. +For example, upon approval in C1.ai, provisioning can automatically create a new employee’s user account in Active Directory and assign them to the relevant Active Directory groups. -Specifically, C1 can provision: +Specifically, C1.ai can provision: - **Entitlements** by granting a specific user permission to a specific account, such as granting Justin Thyme’s account push permission on the Project-Puffin repo in GitHub. - **Accounts** by creating a brand-new account in the integrated system. -Provisioning is a write operation from C1 to the integrated system. Not all connectors can provision accounts or all the resource types the connector syncs. You can decide whether or not to enable provisioning on provisioning-capable connectors. +Provisioning is a write operation from C1.ai to the integrated system. Not all connectors can provision accounts or all the resource types the connector syncs. You can decide whether or not to enable provisioning on provisioning-capable connectors. ### Ticketing -Select connectors for helpdesk ticketing systems can also be configured to automatically create tickets to track manual provisioning assignments. C1 tracks the status of the tickets it creates and updates the status of the access request in C1 accordingly. +Select connectors for helpdesk ticketing systems can also be configured to automatically create tickets to track manual provisioning assignments. C1.ai tracks the status of the tickets it creates and updates the status of the access request in C1.ai accordingly. -Ticketing is a read-write operation from C1 to the integrated ticketing system. +Ticketing is a read-write operation from C1.ai to the integrated ticketing system. To learn more about configuring ticketing, check out [External ticketing](/product/admin/external-ticketing). @@ -64,15 +64,15 @@ To learn more about configuring ticketing, check out [External ticketing](/produ - C1 offers two hosting methods for connectors: + C1.ai offers two hosting methods for connectors: - - **Cloud-hosted connectors** are the built-in, no-code connectors hosted directly in the C1 tenant and provided via our SaaS service. They are configured on the **Connectors** page of C1. + - **Cloud-hosted connectors** are the built-in, no-code connectors hosted directly in the C1.ai tenant and provided via our SaaS service. They are configured on the **Connectors** page of C1.ai. - **Self-hosted connectors** are connectors that are hosted and run in your own environment. To learn more about your options for deploying self-hosted connectors, go to the [Deploy self-hosted connectors](/baton/deploy) page. Each connector’s documentation shows which hosting methods are available. - Docker is recommended for ease of management, but the hosting environment doesn’t matter to C1. Use whatever best fits your existing setup (Windows/Linux, Docker hosting options, on-prem vs. cloud, etc.). Our Customer Success team is happy to talk through your options with you. + Docker is recommended for ease of management, but the hosting environment doesn’t matter to C1.ai. Use whatever best fits your existing setup (Windows/Linux, Docker hosting options, on-prem vs. cloud, etc.). Our Customer Success team is happy to talk through your options with you. @@ -81,32 +81,32 @@ To learn more about configuring ticketing, check out [External ticketing](/produ - Connectors can be run in different modes depending on your goals and needs. All connectors can be run in **read-only mode**, which pulls identity, resource, and access rights data from the application. Some connectors can alternatively be run in **read-write (provision) mode**, which additionally allows C1 to manage provisioning and deprovisioning for the connected technology. + Connectors can be run in different modes depending on your goals and needs. All connectors can be run in **read-only mode**, which pulls identity, resource, and access rights data from the application. Some connectors can alternatively be run in **read-write (provision) mode**, which additionally allows C1.ai to manage provisioning and deprovisioning for the connected technology. All connectors support read-only mode, and certain connectors support read-write mode. Permissions needed to run the connector and connector-specific setup instructions are provided in the connector’s documentation. - Data from the application or technology needs to be ingested into the C1 platform. Connectors sync and store data in a custom data format: the `.c1z` file format. This file contains all of the identity graph data for a system. + Data from the application or technology needs to be ingested into the C1.ai platform. Connectors sync and store data in a custom data format: the `.c1z` file format. This file contains all of the identity graph data for a system. - When using cloud connectors, the `.c1z` file is an implementation detail and is never seen or touched by the end user. When using self-hosted connectors, the `.c1z` file must be transported to the C1 service to be ingested. + When using cloud connectors, the `.c1z` file is an implementation detail and is never seen or touched by the end user. When using self-hosted connectors, the `.c1z` file must be transported to the C1.ai service to be ingested. You can run multiple instances of the same connector using the same client ID and secret. Each instance must have a unique host identifier — this happens automatically when instances run on separate hosts (since the system hostname is used by default), but if you run multiple instances on the same host, set the `BATON_HOST_ID` environment variable to a unique value for each instance. - Connectors periodically check in with C1 to request work. When tasks are available, any idle instance can claim the next task. This creates a worker-queue architecture: if one connector instance goes down, the remaining instances will pick up subsequent tasks. Note that only one sync task runs at a time per connector, and if an instance processing a task becomes unavailable, there may be a short delay (up to a few minutes) before the task is released and becomes available for another instance to claim. + Connectors periodically check in with C1.ai to request work. When tasks are available, any idle instance can claim the next task. This creates a worker-queue architecture: if one connector instance goes down, the remaining instances will pick up subsequent tasks. Note that only one sync task runs at a time per connector, and if an instance processing a task becomes unavailable, there may be a short delay (up to a few minutes) before the task is released and becomes available for another instance to claim. - C1 automatically syncs each connector on a recurring schedule. The default sync interval depends on your tenant configuration: + C1.ai automatically syncs each connector on a recurring schedule. The default sync interval depends on your tenant configuration: - **Tenants with access requests enabled:** Every **1 hour**. - **All other tenants:** Every **24 hours**. You can customize the sync schedule for individual connectors by setting a fixed interval (minimum 30 minutes) or a cron expression with timezone support. Some connector types enforce a minimum interval that overrides shorter custom schedules. You can also trigger a sync on demand at any time from the connector's integration page. - Connectors that support **continuous sync** supplement the scheduled cycle by listening for change events from the external system in near real-time, reducing the delay between changes and their reflection in C1. Continuous sync works alongside scheduled syncs and does not replace them. + Connectors that support **continuous sync** supplement the scheduled cycle by listening for change events from the external system in near real-time, reducing the delay between changes and their reflection in C1.ai. Continuous sync works alongside scheduled syncs and does not replace them. diff --git a/baton/fastly.mdx b/baton/fastly.mdx index 4816dd4c..41f6825e 100644 --- a/baton/fastly.mdx +++ b/baton/fastly.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Fastly connector" og:title: "Set up a Fastly connector" -description: "C1 provides identity governance and just-in-time provisioning for Fastly. Integrate your Fastly 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 Fastly. Integrate your Fastly instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Fastly. Integrate your Fastly instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Fastly. Integrate your Fastly instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Fastly" --- @@ -35,7 +35,7 @@ A user with the **Superuser** role in Fastly must perform this task. Click **Create Token**. - On the **Create a Token** page, give the new API token a name (such as "C1"). + On the **Create a Token** page, give the new API token a name (such as "C1.ai"). In the **Type** area of the page, select **Automation token** and fill out the form as follows: @@ -43,7 +43,7 @@ A user with the **Superuser** role in Fastly must perform this task. - TLS management: leave the box unchecked - Scope: Select **Read-only access** - Access: Select the relevant services or all services, as appropriate - - Expiration: If you set an expiration date, remember that the connection with C1 will fail if the token expires. + - Expiration: If you set an expiration date, remember that the connection with C1.ai will fail if the token expires. Click **Create Token**. @@ -60,17 +60,17 @@ A user with the **Superuser** role in Fastly must perform this task. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Fastly 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Fastly** and click **Add**. @@ -103,13 +103,13 @@ To complete this task, you'll need: -**Done.** Your Fastly connector is now pulling access data into C1. +**Done.** Your Fastly connector is now pulling access data into C1.ai. **Follow these instructions to use the Fastly 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -119,7 +119,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -212,14 +212,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 C1.ai 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 Fastly connector to. Fastly data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Fastly connector to. Fastly data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Fastly connector is now pulling access data into C1. +**Done.** Your Fastly connector is now pulling access data into C1.ai. diff --git a/baton/fifteenfive.mdx b/baton/fifteenfive.mdx index c587e0b8..dbb5951f 100644 --- a/baton/fifteenfive.mdx +++ b/baton/fifteenfive.mdx @@ -1,8 +1,8 @@ --- title: "Set up 15Five connector" -description: "C1 provides identity governance for 15Five. Integrate your 15Five instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for 15Five. Integrate your 15Five instance with C1.ai for unified visibility and governance over user access." og:title: "Set up 15Five connector" -og:description: "C1 provides identity governance for 15Five. Integrate your 15Five instance with C1 for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for 15Five. Integrate your 15Five instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "15Five" --- @@ -32,17 +32,17 @@ See the 15Five docs for information on how to acquire credentials: [View the doc **To complete this task, you’ll need:** -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of 15Five 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **15Five** and click **Add**. @@ -75,12 +75,12 @@ See the 15Five docs for information on how to acquire credentials: [View the doc -**That’s it!** Your 15Five connector is now pulling access data into C1. +**That’s it!** Your 15Five connector is now pulling access data into C1.ai. **Follow these instructions to use the 15Five 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -90,7 +90,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -179,14 +179,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 C1.ai 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 fifteenfive connector to. fifteenfive data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the fifteenfive connector to. fifteenfive data should be found on the **Entitlements** and **Accounts** tabs. -**That’s it!** Your 15Five connector is now pulling access data into C1. +**That’s it!** Your 15Five connector is now pulling access data into C1.ai. diff --git a/baton/file-connectors.mdx b/baton/file-connectors.mdx index 68282273..6f43d993 100644 --- a/baton/file-connectors.mdx +++ b/baton/file-connectors.mdx @@ -7,18 +7,18 @@ sidebarTitle: "File connectors" --- -**Quick tips for success when uploading files to C1:** +**Quick tips for success when uploading files to C1.ai:** - Use **.xlsx**, **.csv**, or **.c1z** file format. - Include a **User ID** column in your file, or map a data value in your source file to the **User ID** column. - - Map your source file’s data values to C1’s expected data values. + - Map your source file’s data values to C1.ai’s expected data values. ## What are file connectors? File connectors sync application data from apps that do not have an automated connector available, such as non-API-enabled, legacy, or homegrown on-prem apps. -You can add file connectors to C1 in two ways: +You can add file connectors to C1.ai in two ways: - Manually, by uploading a file. - Automatically, by syncing data from an [external datasource](/product/admin/external-datasources). @@ -26,22 +26,22 @@ You can add file connectors to C1 in two ways: **Note:** -C1 allows you to add more than one connector to an application. This is useful if entitlement, user, or permission data is extracted from the target application with multiple exports. +C1.ai allows you to add more than one connector to an application. This is useful if entitlement, user, or permission data is extracted from the target application with multiple exports. ## Supported file formats -Application data can be imported into C1 using three different file formats: +Application data can be imported into C1.ai using three different file formats: - Comma Separated Value (.csv) files (values can be either comma- or tab-separated) - Excel (.xlsx) files -- C1 Baton (.c1z) files: these files are generated using the [Baton protocol](/baton/faq) +- C1.ai Baton (.c1z) files: these files are generated using the [Baton protocol](/baton/faq) Other file formats will not upload successfully. ## Creating Excel and CSV files -C1 allows for custom configurations in your Excel or CSV file, as each file can be dynamically mapped into different data elements in C1, such as username, email, or manager. +C1.ai allows for custom configurations in your Excel or CSV file, as each file can be dynamically mapped into different data elements in C1.ai, such as username, email, or manager. You can use one of our templates as a starting point: @@ -57,7 +57,7 @@ Use this template if your data is organized by entitlements or permissions. ### Expected data values -C1 looks for the following column names to automatically understand and process the data in your uploaded file. You can give the columns in your file any names you like and manually [map the data values](/baton/file-connectors#map-data-values), but if you use the column names listed below, they will be automatically understood and processed by C1 without further intervention from you. +C1.ai looks for the following column names to automatically understand and process the data in your uploaded file. You can give the columns in your file any names you like and manually [map the data values](/baton/file-connectors#map-data-values), but if you use the column names listed below, they will be automatically understood and processed by C1.ai without further intervention from you. **For identity-focused files:** @@ -81,7 +81,7 @@ C1 looks for the following column names to automatically understand and process | Entitlement | Yes | Used with Resource Type and Resource Name to generate a stable entitlement ID — must remain consistent across uploads | | Entitlement Description | | | | Entitlement Display Name | Strongly recommended | | -| Entitlement Slug | Strongly recommended | [A short term that describes the access right or permission](/product/admin/managing-entitlements#rename-the-entitlement), which is shown throughout C1. | +| Entitlement Slug | Strongly recommended | [A short term that describes the access right or permission](/product/admin/managing-entitlements#rename-the-entitlement), which is shown throughout C1.ai. | **Can be included in either file type:** @@ -102,7 +102,7 @@ Follow this process to designate service accounts and system accounts in your fi Add a column titled **User Type** and a column titled **Account Owner** to your file. - Make sure to use these exact column titles so C1 understands how to process the data. + Make sure to use these exact column titles so C1.ai understands how to process the data. In the **User Type** column, use **Service** and **System** to designate these special account types. Any account that is not specifically designated will be interpreted as a user account. @@ -117,7 +117,7 @@ These fields will map account types and account owners respectively, and this in **Why is this process necessary?** -Options for mapping account type and account owner information to the column names of your choice have not yet been added to the [**Set mappings** page](/baton/file-connectors#map-data-values). We’re planning to make this change soon. In the meantime, use the exact column headers **User Type** and **Account Owner** in your spreadsheet so C1 can correctly understand and process the information. +Options for mapping account type and account owner information to the column names of your choice have not yet been added to the [**Set mappings** page](/baton/file-connectors#map-data-values). We’re planning to make this change soon. In the meantime, use the exact column headers **User Type** and **Account Owner** in your spreadsheet so C1.ai can correctly understand and process the information. ### Import last login info @@ -152,7 +152,7 @@ The following date formats are accepted: ## Using .c1z files -Files in the [C1 Baton file format](/baton/faq) are supported natively for application data uploads in a non-lossy format. In other words, the .c1z file preserves all resource metadata, hierarchy, and grant structures that are discovered in an application. When uploading a .c1z file, there is no need to configure file mappings. C1 understands and ingests the application data automatically. +Files in the [C1.ai Baton file format](/baton/faq) are supported natively for application data uploads in a non-lossy format. In other words, the .c1z file preserves all resource metadata, hierarchy, and grant structures that are discovered in an application. When uploading a .c1z file, there is no need to configure file mappings. C1.ai understands and ingests the application data automatically. ## Add a file connector to an app @@ -160,7 +160,7 @@ To add file data to an application: - Navigate to a C1 application and find the **Connectors** area of the page. + Navigate to a C1.ai application and find the **Connectors** area of the page. Click **Import app data** and choose your import method: @@ -169,7 +169,7 @@ To add file data to an application: -C1 will now begin ingesting the data into the C1 application. To review the detected delta between files, click **View logs** on the connector. +C1.ai will now begin ingesting the data into the C1.ai application. To review the detected delta between files, click **View logs** on the connector. **You can upload data to any application, even if the application has another connector.** @@ -180,9 +180,9 @@ This allows you to digest all entitlements for an app, even if an existing conne ## Map data values {/* header name used in links, change with caution */} -When you upload a custom spreadsheet, the data values in your file might not automatically be matched with C1 attributes. For example, a data file that includes a column titled “Last” for a user’s last name might not automatically be understood by C1, which expects the data in that column to be titled “Last Name”. You can avoid needing to map data values by using the column headers listed in the table above. +When you upload a custom spreadsheet, the data values in your file might not automatically be matched with C1.ai attributes. For example, a data file that includes a column titled “Last” for a user’s last name might not automatically be understood by C1.ai, which expects the data in that column to be titled “Last Name”. You can avoid needing to map data values by using the column headers listed in the table above. -To ensure that the data in your spreadsheet maps accurately into C1’s system, map your spreadsheet’s values to those used by C1. +To ensure that the data in your spreadsheet maps accurately into C1.ai’s system, map your spreadsheet’s values to those used by C1.ai. @@ -192,11 +192,11 @@ To ensure that the data in your spreadsheet maps accurately into C1’s system, Click the **…** (more actions) menu and select **Set mappings**. - In the **Set data value mappings** drawer, choose the data values from your source file that align with the data values used by C1. + In the **Set data value mappings** drawer, choose the data values from your source file that align with the data values used by C1.ai. - **Mapping a source file value to each C1 value is not required.** + **Mapping a source file value to each C1.ai value is not required.** - You can leave values that do not apply to your source file’s data unmapped. However, any values in the source file that are not mapped to a C1 data value will not be imported. + You can leave values that do not apply to your source file’s data unmapped. However, any values in the source file that are not mapped to a C1.ai data value will not be imported. @@ -204,18 +204,18 @@ To ensure that the data in your spreadsheet maps accurately into C1’s system, -When you set the mappings, C1 automatically reprocesses the data with the changed mappings. You can see the output of the changes by viewing the log. +When you set the mappings, C1.ai automatically reprocesses the data with the changed mappings. You can see the output of the changes by viewing the log. ## Refresh or replace file data -Periodically, you may need to refresh data in your file connector, whether to prepare for upcoming access review campaigns or simply to refresh the source of truth of accounts and permissions in C1. Doing so is as simple as replacing the current uploaded file with a more current version. +Periodically, you may need to refresh data in your file connector, whether to prepare for upcoming access review campaigns or simply to refresh the source of truth of accounts and permissions in C1.ai. Doing so is as simple as replacing the current uploaded file with a more current version. **Keep Resource Type, Resource Name, and Entitlement values consistent across uploads.** -C1 uses these three values to generate a stable ID for each entitlement. IDs are lowercased and stripped of leading/trailing whitespace, but spaces, hyphens, and underscores are treated as distinct characters. +C1.ai uses these three values to generate a stable ID for each entitlement. IDs are lowercased and stripped of leading/trailing whitespace, but spaces, hyphens, and underscores are treated as distinct characters. -If any of these values change formatting between uploads — for example, `"engineering leaders"` becomes `"engineering-leaders"` — C1 treats the entitlement as new, creates a fresh entry with no configuration, and orphans the original. All manually configured settings on the original entitlement (owner, policies, bindings, and provisioning steps) are lost. +If any of these values change formatting between uploads — for example, `"engineering leaders"` becomes `"engineering-leaders"` — C1.ai treats the entitlement as new, creates a fresh entry with no configuration, and orphans the original. All manually configured settings on the original entitlement (owner, policies, bindings, and provisioning steps) are lost. Keep these column values identical across uploads. If a rename is unavoidable, you will need to reconfigure entitlement settings on the newly created entries. diff --git a/baton/file.mdx b/baton/file.mdx index 8b6c6697..a15d7aa2 100644 --- a/baton/file.mdx +++ b/baton/file.mdx @@ -1,14 +1,14 @@ --- title: "Set up a File connector" -description: "C1 provides identity governance for systems without a native API by syncing identity and access data from a file. Integrate a file-based source with C1 to run user access reviews (UARs)." +description: "C1.ai provides identity governance for systems without a native API by syncing identity and access data from a file. Integrate a file-based source with C1.ai to run user access reviews (UARs)." og:title: "Set up a File connector" -og:description: "C1 provides identity governance for systems without a native API by syncing identity and access data from a file. Integrate a file-based source with C1 to run user access reviews (UARs)." +og:description: "C1.ai provides identity governance for systems without a native API by syncing identity and access data from a file. Integrate a file-based source with C1.ai to run user access reviews (UARs)." sidebarTitle: "File" --- ## Overview -The File connector (`baton-file`) is a **read-only** connector that syncs identity and access data from a local file into C1. It is designed for systems that have no native API: you export users, resources, entitlements, and grants to a file using the baton-file template, and C1 syncs it like any other connector. +The File connector (`baton-file`) is a **read-only** connector that syncs identity and access data from a local file into C1.ai. It is designed for systems that have no native API: you export users, resources, entitlements, and grants to a file using the baton-file template, and C1.ai syncs it like any other connector. Supported input formats: **YAML**, **JSON / JSONC**, **CSV**, and **Excel (XLSX)**. All formats share the same five-section data model — `users`, `resources`, `entitlements`, `direct_user_grants`, and `grant_inheritance_mappings`. See the format-specific guides (`docs/yaml_instructions.md`, `docs/json_instructions.md`, `docs/csv_instructions.md`, `docs/excel_instructions.md`) for the exact schema. @@ -22,24 +22,24 @@ Supported input formats: **YAML**, **JSON / JSONC**, **CSV**, and **Excel (XLSX) | Apps | | — | | Secrets | | — | -Resource types are defined by the input file (via each row's `trait`), so the exact set that appears in C1 depends on your data. The connector is **sync-only** — it does not provision, deprovision, or run actions. +Resource types are defined by the input file (via each row's `trait`), so the exact set that appears in C1.ai depends on your data. The connector is **sync-only** — it does not provision, deprovision, or run actions. **Additional functionality:** -- **Grant inheritance.** In addition to direct user grants, the connector supports resource-to-resource inheritance mappings with configurable depth (`full` or `shallow`), modeled as grant expansion in C1. +- **Grant inheritance.** In addition to direct user grants, the connector supports resource-to-resource inheritance mappings with configurable depth (`full` or `shallow`), modeled as grant expansion in C1.ai. - **Rich user attributes.** MFA/SSO status, employee IDs, login aliases, additional emails, and status details are synced when present in the file. **Notes:** - **Read-only.** The connector cannot create, modify, revoke, or deprovision access in the source system — it only reads what the file describes. - **Full sync only.** Every sync reads the entire file; there is no incremental/targeted sync. -- **File-defined data.** C1 only knows what the file contains. Resource IDs must be globally unique across users and resources. +- **File-defined data.** C1.ai only knows what the file contains. Resource IDs must be globally unique across users and resources. - **File edits apply on the next sync.** When the connector runs as a long-lived service, changes to the file's data — users, resources, entitlements, grants, and inheritance mappings — are picked up automatically at the start of the next sync, with no restart needed. Adding a new resource type, or changing an existing type's trait, does require restarting the connector. If an edited file fails validation, the sync fails with the validation error and the connector keeps serving the last successfully loaded data. A file with no data rows is valid: the connector syncs empty and picks up rows as they are added. If the file is rewritten repeatedly while a sync is running, the sync may fail with a "rewritten faster than syncs can read it" or "kept changing while being loaded" error — the next sync starts fresh; avoid continuous rewrites during syncs. If the file is invalid when the connector first starts (rather than edited mid-run), fix the file and restart the connector. ## Gather File connector credentials -The File connector does not call a vendor API, so there are no third-party credentials to gather. You only need the C1 **Client ID** and **Client Secret** generated in the Configure section below, plus an input file (YAML, JSON/JSONC, CSV, or XLSX) built from the baton-file template. +The File connector does not call a vendor API, so there are no third-party credentials to gather. You only need the C1.ai **Client ID** and **Client Secret** generated in the Configure section below, plus an input file (YAML, JSON/JSONC, CSV, or XLSX) built from the baton-file template. ## Configure the File connector @@ -47,7 +47,7 @@ The File connector does not call a vendor API, so there are no third-party crede **To complete this task, you'll need:** -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - An input file (YAML, JSON/JSONC, CSV, or XLSX) built from the baton-file template @@ -69,7 +69,7 @@ The File connector is **self-hosted** — it runs in your own environment and re - In C1, navigate to **Apps** > **Connectors** > **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** > **Add connector**. Search for **Baton** and click **Add**. @@ -91,7 +91,7 @@ The File connector is **self-hosted** — it runs in your own environment and re ### Step 2: Run the connector -Run the connector binary with your rotated C1 credentials and the path to your input file: +Run the connector binary with your rotated C1.ai credentials and the path to your input file: ```bash baton-file \ @@ -100,9 +100,9 @@ baton-file \ --input /path/to/your-data.xlsx ``` -The connector maintains an ongoing connection with C1, syncing and uploading data at regular intervals. This data is immediately available in the C1 UI for access reviews and access requests. +The connector maintains an ongoing connection with C1.ai, syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. -You can also run baton-file locally in file mode to produce a `.c1z` bundle without C1: +You can also run baton-file locally in file mode to produce a `.c1z` bundle without C1.ai: ```bash baton-file --input /path/to/your-data.yaml # writes sync.c1z @@ -110,7 +110,7 @@ baton-file --input /path/to/your-data.yaml # writes sync.c1z See the connector's README or run `baton-file --help` for all available flags and environment variables. -**Done.** Your File connector is now pulling access data into C1. +**Done.** Your File connector is now pulling access data into C1.ai. diff --git a/baton/fileshare.mdx b/baton/fileshare.mdx index fd994339..85a7e318 100644 --- a/baton/fileshare.mdx +++ b/baton/fileshare.mdx @@ -1,8 +1,8 @@ --- title: Set up a Microsoft Windows File Share connector -og:title: Set up a Microsoft Windows File Share connector - C1 docs -og:description: Integrate your Windows file share NTFS permissions with C1 to run access reviews and govern shared folder access. -description: C1 provides identity governance for Windows file shares. Integrate your file share NTFS permissions with C1 to run user access reviews (UARs) and gain visibility into shared folder access. +og:title: Set up a Microsoft Windows File Share connector - C1.ai docs +og:description: Integrate your Windows file share NTFS permissions with C1.ai to run access reviews and govern shared folder access. +description: C1.ai provides identity governance for Windows file shares. Integrate your file share NTFS permissions with C1.ai to run user access reviews (UARs) and gain visibility into shared folder access. sidebarTitle: Microsoft Windows File Share --- @@ -29,7 +29,7 @@ Grants connect AD groups to folder entitlements. The connector reads each folder - **Groups only** — Only ACEs for Active Directory domain groups (`SidTypeGroup`) produce grants. **Individual user ACEs are ignored**, even if a user has direct access to a folder. User-to-folder access is only visible when it flows through an AD group. - **External matching** — Groups are matched to the `baton-active-directory` connector via `ExternalResourceMatch` using the `downlevel_logon_name` key (i.e., the `DOMAIN\GroupName` format). The AD connector must be configured as a shared identity source. -- **Grant expansion** — Each folder grant includes a `GrantExpandable` annotation pointing to the matched group's `member` entitlement. This allows C1 to expand group membership to see which individual users have access to each folder. +- **Grant expansion** — Each folder grant includes a `GrantExpandable` annotation pointing to the matched group's `member` entitlement. This allows C1.ai to expand group membership to see which individual users have access to each folder. - **Built-in group filtering** — Common built-in and administrative groups are automatically excluded (e.g., Administrators, Backup Operators, Guests, Users, Print Operators, and others). Groups from the `BUILTIN\` and `NT AUTHORITY\` domains are also excluded. - **Inheritance handling** — When `skip-inherited` is enabled (the default), the connector skips grants where the ACE is flagged as inherited or is a duplicate of a parent folder's ACE. This reduces noise by only showing grants where permissions were explicitly assigned. The root folder is exempt from inheritance filtering. - **Deduplication** — When a group appears in multiple ACEs on the same folder, the connector keeps the highest-privilege entry (`Read Write` over `Read Only`) and prefers directly-assigned over inherited. @@ -45,7 +45,7 @@ Unlike most connectors, `baton-fileshare` does not require API tokens or credent Before setting up this connector, ensure: -- **`baton-active-directory` is configured as a shared identity source** in C1. The file share connector discovers Active Directory groups in folder ACLs, and relies on the AD connector to match those groups and their members to C1 identities. +- **`baton-active-directory` is configured as a shared identity source** in C1.ai. The file share connector discovers Active Directory groups in folder ACLs, and relies on the AD connector to match those groups and their members to C1.ai identities. - **A Windows account with file share access** is available. The account running the connector must have: - Read access to the target file share path - Permission to read NTFS ACLs (security descriptors) on the folders within it @@ -59,14 +59,14 @@ The `baton-active-directory` connector must be set up and configured as a shared To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - A Windows account with read access to the file share and NTFS ACLs - The `baton-active-directory` connector already configured as a shared identity source -**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 C1.ai.** *Cloud-hosted connector not currently available.* @@ -74,17 +74,17 @@ To complete this task, you'll need: **Follow these instructions to use the Windows File Share connector, hosted and run in your own environment.** -When running as a Windows service, the 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 as a Windows service, the self-hosted connector maintains an ongoing connection with C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources * [GitHub repository](https://github.com/conductorone/baton-fileshare): Access the source code, report issues, or contribute to the project. -### Step 1: Configure the File Share connector in C1 +### Step 1: Configure the File Share connector in C1.ai -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -157,12 +157,12 @@ Install and start the Windows service: -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 File Share connector to. File share data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the File Share connector to. File share data should be found on the **Entitlements** and **Accounts** tabs. Verify that folders appear with their `Read Only` and `Read Write` entitlements, and that Active Directory groups are correctly associated with folder grants. -**Done.** Your Windows File Share connector is now pulling access data into C1. +**Done.** Your Windows File Share connector is now pulling access data into C1.ai. diff --git a/baton/fireworks-ai.mdx b/baton/fireworks-ai.mdx index ae54aa06..e9e78706 100644 --- a/baton/fireworks-ai.mdx +++ b/baton/fireworks-ai.mdx @@ -1,12 +1,12 @@ --- title: "Set up a Fireworks AI connector" og:title: "Set up a Fireworks AI connector" -description: "Connect Fireworks AI to C1 to govern users, service accounts, roles, and API keys." -og:description: "Connect Fireworks AI to C1 to govern users, service accounts, roles, and API keys." +description: "Connect Fireworks AI to C1.ai to govern users, service accounts, roles, and API keys." +og:description: "Connect Fireworks AI to C1.ai to govern users, service accounts, roles, and API keys." sidebarTitle: "Fireworks AI" --- -C1 provides identity governance for Fireworks AI. The connector syncs account +C1.ai provides identity governance for Fireworks AI. The connector syncs account members, machine identities, role assignments, and API key metadata. ## Capabilities @@ -48,11 +48,11 @@ access, and other users' API keys. - Follow these instructions to use the connector hosted by C1. + Follow these instructions to use the connector hosted by C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -68,7 +68,7 @@ access, and other users' API keys. - **Account ID**: The Fireworks account ID to sync. - **API key**: The API key owned by an account administrator. - - **Base URL**: Leave empty unless C1 support gives you a different Fireworks API URL. + - **Base URL**: Leave empty unless C1.ai support gives you a different Fireworks API URL. @@ -81,7 +81,7 @@ access, and other users' API keys. - **Done.** The Fireworks AI connector is now pulling identity and access data into C1. + **Done.** The Fireworks AI connector is now pulling identity and access data into C1.ai. diff --git a/baton/fis-ibs.mdx b/baton/fis-ibs.mdx index cab8dc0d..7d3e2186 100644 --- a/baton/fis-ibs.mdx +++ b/baton/fis-ibs.mdx @@ -1,8 +1,8 @@ --- title: "Set up a FIS IBS connector" og:title: "Set up a FIS IBS connector" -description: "C1 provides identity governance and just-in-time provisioning for FIS IBS. Integrate your FIS IBS 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 FIS IBS. Integrate your FIS IBS instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for FIS IBS. Integrate your FIS IBS instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for FIS IBS. Integrate your FIS IBS instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "FIS IBS" --- @@ -65,11 +65,11 @@ To configure the FIS IBS connector, you need administrator access to the FIS Cod - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -121,19 +121,19 @@ To configure the FIS IBS connector, you need administrator access to the FIS Cod - **Done.** Your FIS IBS connector is now pulling access data into C1. + **Done.** Your FIS IBS connector is now pulling access data into C1.ai. Follow these instructions to use the [FIS IBS](https://github.com/conductorone/baton-fis-ibs) 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. + When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1.ai, automatically syncing and uploading data at regular intervals. ### Step 1: Set up a new FIS IBS connector - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -233,15 +233,15 @@ To configure the FIS IBS connector, you need administrator access to the FIS Cod - 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 C1.ai 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 FIS IBS connector to. FIS IBS data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the FIS IBS connector to. FIS IBS data should be found on the **Entitlements** and **Accounts** tabs. - **Done.** Your FIS IBS connector is now pulling access data into C1. + **Done.** Your FIS IBS connector is now pulling access data into C1.ai. diff --git a/baton/fivetran.mdx b/baton/fivetran.mdx index f183ce86..df311874 100644 --- a/baton/fivetran.mdx +++ b/baton/fivetran.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Fivetran connector" og:title: "Set up a Fivetran connector" -description: "C1 provides identity governance and just-in-time provisioning for Fivetran. Integrate your Fivetran 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 Fivetran. Integrate your Fivetran instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Fivetran. Integrate your Fivetran instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Fivetran. Integrate your Fivetran instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Fivetran" --- @@ -80,17 +80,17 @@ System key scopes only apply to System Keys. User API Keys inherit permissions f To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Fivetran 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Fivetran** and click **Add**. @@ -123,13 +123,13 @@ To complete this task, you'll need: -**Done.** Your Fivetran connector is now pulling access data into C1. +**Done.** Your Fivetran connector is now pulling access data into C1.ai. **Follow these instructions to use the Fivetran 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -139,7 +139,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -233,14 +233,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 C1.ai 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 Fivetran connector to. Fivetran data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Fivetran connector to. Fivetran data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Fivetran connector is now pulling access data into C1. +**Done.** Your Fivetran connector is now pulling access data into C1.ai. diff --git a/baton/flagsmith.mdx b/baton/flagsmith.mdx index 8d107233..35c8e23d 100644 --- a/baton/flagsmith.mdx +++ b/baton/flagsmith.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Flagsmith connector" og:title: "Set up a Flagsmith connector" -description: "C1 provides identity governance for Flagsmith. Integrate your Flagsmith organisation with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Flagsmith. Integrate your Flagsmith organisation with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Flagsmith. Integrate your Flagsmith organisation with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Flagsmith. Integrate your Flagsmith organisation with C1.ai for unified visibility and governance over user access." sidebarTitle: "Flagsmith" --- -C1 provides identity governance for Flagsmith. Integrate your Flagsmith -organisation with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Flagsmith. Integrate your Flagsmith +organisation with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -48,11 +48,11 @@ project in the organisation, so treat it as a secret. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -95,7 +95,7 @@ project in the organisation, so treat it as a secret. - **Done.** Your Flagsmith connector is now pulling access data into C1. + **Done.** Your Flagsmith connector is now pulling access data into C1.ai. @@ -120,6 +120,6 @@ project in the organisation, so treat it as a secret. - **Done.** Your Flagsmith connector is now pulling access data into C1. + **Done.** Your Flagsmith connector is now pulling access data into C1.ai. diff --git a/baton/fleetdm.mdx b/baton/fleetdm.mdx index c3f9235f..9764aab1 100644 --- a/baton/fleetdm.mdx +++ b/baton/fleetdm.mdx @@ -1,8 +1,8 @@ --- title: "Set up a FleetDM connector" og:title: "Set up a FleetDM connector" -description: "C1 provides identity governance and just-in-time provisioning for FleetDM. Integrate your FleetDM instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." -og:escription: "C1 provides identity governance and just-in-time provisioning for FleetDM. Integrate your FleetDM instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for FleetDM. Integrate your FleetDM instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:escription: "C1.ai provides identity governance and just-in-time provisioning for FleetDM. Integrate your FleetDM instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "FleetDM" --- @@ -36,16 +36,16 @@ Note that the user account associated with the API token or the username and pas To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of FleetDM 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **FleetDM** and click **Add**. @@ -85,13 +85,13 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your FleetDM connector is now pulling access data into C1. +**Done.** Your FleetDM connector is now pulling access data into C1.ai. **Follow these instructions to use the FleetDM 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -100,7 +100,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an ### Step 1: Set up a new FleetDM connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -194,13 +194,13 @@ spec: ### 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. +Create a namespace in which to run C1.ai 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 FleetDM connector to. FleetDM data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the FleetDM connector to. FleetDM data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your FleetDM connector is now pulling access data into C1. +**Done.** Your FleetDM connector is now pulling access data into C1.ai. diff --git a/baton/float.mdx b/baton/float.mdx index 37668864..cd3dfbbf 100644 --- a/baton/float.mdx +++ b/baton/float.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Float connector" og:title: "Set up a Float connector" -description: "C1 provides identity governance for Float. Integrate your Float instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Float. Integrate your Float instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Float. Integrate your Float instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Float. Integrate your Float instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Float" --- -C1 provides identity governance for Float. Integrate your Float -team with C1 for unified visibility and governance over who can sign in +C1.ai provides identity governance for Float. Integrate your Float +team with C1.ai for unified visibility and governance over who can sign in and which department each member belongs to. ## Capabilities @@ -54,11 +54,11 @@ access token. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -103,7 +103,7 @@ access token. - **Done.** Your Float connector is now pulling access data into C1. + **Done.** Your Float connector is now pulling access data into C1.ai. @@ -127,6 +127,6 @@ access token. - **Done.** Your Float connector is now pulling access data into C1. + **Done.** Your Float connector is now pulling access data into C1.ai. diff --git a/baton/floqast.mdx b/baton/floqast.mdx index b47e11da..aa11072e 100644 --- a/baton/floqast.mdx +++ b/baton/floqast.mdx @@ -1,8 +1,8 @@ --- title: "Set up FloQast connector" og:title: "Set up FloQast connector" -description: "C1 provides identity governance for FloQast. Integrate your FloQast instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for FloQast. Integrate your FloQast instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for FloQast. Integrate your FloQast instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for FloQast. Integrate your FloQast instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "FloQast" --- @@ -36,16 +36,16 @@ See the FloQast docs for information on how to acquire credentials: [View the do To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of FloQast 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **FloQast** and click **Add**. @@ -77,22 +77,22 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your FloQast connector is now pulling access data into C1. +**Done.** Your FloQast connector is now pulling access data into C1.ai. **Follow these instructions to use the FloQast 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai 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 C1.ai's support team](mailto:support@conductorone.com) to download the latest version of the connector. ### Step 1: Set up a new FloQast connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -181,12 +181,12 @@ spec: ### 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. +Create a namespace in which to run C1.ai 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 floqast connector to. floqast data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the floqast connector to. floqast data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your FloQast connector is now pulling access data into C1. +**Done.** Your FloQast connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/fluid-topics.mdx b/baton/fluid-topics.mdx index 17570001..1f8a20d8 100644 --- a/baton/fluid-topics.mdx +++ b/baton/fluid-topics.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Fluid Topics connector" og:title: "Set up a Fluid Topics connector" -sdescription: "C1 provides identity governance and just-in-time provisioning for Fluid Topics. Integrate your Fluid Topics (Akamai) 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 Fluid Topics. Integrate your Fluid Topics (Akamai) instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +sdescription: "C1.ai provides identity governance and just-in-time provisioning for Fluid Topics. Integrate your Fluid Topics (Akamai) instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Fluid Topics. Integrate your Fluid Topics (Akamai) instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Fluid Topics" --- @@ -15,7 +15,7 @@ sidebarTitle: "Fluid Topics" The Fluid Topics connector supports [automatic account provisioning](/product/admin/account-provisioning). -When a new account is created by C1, the account's password will be sent to a [vault](/product/admin/vaults). +When a new account is created by C1.ai, the account's password will be sent to a [vault](/product/admin/vaults). This connector does not support account deprovisioning. You must deprovision accounts directly in Fluid Topics. @@ -33,7 +33,7 @@ A user with the **Admin** role in in Fluid Topics must perform this task. In Fluid Topics, navigate to **Administration** > **Integration** > **API keys**. -Create a new API key. Give the new key a name, such as "C1", then click **Create & Add**. +Create a new API key. Give the new key a name, such as "C1.ai", then click **Create & Add**. The **Edit API key** drawer opens. Give the key the **Admin** role. @@ -52,16 +52,16 @@ Locate your newly created API key in the list of keys, and carefully copy and sa To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Fluid Topics 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Fluid Topics** and click **Add**. @@ -96,22 +96,22 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Fluid Topics connector is now pulling access data into C1. +**Done.** Your Fluid Topics connector is now pulling access data into C1.ai. **Follow these instructions to use the Fluid Topics 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources -[Contact C1's support team](mailto:support@c1.ai) to download the latest version of the connector. +[Contact C1.ai's support team](mailto:support@c1.ai) to download the latest version of the connector. ### Step 1: Configure the Fluid Topics connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -203,13 +203,13 @@ spec: ### 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. +Create a namespace in which to run C1.ai 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 Fluid Topics connector to. Fluid Topics data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Fluid Topics connector to. Fluid Topics data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Fluid Topics connector is now pulling access data into C1. +**Done.** Your Fluid Topics connector is now pulling access data into C1.ai. diff --git a/baton/forma.mdx b/baton/forma.mdx index 4d46b24b..24d952cb 100644 --- a/baton/forma.mdx +++ b/baton/forma.mdx @@ -1,12 +1,12 @@ --- title: "Set up a Forma connector" og:title: "Set up a Forma connector" -description: "C1 provides identity governance for Forma. Integrate your Forma instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Forma. Integrate your Forma instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Forma. Integrate your Forma instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Forma. Integrate your Forma instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Forma" --- -C1 provides identity governance for Forma. Integrate your Forma instance with C1 +C1.ai provides identity governance for Forma. Integrate your Forma instance with C1.ai for unified visibility and governance over user access. The connector reads identity and access data from Forma's SCIM 2.0 API. @@ -72,11 +72,11 @@ from the Forma admin console. The connector performs read-only calls. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -123,7 +123,7 @@ from the Forma admin console. The connector performs read-only calls. - **Done.** Your Forma connector is now pulling access data into C1. + **Done.** Your Forma connector is now pulling access data into C1.ai. @@ -148,6 +148,6 @@ from the Forma admin console. The connector performs read-only calls. - **Done.** Your Forma connector is now pulling access data into C1. + **Done.** Your Forma connector is now pulling access data into C1.ai. diff --git a/baton/formal.mdx b/baton/formal.mdx index ac3a8523..16bbdddf 100644 --- a/baton/formal.mdx +++ b/baton/formal.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Formal connector" og:title: "Set up a Formal connector" -description: "C1 provides identity governance and just-in-time provisioning for Formal. Integrate your Formal 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 Formal. Integrate your Formal instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Formal. Integrate your Formal instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Formal. Integrate your Formal instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Formal" --- @@ -18,7 +18,7 @@ sidebarTitle: "Formal" Configuring the connector requires you to pass in credentials generated in Formal. Gather these credentials before you move on. -A user with the **Connector Administrator** or **Super Administrator** role in C1 and the ability to generate API keys in Formal must perform this task. +A user with the **Connector Administrator** or **Super Administrator** role in C1.ai and the ability to generate API keys in Formal must perform this task. ### Generate a Formal API key @@ -30,7 +30,7 @@ Sign into Formal and click the **API Keys** tile. Click **Create API Key**. -Give the new key a name, such as "C1 integration". +Give the new key a name, such as "C1.ai integration". Click **Create**. The new API key is generated. @@ -46,16 +46,16 @@ Carefully and copy and save the API key. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Formal 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Formal** and click **Add**. @@ -87,13 +87,13 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Formal connector is now pulling access data into C1. +**Done.** Your Formal connector is now pulling access data into C1.ai. **Follow these instructions to use the Formal 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -102,7 +102,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an ### Step 1: Set up a new Formal connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -193,13 +193,13 @@ spec: ### 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. +Create a namespace in which to run C1.ai 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 Formal connector to. Formal data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Formal connector to. Formal data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Formal connector is now pulling access data into C1. +**Done.** Your Formal connector is now pulling access data into C1.ai. diff --git a/baton/fortimanager.mdx b/baton/fortimanager.mdx index a8dcae95..fc849d49 100644 --- a/baton/fortimanager.mdx +++ b/baton/fortimanager.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Fortinet FortiManager connector" og:title: "Set up a Fortinet FortiManager connector" -description: "C1 provides read-only identity governance for Fortinet FortiManager management administrator accounts and admin profiles." -og:description: "C1 provides read-only identity governance for Fortinet FortiManager management administrator accounts and admin profiles." +description: "C1.ai provides read-only identity governance for Fortinet FortiManager management administrator accounts and admin profiles." +og:description: "C1.ai provides read-only identity governance for Fortinet FortiManager management administrator accounts and admin profiles." sidebarTitle: "Fortinet FortiManager" --- -C1 provides read-only identity governance for Fortinet FortiManager. Integrate -your FortiManager instance with C1 for unified visibility over privileged +C1.ai provides read-only identity governance for Fortinet FortiManager. Integrate +your FortiManager instance with C1.ai for unified visibility over privileged management administrator accounts and the admin profiles they are assigned. ## Capabilities @@ -29,7 +29,7 @@ It supports two authentication modes; configure one. API-token auth (FortiManager 7.2.2+) sends the token as an HTTP -`Authorization: Bearer` header and stores it as a masked secret in C1. +`Authorization: Bearer` header and stores it as a masked secret in C1.ai. Session auth sends the username and password to `/sys/login/user` to obtain a session key; the password field is not masked. Prefer API-token auth when possible. @@ -40,7 +40,7 @@ auth when possible. In FortiManager, create an administrator with **RPC Permit (JSON API - Access)** enabled and Trusted Hosts restricted to the C1 egress range. + Access)** enabled and Trusted Hosts restricted to the C1.ai egress range. Generate the API token for that admin and copy it. diff --git a/baton/freshbooks.mdx b/baton/freshbooks.mdx index aa34d715..e4ebd6da 100644 --- a/baton/freshbooks.mdx +++ b/baton/freshbooks.mdx @@ -1,8 +1,8 @@ --- title: "Set up a FreshBooks connector" og:title: "Set up a FreshBooks connector" -description: "C1 provides identity governance for FreshBooks. Integrate your FreshBooks instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for FreshBooks. Integrate your FreshBooks instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for FreshBooks. Integrate your FreshBooks instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for FreshBooks. Integrate your FreshBooks instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "FreshBooks" --- @@ -39,7 +39,7 @@ Give the app the following scopes: - user:account:write -Enter whichever redirect URI matches your C1 tenant's domain as the **Redirect URI**: +Enter whichever redirect URI matches your C1.ai tenant's domain as the **Redirect URI**: - Default instance: `https://accounts.conductor.one/oauth/callback` - EU data residency instance: `https://accounts.c1eu.ai/oauth/callback` @@ -96,16 +96,16 @@ Carefully copy and save the **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 C1.ai - Access to the set of FreshBooks 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **FreshBooks** and click **Add**. @@ -136,19 +136,19 @@ Click **Save**. Click **Login with OAuth** and follow the prompts. - After authenticating with FreshBooks, you'll be redirected back to the connector setup page in C1, where you'll see an authorization message. + After authenticating with FreshBooks, you'll be redirected back to the connector setup page in C1.ai, where you'll see an authorization message. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your FreshBooks connector is now pulling access data into C1. +**Done.** Your FreshBooks connector is now pulling access data into C1.ai. **Follow these instructions to use the FreshBooks 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -157,7 +157,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an ### Step 1: Set up a new FreshBooks connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -247,13 +247,13 @@ spec: ### 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. +Create a namespace in which to run C1.ai 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 FreshBooks connector to. FreshBooks data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the FreshBooks connector to. FreshBooks data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your FreshBooks connector is now pulling access data into C1. +**Done.** Your FreshBooks connector is now pulling access data into C1.ai. diff --git a/baton/freshdesk.mdx b/baton/freshdesk.mdx index e76be03e..de2a7ecc 100644 --- a/baton/freshdesk.mdx +++ b/baton/freshdesk.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Freshdesk connector" og:title: "Set up a Freshdesk connector" -description: "C1 provides identity governance and just-in-time provisioning for Freshdesk. Integrate your Freshdesk 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 Freshdesk. Integrate your Freshdesk instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Freshdesk. Integrate your Freshdesk instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Freshdesk. Integrate your Freshdesk instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Freshdesk" --- @@ -54,16 +54,16 @@ In the sample URL `https://example.freshdesk.com`, the domain is `example`. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Freshdesk 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Freshdesk** and click **Add**. @@ -100,13 +100,13 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Freshdesk connector is now pulling access data into C1. +**Done.** Your Freshdesk connector is now pulling access data into C1.ai. **Follow these instructions to use the Freshdesk 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -115,7 +115,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an ### Step 1: Set up a new Freshdesk connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -207,14 +207,14 @@ spec: ### 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. +Create a namespace in which to run C1.ai 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 Freshdesk connector to. Freshdesk data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Freshdesk connector to. Freshdesk data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Freshdesk connector is now pulling access data into C1. +**Done.** Your Freshdesk connector is now pulling access data into C1.ai. diff --git a/baton/freshservice.mdx b/baton/freshservice.mdx index a9319988..155b8c0a 100644 --- a/baton/freshservice.mdx +++ b/baton/freshservice.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Freshservice connector" og:title: "Set up a Freshservice connector" -description: "C1 provides identity governance and just-in-time provisioning for Freshservice. Integrate your Freshservice 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 Freshservice. Integrate your Freshservice instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Freshservice. Integrate your Freshservice instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Freshservice. Integrate your Freshservice instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Freshservice" --- @@ -62,16 +62,16 @@ Carefully and copy and save the API key. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Freshservice 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Freshservice** and click **Add**. @@ -111,13 +111,13 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Freshservice connector is now pulling access data into C1. +**Done.** Your Freshservice connector is now pulling access data into C1.ai. **Follow these instructions to use the Freshservice 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -126,7 +126,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an ### Step 1: Set up a new Freshservice connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -218,13 +218,13 @@ spec: ### 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. +Create a namespace in which to run C1.ai 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 Freshservice connector to. Freshservice data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Freshservice connector to. Freshservice data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Freshservice connector is now pulling access data into C1. +**Done.** Your Freshservice connector is now pulling access data into C1.ai. diff --git a/baton/front.mdx b/baton/front.mdx index e2c90898..eca19c42 100644 --- a/baton/front.mdx +++ b/baton/front.mdx @@ -1,8 +1,8 @@ --- title: "Set up Front connector" og:title: "Set up Front connector" -description: "C1 provides identity governance for Front. Integrate your Front instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Front. Integrate your Front instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Front. Integrate your Front instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Front. Integrate your Front instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Front" --- @@ -33,16 +33,16 @@ See the Front docs for information on how to acquire credentials: [View the docu To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Front 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Front** and click **Add**. @@ -74,22 +74,22 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Front connector is now pulling access data into C1. +**Done.** Your Front connector is now pulling access data into C1.ai. **Follow these instructions to use the Front 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources -[Contact C1's support team](mailto:support@c1.ai) to download the latest version of the connector. +[Contact C1.ai's support team](mailto:support@c1.ai) to download the latest version of the connector. ### Step 1: Set up a new Front connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -178,13 +178,13 @@ spec: ### 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. +Create a namespace in which to run C1.ai 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 front connector to. front data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the front connector to. front data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Front connector is now pulling access data into C1. +**Done.** Your Front connector is now pulling access data into C1.ai. diff --git a/baton/frontegg.mdx b/baton/frontegg.mdx index 802fe1f7..dca232a6 100644 --- a/baton/frontegg.mdx +++ b/baton/frontegg.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Frontegg connector" og:title: "Set up a Frontegg connector" -description: "C1 provides identity governance for Frontegg. Integrate your Frontegg environment with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Frontegg. Integrate your Frontegg environment with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Frontegg. Integrate your Frontegg environment with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Frontegg. Integrate your Frontegg environment with C1.ai for unified visibility and governance over user access." sidebarTitle: "Frontegg" --- -C1 provides identity governance for Frontegg. Integrate your Frontegg -environment with C1 for unified visibility and governance over tenants, users, +C1.ai provides identity governance for Frontegg. Integrate your Frontegg +environment with C1.ai for unified visibility and governance over tenants, users, roles, groups, and permissions. ## Capabilities @@ -79,11 +79,11 @@ Grant relationships synced: - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -129,7 +129,7 @@ Grant relationships synced: - **Done.** Your Frontegg connector is now pulling access data into C1. + **Done.** Your Frontegg connector is now pulling access data into C1.ai. @@ -156,7 +156,7 @@ Grant relationships synced: - **Done.** Your Frontegg connector is now pulling access data into C1. + **Done.** Your Frontegg connector is now pulling access data into C1.ai. diff --git a/baton/fullstory.mdx b/baton/fullstory.mdx index 74f87887..8fdc23b2 100644 --- a/baton/fullstory.mdx +++ b/baton/fullstory.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Fullstory connector" og:title: "Set up a Fullstory connector" -description: "C1 provides identity governance for Fullstory. Integrate your Fullstory instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Fullstory. Integrate your Fullstory instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Fullstory. Integrate your Fullstory instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Fullstory. Integrate your Fullstory instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Fullstory" --- @@ -45,16 +45,16 @@ Copy the **SCIM Base URL** shown on the same page. It typically looks like `http To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Fullstory 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Fullstory** and click **Add**. @@ -86,13 +86,13 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Fullstory connector is now pulling access data into C1. +**Done.** Your Fullstory connector is now pulling access data into C1.ai. **Follow these instructions to use the Fullstory 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -101,7 +101,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an ### Step 1: Set up a new Fullstory connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -190,13 +190,13 @@ spec: ### 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. +Create a namespace in which to run C1.ai 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 Fullstory connector to. Fullstory data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Fullstory connector to. Fullstory data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Fullstory connector is now pulling access data into C1. +**Done.** Your Fullstory connector is now pulling access data into C1.ai. diff --git a/baton/fusionauth.mdx b/baton/fusionauth.mdx index bf9ee1cb..e25635c9 100644 --- a/baton/fusionauth.mdx +++ b/baton/fusionauth.mdx @@ -1,13 +1,13 @@ --- title: "Set up a FusionAuth connector" og:title: "Set up a FusionAuth connector" -description: "C1 provides identity governance for FusionAuth. Integrate your FusionAuth instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for FusionAuth. Integrate your FusionAuth instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for FusionAuth. Integrate your FusionAuth instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for FusionAuth. Integrate your FusionAuth instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "FusionAuth" --- -C1 provides identity governance for FusionAuth. Integrate your FusionAuth -instance with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for FusionAuth. Integrate your FusionAuth +instance with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -50,11 +50,11 @@ instance. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -100,7 +100,7 @@ instance. - **Done.** Your FusionAuth connector is now pulling access data into C1. + **Done.** Your FusionAuth connector is now pulling access data into C1.ai. @@ -125,6 +125,6 @@ instance. - **Done.** Your FusionAuth connector is now pulling access data into C1. + **Done.** Your FusionAuth connector is now pulling access data into C1.ai. diff --git a/baton/galileo-ft.mdx b/baton/galileo-ft.mdx index efa1ffd4..18d94677 100644 --- a/baton/galileo-ft.mdx +++ b/baton/galileo-ft.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Galileo FT connector" og:title: "Set up a Galileo FT connector" -description: "C1 provides identity governance and just-in-time provisioning for Galileo Financial Technologies. Integrate your Galileo FT 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 Galileo Financial Technologies. Integrate your Galileo FT instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Galileo Financial Technologies. Integrate your Galileo FT instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Galileo Financial Technologies. Integrate your Galileo FT instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Galileo Financial Technologies" --- @@ -36,17 +36,17 @@ Configuring the connector requires you to pass in credentials generated in Galil To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Galileo FT 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Galileo FT** and click **Add**. @@ -85,13 +85,13 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Galileo FT connector is now pulling access data into C1. +**Done.** Your Galileo FT connector is now pulling access data into C1.ai. **Follow these instructions to use the Galileo FT 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -101,7 +101,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -198,14 +198,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 C1.ai 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 Galileo FT connector to. Galileo FT data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Galileo FT connector to. Galileo FT data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Galileo FT connector is now pulling access data into C1. +**Done.** Your Galileo FT connector is now pulling access data into C1.ai. diff --git a/baton/gitbook.mdx b/baton/gitbook.mdx index e1eaa2f6..900e0393 100644 --- a/baton/gitbook.mdx +++ b/baton/gitbook.mdx @@ -1,13 +1,13 @@ --- title: "Set up a GitBook connector" og:title: "Set up a GitBook connector" -description: "C1 provides identity governance for GitBook. Integrate your GitBook organization with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for GitBook. Integrate your GitBook organization with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for GitBook. Integrate your GitBook organization with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for GitBook. Integrate your GitBook organization with C1.ai for unified visibility and governance over user access." sidebarTitle: "GitBook" --- -C1 provides identity governance for GitBook. Integrate your GitBook -organization with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for GitBook. Integrate your GitBook +organization with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -73,11 +73,11 @@ reads a single organization. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -123,7 +123,7 @@ reads a single organization. - **Done.** Your GitBook connector is now pulling access data into C1. + **Done.** Your GitBook connector is now pulling access data into C1.ai. @@ -148,6 +148,6 @@ reads a single organization. - **Done.** Your GitBook connector is now pulling access data into C1. + **Done.** Your GitBook connector is now pulling access data into C1.ai. diff --git a/baton/gitea.mdx b/baton/gitea.mdx index 5aa0acd2..5e862a90 100644 --- a/baton/gitea.mdx +++ b/baton/gitea.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Gitea connector" og:title: "Set up a Gitea connector" -description: "C1 provides identity governance for Gitea. Integrate your Gitea instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Gitea. Integrate your Gitea instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Gitea. Integrate your Gitea instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Gitea. Integrate your Gitea instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Gitea" --- -C1 provides identity governance for Gitea. Integrate your Gitea -instance with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Gitea. Integrate your Gitea +instance with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -54,11 +54,11 @@ scope. A token without site-admin rights cannot list users or organizations. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -107,7 +107,7 @@ scope. A token without site-admin rights cannot list users or organizations. - **Done.** Your Gitea connector is now pulling access data into C1. + **Done.** Your Gitea connector is now pulling access data into C1.ai. @@ -134,6 +134,6 @@ scope. A token without site-admin rights cannot list users or organizations. - **Done.** Your Gitea connector is now pulling access data into C1. + **Done.** Your Gitea connector is now pulling access data into C1.ai. diff --git a/baton/gitguardian.mdx b/baton/gitguardian.mdx index 5bc3d2a7..18fe7180 100644 --- a/baton/gitguardian.mdx +++ b/baton/gitguardian.mdx @@ -1,13 +1,13 @@ --- title: "Set up a GitGuardian connector" og:title: "Set up a GitGuardian connector" -description: "C1 provides identity governance for GitGuardian. Integrate your GitGuardian workspace with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for GitGuardian. Integrate your GitGuardian workspace with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for GitGuardian. Integrate your GitGuardian workspace with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for GitGuardian. Integrate your GitGuardian workspace with C1.ai for unified visibility and governance over user access." sidebarTitle: "GitGuardian" --- -C1 provides identity governance for GitGuardian. Integrate your -GitGuardian workspace with C1 for unified visibility and governance over +C1.ai provides identity governance for GitGuardian. Integrate your +GitGuardian workspace with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -55,11 +55,11 @@ create an API token with the required scopes. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -103,7 +103,7 @@ create an API token with the required scopes. - **Done.** Your GitGuardian connector is now pulling access data into C1. + **Done.** Your GitGuardian connector is now pulling access data into C1.ai. @@ -127,6 +127,6 @@ create an API token with the required scopes. - **Done.** Your GitGuardian connector is now pulling access data into C1. + **Done.** Your GitGuardian connector is now pulling access data into C1.ai. diff --git a/baton/github-enterprise-cloud.mdx b/baton/github-enterprise-cloud.mdx index d1d6d5f9..8677f81e 100644 --- a/baton/github-enterprise-cloud.mdx +++ b/baton/github-enterprise-cloud.mdx @@ -1,8 +1,8 @@ --- title: "Set up a GitHub Enterprise Cloud connector" og:title: "Set up a GitHub Enterprise Cloud connector" -description: "C1 provides identity governance and just-in-time provisioning for GitHub Enterprise Cloud. Integrate your GitHub Enterprise Cloud 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 GitHub Enterprise Cloud. Integrate your GitHub Enterprise Cloud instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for GitHub Enterprise Cloud. Integrate your GitHub Enterprise Cloud instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for GitHub Enterprise Cloud. Integrate your GitHub Enterprise Cloud instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "GitHub Enterprise Cloud" --- @@ -24,7 +24,7 @@ new users directly to the enterprise as unaffiliated members. Use a GitHub App, not a personal access token. The app must be installed on -the enterprise and on each organization and repository set that C1 will sync or +the enterprise and on each organization and repository set that C1.ai will sync or manage. Enterprise installation alone does not grant organization or repository API access. @@ -40,21 +40,21 @@ API access. Grant the enterprise installation read access for enterprise members and - organizations. If C1 should discover organization installations, also grant + organizations. If C1.ai should discover organization installations, also grant read access for enterprise organization installations. To invite new - members through C1, also grant **Enterprise people management** write + members through C1.ai, also grant **Enterprise people management** write access on the enterprise installation. - Install the same GitHub App on each organization that C1 should sync. Grant - **Members** read access for sync, or **Members** write access if C1 should + Install the same GitHub App on each organization that C1.ai should sync. Grant + **Members** read access for sync, or **Members** write access if C1.ai should invite users or manage organization and team membership. Grant repository **Metadata** read access and **Administration** read access - for repository access sync. Use **Administration** write access if C1 should + for repository access sync. Use **Administration** write access if C1.ai should manage repository collaborators or team repository access. @@ -106,11 +106,11 @@ API access. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -159,7 +159,7 @@ API access. - **Done.** Your GitHub Enterprise Cloud connector is now pulling access data into C1. + **Done.** Your GitHub Enterprise Cloud connector is now pulling access data into C1.ai. @@ -168,7 +168,7 @@ API access. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -273,13 +273,13 @@ API access. - 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 C1.ai 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 GitHub Enterprise Cloud connector to. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the GitHub Enterprise Cloud connector to. - **Done.** Your GitHub Enterprise Cloud connector is now pulling access data into C1. + **Done.** Your GitHub Enterprise Cloud connector is now pulling access data into C1.ai. diff --git a/baton/github-enterprise.mdx b/baton/github-enterprise.mdx index 035b6038..35a2facf 100644 --- a/baton/github-enterprise.mdx +++ b/baton/github-enterprise.mdx @@ -1,8 +1,8 @@ --- title: "Set up a GitHub Enterprise connector" og:title: "Set up a GitHub Enterprise connector" -description: "C1 provides identity governance and just-in-time provisioning for GitHub Enterprise. Integrate your GitHub 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 GitHub Enterprise. Integrate your GitHub Enterprise instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for GitHub Enterprise. Integrate your GitHub Enterprise instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for GitHub Enterprise. Integrate your GitHub Enterprise instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "GitHub Enterprise" --- @@ -74,12 +74,12 @@ Name your token (for example, **C1 Integration**). Optionally, add a token expir Select the following **Scopes:** - **repo** - select all - - **admin:org** - select all if using C1 for GitHub Enterprise provisioning (see the note below), or **read:org** + - **admin:org** - select all if using C1.ai for GitHub Enterprise provisioning (see the note below), or **read:org** - **user** - select all - **admin:enterprise** - select **read:enterprise** - The **write::org** scope is used by C1 when automatically provisioning and deprovisioning GitHub Enterprise access on your behalf. **If you do not want C1 to perform these tasks for you, do not give your token this scope.** + The **write::org** scope is used by C1.ai when automatically provisioning and deprovisioning GitHub Enterprise access on your behalf. **If you do not want C1.ai to perform these tasks for you, do not give your token this scope.** @@ -97,14 +97,14 @@ If you use SAML SSO, you must authorize the PAT using [these instructions](https Follow these instructions to integrate your GitHub instance by using a [GitHub app](https://docs.github.com/en/apps/creating-github-apps/about-creating-github-apps/about-creating-github-apps). -This process creates a GitHub app that is only available to your GitHub organization, then generates an installation token for that app, which can be used to integrate the GitHub organization with C1. This creates the equivalent of a personal access token, but does not tie the token to a specific identity. +This process creates a GitHub app that is only available to your GitHub organization, then generates an installation token for that app, which can be used to integrate the GitHub organization with C1.ai. This creates the equivalent of a personal access token, but does not tie the token to a specific identity. **Integrating multiple GitHub organizations requires separate GitHub Apps and connectors.** GitHub Enterprise APIs do not support GitHub App tokens and require classic PATs with the [`admin:enterprise`](https://docs.github.com/en/rest/enterprise-teams/enterprise-teams?apiVersion=2022-11-28) scope. -A user with the **Org Owner** permission in the GitHub organization to be integrated with C1 must perform this task. +A user with the **Org Owner** permission in the GitHub organization to be integrated with C1.ai must perform this task. @@ -195,17 +195,17 @@ Click **Install**. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of GitHub Enterprise 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **GitHub Enterprise** and click **Add**. @@ -236,7 +236,7 @@ If you're using a personal access token to set up the connector: 1. Paste the token you generated into the **Personal access token** field. - 1. **Optional.** If you want to sync only specific organizations, enter the organizations' names in the **Organizations** field. If you do not specify specific organizations, C1 will sync all organizations. + 1. **Optional.** If you want to sync only specific organizations, enter the organizations' names in the **Organizations** field. If you do not specify specific organizations, C1.ai will sync all organizations. 1. **Optional.** If you want to sync roles for only some enterprises, add the names of the enterprises in the **Enterprises to sync enterprise roles for** field. @@ -271,21 +271,21 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your GitHub Enterprise connector is now pulling access data into C1. +**Done.** Your GitHub Enterprise connector is now pulling access data into C1.ai. **Follow these instructions to use the GitHub Enterprise connector, hosted and run in your own environment.** -Self-hosted deployment requires **baton-github-enterprise v0.0.4 or later**. Earlier versions fail to register with C1 when deployed in minimal container environments (for example, Debian Bookworm slim on Kubernetes) due to missing OS info fallbacks. +Self-hosted deployment requires **baton-github-enterprise v0.0.4 or later**. Earlier versions fail to register with C1.ai when deployed in minimal container environments (for example, Debian Bookworm slim on Kubernetes) due to missing OS info fallbacks. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 -- A **Client ID** and **Client Secret** from C1 (navigate to **Settings** > **API Credentials** to generate these) +- The **Connector Administrator** or **Super Administrator** role in C1.ai +- A **Client ID** and **Client Secret** from C1.ai (navigate to **Settings** > **API Credentials** to generate these) - Access to the GitHub Enterprise credentials generated by following the instructions above @@ -322,7 +322,7 @@ baton-github-enterprise | `BATON_SYNC_SECRETS` | Set to `true` to sync secrets (API keys). | -The connector connects to your C1 tenant and begins syncing. Verify it appears as **Connected** in **Apps** > **Connectors**. +The connector connects to your C1.ai tenant and begins syncing. Verify it appears as **Connected** in **Apps** > **Connectors**. @@ -359,7 +359,7 @@ baton-github-enterprise \ | `--provisioning` | Enable provisioning and deprovisioning. | -The connector connects to your C1 tenant and begins syncing. Verify it appears as **Connected** in **Apps** > **Connectors**. +The connector connects to your C1.ai tenant and begins syncing. Verify it appears as **Connected** in **Apps** > **Connectors**. diff --git a/baton/github.mdx b/baton/github.mdx index b118f85e..303bc6df 100644 --- a/baton/github.mdx +++ b/baton/github.mdx @@ -1,13 +1,13 @@ --- title: "Set up a GitHub connector" og:title: "Set up a GitHub connector" -description: "C1 provides identity governance and just-in-time provisioning for GitHub. Integrate your GitHub 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 GitHub. Integrate your GitHub instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for GitHub. Integrate your GitHub instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for GitHub. Integrate your GitHub instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "GitHub" --- -**This is an updated and improved version of the GitHub integration!** The v2 version of the GitHub integration adds provisioning support for repositories and modernizes the underlying architecture. If you're setting up a GitHub connector with C1 for the first time, you're in the right place. +**This is an updated and improved version of the GitHub integration!** The v2 version of the GitHub integration adds provisioning support for repositories and modernizes the underlying architecture. If you're setting up a GitHub connector with C1.ai for the first time, you're in the right place. Use this integration if your organization accesses GitHub at `github.com`. If you use a custom domain, follow the instructions to set up the [GitHub Enterprise](/baton/github-enterprise) integration. @@ -25,7 +25,7 @@ Use this integration if your organization accesses GitHub at `github.com`. If yo The GitHub connector supports [automatic account provisioning and deprovisioning](/product/admin/account-provisioning). New accounts will send an invitation to the account owner; if an invitation is pending, the account status will be shown as **Unspecified**. -Repository permissions that are inherited through team membership are labeled as such on the relevant entitlement's **Grants** tab in the C1 web app. +Repository permissions that are inherited through team membership are labeled as such on the relevant entitlement's **Grants** tab in the C1.ai web app. [This connector can sync secrets](/product/admin/inventory) and display them on the **Inventory** page. @@ -69,11 +69,11 @@ Name your token (for example, **C1 Integration**). Optionally, add a token expir Select the following **Scopes:** - **repo** - select all - - **admin:org** - select all if using C1 for GitHub provisioning (see the note below), or **read::org** otherwise + - **admin:org** - select all if using C1.ai for GitHub provisioning (see the note below), or **read::org** otherwise - **user** - select all - The **write::org** scope is used by C1 when automatically provisioning and deprovisioning GitHub access on your behalf. **If you do not want C1 to perform these tasks for you, do not give your token this scope.** + The **write::org** scope is used by C1.ai when automatically provisioning and deprovisioning GitHub access on your behalf. **If you do not want C1.ai to perform these tasks for you, do not give your token this scope.** @@ -136,7 +136,7 @@ In the **Permissions** section of the page, give the token the following permiss - **Metadata**: Read-only access - The repository permissions are used by C1 to sync and display data on repo membership, and to provision repository permissions for GitHub accounts. **If you do not want C1 to sync and display your GitHub organization's repo data, do not give your token these permissions.** + The repository permissions are used by C1.ai to sync and display data on repo membership, and to provision repository permissions for GitHub accounts. **If you do not want C1.ai to sync and display your GitHub organization's repo data, do not give your token these permissions.** @@ -150,12 +150,12 @@ Click **Generate token**. Carefully copy and save the new token. Follow these instructions to integrate your GitHub instance by using a [GitHub app](https://docs.github.com/en/apps/creating-github-apps/about-creating-github-apps/about-creating-github-apps). -This process creates a GitHub app that is only available to your GitHub organization, then generates an installation token for that app, which can be used to integrate the GitHub organization with C1. This creates the equivalent of a personal access token, but does not tie the token to a specific identity. +This process creates a GitHub app that is only available to your GitHub organization, then generates an installation token for that app, which can be used to integrate the GitHub organization with C1.ai. This creates the equivalent of a personal access token, but does not tie the token to a specific identity. -**If you want to integrate multiple GitHub organizations with C1, you must create an app and set up a connector for each one.** +**If you want to integrate multiple GitHub organizations with C1.ai, you must create an app and set up a connector for each one.** -A user with the **Org Owner** permission in the GitHub organization to be integrated with C1 must perform this task. +A user with the **Org Owner** permission in the GitHub organization to be integrated with C1.ai must perform this task. @@ -241,17 +241,17 @@ Click **Install**. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of GitHub 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **GitHub v2** and click **Add**. @@ -280,7 +280,7 @@ If you're using a personal access token to set up the connector: 1. Paste the token you generated into the **Personal access token** field. - 1. **Optional.** If you want to sync only specific GitHub organizations, enter the organizations' names in the **Orgs** field. If you do not specify specific organizations, C1 will sync all organizations. + 1. **Optional.** If you want to sync only specific GitHub organizations, enter the organizations' names in the **Orgs** field. If you do not specify specific organizations, C1.ai will sync all organizations. 1. **Optional.** If you do not want to include archived repos in syncs, click to enable **Omit archived repositories**. @@ -311,13 +311,13 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your GitHub connector is now pulling access data into C1. +**Done.** Your GitHub connector is now pulling access data into C1.ai. **Follow these instructions to use the GitHub 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -329,7 +329,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -458,14 +458,14 @@ The `volumeMounts` and `volumes` entries above are only needed if you're configu -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 C1.ai 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 GitHub connector to. GitHub data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the GitHub connector to. GitHub data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your GitHub connector is now pulling access data into C1. +**Done.** Your GitHub connector is now pulling access data into C1.ai. @@ -478,7 +478,7 @@ Enabling **Optimize sync for large organizations** (env var: `BATON_DIRECT_COLLA - **Direct collaborators only.** GitHub is asked only for users with direct repository access. Team-based access is reconstructed from team membership, which the connector already syncs separately. - **Skips per-team detail calls.** The `members_count` and `repos_count` profile fields are not synced for team resources. -**Enable this option if** your GitHub organization has thousands of repositories or thousands of members and you want faster syncs and fewer API calls. Repository access data in C1 is equivalent — only the way grants are sourced (direct vs. team-expanded) differs. +**Enable this option if** your GitHub organization has thousands of repositories or thousands of members and you want faster syncs and fewer API calls. Repository access data in C1.ai is equivalent — only the way grants are sourced (direct vs. team-expanded) differs. ## Troubleshooting diff --git a/baton/gitlab.mdx b/baton/gitlab.mdx index 6b4278ff..96fcd427 100644 --- a/baton/gitlab.mdx +++ b/baton/gitlab.mdx @@ -1,13 +1,13 @@ --- title: "Set up a GitLab connector" og:title: "Set up a GitLab connector" -description: "C1 provides identity governance for GitLab. Integrate your GitLab instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." -og:description: "C1 provides identity governance for GitLab. Integrate your GitLab instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance for GitLab. Integrate your GitLab instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance for GitLab. Integrate your GitLab instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "GitLab" --- -**This is an updated and improved version of the GitLab integration!** If you're setting up a GitLab connector with C1 for the first time, you're in the right place. +**This is an updated and improved version of the GitLab integration!** If you're setting up a GitLab connector with C1.ai for the first time, you're in the right place. ## Capabilities @@ -23,7 +23,7 @@ The GitLab connector supports [automatic account provisioning and deprovisioning Information on last login is synced from self-hosted GitLab instances; this capability is not supported on GitLab.com due to permissions limitations. -**Access path visibility (optional).** By default, C1 shows effective membership as a single flattened list of grants. Enable the **Sync access paths** setting to instead label each grant by how the access was obtained — direct membership, inheritance from a parent or top-level group, or access through an invited (shared) group — so reviewers can see and act on each access path separately. This setting is off by default and does not change existing grants until you enable it. +**Access path visibility (optional).** By default, C1.ai shows effective membership as a single flattened list of grants. Enable the **Sync access paths** setting to instead label each grant by how the access was obtained — direct membership, inheritance from a parent or top-level group, or access through an invited (shared) group — so reviewers can see and act on each access path separately. This setting is off by default and does not change existing grants until you enable it. ## Gather GitLab credentials @@ -66,7 +66,7 @@ When new GitLab.com accounts are created, they must be assigned to a GitLab grou Navigate to **Menu** > **Groups** > **Your Groups**. -Click on the group you wish to connect to C1. +Click on the group you wish to connect to C1.ai. Make a note of the group name. @@ -82,17 +82,17 @@ If you do not have any groups, follow the prompts to create a new group, and mak To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of GitLab 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **GitLab** and click **Add**. @@ -131,13 +131,13 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your GitLab connector is now pulling access data into C1. +**Done.** Your GitLab connector is now pulling access data into C1.ai. -**Follow these instructions to use the GitLab](https://gitlab.com/C1/baton-gitlab) connector, hosted and run in your own environment.** +**Follow these instructions to use the GitLab](https://gitlab.com/C1.ai/baton-gitlab) 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -147,7 +147,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -246,14 +246,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 C1.ai 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 GitLab connector to. GitLab data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the GitLab connector to. GitLab data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your GitLab connector is now pulling access data into C1. +**Done.** Your GitLab connector is now pulling access data into C1.ai. diff --git a/baton/gke.mdx b/baton/gke.mdx index 1be7f66c..d110f2c5 100644 --- a/baton/gke.mdx +++ b/baton/gke.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Google Kubernetes Engine connector" og:title: "Set up a Google Kubernetes Engine connector" -description: "C1 provides identity governance for Google Kubernetes Engine (GKE). Integrate your GKE cluster with C1 to run user access reviews (UARs) and manage Kubernetes RBAC roles and the GCP IAM role bindings on the cluster's project." -og:description: "C1 provides identity governance for Google Kubernetes Engine (GKE). Integrate your GKE cluster with C1 to run user access reviews (UARs) and manage Kubernetes RBAC roles and the GCP IAM role bindings on the cluster's project." +description: "C1.ai provides identity governance for Google Kubernetes Engine (GKE). Integrate your GKE cluster with C1.ai to run user access reviews (UARs) and manage Kubernetes RBAC roles and the GCP IAM role bindings on the cluster's project." +og:description: "C1.ai provides identity governance for Google Kubernetes Engine (GKE). Integrate your GKE cluster with C1.ai to run user access reviews (UARs) and manage Kubernetes RBAC roles and the GCP IAM role bindings on the cluster's project." sidebarTitle: "Google Kubernetes Engine" --- @@ -140,11 +140,11 @@ In addition, provisioning Kubernetes RBAC roles (ClusterRoles and Roles) require - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -195,19 +195,19 @@ In addition, provisioning Kubernetes RBAC roles (ClusterRoles and Roles) require - **Done.** Your GKE connector is now pulling access data into C1. + **Done.** Your GKE connector is now pulling access data into C1.ai. Follow these instructions to use the [GKE](https://github.com/conductorone/baton-gke) 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Step 1: Set up a new GKE connector - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -307,14 +307,14 @@ In addition, provisioning Kubernetes RBAC roles (ClusterRoles and Roles) require - 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 C1.ai 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 GKE connector to. GKE data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the GKE connector to. GKE data should be found on the **Entitlements** and **Accounts** tabs. - **Done.** Your GKE connector is now pulling access data into C1. + **Done.** Your GKE connector is now pulling access data into C1.ai. diff --git a/baton/gladly.mdx b/baton/gladly.mdx index 3e21ae08..f97ba429 100644 --- a/baton/gladly.mdx +++ b/baton/gladly.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Gladly connector" og:title: "Set up a Gladly connector" -description: "C1 provides identity governance for Gladly. Integrate your Gladly instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Gladly. Integrate your Gladly instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Gladly. Integrate your Gladly instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Gladly. Integrate your Gladly instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Gladly" --- -C1 provides identity governance for Gladly. Integrate your Gladly -instance with C1 for unified visibility and governance over agent access. +C1.ai provides identity governance for Gladly. Integrate your Gladly +instance with C1.ai for unified visibility and governance over agent access. ## Capabilities @@ -50,11 +50,11 @@ API User and grant it API permission. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -102,7 +102,7 @@ API User and grant it API permission. - **Done.** Your Gladly connector is now pulling access data into C1. + **Done.** Your Gladly connector is now pulling access data into C1.ai. @@ -129,6 +129,6 @@ API User and grant it API permission. - **Done.** Your Gladly connector is now pulling access data into C1. + **Done.** Your Gladly connector is now pulling access data into C1.ai. diff --git a/baton/gocd.mdx b/baton/gocd.mdx index b89c77b7..63d87e47 100644 --- a/baton/gocd.mdx +++ b/baton/gocd.mdx @@ -1,14 +1,14 @@ --- title: "Set up a GoCD connector" og:title: "Set up a GoCD connector" -description: "C1 provides identity governance for GoCD. Integrate your GoCD server with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for GoCD. Integrate your GoCD server with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for GoCD. Integrate your GoCD server with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for GoCD. Integrate your GoCD server with C1.ai for unified visibility and governance over user access." sidebarTitle: "GoCD" --- {/* stargate: cf-gocd-20260605 */} -C1 provides identity governance for GoCD. Integrate your GoCD server with C1 for +C1.ai provides identity governance for GoCD. Integrate your GoCD server with C1.ai for unified visibility and governance over who can sign in to GoCD, which of them are administrators, and the security roles each user holds. @@ -55,11 +55,11 @@ so a non-admin token cannot be used. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -104,7 +104,7 @@ so a non-admin token cannot be used. - **Done.** Your GoCD connector is now pulling access data into C1. + **Done.** Your GoCD connector is now pulling access data into C1.ai. @@ -127,6 +127,6 @@ so a non-admin token cannot be used. - **Done.** Your GoCD connector is now pulling access data into C1. + **Done.** Your GoCD connector is now pulling access data into C1.ai. diff --git a/baton/gong.mdx b/baton/gong.mdx index 097e28a8..212da6c6 100644 --- a/baton/gong.mdx +++ b/baton/gong.mdx @@ -1,8 +1,8 @@ --- title: "Set up Gong connector" og:title: "Set up Gong connector" -description: "C1 provides identity governance for Gong. Integrate your Gong instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Gong. Integrate your Gong instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Gong. Integrate your Gong instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Gong. Integrate your Gong instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Gong" --- @@ -40,17 +40,17 @@ This connector requires the following scopes: To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Gong configuration information gathered by following the instructions above -**Follow these instructions to use a built-in, no-code connector hosted by C1.** +**Follow these instructions to use a built-in, no-code connector hosted by C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Gong** and click **Add**. @@ -83,23 +83,23 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Gong connector is now pulling access data into C1. +**Done.** Your Gong connector is now pulling access data into C1.ai. **Follow these instructions to use the Gong connector, hosted and run in your own environment.** -When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources -[Contact C1's support team](mailto:support@c1.ai) to download the latest version of the connector. +[Contact C1.ai's support team](mailto:support@c1.ai) to download the latest version of the connector. ### Step 1: Set up a new Gong connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -192,13 +192,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 C1.ai 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 gong connector to. gong data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the gong connector to. gong data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Gong connector is now pulling access data into C1. +**Done.** Your Gong connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/google-bigquery.mdx b/baton/google-bigquery.mdx index 491d58ad..e7b6e5b6 100644 --- a/baton/google-bigquery.mdx +++ b/baton/google-bigquery.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Google BigQuery connector" og:title: "Set up a Google BigQuery connector" -description: "C1 provides identity governance for Google BigQuery. Integrate your Google BigQuery instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Google BigQuery. Integrate your Google BigQuery instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Google BigQuery. Integrate your Google BigQuery instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Google BigQuery. Integrate your Google BigQuery instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Google BigQuery" --- @@ -81,17 +81,17 @@ Click **Close**. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Google BigQuery 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Google BigQuery** and click **Add**. @@ -124,13 +124,13 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Google BigQuery connector is now pulling access data into C1. +**Done.** Your Google BigQuery connector is now pulling access data into C1.ai. **Follow these instructions to use the Google BigQuery 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -140,7 +140,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -232,14 +232,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 C1.ai 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 BigQuery connector to. Google BigQuery data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Google BigQuery connector to. Google BigQuery data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Google BigQuery connector is now pulling access data into C1. +**Done.** Your Google BigQuery connector is now pulling access data into C1.ai. diff --git a/baton/google-cloud-platform.mdx b/baton/google-cloud-platform.mdx index 3a850136..cca00403 100644 --- a/baton/google-cloud-platform.mdx +++ b/baton/google-cloud-platform.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Google Cloud Platform with Google Workspace connector" og:title: "Set up a Google Cloud Platform with Google Workspace connector" -description: "C1 provides identity governance and just-in-time provisioning for Google Cloud Platform with Google Workspace. Integrate your Google Cloud Platform with 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 Cloud Platform with Google Workspace. Integrate your Google Cloud Platform with Google Workspace instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Google Cloud Platform with Google Workspace. Integrate your Google Cloud Platform with Google Workspace instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Google Cloud Platform with Google Workspace. Integrate your Google Cloud Platform with Google Workspace instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Google Cloud Platform with Google Workspace" --- @@ -27,17 +27,17 @@ sidebarTitle: "Google Cloud Platform with Google Workspace" \*Workforce Identity Federation support is optional and must be configured when you set up the connector. -**What Workforce Identity provisioning covers.** Entitlements on a Workforce Identity pool are the administrative roles bound on the pool itself — who may manage the pool and its providers. Reading them requires `iam.workforcePools.getIamPolicy`, and granting or revoking them additionally requires `iam.workforcePools.setIamPolicy`. The three roles GCP predefines for this (`roles/iam.workforcePoolAdmin`, `roles/iam.workforcePoolEditor`, `roles/iam.workforcePoolViewer`) always appear as entitlements, so a newly created pool can be administered from C1 straight away, and any other role the pool binds appears alongside them. C1 shows who holds each of those roles, including principals GCP grants only while an IAM condition holds. Granting a pool role writes an unconditional binding. If the principal also holds that role under a condition — either by itself or alongside an unconditional binding — C1 refuses the revoke before making any policy change. Remove the conditional binding in GCP, then retry the revoke in C1 to remove any remaining unconditional binding. +**What Workforce Identity provisioning covers.** Entitlements on a Workforce Identity pool are the administrative roles bound on the pool itself — who may manage the pool and its providers. Reading them requires `iam.workforcePools.getIamPolicy`, and granting or revoking them additionally requires `iam.workforcePools.setIamPolicy`. The three roles GCP predefines for this (`roles/iam.workforcePoolAdmin`, `roles/iam.workforcePoolEditor`, `roles/iam.workforcePoolViewer`) always appear as entitlements, so a newly created pool can be administered from C1.ai straight away, and any other role the pool binds appears alongside them. C1.ai shows who holds each of those roles, including principals GCP grants only while an IAM condition holds. Granting a pool role writes an unconditional binding. If the principal also holds that role under a condition — either by itself or alongside an unconditional binding — C1.ai refuses the revoke before making any policy change. Remove the conditional binding in GCP, then retry the revoke in C1.ai to remove any remaining unconditional binding. -Separately, federated identities can be granted and revoked IAM roles on organizations, folders, projects, buckets, and secrets. The connector writes the appropriate GCP principal for each shape — `principal://…/subject/…` for a single user, and `principalSet://…/group/…`, `principalSet://…/attribute.NAME/…` or `principalSet://…/*` for the set-based bindings. Across these resource roles and the pool administrative roles above, when a Shared identity source matches the same identity through more than one workforce pool, C1 refuses a revoke that would remove only one binding and leave the matched identity's access in place through another pool. Remove the duplicate binding in GCP, sync the connector, and retry the revoke. +Separately, federated identities can be granted and revoked IAM roles on organizations, folders, projects, buckets, and secrets. The connector writes the appropriate GCP principal for each shape — `principal://…/subject/…` for a single user, and `principalSet://…/group/…`, `principalSet://…/attribute.NAME/…` or `principalSet://…/*` for the set-based bindings. Across these resource roles and the pool administrative roles above, when a Shared identity source matches the same identity through more than one workforce pool, C1.ai refuses a revoke that would remove only one binding and leave the matched identity's access in place through another pool. Remove the duplicate binding in GCP, sync the connector, and retry the revoke. -Granting access to a **federated group** must be done in GCP. GCP identifies such a group by the value its provider asserts in the `google.groups` claim, which varies by identity provider and cannot be derived from the group itself, so the connector refuses the grant rather than writing a binding that would match no one. Once the `principalSet://…/group/…` binding exists in GCP, the connector syncs it and can revoke it. With a **Shared identity source** configured, C1 matches the asserted group to the group from that source and shows the binding's inherited IAM access for its members in Inventory and access reviews. Configure the Shared identity source when you enable Workforce Identity Federation so group-derived access includes those members. Without it, C1 still shows access held by the federated group binding itself. +Granting access to a **federated group** must be done in GCP. GCP identifies such a group by the value its provider asserts in the `google.groups` claim, which varies by identity provider and cannot be derived from the group itself, so the connector refuses the grant rather than writing a binding that would match no one. Once the `principalSet://…/group/…` binding exists in GCP, the connector syncs it and can revoke it. With a **Shared identity source** configured, C1.ai matches the asserted group to the group from that source and shows the binding's inherited IAM access for its members in Inventory and access reviews. Configure the Shared identity source when you enable Workforce Identity Federation so group-derived access includes those members. Without it, C1.ai still shows access held by the federated group binding itself. -Bindings that address an **open-ended set** of identities — `principalSet://…/attribute.NAME/…` and `principalSet://…/*` — are synced as read-only. C1 shows them against every identity they match, so removing the binding to revoke one person would cut access for everyone matching it; the connector refuses that revoke instead of performing it. Remove those bindings in GCP directly. Subject and group bindings revoke normally, since each maps to exactly one identity or one group. +Bindings that address an **open-ended set** of identities — `principalSet://…/attribute.NAME/…` and `principalSet://…/*` — are synced as read-only. C1.ai shows them against every identity they match, so removing the binding to revoke one person would cut access for everyone matching it; the connector refuses that revoke instead of performing it. Remove those bindings in GCP directly. Subject and group bindings revoke normally, since each maps to exactly one identity or one group. -**Pool membership itself cannot be provisioned.** GCP exposes no API to add or remove identities from a Workforce Identity pool — subjects and groups come from the identity provider's assertion at sign-in. To change who reaches Google Cloud through a pool, manage the user or group in the upstream IdP (for example, in Microsoft Entra ID or Okta) and govern it in C1 through that connector, using the pool's `principalSet://…/group/…` bindings for the mapping. +**Pool membership itself cannot be provisioned.** GCP exposes no API to add or remove identities from a Workforce Identity pool — subjects and groups come from the identity provider's assertion at sign-in. To change who reaches Google Cloud through a pool, manage the user or group in the upstream IdP (for example, in Microsoft Entra ID or Okta) and govern it in C1.ai through that connector, using the pool's `principalSet://…/group/…` bindings for the mapping. -**Pools and providers have a lifecycle of their own.** A pool can be created under an organization and deleted; a provider can be deleted from its pool. Deleting either is a soft delete: it stops authenticating immediately, but GCP keeps the record for 30 days, during which it can be restored in GCP and its ID cannot be reused. Deleting a pool cuts off every identity that signs in through it, not just one person's access. Creating a **provider** is not offered: GCP requires the provider's full OIDC or SAML configuration (issuer URI and client ID/secret, or the identity provider's SAML metadata, plus the attribute mapping), which is not part of what C1 sends when it creates a resource, so it must be created in GCP. Providers hold no IAM policy of their own, so they have no entitlements or grants either way. +**Pools and providers have a lifecycle of their own.** A pool can be created under an organization and deleted; a provider can be deleted from its pool. Deleting either is a soft delete: it stops authenticating immediately, but GCP keeps the record for 30 days, during which it can be restored in GCP and its ID cannot be reused. Deleting a pool cuts off every identity that signs in through it, not just one person's access. Creating a **provider** is not offered: GCP requires the provider's full OIDC or SAML configuration (issuer URI and client ID/secret, or the identity provider's SAML metadata, plus the attribute mapping), which is not part of what C1.ai sends when it creates a resource, so it must be created in GCP. Providers hold no IAM policy of their own, so they have no entitlements or grants either way. @@ -51,7 +51,7 @@ Bindings that address an **open-ended set** of identities — `principalSet:// conditional binding as access held, so a grant there can represent access GCP applies only while its condition holds — check the binding in GCP (Console or `gcloud`) when its exact, currently-in-effect state matters. On Workforce - Identity pools, C1 also shows condition-scoped administrative access as the + Identity pools, C1.ai also shows condition-scoped administrative access as the recovered role held, matching organizations, folders, and projects — check the binding in GCP when its currently-in-effect state matters. A pool Grant or Revoke rewrites the full policy after a GCP read that omits the CEL @@ -62,7 +62,7 @@ Bindings that address an **open-ended set** of identities — `principalSet:// **Revoking conditional access on an organization, folder, or project deletes the condition.** A condition is stored on the IAM binding itself, and GCP does not allow a binding with no members. So when a revoke removes the last member of a conditional binding, GCP deletes the binding and its CEL expression along with it — the same thing `gcloud remove-iam-policy-binding` does. -The connector logs the full expression at `WARN` when this happens, so the connector logs are where the expression survives and can be recovered from. If a conditional binding's CEL expression is something you need to keep, revoke that access directly in GCP rather than through C1, or ensure the binding retains at least one other member. +The connector logs the full expression at `WARN` when this happens, so the connector logs are where the expression survives and can be recovered from. If a conditional binding's CEL expression is something you need to keep, revoke that access directly in GCP rather than through C1.ai, or ensure the binding retains at least one other member. On the IAM Role Assignments model, a grant writes an unconditional binding, so a principal who already holds the role under a condition ends up with unconditional access. On the flat-grants model, a grant joins an existing binding for that role — including a conditional one, when that is the binding already on the policy. A revoke targets the role, so it removes the principal from every binding for that role, conditional ones included. After a revoke that deleted the last member of a conditional binding, a re-grant writes a new unconditional binding. Manage those bindings in GCP when conditions are part of how you control access to an organization, folder, or project. @@ -75,7 +75,7 @@ On the IAM Role Assignments model, a grant writes an unconditional binding, so a Configuring the connector requires credentials from both Google Cloud Platform and the Google Workspace Admin console. You'll complete the following steps: -1. Create a dedicated GCP project for the C1 integration +1. Create a dedicated GCP project for the C1.ai integration 2. Enable the required APIs 3. Create a service account and assign it the necessary permissions 4. Download the service account's JSON key @@ -89,7 +89,7 @@ Configuring the connector requires credentials from both Google Cloud Platform a ### Create a new project -We recommend creating a dedicated GCP project for the C1 integration. This keeps the integration's permissions and audit logs isolated from your other projects. +We recommend creating a dedicated GCP project for the C1.ai integration. This keeps the integration's permissions and audit logs isolated from your other projects. @@ -101,7 +101,7 @@ In the toolbar, click the project select dropdown, and click **NEW PROJECT**. Create a new project for your organization: -- **Project Name**: Choose a name, such as "C1 Integration" +- **Project Name**: Choose a name, such as "C1.ai Integration" - **Organization/Location**: Choose the appropriate Organization/Location @@ -163,8 +163,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 Cloud Platform with Google Workspace Integration" +- **Service account name:** C1.ai Integration +- **Service account description:** for example, "Service account for C1.ai Google Cloud Platform with Google Workspace Integration" Click **CREATE AND CONTINUE**. @@ -226,7 +226,7 @@ The `iam.workforcePool*` permissions are only needed when Workforce Identity Fed versions synced pools without reading their allow policy; the connector now reads it on every sync to produce each pool's entitlements and grants. Without the permission the sync fails — deliberately, because reporting an empty - policy instead would make C1 treat every pool grant it had already synced as + policy instead would make C1.ai treat every pool grant it had already synced as revoked. The error names the permission to add. @@ -260,7 +260,7 @@ Click **ADD KEY** > **Create new key**. Choose **JSON** and click **CREATE**. The new key is created and downloaded to your computer. -Keep the downloaded file safe — you'll upload it when configuring the connector in C1. +Keep the downloaded file safe — you'll upload it when configuring the connector in C1.ai. @@ -284,13 +284,13 @@ Click **Add new** and fill out the form: - **Client ID**: The **Unique ID** you saved from the service account details page - **OAuth Scopes**: Copy and paste in the relevant scopes - - Use the following scopes to give C1 **READ** access (syncing access data): + - Use the following scopes to give C1.ai **READ** access (syncing access data): ```bash https://www.googleapis.com/auth/admin.directory.user.alias.readonly,https://www.googleapis.com/auth/admin.directory.rolemanagement.readonly,https://www.googleapis.com/auth/admin.directory.group.member.readonly,https://www.googleapis.com/auth/admin.directory.group.readonly,https://www.googleapis.com/auth/admin.directory.user.readonly,https://www.googleapis.com/auth/admin.directory.domain.readonly,https://www.googleapis.com/auth/admin.reports.audit.readonly ``` - - Use the following scopes to give C1 **READ/WRITE** access (syncing access data and provisioning access): + - Use the following scopes to give C1.ai **READ/WRITE** access (syncing access data and provisioning access): ```bash https://www.googleapis.com/auth/admin.directory.user.alias.readonly,https://www.googleapis.com/auth/admin.directory.rolemanagement,https://www.googleapis.com/auth/admin.directory.group.member,https://www.googleapis.com/auth/admin.directory.group,https://www.googleapis.com/auth/admin.directory.user.readonly,https://www.googleapis.com/auth/admin.directory.domain.readonly,https://www.googleapis.com/auth/admin.reports.audit.readonly @@ -331,18 +331,18 @@ Before moving on, confirm you have the following ready for the connector configu To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Google Cloud Platform with Google Workspace 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Google Cloud Platform with Google Workspace** and click **Add**. @@ -406,7 +406,7 @@ By default, the connector only syncs roles that are assigned to an IAM policy. T **Optional.** Check the box to **Cloud Infrastructure Access: Use RBAC** to enable the RBAC model for IAM role assignments. When enabled, role assignments are synced as scope binding resources (IAM Role Assignments) instead of flat grants on projects, folders, and organizations. This also enables provisioning of IAM role assignments via the scope binding model. -Enabling this option changes how IAM access data is represented in C1. Flat grants on projects, folders, and organizations will no longer be synced — only the IAM Role Assignment resources will carry that data. Enable this only if your C1 configuration is set up to use the RBAC model. +Enabling this option changes how IAM access data is represented in C1.ai. Flat grants on projects, folders, and organizations will no longer be synced — only the IAM Role Assignment resources will carry that data. Enable this only if your C1.ai configuration is set up to use the RBAC model. @@ -428,14 +428,14 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Google Cloud Platform with Google Workspace connector is now pulling access data into C1. +**Done.** Your Google Cloud Platform with Google Workspace connector is now pulling access data into C1.ai. **Follow these instructions to use the Google Cloud Platform with 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -445,7 +445,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -573,18 +573,18 @@ spec: - Create a namespace in which to run C1 connectors (if desired), then apply + Create a namespace in which to run C1.ai connectors (if desired), then apply the secret config and deployment config files. - Check that the connector data uploaded correctly. In C1, click **Apps**. On + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Google Cloud Platform with Google Workspace connector to. Data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Google Cloud Platform with Google Workspace connector is now pulling access data into C1. +**Done.** Your Google Cloud Platform with Google Workspace connector is now pulling access data into C1.ai. diff --git a/baton/google-identity-platform.mdx b/baton/google-identity-platform.mdx index a26a9f1f..69b77b13 100644 --- a/baton/google-identity-platform.mdx +++ b/baton/google-identity-platform.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Google Identity Platform connector" og:title: "Set up a Google Identity Platform connector" -description: "C1 provides identity governance for Google Identity Platform. Integrate your Google Identity Platform instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." -og:description: "C1 provides identity governance for Google Identity Platform. Integrate your Google Identity Platform instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance for Google Identity Platform. Integrate your Google Identity Platform instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance for Google Identity Platform. Integrate your Google Identity Platform instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Google Identity Platform " --- @@ -35,7 +35,7 @@ In the toolbar, click 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 "C1.ai Integration" - **Organization/Location**: Choose the appropriate Organization/Location @@ -75,8 +75,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 Identity Platform integration" + - **Service account name:** C1.ai Integration + - **Service account description:** for example, "Service account for C1.ai Google Identity Platform integration" - Click **CREATE AND CONTINUE** @@ -126,17 +126,17 @@ Keep the downloaded file safe, you'll use it to set up the connector. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Google Identity Platform 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Google Identity Platform** and click **Add**. @@ -169,13 +169,13 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Google Identity Platform connector is now pulling access data into C1. +**Done.** Your Google Identity Platform connector is now pulling access data into C1.ai. **Follow these instructions to use the Google Identity Platform 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -185,7 +185,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -278,14 +278,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 C1.ai 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 Identity Platform connector to. Google Identity Platform data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Google Identity Platform connector to. Google Identity Platform data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Google Identity Platform connector is now pulling access data into C1. +**Done.** Your Google Identity Platform connector is now pulling access data into C1.ai. diff --git a/baton/google-workspace.mdx b/baton/google-workspace.mdx index 40e5970c..5a60a8f7 100644 --- a/baton/google-workspace.mdx +++ b/baton/google-workspace.mdx @@ -1,17 +1,17 @@ --- 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: "C1.ai provides identity governance and just-in-time provisioning for Google Workspace. Integrate your Google Workspace instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Google Workspace. Integrate your Google Workspace instance with C1.ai 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 C1.ai for the first time, you're in the right place. -This page covers the Google Workspace **connector**, which syncs and provisions access data for identity governance. It does not control how you sign in to C1. To set up signing in to C1 with your Google account, see [Authenticate with Google](/product/how-to/qs-set-up-c1#authenticate-with-google). +This page covers the Google Workspace **connector**, which syncs and provisions access data for identity governance. It does not control how you sign in to C1.ai. To set up signing in to C1.ai with your Google account, see [Authenticate with Google](/product/how-to/qs-set-up-c1#authenticate-with-google). ## Capabilities @@ -33,7 +33,7 @@ Continuous sync streams sign-in activity, app usage, and admin audit events betw ### 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 C1.ai 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 | |-------------|-------------------|-------------| @@ -52,7 +52,7 @@ Connector actions are custom capabilities that extend C1 automations with app-sp | modify_group_settings | `group_key` (string, required)
`allow_external_members` (boolean, optional)
`allow_web_posting` (boolean, optional)
`who_can_post_message` (string, optional)
`message_moderation_level` (string, optional) | Updates settings for an existing Google Group. `who_can_post_message` accepts `ANYONE_CAN_POST`, `ALL_IN_DOMAIN_CAN_POST`, `ALL_MEMBERS_CAN_POST`, `ALL_MANAGERS_CAN_POST`, `ALL_OWNERS_CAN_POST`, or `NONE_CAN_POST`. `message_moderation_level` accepts `MODERATE_NONE`, `MODERATE_NEW_MEMBERS`, `MODERATE_NON_MEMBERS`, or `MODERATE_ALL_MESSAGES`. Other values are rejected. | | update_user_manager | `user_id` (string, required)
`manager_email` (string, required) | Updates the manager relation for a user in Google Workspace. Updates the 'manager' entry in the user's Relations field | | update_user_profile | `user_id` (resource ID, required)
`given_name` (string, optional)
`family_name` (string, optional)
`recovery_email` (string, optional)
`recovery_phone` (string, optional)
`department` (string, optional)
`job_title` (string, optional)
`cost_center` (string, optional)
`employee_type` (string, optional)
`employee_id` (string, optional)
`manager_email` (string, optional)
`custom_schemas` (JSON string, optional) | Applies a partial update to a user's profile using patch semantics (only the provided fields change). Supports name fields, recovery details, Employee Information attributes (department, job title, cost center, employee ID, employee type), the manager relation, and custom-schema attribute values. Custom-schema definitions must already exist in the Workspace tenant. At least one updatable field is required. One narrow exception: an `employee_id` change that reduces the number of external IDs on the account (clearing it, or consolidating duplicate entries down to the new value) uses a full-object update instead of a sparse patch (Google does not reliably shrink a repeated field via patch), which widens the read-modify-write window to the whole user for that specific call. An empty or invalid `manager_email` does not fail the call when another provided field is valid — see the partial-success note below. | -| update_user | `user_id` (resource ID, required)
`user_profile` (JSON string, required) | Updates a user's profile from a `user_profile` JSON object (keys: `given_name`, `family_name`, `recovery_email`, `recovery_phone`, `department`, `job_title`, `cost_center`, `employee_type`, `employee_id`, `manager_email`, `custom_schemas`). Consumed by C1 push rules for automated profile sync. Same partial-success behavior as `update_user_profile` for `manager_email`. | +| update_user | `user_id` (resource ID, required)
`user_profile` (JSON string, required) | Updates a user's profile from a `user_profile` JSON object (keys: `given_name`, `family_name`, `recovery_email`, `recovery_phone`, `department`, `job_title`, `cost_center`, `employee_type`, `employee_id`, `manager_email`, `custom_schemas`). Consumed by C1.ai push rules for automated profile sync. Same partial-success behavior as `update_user_profile` for `manager_email`. | | make_admin | `user_id` (resource ID, required)
`status` (boolean, required) | Promotes (`status=true`) or demotes (`status=false`) a user to/from super administrator | @@ -67,7 +67,7 @@ Both actions return `skipped_fields`, a comma-separated list naming any provided ### Example automations -The following examples show how to sequence connector actions for common Google Workspace workflows. Enabling and disabling accounts uses the [Account lifecycle action](/product/admin/automations-steps-reference#account-lifecycle-action) step, with its own **Target account** selector. Every other action listed maps to a [Perform connector action](/product/admin/automations-steps-reference#perform-connector-action) step in the C1 automation builder. +The following examples show how to sequence connector actions for common Google Workspace workflows. Enabling and disabling accounts uses the [Account lifecycle action](/product/admin/automations-steps-reference#account-lifecycle-action) step, with its own **Target account** selector. Every other action listed maps to a [Perform connector action](/product/admin/automations-steps-reference#perform-connector-action) step in the C1.ai automation builder. #### Employee offboarding @@ -106,7 +106,7 @@ You need: - **Permission to create the project**, if you are creating a new one: **Project Creator** (`roles/resourcemanager.projectCreator`), granted at the organization or folder level. A project-level role cannot create a project. Skip this if you are using an existing project. - **Google Cloud roles on the project.** **Owner** covers everything else. Otherwise, grant three roles: **Service Usage Admin** (`roles/serviceusage.serviceUsageAdmin`) to enable APIs, **Service Account Creator** (`roles/iam.serviceAccountCreator`) to create the service account, and **Service Account Key Admin** (`roles/iam.serviceAccountKeyAdmin`) to create its JSON key. These roles belong to you, the person doing the setup. The service account itself needs no project role. See [Allow service account key creation](#allow-service-account-key-creation). - **A Google Workspace super admin** to authorize domain-wide delegation and to act as the impersonated administrator. -- Either the **Connector Administrator** or **Super Administrator** role in C1. +- Either the **Connector Administrator** or **Super Administrator** role in C1.ai. **Check your organization's key policy first.** Google organizations created on or after May 3, 2024 block service account key creation by default. The connector requires a JSON key, so confirm you can create one before you start. See [Allow service account key creation](#allow-service-account-key-creation). @@ -117,8 +117,8 @@ You need: | What | Why it matters | | :--- | :--- | | **Enabled APIs** | The connector calls the Admin SDK and Cloud Identity APIs, plus the Groups Settings API if you use group settings. The Admin SDK API must be enabled. See the table below for the others. | -| **Service account** | The single identity C1 authenticates as. It needs no project IAM role. | -| **JSON key** | The credential you upload to C1. Creating one requires the Service Account Key Admin role and an organization policy that permits key creation. | +| **Service account** | The single identity C1.ai authenticates as. It needs no project IAM role. | +| **JSON key** | The credential you upload to C1.ai. Creating one requires the Service Account Key Admin role and an organization policy that permits key creation. | | **Domain-wide delegation** | The Workspace-side grant that authorizes the service account's scopes. This is what actually lets the connector read and write directory data. | @@ -145,7 +145,7 @@ In the toolbar, open the project select dropdown and click **NEW PROJECT**. Create a new project for your organization: - - **Project Name**: Choose a name, such as "C1 Integration" + - **Project Name**: Choose a name, such as "C1.ai Integration" - **Organization/Location**: Choose the appropriate Organization/Location @@ -217,7 +217,7 @@ gcloud services list --enabled --project=YOUR_PROJECT_ID ### Create a service account -Create the service account C1 will authenticate as. +Create the service account C1.ai will authenticate as. @@ -229,8 +229,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:** C1.ai Integration + - **Service account description:** for example, "Service account for C1.ai Google Workspace Integration" - Click **CREATE AND CONTINUE** @@ -279,7 +279,7 @@ In the console, the **ADD KEY** option is unavailable and Google reports that se | :--- | :--- | | IAM permission | `iam.serviceAccountKeys.create`, granted by the **Service Account Key Admin** role (`roles/iam.serviceAccountKeyAdmin`). The basic **Editor** role also includes it. | | Organization policy | `constraints/iam.disableServiceAccountKeyCreation` must not be enforced on the project. A managed equivalent, `iam.managed.disableServiceAccountKeyCreation`, controls the same behavior. | -| Related policies | `constraints/iam.serviceAccountKeyExpiryHours` caps how long new keys stay valid. If your organization sets it, plan to rotate the key in C1 before it expires. | +| Related policies | `constraints/iam.serviceAccountKeyExpiryHours` caps how long new keys stay valid. If your organization sets it, plan to rotate the key in C1.ai before it expires. | Grant the key admin role to whoever creates the key: @@ -400,7 +400,7 @@ Click **AUTHORIZE**. ### OAuth scopes -Choose one of the two sets below. Read-only access lets C1 sync access data. Read/write access lets C1 sync access data and provision access. +Choose one of the two sets below. Read-only access lets C1.ai sync access data. Read/write access lets C1.ai sync access data and provision access. @@ -446,9 +446,9 @@ https://www.googleapis.com/auth/admin.directory.domain.readonly, https://www.goo -The write scopes let C1 provision and deprovision access. **If you do not want C1 to perform these tasks, use the read-only scope set.** Read-only still syncs users, groups, roles, and enterprise applications, so it is sufficient when you use Google Workspace as your [directory](#set-google-workspace-as-your-c1-directory) and run access reviews. +The write scopes let C1.ai provision and deprovision access. **If you do not want C1.ai to perform these tasks, use the read-only scope set.** Read-only still syncs users, groups, roles, and enterprise applications, so it is sufficient when you use Google Workspace as your [directory](#set-google-workspace-as-your-c1-directory) and run access reviews. -The read-only set has one exception. `admin.directory.user.security` appears in both sets, and it permits three actions that revoke a user's access: `sign_out_user`, `delete_all_oauth_tokens`, and `delete_all_application_passwords`. These actions remain available with the read-only set. **If you do not want C1 to perform these tasks, do not grant this scope.** The connector then stops discovering OAuth apps and stops syncing enterprise applications. +The read-only set has one exception. `admin.directory.user.security` appears in both sets, and it permits three actions that revoke a user's access: `sign_out_user`, `delete_all_oauth_tokens`, and `delete_all_application_passwords`. These actions remain available with the read-only set. **If you do not want C1.ai to perform these tasks, do not grant this scope.** The connector then stops discovering OAuth apps and stops syncing enterprise applications. ### Find your customer ID and primary domain @@ -475,16 +475,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 C1.ai. -**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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Google Workspace v2** and click **Add**. @@ -510,7 +510,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 your primary domain. If you leave this field blank, C1 will sync all available domains. +**Optional.** If you want to limit which domains C1.ai syncs, in the **Domain** field, enter your primary domain. If you leave this field blank, C1.ai will sync all available domains. In the **Administrator email** field, enter the email address of a Google Workspace super admin. The service account impersonates this user. @@ -526,13 +526,13 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Google Workspace connector is now pulling access data into C1. +**Done.** Your Google Workspace connector is now pulling access data into C1.ai. **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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -544,7 +544,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector** +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector** Search for **Baton** and click **Add** @@ -654,20 +654,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 C1.ai 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 C1.ai, 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. -**Done.** Your Google Workspace connector is now pulling access data into C1. +**Done.** Your Google Workspace connector is now pulling access data into C1.ai. -## Set Google Workspace as your C1 directory +## Set Google Workspace as your C1.ai directory -If Google Workspace is your source of truth for who works at your company, designate the connector's app as your [directory](/product/admin/directory). C1 then creates a C1 user for each Workspace account it syncs, and accounts from your other connectors attach to those users. +If Google Workspace is your source of truth for who works at your company, designate the connector's app as your [directory](/product/admin/directory). C1.ai then creates a C1.ai user for each Workspace account it syncs, and accounts from your other connectors attach to those users. Importing users and groups doesn't require provisioning. If all you want is a directory and access reviews, the read-only scope set in [OAuth scopes](#oauth-scopes) is sufficient, and the service account still needs no Google Cloud IAM role. @@ -678,7 +678,7 @@ Importing users and groups doesn't require provisioning. If all you want is a di Wait for the connector's first sync to finish. An app becomes available to select only after it has synced at least once. -In C1, navigate to **Directory** > **Directory sources**. +In C1.ai, navigate to **Directory** > **Directory sources**. On the **Directories** tab, click **Add directory data source**. @@ -687,18 +687,18 @@ On the **Directories** tab, click **Add directory data source**. Select the app your Google Workspace connector is attached to. -**Optional.** [Limit which accounts will be pulled into C1](/product/admin/directory#optional-limit-which-accounts-will-be-pulled-into-c1) or [configure merge matching](/product/admin/directory#configure-merge-matching). You can change both later. +**Optional.** [Limit which accounts will be pulled into C1.ai](/product/admin/directory#optional-limit-which-accounts-will-be-pulled-into-c1) or [configure merge matching](/product/admin/directory#configure-merge-matching). You can change both later. Click **Create directory**. -For how directory accounts become C1 users, and how accounts from non-directory apps find an owner, see [Connect a directory](/product/admin/directory). +For how directory accounts become C1.ai users, and how accounts from non-directory apps find an owner, see [Connect a directory](/product/admin/directory). ## 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 C1.ai 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/googleads.mdx b/baton/googleads.mdx index 633814ad..7fb1b577 100644 --- a/baton/googleads.mdx +++ b/baton/googleads.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Google Ads connector" og:title: "Set up a Google Ads connector" -description: "C1 provides identity governance for Google Ads. Integrate your Google Ads instance with C1 to run user access reviews (UARs)." -og:description: "C1 provides identity governance for Google Ads. Integrate your Google Ads instance with C1 to run user access reviews (UARs)." +description: "C1.ai provides identity governance for Google Ads. Integrate your Google Ads instance with C1.ai to run user access reviews (UARs)." +og:description: "C1.ai provides identity governance for Google Ads. Integrate your Google Ads instance with C1.ai to run user access reviews (UARs)." sidebarTitle: "Google Ads" --- @@ -19,7 +19,7 @@ sidebarTitle: "Google Ads" **To complete this task, you'll need:** -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - A Google Ads account with a developer token - A service account credentials JSON file diff --git a/baton/gorgias.mdx b/baton/gorgias.mdx index d421a960..3b18e748 100644 --- a/baton/gorgias.mdx +++ b/baton/gorgias.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Gorgias connector" og:title: "Set up a Gorgias connector" -description: "C1 provides identity governance for Gorgias. Integrate your Gorgias instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Gorgias. Integrate your Gorgias instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Gorgias. Integrate your Gorgias instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Gorgias. Integrate your Gorgias instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Gorgias" --- -C1 provides identity governance for Gorgias. Integrate your Gorgias account -with C1 for unified visibility and governance over agent access. +C1.ai provides identity governance for Gorgias. Integrate your Gorgias account +with C1.ai for unified visibility and governance over agent access. ## Capabilities @@ -49,11 +49,11 @@ can see every agent on the account. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -99,7 +99,7 @@ can see every agent on the account. - **Done.** Your Gorgias connector is now pulling access data into C1. + **Done.** Your Gorgias connector is now pulling access data into C1.ai. @@ -124,6 +124,6 @@ can see every agent on the account. - **Done.** Your Gorgias connector is now pulling access data into C1. + **Done.** Your Gorgias connector is now pulling access data into C1.ai. diff --git a/baton/grafana.mdx b/baton/grafana.mdx index 0dcf40fe..963cc005 100644 --- a/baton/grafana.mdx +++ b/baton/grafana.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Grafana connector" og:title: "Set up a Grafana connector" -description: "C1 provides identity governance and just-in-time provisioning for Grafana. Integrate your Grafana 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 Grafana. Integrate your Grafana instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Grafana. Integrate your Grafana instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Grafana. Integrate your Grafana instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Grafana" --- @@ -23,14 +23,14 @@ Team membership can be granted and revoked. Grafana RBAC roles that a team holds **Roles are optional** -IRM / OnCall RBAC roles are available only on Grafana Cloud and Enterprise. Role sync is disabled by default — enable the **Role** resource type in the connector's settings in C1 when your instance has access-control. +IRM / OnCall RBAC roles are available only on Grafana Cloud and Enterprise. Role sync is disabled by default — enable the **Role** resource type in the connector's settings in C1.ai when your instance has access-control. The Grafana connector supports both **self-hosted Grafana** instances and **Grafana Cloud**. The required credentials and provisioning behavior differ between the two — see [Gather Grafana credentials](#gather-grafana-credentials) below. The Grafana connector supports [automatic account provisioning and deprovisioning](/product/admin/account-provisioning). -For self-hosted Grafana, when a new account is created by C1, the account's password is sent to a [vault](/product/admin/vaults). +For self-hosted Grafana, when a new account is created by C1.ai, the account's password is sent to a [vault](/product/admin/vaults). For Grafana Cloud, account creation is invite-based and no connector-generated password is returned. **Grafana Cloud: enabling the basic login form is a prerequisite for creating brand-new users** @@ -45,7 +45,7 @@ With the service-account token the connector uses, this means: * **Users who already exist in the instance** (provisioned earlier via SSO, SCIM, or grafana.com) are added to the organization normally — account provisioning works for them without any change. * **Brand-new users** cannot be created until you either: - * enable [SCIM provisioning](https://grafana.com/docs/grafana/latest/setup-grafana/configure-access/configure-scim-provisioning/) (Grafana's recommended path for automatic user lifecycle in Cloud), so users are provisioned by your identity provider before C1 assigns organization roles; or + * enable [SCIM provisioning](https://grafana.com/docs/grafana/latest/setup-grafana/configure-access/configure-scim-provisioning/) (Grafana's recommended path for automatic user lifecycle in Cloud), so users are provisioned by your identity provider before C1.ai assigns organization roles; or * enable the basic login form on the instance (set `disable_login_form = false`), which permits instance-level invites for external users. Managing membership directly through the grafana.com portal is a separate API and credential (a Grafana Cloud Access Policy token) that the connector's instance service-account token cannot use. @@ -54,22 +54,22 @@ Managing membership directly through the grafana.com portal is a separate API an **Grafana Cloud: provisioning organization roles for externally synced users** -In Grafana Cloud, users who sign in through an external identity provider (such as Grafana.com SSO, Okta, Azure AD, or any OAuth/SAML provider) have their organization roles controlled by that provider. By default, Grafana blocks API-level role changes for these users, which prevents C1 from provisioning organization entitlements for them. +In Grafana Cloud, users who sign in through an external identity provider (such as Grafana.com SSO, Okta, Azure AD, or any OAuth/SAML provider) have their organization roles controlled by that provider. By default, Grafana blocks API-level role changes for these users, which prevents C1.ai from provisioning organization entitlements for them. -To allow C1 to manage organization roles for these users, enable **Skip org role sync** for the relevant SSO provider in your Grafana instance: +To allow C1.ai to manage organization roles for these users, enable **Skip org role sync** for the relevant SSO provider in your Grafana instance: 1. In Grafana, go to **Administration** → **Authentication**. 2. Select the SSO provider your users log in with. 3. Enable **Skip org role sync** (equivalent to setting `skip_org_role_sync = true`). -Once this is enabled, Grafana stops overriding org roles on login and C1 becomes the authoritative source for role assignments. This is a global setting that applies to all users under that provider. +Once this is enabled, Grafana stops overriding org roles on login and C1.ai becomes the authoritative source for role assignments. This is a global setting that applies to all users under that provider. This step is not required for self-hosted Grafana instances using basic (username/password) authentication. ## Account access origin -Starting with connector version 0.2.3, each synced account's profile includes attributes that identify how the user's access originated. They appear in the account's **Profile attributes** in C1 and support access reviews where the origin of access matters: +Starting with connector version 0.2.3, each synced account's profile includes attributes that identify how the user's access originated. They appear in the account's **Profile attributes** in C1.ai and support access reviews where the origin of access matters: | Attribute | Type | Present | Meaning | | :--- | :--- | :--- | :--- | @@ -124,17 +124,17 @@ On Grafana Enterprise that account also needs `teams.roles:read`, which team syn To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Grafana credentials 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Grafana** and click **Add**. @@ -174,13 +174,13 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Grafana connector is now pulling access data into C1. +**Done.** Your Grafana connector is now pulling access data into C1.ai. **Follow these instructions to use the Grafana 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -190,7 +190,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -307,13 +307,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 C1.ai 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 Grafana connector to. Grafana data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Grafana connector to. Grafana data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Grafana connector is now pulling access data into C1. +**Done.** Your Grafana connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/grammarly.mdx b/baton/grammarly.mdx index da273e65..89d00cf3 100644 --- a/baton/grammarly.mdx +++ b/baton/grammarly.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Grammarly connector" og:title: "Set up a Grammarly connector" -description: "C1 provides identity governance for Grammarly. Integrate your Grammarly institution with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Grammarly. Integrate your Grammarly institution with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Grammarly. Integrate your Grammarly institution with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Grammarly. Integrate your Grammarly institution with C1.ai for unified visibility and governance over user access." sidebarTitle: "Grammarly" --- -C1 provides identity governance for Grammarly. Integrate your Grammarly -institution with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Grammarly. Integrate your Grammarly +institution with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -55,11 +55,11 @@ to create OAuth 2.0 credentials. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -111,7 +111,7 @@ to create OAuth 2.0 credentials. - **Done.** Your Grammarly connector is now pulling access data into C1. + **Done.** Your Grammarly connector is now pulling access data into C1.ai. @@ -142,6 +142,6 @@ to create OAuth 2.0 credentials. - **Done.** Your Grammarly connector is now pulling access data into C1. + **Done.** Your Grammarly connector is now pulling access data into C1.ai. diff --git a/baton/greenhouse.mdx b/baton/greenhouse.mdx index c7651e0e..37bcba40 100644 --- a/baton/greenhouse.mdx +++ b/baton/greenhouse.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Greenhouse connector" og:title: "Set up a Greenhouse connector" -description: "C1 provides identity governance and just-in-time provisioning for Greenhouse. Integrate your Greenhouse 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 Greenhouse. Integrate your Greenhouse instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Greenhouse. Integrate your Greenhouse instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Greenhouse. Integrate your Greenhouse instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Greenhouse" --- @@ -43,7 +43,7 @@ Click **Create new API key** and fill out the form: - **API Type**: Harvest - **Partner**: Custom integration - - **Description**: C1 integration + - **Description**: C1.ai integration Click **Manage Permissions**. The new key is generated. @@ -59,11 +59,11 @@ Carefully copy and save the API key, then click **I have stored the API Key**. On the next screen, select the relevant permissions: - To give C1 **READ** (sync) permissions: + To give C1.ai **READ** (sync) permissions: - User roles - Get: List User Roles - To give C1 **READ/WRITE** (sync and provision) permissions: + To give C1.ai **READ/WRITE** (sync and provision) permissions: - User roles - All permissions - Users - All permissions @@ -80,17 +80,17 @@ Click **Save**. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Greenhouse 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Greenhouse** and click **Add**. @@ -126,13 +126,13 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Greenhouse connector is now pulling access data into C1. +**Done.** Your Greenhouse connector is now pulling access data into C1.ai. **Follow these instructions to use the Greenhouse 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -142,7 +142,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -238,13 +238,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 C1.ai 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 Greenhouse connector to. Greenhouse data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Greenhouse connector to. Greenhouse data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Greenhouse connector is now pulling access data into C1. +**Done.** Your Greenhouse connector is now pulling access data into C1.ai. diff --git a/baton/growthbook.mdx b/baton/growthbook.mdx index bedf8875..7e6fe456 100644 --- a/baton/growthbook.mdx +++ b/baton/growthbook.mdx @@ -1,13 +1,13 @@ --- title: "Set up a GrowthBook connector" og:title: "Set up a GrowthBook connector" -description: "C1 provides identity governance for GrowthBook. Integrate your GrowthBook organization with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for GrowthBook. Integrate your GrowthBook organization with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for GrowthBook. Integrate your GrowthBook organization with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for GrowthBook. Integrate your GrowthBook organization with C1.ai for unified visibility and governance over user access." sidebarTitle: "GrowthBook" --- -C1 provides identity governance for GrowthBook. Integrate your GrowthBook -organization with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for GrowthBook. Integrate your GrowthBook +organization with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -50,11 +50,11 @@ will not work — the REST API requires a secret key. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -101,7 +101,7 @@ will not work — the REST API requires a secret key. - **Done.** Your GrowthBook connector is now pulling access data into C1. + **Done.** Your GrowthBook connector is now pulling access data into C1.ai. @@ -125,6 +125,6 @@ will not work — the REST API requires a secret key. - **Done.** Your GrowthBook connector is now pulling access data into C1. + **Done.** Your GrowthBook connector is now pulling access data into C1.ai. diff --git a/baton/guru.mdx b/baton/guru.mdx index 45892793..ba0bc8f9 100644 --- a/baton/guru.mdx +++ b/baton/guru.mdx @@ -1,12 +1,12 @@ --- title: "Set up a Guru connector" og:title: "Set up a Guru connector" -description: "C1 provides identity governance for Guru. Integrate your Guru team with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Guru. Integrate your Guru team with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Guru. Integrate your Guru team with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Guru. Integrate your Guru team with C1.ai for unified visibility and governance over user access." sidebarTitle: "Guru" --- -C1 provides identity governance for Guru. Integrate your Guru team with C1 for +C1.ai provides identity governance for Guru. Integrate your Guru team with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -67,11 +67,11 @@ administrative role on the team is the safest choice. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -116,7 +116,7 @@ administrative role on the team is the safest choice. - **Done.** Your Guru connector is now pulling access data into C1. + **Done.** Your Guru connector is now pulling access data into C1.ai. @@ -124,7 +124,7 @@ administrative role on the team is the safest choice. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -142,7 +142,7 @@ administrative role on the team is the safest choice. - Configure C1 credentials and Guru credentials as environment variables: + Configure C1.ai credentials and Guru credentials as environment variables: ```bash BATON_CLIENT_ID= @@ -158,6 +158,6 @@ administrative role on the team is the safest choice. - **Done.** Your Guru connector is now pulling access data into C1. + **Done.** Your Guru connector is now pulling access data into C1.ai. diff --git a/baton/gusto.mdx b/baton/gusto.mdx index 90e71274..2c45fa77 100644 --- a/baton/gusto.mdx +++ b/baton/gusto.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Gusto connector" og:title: "Set up a Gusto connector" -description: "C1 provides identity governance and just-in-time provisioning for Gusto. Integrate your Gusto 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 Gusto. Integrate your Gusto instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for Gusto. Integrate your Gusto instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Gusto. Integrate your Gusto instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "Gusto" --- @@ -31,12 +31,12 @@ The Gusto connector syncs the following resources: ## Gather Gusto credentials -To configure the Gusto connector, you need administrator permissions in the Gusto company you are connecting. The connector authenticates via OAuth brokered by C1 — you do not need to create or manage an API key. +To configure the Gusto connector, you need administrator permissions in the Gusto company you are connecting. The connector authenticates via OAuth brokered by C1.ai — you do not need to create or manage an API key. - Confirm you can sign in to the Gusto company as an admin. You will authorize C1's access during connector setup. + Confirm you can sign in to the Gusto company as an admin. You will authorize C1.ai's access during connector setup. @@ -44,11 +44,11 @@ To configure the Gusto connector, you need administrator permissions in the Gust - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -88,7 +88,7 @@ To configure the Gusto connector, you need administrator permissions in the Gust Generated from config_schema.json. Do not edit manually. */} - Click **Authorize** and complete the Gusto OAuth consent flow while signed in as a Gusto admin. C1 negotiates and stores the OAuth tokens for you — there is no API key to enter. + Click **Authorize** and complete the Gusto OAuth consent flow while signed in as a Gusto admin. C1.ai negotiates and stores the OAuth tokens for you — there is no API key to enter. {/* AUTO-GENERATED:END - config-params */} @@ -102,13 +102,13 @@ To configure the Gusto connector, you need administrator permissions in the Gust - **Done.** Your Gusto connector is now pulling access data into C1. + **Done.** Your Gusto connector is now pulling access data into C1.ai. Follow these instructions to use the [Gusto](https://github.com/conductorone/baton-gusto) 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. + When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1.ai, automatically syncing and uploading data at regular intervals. ### Resources @@ -121,7 +121,7 @@ To configure the Gusto connector, you need administrator permissions in the Gust - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -218,15 +218,15 @@ To configure the Gusto connector, you need administrator permissions in the Gust - 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 C1.ai 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 Gusto connector to. Gusto data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the Gusto connector to. Gusto data should be found on the **Entitlements** and **Accounts** tabs. - **Done.** Your Gusto connector is now pulling access data into C1. + **Done.** Your Gusto connector is now pulling access data into C1.ai. diff --git a/baton/halo-service-desk.mdx b/baton/halo-service-desk.mdx index 4d18ea6b..ca9d8b7f 100644 --- a/baton/halo-service-desk.mdx +++ b/baton/halo-service-desk.mdx @@ -1,8 +1,8 @@ --- title: "Set up a HaloITSM connector" og:title: "Set up a HaloITSM connector" -description: "C1 provides identity governance for HaloITSM. Integrate your HaloITSM instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for HaloITSM. Integrate your HaloITSM instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for HaloITSM. Integrate your HaloITSM instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for HaloITSM. Integrate your HaloITSM instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "HaloITSM" --- @@ -81,17 +81,17 @@ Click **Save** to finalize the application setup. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of HaloITSM 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **HaloITSM** and click **Add**. @@ -130,13 +130,13 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your HaloITSM connector is now pulling access data into C1. +**Done.** Your HaloITSM connector is now pulling access data into C1.ai. **Follow these instructions to use the HaloITSM 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -148,7 +148,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -243,14 +243,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 C1.ai 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 HaloITSM connector to. HaloITSM data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the HaloITSM connector to. HaloITSM data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your HaloITSM connector is now pulling access data into C1. +**Done.** Your HaloITSM connector is now pulling access data into C1.ai. diff --git a/baton/happyfox.mdx b/baton/happyfox.mdx index dd0963cf..2164f1bd 100644 --- a/baton/happyfox.mdx +++ b/baton/happyfox.mdx @@ -1,13 +1,13 @@ --- title: "Set up a HappyFox connector" og:title: "Set up a HappyFox connector" -description: "C1 provides identity governance for HappyFox. Integrate your HappyFox account with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for HappyFox. Integrate your HappyFox account with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for HappyFox. Integrate your HappyFox account with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for HappyFox. Integrate your HappyFox account with C1.ai for unified visibility and governance over user access." sidebarTitle: "HappyFox" --- -C1 provides identity governance for HappyFox. Integrate your HappyFox account -with C1 for unified visibility and governance over the staff who can access +C1.ai provides identity governance for HappyFox. Integrate your HappyFox account +with C1.ai for unified visibility and governance over the staff who can access your HappyFox help desk. ## Capabilities @@ -48,11 +48,11 @@ account-administrator permissions in HappyFox. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -98,7 +98,7 @@ account-administrator permissions in HappyFox. - **Done.** Your HappyFox connector is now pulling access data into C1. + **Done.** Your HappyFox connector is now pulling access data into C1.ai. @@ -123,6 +123,6 @@ account-administrator permissions in HappyFox. - **Done.** Your HappyFox connector is now pulling access data into C1. + **Done.** Your HappyFox connector is now pulling access data into C1.ai. diff --git a/baton/harness.mdx b/baton/harness.mdx index e14f99da..569d1edc 100644 --- a/baton/harness.mdx +++ b/baton/harness.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Harness connector" og:title: "Set up a Harness connector" -description: "C1 provides identity governance for Harness. Integrate your Harness instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Harness. Integrate your Harness instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Harness. Integrate your Harness instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Harness. Integrate your Harness instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Harness" --- @@ -20,13 +20,13 @@ sidebarTitle: "Harness" Use a Harness service account API key token with account-scope read access to -the RBAC surface. A personal API key token also works, but C1 recommends a +the RBAC surface. A personal API key token also works, but C1.ai recommends a dedicated service account for connector sync. - In Harness, create or select the service account that C1 will use. + In Harness, create or select the service account that C1.ai will use. @@ -81,11 +81,11 @@ dedicated service account for connector sync. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -133,7 +133,7 @@ dedicated service account for connector sync. - **Done.** Your Harness connector is now pulling access data into C1. + **Done.** Your Harness connector is now pulling access data into C1.ai. @@ -142,7 +142,7 @@ dedicated service account for connector sync. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -160,7 +160,7 @@ dedicated service account for connector sync. - Configure C1 credentials and Harness settings as environment variables: + Configure C1.ai credentials and Harness settings as environment variables: ```bash BATON_CLIENT_ID= @@ -183,6 +183,6 @@ dedicated service account for connector sync. - **Done.** Your Harness connector is now pulling access data into C1. + **Done.** Your Harness connector is now pulling access data into C1.ai. diff --git a/baton/harvest.mdx b/baton/harvest.mdx index 39ef5df9..01ae3bed 100644 --- a/baton/harvest.mdx +++ b/baton/harvest.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Harvest connector" og:title: "Set up a Harvest connector" -description: "C1 provides identity governance for Harvest. Integrate your Harvest account with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Harvest. Integrate your Harvest account with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Harvest. Integrate your Harvest account with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Harvest. Integrate your Harvest account with C1.ai for unified visibility and governance over user access." sidebarTitle: "Harvest" --- -C1 provides identity governance for Harvest. Integrate your Harvest account -with C1 for unified visibility and governance over the people who can access +C1.ai provides identity governance for Harvest. Integrate your Harvest account +with C1.ai for unified visibility and governance over the people who can access your Harvest time-tracking account. ## Capabilities @@ -55,11 +55,11 @@ access token that can read the full list of people. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -104,7 +104,7 @@ access token that can read the full list of people. - **Done.** Your Harvest connector is now pulling access data into C1. + **Done.** Your Harvest connector is now pulling access data into C1.ai. @@ -128,6 +128,6 @@ access token that can read the full list of people. - **Done.** Your Harvest connector is now pulling access data into C1. + **Done.** Your Harvest connector is now pulling access data into C1.ai. diff --git a/baton/hashicorp-vault.mdx b/baton/hashicorp-vault.mdx index 67e57d70..c2165e0c 100644 --- a/baton/hashicorp-vault.mdx +++ b/baton/hashicorp-vault.mdx @@ -1,8 +1,8 @@ --- title: "Set up a HashiCorp Vault connector" og:title: "Set up a HashiCorp Vault connector" -description: "C1 provides identity governance and just-in-time provisioning for HashiCorp Vault. Integrate your HashiCorp Vault 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 HashiCorp Vault. Integrate your HashiCorp Vault instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for HashiCorp Vault. Integrate your HashiCorp Vault instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for HashiCorp Vault. Integrate your HashiCorp Vault instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "HashiCorp Vault" --- @@ -93,13 +93,13 @@ Next, move on to the connector configuration instructions. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of HashiCorp Vault 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 C1.ai.** *Cloud-hosted connector not currently available.* @@ -107,7 +107,7 @@ To complete this task, you'll need: **Follow these instructions to use the HashiCorp Vault 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -117,7 +117,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -219,14 +219,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 C1.ai 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 HashiCorp Vault connector to. HashiCorp Vault data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the HashiCorp Vault connector to. HashiCorp Vault data should be found on the **Entitlements** and **Accounts** tabs. -Your HashiCorp Vault connector is now pulling access data into C1. +Your HashiCorp Vault connector is now pulling access data into C1.ai. diff --git a/baton/health-checks.mdx b/baton/health-checks.mdx index e04a667c..90ae7f47 100644 --- a/baton/health-checks.mdx +++ b/baton/health-checks.mdx @@ -9,7 +9,7 @@ sidebarTitle: "Health checks" Baton connectors [running in service mode](/baton/deploy#run-a-self-hosted-connector-in-service-mode) can expose HTTP health check endpoints for container orchestrators (ECS Fargate, Kubernetes, etc.) to monitor connector health. -When C1 encounters a 503 from a connector during provisioning, it treats this as a transient error and retries automatically (up to 5 attempts). Errors indicating a configuration problem — such as 401, 403, or 404 — are not retried. If provisioning still fails after retries, the task falls back to a manual path and appears in the **Assigned to me** area for follow-up. Learn more about [automatic account provisioning](/product/admin/account-provisioning). +When C1.ai encounters a 503 from a connector during provisioning, it treats this as a transient error and retries automatically (up to 5 attempts). Errors indicating a configuration problem — such as 401, 403, or 404 — are not retried. If provisioning still fails after retries, the task falls back to a manual path and appears in the **Assigned to me** area for follow-up. Learn more about [automatic account provisioning](/product/admin/account-provisioning). ## Enabling health checks diff --git a/baton/height.mdx b/baton/height.mdx index 5f143e5a..f53b9887 100644 --- a/baton/height.mdx +++ b/baton/height.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Height connector" og:title: "Set up a Height connector" -description: "C1 provides identity governance for Height. Integrate your Height workspace with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Height. Integrate your Height workspace with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Height. Integrate your Height workspace with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Height. Integrate your Height workspace with C1.ai for unified visibility and governance over user access." sidebarTitle: "Height" --- -C1 provides identity governance for Height. Integrate your Height workspace -with C1 for unified visibility and governance over who belongs to your +C1.ai provides identity governance for Height. Integrate your Height workspace +with C1.ai for unified visibility and governance over who belongs to your workspace and which groups they are members of. ## Capabilities @@ -44,11 +44,11 @@ have access to your Height workspace settings. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -92,7 +92,7 @@ have access to your Height workspace settings. - **Done.** Your Height connector is now pulling access data into C1. + **Done.** Your Height connector is now pulling access data into C1.ai. @@ -115,6 +115,6 @@ have access to your Height workspace settings. - **Done.** Your Height connector is now pulling access data into C1. + **Done.** Your Height connector is now pulling access data into C1.ai. diff --git a/baton/helpjuice.mdx b/baton/helpjuice.mdx index ee13885e..19354131 100644 --- a/baton/helpjuice.mdx +++ b/baton/helpjuice.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Helpjuice connector" og:title: "Set up a Helpjuice connector" -description: "C1 provides identity governance for Helpjuice. Integrate your Helpjuice instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Helpjuice. Integrate your Helpjuice instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Helpjuice. Integrate your Helpjuice instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Helpjuice. Integrate your Helpjuice instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Helpjuice" --- -C1 provides identity governance for Helpjuice. Integrate your Helpjuice -instance with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Helpjuice. Integrate your Helpjuice +instance with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -49,11 +49,11 @@ You need administrator access to your Helpjuice account to find its API key. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -100,7 +100,7 @@ You need administrator access to your Helpjuice account to find its API key. - **Done.** Your Helpjuice connector is now pulling access data into C1. + **Done.** Your Helpjuice connector is now pulling access data into C1.ai. @@ -127,6 +127,6 @@ You need administrator access to your Helpjuice account to find its API key. - **Done.** Your Helpjuice connector is now pulling access data into C1. + **Done.** Your Helpjuice connector is now pulling access data into C1.ai. diff --git a/baton/helpscout.mdx b/baton/helpscout.mdx index 25c882ec..bca1eb14 100644 --- a/baton/helpscout.mdx +++ b/baton/helpscout.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Help Scout connector" og:title: "Set up a Help Scout connector" -description: "C1 provides identity governance for Help Scout. Integrate your Help Scout account with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Help Scout. Integrate your Help Scout account with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Help Scout. Integrate your Help Scout account with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Help Scout. Integrate your Help Scout account with C1.ai for unified visibility and governance over user access." sidebarTitle: "Help Scout" --- -C1 provides identity governance for Help Scout. Integrate your Help Scout -account with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Help Scout. Integrate your Help Scout +account with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -39,7 +39,7 @@ permissions of the user who creates them. - Give the app a name (for example, "C1") and a redirection URL. The + Give the app a name (for example, "C1.ai") and a redirection URL. The redirection URL is required by Help Scout but is not used by the connector — any valid HTTPS URL works. @@ -53,11 +53,11 @@ permissions of the user who creates them. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -102,7 +102,7 @@ permissions of the user who creates them. - **Done.** Your Help Scout connector is now pulling access data into C1. + **Done.** Your Help Scout connector is now pulling access data into C1.ai. @@ -126,6 +126,6 @@ permissions of the user who creates them. - **Done.** Your Help Scout connector is now pulling access data into C1. + **Done.** Your Help Scout connector is now pulling access data into C1.ai. diff --git a/baton/heroku.mdx b/baton/heroku.mdx index 13ee3772..d2c339fc 100644 --- a/baton/heroku.mdx +++ b/baton/heroku.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Heroku connector" og:title: "Set up a Heroku connector" -description: "C1 provides identity governance for Heroku. Integrate your Heroku platform with C1 for unified visibility and governance over user, team, app collaborator, and enterprise account access." -og:description: "C1 provides identity governance for Heroku. Integrate your Heroku platform with C1 for unified visibility and governance over user, team, app collaborator, and enterprise account access." +description: "C1.ai provides identity governance for Heroku. Integrate your Heroku platform with C1.ai for unified visibility and governance over user, team, app collaborator, and enterprise account access." +og:description: "C1.ai provides identity governance for Heroku. Integrate your Heroku platform with C1.ai for unified visibility and governance over user, team, app collaborator, and enterprise account access." sidebarTitle: "Heroku" --- -C1 provides identity governance for Heroku. Integrate your Heroku instance -with C1 for unified visibility and governance over user, team, app +C1.ai provides identity governance for Heroku. Integrate your Heroku instance +with C1.ai for unified visibility and governance over user, team, app collaborator, and enterprise account access. ## Capabilities @@ -63,11 +63,11 @@ service account in that case. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -111,7 +111,7 @@ service account in that case. - **Done.** Your Heroku connector is now pulling access data into C1. + **Done.** Your Heroku connector is now pulling access data into C1.ai. @@ -134,6 +134,6 @@ service account in that case. - **Done.** Your Heroku connector is now pulling access data into C1. + **Done.** Your Heroku connector is now pulling access data into C1.ai. diff --git a/baton/hibob.mdx b/baton/hibob.mdx index 91336d5f..b95c7f24 100644 --- a/baton/hibob.mdx +++ b/baton/hibob.mdx @@ -1,13 +1,13 @@ --- title: "Set up a HiBob connector" og:title: "Set up a HiBob connector" -description: "C1 provides identity governance for HiBob. Integrate your HiBob instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for HiBob. Integrate your HiBob instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for HiBob. Integrate your HiBob instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for HiBob. Integrate your HiBob instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "HiBob" --- -C1 provides identity governance for HiBob. Integrate your HiBob instance with -C1 for unified visibility and governance over user access. +C1.ai provides identity governance for HiBob. Integrate your HiBob instance with +C1.ai for unified visibility and governance over user access. ## Capabilities @@ -89,11 +89,11 @@ permission group grants. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -141,7 +141,7 @@ permission group grants. - **Done.** Your HiBob connector is now pulling access data into C1. + **Done.** Your HiBob connector is now pulling access data into C1.ai. @@ -150,7 +150,7 @@ permission group grants. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -168,7 +168,7 @@ permission group grants. - Configure C1 credentials and HiBob credentials as environment + Configure C1.ai credentials and HiBob credentials as environment variables: ```bash @@ -192,6 +192,6 @@ permission group grants. - **Done.** Your HiBob connector is now pulling access data into C1. + **Done.** Your HiBob connector is now pulling access data into C1.ai. diff --git a/baton/honeybadger.mdx b/baton/honeybadger.mdx index 2dac4d61..9b0613c6 100644 --- a/baton/honeybadger.mdx +++ b/baton/honeybadger.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Honeybadger connector" og:title: "Set up a Honeybadger connector" -description: "C1 provides identity governance for Honeybadger. Integrate your Honeybadger instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Honeybadger. Integrate your Honeybadger instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Honeybadger. Integrate your Honeybadger instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Honeybadger. Integrate your Honeybadger instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Honeybadger" --- -C1 provides identity governance for Honeybadger. Integrate your Honeybadger -account with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Honeybadger. Integrate your Honeybadger +account with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -69,11 +69,11 @@ single account. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -119,7 +119,7 @@ single account. - **Done.** Your Honeybadger connector is now pulling access data into C1. + **Done.** Your Honeybadger connector is now pulling access data into C1.ai. @@ -144,6 +144,6 @@ single account. - **Done.** Your Honeybadger connector is now pulling access data into C1. + **Done.** Your Honeybadger connector is now pulling access data into C1.ai. diff --git a/baton/hubspot.mdx b/baton/hubspot.mdx index a2163ce0..bbfbb141 100644 --- a/baton/hubspot.mdx +++ b/baton/hubspot.mdx @@ -1,8 +1,8 @@ --- title: "Set up a HubSpot connector" og:title: "Set up a HubSpot connector" -description: "C1 provides identity governance and just-in-time provisioning for HubSpot. Integrate your HubSpot 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 HubSpot. Integrate your HubSpot instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for HubSpot. Integrate your HubSpot instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for HubSpot. Integrate your HubSpot instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "HubSpot" --- @@ -19,7 +19,7 @@ sidebarTitle: "HubSpot" ## Provisioning -C1 can provision access in HubSpot using this connector. Provisioning requires the `settings.users.write` scope on the private app (see the credentials steps below) and that the connector runs with provisioning enabled (`BATON_PROVISIONING=true` when self-hosted). +C1.ai can provision access in HubSpot using this connector. Provisioning requires the `settings.users.write` scope on the private app (see the credentials steps below) and that the connector runs with provisioning enabled (`BATON_PROVISIONING=true` when self-hosted). | Operation | Supported | Notes | | :--- | :--- | :--- | @@ -34,7 +34,7 @@ C1 can provision access in HubSpot using this connector. Provisioning requires t HubSpot provides no API to re-enable a deactivated user. To restore access for a user who was deactivated in HubSpot, delete the account and re-invite it. This creates a new account and does not preserve the previous user's history. -Deactivated HubSpot users continue to appear in C1 with their existing entitlement grants, because the account still exists in HubSpot. Enable **user status** syncing (see the configuration steps below) to have these users flagged as disabled in C1. +Deactivated HubSpot users continue to appear in C1.ai with their existing entitlement grants, because the account still exists in HubSpot. Enable **user status** syncing (see the configuration steps below) to have these users flagged as disabled in C1.ai. ## Gather HubSpot credentials @@ -54,7 +54,7 @@ Log into HubSpot and navigate **Settings** > **Private Apps**. Click **Create a private app** -On the **Basic info** tab, enter a name (such as "C1") and description for the new app. +On the **Basic info** tab, enter a name (such as "C1.ai") and description for the new app. On the **Scopes** tab, select the following scopes: @@ -71,7 +71,7 @@ On the **Scopes** tab, select the following scopes: - `oauth` - Request -**Optional.** If you want to use C1 to provision users (invite, deactivate) or manage team/role membership, add `settings.users.write`. +**Optional.** If you want to use C1.ai to provision users (invite, deactivate) or manage team/role membership, add `settings.users.write`. **Optional.** To sync user status, search for and add the `crm.objects.users.read` scope to the app. @@ -91,17 +91,17 @@ The new private app's token is shown. Carefully copy and save the 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 C1.ai - Access to the set of HubSpot 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **HubSpot** and click **Add**. @@ -139,13 +139,13 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**That's it!** Your HubSpot connector is now pulling access data into C1. +**That's it!** Your HubSpot connector is now pulling access data into C1.ai. **Follow these instructions to use the Hubspot 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -155,7 +155,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -251,13 +251,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 C1.ai 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 HubSpot connector to. HubSpot data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the HubSpot connector to. HubSpot data should be found on the **Entitlements** and **Accounts** tabs. -**That's it!** Your HubSpot connector is now pulling access data into C1. +**That's it!** Your HubSpot connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/huggingface.mdx b/baton/huggingface.mdx index ac561b44..a5c55a20 100644 --- a/baton/huggingface.mdx +++ b/baton/huggingface.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Hugging Face connector" og:title: "Set up a Hugging Face connector" -description: "C1 provides identity governance for Hugging Face. Integrate your Hugging Face organization with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Hugging Face. Integrate your Hugging Face organization with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Hugging Face. Integrate your Hugging Face organization with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Hugging Face. Integrate your Hugging Face organization with C1.ai for unified visibility and governance over user access." sidebarTitle: "Hugging Face" --- -C1 provides identity governance for Hugging Face. Integrate your Hugging Face -organization with C1 for unified visibility and governance over who can access +C1.ai provides identity governance for Hugging Face. Integrate your Hugging Face +organization with C1.ai for unified visibility and governance over who can access your organization and the role each member holds. ## Capabilities @@ -49,11 +49,11 @@ organization members. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -98,7 +98,7 @@ organization members. - **Done.** Your Hugging Face connector is now pulling access data into C1. + **Done.** Your Hugging Face connector is now pulling access data into C1.ai. @@ -122,6 +122,6 @@ organization members. - **Done.** Your Hugging Face connector is now pulling access data into C1. + **Done.** Your Hugging Face connector is now pulling access data into C1.ai. diff --git a/baton/humaans.mdx b/baton/humaans.mdx index 431be2dc..136a3ea3 100644 --- a/baton/humaans.mdx +++ b/baton/humaans.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Humaans connector" og:title: "Set up a Humaans connector" -description: "C1 provides identity governance for Humaans. Integrate your Humaans HRIS with C1 for unified visibility over employees and job titles." -og:description: "C1 provides identity governance for Humaans. Integrate your Humaans HRIS with C1 for unified visibility over employees and job titles." +description: "C1.ai provides identity governance for Humaans. Integrate your Humaans HRIS with C1.ai for unified visibility over employees and job titles." +og:description: "C1.ai provides identity governance for Humaans. Integrate your Humaans HRIS with C1.ai for unified visibility over employees and job titles." sidebarTitle: "Humaans" --- -C1 provides identity governance for Humaans. Integrate your Humaans HRIS -with C1 for unified visibility over employees and job titles. +C1.ai provides identity governance for Humaans. Integrate your Humaans HRIS +with C1.ai for unified visibility over employees and job titles. ## Capabilities @@ -61,11 +61,11 @@ scopes — the connector does not read those surfaces. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -110,7 +110,7 @@ scopes — the connector does not read those surfaces. - **Done.** Your Humaans connector is now pulling HR data into C1. + **Done.** Your Humaans connector is now pulling HR data into C1.ai. @@ -136,7 +136,7 @@ scopes — the connector does not read those surfaces. - **Done.** Your Humaans connector is now pulling HR data into C1. + **Done.** Your Humaans connector is now pulling HR data into C1.ai. diff --git a/baton/ilert.mdx b/baton/ilert.mdx index 578d9e33..64113e5c 100644 --- a/baton/ilert.mdx +++ b/baton/ilert.mdx @@ -1,13 +1,13 @@ --- title: "Set up an ilert connector" og:title: "Set up an ilert connector" -description: "C1 provides identity governance for ilert. Integrate your ilert account with C1 for unified visibility and governance over user and team access." -og:description: "C1 provides identity governance for ilert. Integrate your ilert account with C1 for unified visibility and governance over user and team access." +description: "C1.ai provides identity governance for ilert. Integrate your ilert account with C1.ai for unified visibility and governance over user and team access." +og:description: "C1.ai provides identity governance for ilert. Integrate your ilert account with C1.ai for unified visibility and governance over user and team access." sidebarTitle: "ilert" --- -C1 provides identity governance for ilert. Integrate your ilert account with -C1 for unified visibility and governance over user and team access. +C1.ai provides identity governance for ilert. Integrate your ilert account with +C1.ai for unified visibility and governance over user and team access. ## Capabilities @@ -49,11 +49,11 @@ see every user and team in the account. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -98,7 +98,7 @@ see every user and team in the account. - **Done.** Your ilert connector is now pulling access data into C1. + **Done.** Your ilert connector is now pulling access data into C1.ai. @@ -122,6 +122,6 @@ see every user and team in the account. - **Done.** Your ilert connector is now pulling access data into C1. + **Done.** Your ilert connector is now pulling access data into C1.ai. diff --git a/baton/imperva.mdx b/baton/imperva.mdx index a07d98f3..fdcb0b62 100644 --- a/baton/imperva.mdx +++ b/baton/imperva.mdx @@ -1,13 +1,13 @@ --- title: "Set up an Imperva connector" og:title: "Set up an Imperva connector" -description: "C1 provides identity governance for Imperva Cloud WAF. Integrate your Imperva account with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Imperva Cloud WAF. Integrate your Imperva account with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Imperva Cloud WAF. Integrate your Imperva account with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Imperva Cloud WAF. Integrate your Imperva account with C1.ai for unified visibility and governance over user access." sidebarTitle: "Imperva" --- -C1 provides identity governance for Imperva Cloud WAF. Integrate your Imperva -account with C1 for unified visibility and governance over the roles defined in +C1.ai provides identity governance for Imperva Cloud WAF. Integrate your Imperva +account with C1.ai for unified visibility and governance over the roles defined in your account and the users assigned to them. ## Capabilities @@ -46,11 +46,11 @@ user-management area so the connector can list roles and their assigned users. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -96,7 +96,7 @@ user-management area so the connector can list roles and their assigned users. - **Done.** Your Imperva connector is now pulling access data into C1. + **Done.** Your Imperva connector is now pulling access data into C1.ai. @@ -118,6 +118,6 @@ user-management area so the connector can list roles and their assigned users. - **Done.** Your Imperva connector is now pulling access data into C1. + **Done.** Your Imperva connector is now pulling access data into C1.ai. diff --git a/baton/incident-io.mdx b/baton/incident-io.mdx index f64cc4fe..ca1cc31c 100644 --- a/baton/incident-io.mdx +++ b/baton/incident-io.mdx @@ -1,8 +1,8 @@ --- title: "Set up an Incident.io connector" og:title: "Set up an Incident.io connector" -description: "C1 provides identity governance for Incident.io. Integrate your Incident.io instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Incident.io. Integrate your Incident.io instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Incident.io. Integrate your Incident.io instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Incident.io. Integrate your Incident.io instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Incident.io" --- @@ -40,17 +40,17 @@ Carefully copy and save the API key. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Incident.io 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Incident.io** and click **Add**. @@ -83,13 +83,13 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Incident.io connector is now pulling access data into C1. +**Done.** Your Incident.io connector is now pulling access data into C1.ai. **Follow these instructions to use the Incident.io 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -99,7 +99,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -189,13 +189,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 C1.ai 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 Incident.io connector to. Incident.io data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Incident.io connector to. Incident.io data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Incident.io connector is now pulling access data into C1. +**Done.** Your Incident.io connector is now pulling access data into C1.ai. diff --git a/baton/infisical.mdx b/baton/infisical.mdx index 52cb1080..e773d704 100644 --- a/baton/infisical.mdx +++ b/baton/infisical.mdx @@ -1,13 +1,13 @@ --- title: "Set up an Infisical connector" og:title: "Set up an Infisical connector" -description: "C1 provides identity governance for Infisical. Integrate your Infisical organization with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Infisical. Integrate your Infisical organization with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Infisical. Integrate your Infisical organization with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Infisical. Integrate your Infisical organization with C1.ai for unified visibility and governance over user access." sidebarTitle: "Infisical" --- -C1 provides identity governance for Infisical. Integrate your Infisical -organization with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Infisical. Integrate your Infisical +organization with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -59,11 +59,11 @@ Machine Identity and grant it read access. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -113,7 +113,7 @@ Machine Identity and grant it read access. - **Done.** Your Infisical connector is now pulling access data into C1. + **Done.** Your Infisical connector is now pulling access data into C1.ai. @@ -143,6 +143,6 @@ Machine Identity and grant it read access. - **Done.** Your Infisical connector is now pulling access data into C1. + **Done.** Your Infisical connector is now pulling access data into C1.ai. diff --git a/baton/intercom.mdx b/baton/intercom.mdx index 6db96c9c..9ab2458d 100644 --- a/baton/intercom.mdx +++ b/baton/intercom.mdx @@ -1,15 +1,15 @@ --- title: "Set up an Intercom connector" og:title: "Set up an Intercom connector" -description: "C1 provides identity governance for Intercom. Integrate your Intercom workspace with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Intercom. Integrate your Intercom workspace with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Intercom. Integrate your Intercom workspace with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Intercom. Integrate your Intercom workspace with C1.ai for unified visibility and governance over user access." sidebarTitle: "Intercom" --- {/* stargate */} -C1 provides identity governance for Intercom. Integrate your Intercom workspace -with C1 for unified visibility and governance over who has access to your +C1.ai provides identity governance for Intercom. Integrate your Intercom workspace +with C1.ai for unified visibility and governance over who has access to your customer messaging workspace. ## Capabilities @@ -59,11 +59,11 @@ teammates and teams. Create the app as a workspace admin. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -110,7 +110,7 @@ teammates and teams. Create the app as a workspace admin. - **Done.** Your Intercom connector is now pulling access data into C1. + **Done.** Your Intercom connector is now pulling access data into C1.ai. @@ -136,6 +136,6 @@ teammates and teams. Create the app as a workspace admin. - **Done.** Your Intercom connector is now pulling access data into C1. + **Done.** Your Intercom connector is now pulling access data into C1.ai. diff --git a/baton/intro.mdx b/baton/intro.mdx index bd96239c..d807b388 100644 --- a/baton/intro.mdx +++ b/baton/intro.mdx @@ -9,7 +9,7 @@ og:description: "Here you'll find our library of pre-built connectors, plus supp **If we don't have the connector you're looking for today, never fear.** -C1 supports custom connectors via our open-source Baton SDK, so you can integrate any (and we do mean ANY) app, even niche or legacy systems. +C1.ai supports custom connectors via our open-source Baton SDK, so you can integrate any (and we do mean ANY) app, even niche or legacy systems. You can build it yourself, or we can build it for you. Whether it's API-based, file-based, or something else, you won't ever be limited to the connectors in our library. We give you multiple ways to connect and govern any app. @@ -30,47 +30,47 @@ And if you want to integrate without writing code, check out our configuration-d - Integrate your Okta instance with C1. + Integrate your Okta instance with C1.ai. - Integrate your Google Workspace instance with C1. + Integrate your Google Workspace instance with C1.ai. - Integrate your Microsoft Entra ID instance with C1. + Integrate your Microsoft Entra ID instance with C1.ai. - Integrate your AWS instance with C1. + Integrate your AWS instance with C1.ai. - Integrate your GitHub instance with C1. + Integrate your GitHub instance with C1.ai. - Integrate your Google Cloud Platform instance with C1. + Integrate your Google Cloud Platform instance with C1.ai. - Integrate your Slack instance with C1. + Integrate your Slack instance with C1.ai. - Integrate your Snowflake instance with C1. + Integrate your Snowflake instance with C1.ai. - Integrate your Oracle NetSuite instance with C1. + Integrate your Oracle NetSuite instance with C1.ai. - Integrate your Atlassian Jira Cloud instance with C1. + Integrate your Atlassian Jira Cloud instance with C1.ai. - Integrate your Atlassian Bitbucket instance with C1. + Integrate your Atlassian Bitbucket instance with C1.ai. diff --git a/baton/ipa.mdx b/baton/ipa.mdx index ca28eeb4..8081bca7 100644 --- a/baton/ipa.mdx +++ b/baton/ipa.mdx @@ -1,8 +1,8 @@ --- title: "Set up a FreeIPA connector" og:title: "Set up a FreeIPA connector" -description: "C1 provides identity governance and just-in-time provisioning for FreeIPA. Integrate your FreeIPA deployment 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 FreeIPA. Integrate your FreeIPA deployment with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for FreeIPA. Integrate your FreeIPA deployment with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for FreeIPA. Integrate your FreeIPA deployment with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "FreeIPA" --- @@ -23,16 +23,16 @@ This table is hand-maintained, not generated from `baton_capabilities.json` — **Notes:** - Groups offer two entitlements: **member** and **manager**. Roles offer **member**, and a role membership can be granted to a user, a group, a host, or a host group. -- Host access comes from your HBAC rules rather than from a fixed entitlement. Host groups additionally offer **member** and **manager** entitlements, on top of the HBAC-derived ones. Each rule that names a host or host group becomes an entitlement on that resource, so what C1 shows follows the rules you have written. -- A rule that applies to every host or every user — one whose `hostCategory` or `userCategory` is set to `all`, such as the `allow_all` rule FreeIPA ships — appears in C1 as a grant against a single **Any** or **Anyone** resource, rather than being expanded across your whole estate. -- Group and role memberships expand. When a group is granted a role, C1 resolves the group's members through to that role, including members reached through nested groups. +- Host access comes from your HBAC rules rather than from a fixed entitlement. Host groups additionally offer **member** and **manager** entitlements, on top of the HBAC-derived ones. Each rule that names a host or host group becomes an entitlement on that resource, so what C1.ai shows follows the rules you have written. +- A rule that applies to every host or every user — one whose `hostCategory` or `userCategory` is set to `all`, such as the `allow_all` rule FreeIPA ships — appears in C1.ai as a grant against a single **Any** or **Anyone** resource, rather than being expanded across your whole estate. +- Group and role memberships expand. When a group is granted a role, C1.ai resolves the group's members through to that role, including members reached through nested groups. - Account deprovisioning by deletion is not yet supported end to end: the resource ID the connector stores for a user (`ipaUniqueID`) doesn't match what the delete path expects (a DN), so a delete call currently errors instead of removing the entry. The connector does not create accounts. - Last login comes from the Kerberos `krbLastSuccessfulAuth` attribute, which is an operational attribute. Setting `--disable-operational-attrs` turns off both last login and created-at for every account. ## Gather FreeIPA credentials -To configure the FreeIPA connector you need an account that can read your directory over LDAP. To let C1 provision access, that account also needs write access to the group and role membership attributes. +To configure the FreeIPA connector you need an account that can read your directory over LDAP. To let C1.ai provision access, that account also needs write access to the group and role membership attributes. @@ -40,7 +40,7 @@ To configure the FreeIPA connector you need an account that can read your direct Choose the account the connector will bind as. - Create a dedicated service account rather than reusing `admin`. It keeps the connector's access reviewable and lets you scope it to read-only if you do not want C1 to provision access. + Create a dedicated service account rather than reusing `admin`. It keeps the connector's access reviewable and lets you scope it to read-only if you do not want C1.ai to provision access. @@ -51,14 +51,14 @@ To configure the FreeIPA connector you need an account that can read your direct - Grant the account read access to the parts of the directory you want C1 to see: the user, group, and role containers, your hosts and host groups, and your HBAC rules. + Grant the account read access to the parts of the directory you want C1.ai to see: the user, group, and role containers, your hosts and host groups, and your HBAC rules. - To let C1 provision access, grant the account write access to the `member` and `memberManager` attributes on the groups and roles you want it to manage. + To let C1.ai provision access, grant the account write access to the `member` and `memberManager` attributes on the groups and roles you want it to manage. - Write access is used by C1 when automatically provisioning access. **If you do not want C1 to perform these tasks, grant read access only.** + Write access is used by C1.ai when automatically provisioning access. **If you do not want C1.ai to perform these tasks, grant read access only.** @@ -77,7 +77,7 @@ To configure the FreeIPA connector you need an account that can read your direct - **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 C1.ai.** *Cloud-hosted connector not currently available.* @@ -85,13 +85,13 @@ To configure the FreeIPA connector you need an account that can read your direct Follow these instructions to use the [FreeIPA](https://github.com/conductorone/baton-ipa) 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Step 1: Set up a new FreeIPA connector - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -194,15 +194,15 @@ To configure the FreeIPA connector you need an account that can read your direct - 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 C1.ai 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 FreeIPA connector to. FreeIPA data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the FreeIPA connector to. FreeIPA data should be found on the **Entitlements** and **Accounts** tabs. - **Done.** Your FreeIPA connector is now pulling access data into C1. + **Done.** Your FreeIPA connector is now pulling access data into C1.ai. diff --git a/baton/ironclad.mdx b/baton/ironclad.mdx index 6a34e955..28ff3aa6 100644 --- a/baton/ironclad.mdx +++ b/baton/ironclad.mdx @@ -1,8 +1,8 @@ --- title: "Set up an Ironclad connector" og:title: "Set up an Ironclad connector" -description: "C1 provides identity governance for Ironclad. Integrate your Ironclad instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." -og:description: "C1 provides identity governance for Ironclad. Integrate your Ironclad instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance for Ironclad. Integrate your Ironclad instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance for Ironclad. Integrate your Ironclad instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Ironclad" --- @@ -15,7 +15,7 @@ sidebarTitle: "Ironclad" The Ironclad connector supports [automatic account provisioning](/product/admin/account-provisioning). -When a new account is created by C1, the account's password will be sent to a [vault](/product/admin/vaults). +When a new account is created by C1.ai, the account's password will be sent to a [vault](/product/admin/vaults). This connector does not support account deprovisioning. You must deprovision accounts directly in Ironclad. @@ -37,7 +37,7 @@ In Ironclad, navigate to your profile menu (located in the top right corner of t Select **Create new app**. -Give your OAuth client application a name, such as "C1" and click **Create app**. +Give your OAuth client application a name, such as "C1.ai" and click **Create app**. Carefully copy and save the app's client ID and client secret, then click **Continue**. @@ -49,7 +49,7 @@ In the **Grant Types** area, select the grant type that matches your authenticat - **Authorization Code**: Requires logging in and authorizing. Only available for cloud-hosted connectors. -If you selected **Authorization Code**, enter whichever redirect URI matches your C1 tenant's domain in the **Redirect URI** field: +If you selected **Authorization Code**, enter whichever redirect URI matches your C1.ai tenant's domain in the **Redirect URI** field: - Default instance: `https://accounts.conductor.one/oauth/callback` - EU data residency instance: `https://accounts.c1eu.ai/oauth/callback` @@ -60,7 +60,7 @@ In the **Scopes** area, give the app the following scopes: - scim.users.readUsers - scim.groups.readGroups - If you want to use C1 to provision Ironclad accounts and groups, add these scopes as well: + If you want to use C1.ai to provision Ironclad accounts and groups, add these scopes as well: - scim.groups.updateGroups - scim.users.createUsers @@ -78,17 +78,17 @@ Click **Save changes**. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Ironclad 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Ironclad** and click **Add**. @@ -114,7 +114,7 @@ Find the **Settings** area of the page and click **Edit**. Select your authentication method: - **OAuth Client Credentials** (Recommended): The simplest setup. Authenticate using client credentials without an interactive login. - - **OAuth Authorization Code**: Authenticate by logging in and authorizing C1 with your Ironclad instance. + - **OAuth Authorization Code**: Authenticate by logging in and authorizing C1.ai with your Ironclad instance. Enter the client ID and client secret into their respective fields. @@ -129,20 +129,20 @@ Enter the client ID and client secret into their respective fields. Click **Save**. -**If using OAuth Authorization Code:** Click **Login with OAuth**, then log in and authorize C1 with your Ironclad instance. After authorizing, you'll be redirected back to the C1 integrations page, where an "Authorized as" message is now printed. +**If using OAuth Authorization Code:** Click **Login with OAuth**, then log in and authorize C1.ai with your Ironclad instance. After authorizing, you'll be redirected back to the C1.ai integrations page, where an "Authorized as" message is now printed. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Ironclad connector is now pulling access data into C1. +**Done.** Your Ironclad connector is now pulling access data into C1.ai. **Follow these instructions to use the Ironclad 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -152,7 +152,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -249,14 +249,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 C1.ai 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 Ironclad connector to. Ironclad data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Ironclad connector to. Ironclad data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Ironclad connector is now pulling access data into C1. +**Done.** Your Ironclad connector is now pulling access data into C1.ai. diff --git a/baton/island.mdx b/baton/island.mdx index 1fa7e6a6..4402e756 100644 --- a/baton/island.mdx +++ b/baton/island.mdx @@ -1,8 +1,8 @@ --- title: "Set up an Island connector" og:title: "Set up an Island connector" -description: "C1 provides identity governance for Island Enterprise Browser. Integrate your Island tenant with C1 for unified visibility and governance over user and group access." -og:description: "C1 provides identity governance for Island Enterprise Browser. Integrate your Island tenant with C1 for unified visibility and governance over user and group access." +description: "C1.ai provides identity governance for Island Enterprise Browser. Integrate your Island tenant with C1.ai for unified visibility and governance over user and group access." +og:description: "C1.ai provides identity governance for Island Enterprise Browser. Integrate your Island tenant with C1.ai for unified visibility and governance over user and group access." sidebarTitle: "Island" --- diff --git a/baton/jamf.mdx b/baton/jamf.mdx index 05305495..619dd6f0 100644 --- a/baton/jamf.mdx +++ b/baton/jamf.mdx @@ -44,7 +44,7 @@ A user the **Administrator** role in Jamf Pro must perform this task. ### (Optional) Create a service account -The C1 Jamf Pro connector requires a username and password. If desired, you can set up a service account to be used for the connector. +The C1.ai Jamf Pro connector requires a username and password. If desired, you can set up a service account to be used for the connector. @@ -62,17 +62,17 @@ Give the user you create full access to the Jamf Pro instance and the Administra To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Jamf 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Jamf** and click **Add**. @@ -117,13 +117,13 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Jamf connector is now pulling access data into C1. +**Done.** Your Jamf connector is now pulling access data into C1.ai. **Follow these instructions to use the Jamf 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -134,7 +134,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -236,14 +236,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 C1.ai 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 Jamf connector to. Jamf data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Jamf connector to. Jamf data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Jamf connector is now pulling access data into C1. +**Done.** Your Jamf connector is now pulling access data into C1.ai. diff --git a/baton/jd-edwards.mdx b/baton/jd-edwards.mdx index b6d12a3c..6ea470bd 100644 --- a/baton/jd-edwards.mdx +++ b/baton/jd-edwards.mdx @@ -1,8 +1,8 @@ --- title: "Set up an Oracle JD Edwards connector" og:title: "Set up an Oracle JD Edwards connector" -description: "C1 provides identity governance for Oracle JD Edwards. Integrate your Oracle JD Edwards instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Oracle JD Edwards. Integrate your Oracle JD Edwards instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Oracle JD Edwards. Integrate your Oracle JD Edwards instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Oracle JD Edwards. Integrate your Oracle JD Edwards instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Oracle JD Edwards" --- @@ -35,17 +35,17 @@ The URL of the AIS server. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of JD Edwards 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **JD Edwards** and click **Add**. @@ -81,13 +81,13 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your JD Edwards connector is now pulling access data into C1. +**Done.** Your JD Edwards connector is now pulling access data into C1.ai. **Follow these instructions to use the JD Edwards 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -97,7 +97,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -189,14 +189,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 C1.ai 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 JD Edwards connector to. JD Edwards data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the JD Edwards connector to. JD Edwards data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your JD Edwards connector is now pulling access data into C1. +**Done.** Your JD Edwards connector is now pulling access data into C1.ai. diff --git a/baton/jenkins.mdx b/baton/jenkins.mdx index 552b4ba0..ec3b0065 100644 --- a/baton/jenkins.mdx +++ b/baton/jenkins.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Jenkins connector" og:title: "Set up a Jenkins connector" -description: "C1 provides identity governance and just-in-time provisioning for Jenkins. Integrate your Jenkins 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 Jenkins. Integrate your Jenkins instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Jenkins. Integrate your Jenkins instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Jenkins. Integrate your Jenkins instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Jenkins" --- @@ -32,13 +32,13 @@ Configuring the connector requires you to pass in credentials generated in Jenki To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Jenkins 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 C1.ai.** *Cloud-hosted connector not currently available.* @@ -46,7 +46,7 @@ To complete this task, you'll need: **Follow these instructions to use the Jenkins 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -56,7 +56,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -154,14 +154,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 C1.ai 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 Jenkins connector to. Jenkins data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Jenkins connector to. Jenkins data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Jenkins connector is now pulling access data into C1. +**Done.** Your Jenkins connector is now pulling access data into C1.ai. diff --git a/baton/jira-datacenter.mdx b/baton/jira-datacenter.mdx index 552e43c9..4b059fb0 100644 --- a/baton/jira-datacenter.mdx +++ b/baton/jira-datacenter.mdx @@ -1,8 +1,8 @@ --- title: "Set up an Atlassian Jira Data Center connector" -description: "C1 provides identity governance and just-in-time provisioning for Jira Data Center. Integrate your Jira Data Center instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Jira Data Center. Integrate your Jira Data Center instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." og:title: "Set up an Atlassian Jira Data Center connector" -og:description: "C1 provides identity governance and just-in-time provisioning for Jira Data Center. Integrate your Jira Data Center instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Jira Data Center. Integrate your Jira Data Center instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Atlassian Jira Data Center" --- @@ -18,7 +18,7 @@ sidebarTitle: "Atlassian Jira Data Center" The Jira Data Center connector supports [automatic account provisioning](/product/admin/account-provisioning). -When a new account is created by C1, the account's password will be sent to a [vault](/product/admin/vaults). +When a new account is created by C1.ai, the account's password will be sent to a [vault](/product/admin/vaults). This connector does not support account deprovisioning. You must deprovision accounts directly in Jira. @@ -50,7 +50,7 @@ The Jira Data Center user account used to generate these credentials must have t Click **Personal Access Tokens**. - Select **Create token** and give your new token a name, such as "C1". + Select **Create token** and give your new token a name, such as "C1.ai". Click **Create**. @@ -67,20 +67,20 @@ The Jira Data Center user account used to generate these credentials must have t **To complete this task, you'll need:** -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Jira Data Center 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 C1.ai.** Cloud-hosted connector not currently available. **Follow these instructions to use the Jira Data Center 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -90,7 +90,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -183,14 +183,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 C1.ai 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 Jira Data Center connector to. Jira Data Center data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Jira Data Center connector to. Jira Data Center data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Jira Data Center connector is now pulling access data into C1. +**Done.** Your Jira Data Center connector is now pulling access data into C1.ai. diff --git a/baton/jira.mdx b/baton/jira.mdx index e126bb69..9413002c 100644 --- a/baton/jira.mdx +++ b/baton/jira.mdx @@ -1,8 +1,8 @@ --- title: "Set up an Atlassian Jira Cloud connector" -description: "C1 provides identity governance for Jira Cloud. Integrate your Jira Cloud instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance for Jira Cloud. Integrate your Jira Cloud instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." og:title: "Set up an Atlassian Jira Cloud connector" -og:description: "C1 provides identity governance for Jira Cloud. Integrate your Jira Cloud instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance for Jira Cloud. Integrate your Jira Cloud instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Atlassian Jira Cloud" --- @@ -135,17 +135,17 @@ If you want to set up the Jira Cloud connector to sync managed accounts and mana **To complete this task, you'll need:** -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Jira Cloud 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Jira Cloud** and click **Add**. @@ -187,12 +187,12 @@ If you want to set up the Jira Cloud connector to sync managed accounts and mana -**Done.** Your Jira Cloud connector is now pulling access data into C1. +**Done.** Your Jira Cloud connector is now pulling access data into C1.ai. **Follow these instructions to use the Jira 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -204,7 +204,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -314,14 +314,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 C1.ai 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 Jira Cloud connector to. Jira Cloud data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Jira Cloud connector to. Jira Cloud data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Jira Cloud connector is now pulling access data into C1. +**Done.** Your Jira Cloud connector is now pulling access data into C1.ai. diff --git a/baton/jumpcloud.mdx b/baton/jumpcloud.mdx index 618d466a..185e732c 100644 --- a/baton/jumpcloud.mdx +++ b/baton/jumpcloud.mdx @@ -1,13 +1,13 @@ --- title: "Set up a JumpCloud connector" og:title: "Set up a JumpCloud connector" -description: "C1 provides identity governance for JumpCloud. Integrate your JumpCloud instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." -og:description: "C1 provides identity governance for JumpCloud. Integrate your JumpCloud instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance for JumpCloud. Integrate your JumpCloud instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance for JumpCloud. Integrate your JumpCloud instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "JumpCloud" --- -This page covers the JumpCloud **connector**, which syncs and provisions access data for identity governance. It does not control how you sign in to C1. To set up signing in to C1 with your JumpCloud account, see [Authenticate with JumpCloud](/product/how-to/qs-set-up-c1#authenticate-with-jumpcloud). +This page covers the JumpCloud **connector**, which syncs and provisions access data for identity governance. It does not control how you sign in to C1.ai. To set up signing in to C1.ai with your JumpCloud account, see [Authenticate with JumpCloud](/product/how-to/qs-set-up-c1#authenticate-with-jumpcloud). ## Capabilities @@ -50,17 +50,17 @@ Copy the API key. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of JumpCloud 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **JumpCloud** and click **Add**. @@ -93,13 +93,13 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your JumpCloud connector is now pulling access data into C1. +**Done.** Your JumpCloud connector is now pulling access data into C1.ai. **Follow these instructions to use the JumpCloud 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -111,7 +111,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -204,26 +204,26 @@ 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 C1.ai 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 JumpCloud connector to. JumpCloud data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the JumpCloud connector to. JumpCloud data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your JumpCloud connector is now pulling access data into C1. +**Done.** Your JumpCloud connector is now pulling access data into C1.ai. ### What's next? -If JumpCloud is your company's identity provider (meaning that it is used to SSO into other software), the connector 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 connectors for the SCIMed apps. +If JumpCloud is your company's identity provider (meaning that it is used to SSO into other software), the connector sync will automatically create applications in C1.ai 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 connectors for the SCIMed apps. ## Troubleshooting the JumpCloud integration ### Why do I see multiple accounts for some JumpCloud users? -JumpCloud separates users and admin users, giving each a separate identity and login. Because of this, a user who is both a user and an admin user in JumpCloud will have two JumpCloud accounts in C1. +JumpCloud separates users and admin users, giving each a separate identity and login. Because of this, a user who is both a user and an admin user in JumpCloud will have two JumpCloud accounts in C1.ai. ### Why don't I see profile attributes listed for a JumpCloud admin user? diff --git a/baton/kayako.mdx b/baton/kayako.mdx index 5e0f2919..d0f3b4c5 100644 --- a/baton/kayako.mdx +++ b/baton/kayako.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Kayako connector" og:title: "Set up a Kayako connector" -description: "C1 provides identity governance for Kayako. Integrate your Kayako instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Kayako. Integrate your Kayako instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Kayako. Integrate your Kayako instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Kayako. Integrate your Kayako instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Kayako" --- -C1 provides identity governance for Kayako. Integrate your Kayako instance with -C1 for unified visibility and governance over the people who can access your +C1.ai provides identity governance for Kayako. Integrate your Kayako instance with +C1.ai for unified visibility and governance over the people who can access your Kayako help desk. ## Capabilities @@ -48,11 +48,11 @@ or owner account is the safest choice. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -98,7 +98,7 @@ or owner account is the safest choice. - **Done.** Your Kayako connector is now pulling access data into C1. + **Done.** Your Kayako connector is now pulling access data into C1.ai. @@ -123,6 +123,6 @@ or owner account is the safest choice. - **Done.** Your Kayako connector is now pulling access data into C1. + **Done.** Your Kayako connector is now pulling access data into C1.ai. diff --git a/baton/keeper.mdx b/baton/keeper.mdx index 2d5f3f8d..02318706 100644 --- a/baton/keeper.mdx +++ b/baton/keeper.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Keeper connector" og:title: "Set up a Keeper connector" -description: "C1 provides identity governance for Keeper. Integrate your Keeper instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Keeper. Integrate your Keeper instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Keeper. Integrate your Keeper instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Keeper. Integrate your Keeper instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Keeper" --- -C1 provides identity governance for Keeper. Integrate your Keeper instance with -C1 for unified visibility and governance over team membership. +C1.ai provides identity governance for Keeper. Integrate your Keeper instance with +C1.ai for unified visibility and governance over team membership. ## Capabilities @@ -29,7 +29,7 @@ ability to configure provisioning. Sign in to the [Keeper Admin Console](https://keepersecurity.com/console) - and select the node you want C1 to sync. + and select the node you want C1.ai to sync. @@ -49,11 +49,11 @@ ability to configure provisioning. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -99,7 +99,7 @@ ability to configure provisioning. - **Done.** Your Keeper connector is now pulling access data into C1. + **Done.** Your Keeper connector is now pulling access data into C1.ai. @@ -121,6 +121,6 @@ ability to configure provisioning. - **Done.** Your Keeper connector is now pulling access data into C1. + **Done.** Your Keeper connector is now pulling access data into C1.ai. diff --git a/baton/keycloak.mdx b/baton/keycloak.mdx index ecaf088d..e9bc52a4 100644 --- a/baton/keycloak.mdx +++ b/baton/keycloak.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Keycloak connector" og:title: "Set up a Keycloak connector" -description: "C1 provides identity governance and just-in-time provisioning for Keycloak. Integrate your Keycloak 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 Keycloak. Integrate your Keycloak instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for Keycloak. Integrate your Keycloak instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Keycloak. Integrate your Keycloak instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "Keycloak" --- @@ -32,7 +32,7 @@ The Keycloak connector supports [automatic account provisioning](/product/admin/ ### 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 C1.ai 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 | | -------------- | -------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- | @@ -108,18 +108,18 @@ For more information, see the [Keycloak Server Administration Guide](https://www To complete this task, you need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - The Keycloak 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Keycloak** and click **Add**. @@ -163,14 +163,14 @@ The connector label changes to **Syncing**, followed by **Connected**. You can v -**Done.** Your Keycloak connector is now pulling access data into C1. +**Done.** Your Keycloak connector is now pulling access data into C1.ai. **Follow these instructions to use the Keycloak 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -182,7 +182,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -246,7 +246,7 @@ stringData: **Syncing subgroups**: Set `BATON_SYNC_SUB_GROUPS` to `true` to sync nested Keycloak group hierarchies. When enabled, subgroup membership relationships - are surfaced in C1, and grant and revoke operations are supported for nested + are surfaced in C1.ai, and grant and revoke operations are supported for nested groups. @@ -289,18 +289,18 @@ spec: - Create a namespace in which to run C1 connectors (if desired), then apply + Create a namespace in which to run C1.ai connectors (if desired), then apply the secret config and deployment config files. - Check that the connector data uploaded correctly. In C1, click **Apps**. On + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Keycloak connector to. Keycloak data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Keycloak connector is now pulling access data into C1. +**Done.** Your Keycloak connector is now pulling access data into C1.ai. diff --git a/baton/kinde.mdx b/baton/kinde.mdx index 889b5024..04453781 100644 --- a/baton/kinde.mdx +++ b/baton/kinde.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Kinde connector" og:title: "Set up a Kinde connector" -description: "C1 provides identity governance for Kinde. Integrate your Kinde tenant with C1 for unified visibility and governance over users and organization membership." -og:description: "C1 provides identity governance for Kinde. Integrate your Kinde tenant with C1 for unified visibility and governance over users and organization membership." +description: "C1.ai provides identity governance for Kinde. Integrate your Kinde tenant with C1.ai for unified visibility and governance over users and organization membership." +og:description: "C1.ai provides identity governance for Kinde. Integrate your Kinde tenant with C1.ai for unified visibility and governance over users and organization membership." sidebarTitle: "Kinde" --- -C1 provides identity governance for Kinde. Integrate your Kinde tenant with -C1 for unified visibility and governance over users and their membership +C1.ai provides identity governance for Kinde. Integrate your Kinde tenant with +C1.ai for unified visibility and governance over users and their membership in organizations. ## Capabilities @@ -60,11 +60,11 @@ Kinde Management API with **`read:users`**, **`read:organizations`**, and - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -110,7 +110,7 @@ Kinde Management API with **`read:users`**, **`read:organizations`**, and - **Done.** Your Kinde connector is now pulling access data into C1. + **Done.** Your Kinde connector is now pulling access data into C1.ai. @@ -137,7 +137,7 @@ Kinde Management API with **`read:users`**, **`read:organizations`**, and - **Done.** Your Kinde connector is now pulling access data into C1. + **Done.** Your Kinde connector is now pulling access data into C1.ai. diff --git a/baton/knowbe4.mdx b/baton/knowbe4.mdx index 2b669142..07c5c6a0 100644 --- a/baton/knowbe4.mdx +++ b/baton/knowbe4.mdx @@ -1,13 +1,13 @@ --- title: "Set up a KnowBe4 connector" og:title: "Set up a KnowBe4 connector" -description: "C1 provides identity governance for KnowBe4. Integrate your KnowBe4 instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for KnowBe4. Integrate your KnowBe4 instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for KnowBe4. Integrate your KnowBe4 instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for KnowBe4. Integrate your KnowBe4 instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "KnowBe4" --- -C1 provides identity governance for KnowBe4. Integrate your KnowBe4 instance -with C1 for unified visibility and governance over group membership. +C1.ai provides identity governance for KnowBe4. Integrate your KnowBe4 instance +with C1.ai for unified visibility and governance over group membership. ## Capabilities @@ -48,11 +48,11 @@ console. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -97,7 +97,7 @@ console. - **Done.** Your KnowBe4 connector is now pulling access data into C1. + **Done.** Your KnowBe4 connector is now pulling access data into C1.ai. @@ -119,6 +119,6 @@ console. - **Done.** Your KnowBe4 connector is now pulling access data into C1. + **Done.** Your KnowBe4 connector is now pulling access data into C1.ai. diff --git a/baton/kubernetes.mdx b/baton/kubernetes.mdx index eab14674..05dafe6c 100644 --- a/baton/kubernetes.mdx +++ b/baton/kubernetes.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Kubernetes connector" -description: "C1 provides identity governance for Kubernetes. Integrate your Kubernetes cluster with C1 to run user access reviews (UARs) and gain visibility into RBAC permissions across your cluster." +description: "C1.ai provides identity governance for Kubernetes. Integrate your Kubernetes cluster with C1.ai to run user access reviews (UARs) and gain visibility into RBAC permissions across your cluster." og:title: "Set up a Kubernetes connector" -og:description: "C1 provides identity governance for Kubernetes. Integrate your Kubernetes cluster with C1 to run user access reviews (UARs) and gain visibility into RBAC permissions across your cluster." +og:description: "C1.ai provides identity governance for Kubernetes. Integrate your Kubernetes cluster with C1.ai to run user access reviews (UARs) and gain visibility into RBAC permissions across your cluster." sidebarTitle: "Kubernetes" --- @@ -40,7 +40,7 @@ baton-kubernetes --sync-resource-types namespace,service_account,role,cluster_ro **Notes:** -- Bindings whose subject name contains `system:` are excluded from grants. This covers groups such as `system:masters` and `system:serviceaccounts:`, and users such as `system:kube-controller-manager` — subjects that belong to Kubernetes' own control plane. Roles and cluster roles named `system:*` are still synced; the exclusion applies to the subject side of a binding. If your cluster binds a `system:` group to real users, that binding produces no grant in C1. +- Bindings whose subject name contains `system:` are excluded from grants. This covers groups such as `system:masters` and `system:serviceaccounts:`, and users such as `system:kube-controller-manager` — subjects that belong to Kubernetes' own control plane. Roles and cluster roles named `system:*` are still synced; the exclusion applies to the subject side of a binding. If your cluster binds a `system:` group to real users, that binding produces no grant in C1.ai. ## Cluster role assignments @@ -195,9 +195,9 @@ To resolve those memberships from the directory that does hold them, attach an i ## Matching cluster identities to a directory -A cluster authorizes identities it does not store, so a `User` or `Group` subject in an RBAC binding is only a string the authenticator asserted: an OIDC claim, an x509 `CN=`/`O=` field, a Microsoft Entra object ID, an AWS IAM ARN. The directory that knows who that principal is belongs to a different app in C1. +A cluster authorizes identities it does not store, so a `User` or `Group` subject in an RBAC binding is only a string the authenticator asserted: an OIDC claim, an x509 `CN=`/`O=` field, a Microsoft Entra object ID, an AWS IAM ARN. The directory that knows who that principal is belongs to a different app in C1.ai. -Selecting that app as this connector's **identity source** lets C1 resolve the two. Each `User` and `Group` subject the connector reports is matched against the identity source's principals, and a matched group is expanded through the directory's own membership, so `Group developers → ClusterRole admin` becomes reviewable person by person — the membership Kubernetes itself cannot supply. +Selecting that app as this connector's **identity source** lets C1.ai resolve the two. Each `User` and `Group` subject the connector reports is matched against the identity source's principals, and a matched group is expanded through the directory's own membership, so `Group developers → ClusterRole admin` becomes reviewable person by person — the membership Kubernetes itself cannot supply. Matching is attempted two ways at once, because which one fits depends on the directory rather than on Kubernetes: @@ -320,26 +320,26 @@ rather than dropped. **To complete this task, you'll need:** -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai **Follow these instructions to deploy the Kubernetes connector inside your cluster.** -When running in service mode, 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, a self-hosted connector maintains an ongoing connection with C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources * [GitHub repository](https://github.com/conductorone/baton-kubernetes): Access the source code, report issues, or contribute to the project. -### Step 1: Set up a new Kubernetes connector in C1 +### Step 1: Set up a new Kubernetes connector in C1.ai -Navigate to **Apps** > **Connectors** in C1 to register a new connector and generate credentials. +Navigate to **Apps** > **Connectors** in C1.ai to register a new connector and generate credentials. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -368,7 +368,7 @@ Navigate to **Apps** > **Connectors** in C1 to register a new connector and gene ### Step 2: Deploy the connector to your cluster -Create a secret with your C1 credentials and deploy the connector using the service account created earlier. +Create a secret with your C1.ai credentials and deploy the connector using the service account created earlier. ```yaml apiVersion: v1 @@ -405,7 +405,7 @@ spec: name: baton-conductorone-creds ``` -Save this as `baton-kubernetes.yaml`, fill in your C1 credentials, and apply it: +Save this as `baton-kubernetes.yaml`, fill in your C1.ai credentials, and apply it: ```bash kubectl apply -f baton-kubernetes.yaml @@ -413,7 +413,7 @@ kubectl apply -f baton-kubernetes.yaml ### Step 3: Verify the connector is running -Confirm the pod is healthy and that C1 is receiving data from the cluster. +Confirm the pod is healthy and that C1.ai is receiving data from the cluster. @@ -425,14 +425,14 @@ Confirm the pod is healthy and that C1 is receiving data from the cluster. ``` - In C1, click **Apps**. On the **Managed apps** tab, locate the application you added the connector to. Kubernetes data should appear on the **Entitlements** and **Accounts** tabs after the first sync completes. + In C1.ai, click **Apps**. On the **Managed apps** tab, locate the application you added the connector to. Kubernetes data should appear on the **Entitlements** and **Accounts** tabs after the first sync completes. -**Done.** Your Kubernetes connector is now pulling access data into C1. +**Done.** Your Kubernetes connector is now pulling access data into C1.ai. -**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 C1.ai.** Cloud-hosted mode requires your Kubernetes API server to be publicly accessible. You'll need a bearer token and the public API server URL. @@ -466,13 +466,13 @@ Copy the decoded token — you'll need it when configuring the connector. kubectl cluster-info | grep "Kubernetes control plane" ``` -### Step 3: Configure the connector in C1 +### Step 3: Configure the connector in C1.ai -Add the connector in C1 and enter the credentials you collected in the previous steps. +Add the connector in C1.ai and enter the credentials you collected in the previous steps. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Kubernetes** and click **Add**. @@ -503,6 +503,6 @@ Add the connector in C1 and enter the credentials you collected in the previous -**Done.** Your Kubernetes connector is now pulling access data into C1. +**Done.** Your Kubernetes connector is now pulling access data into C1.ai. diff --git a/baton/kustomer.mdx b/baton/kustomer.mdx index ad5dccf3..43b50ac3 100644 --- a/baton/kustomer.mdx +++ b/baton/kustomer.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Kustomer connector" og:title: "Set up a Kustomer connector" -description: "C1 provides identity governance for Kustomer. Integrate your Kustomer instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Kustomer. Integrate your Kustomer instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Kustomer. Integrate your Kustomer instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Kustomer. Integrate your Kustomer instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Kustomer" --- -C1 provides identity governance for Kustomer. Integrate your Kustomer -instance with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Kustomer. Integrate your Kustomer +instance with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -48,11 +48,11 @@ to read users. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -99,7 +99,7 @@ to read users. - **Done.** Your Kustomer connector is now pulling access data into C1. + **Done.** Your Kustomer connector is now pulling access data into C1.ai. @@ -126,6 +126,6 @@ to read users. - **Done.** Your Kustomer connector is now pulling access data into C1. + **Done.** Your Kustomer connector is now pulling access data into C1.ai. diff --git a/baton/kyriba.mdx b/baton/kyriba.mdx index ebf2e48c..1fdf811c 100644 --- a/baton/kyriba.mdx +++ b/baton/kyriba.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Kyriba connector" og:title: "Set up a Kyriba connector" -description: "C1 provides identity governance and just-in-time provisioning for Kyriba. Integrate your Kyriba 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 Kyriba. Integrate your Kyriba instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for Kyriba. Integrate your Kyriba instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Kyriba. Integrate your Kyriba instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "Kyriba" --- @@ -24,7 +24,7 @@ The Kyriba connector syncs the following resources: ### Connector actions -Connector actions are custom capabilities that extend C1 automations with app-specific operations. Which automation step offers an action is determined by the action itself — you cannot choose: +Connector actions are custom capabilities that extend C1.ai automations with app-specific operations. Which automation step offers an action is determined by the action itself — you cannot choose: | Automation step | Actions offered | How the target is selected | |-----------------|-----------------|----------------------------| @@ -35,7 +35,7 @@ Connector actions are custom capabilities that extend C1 automations with app-sp | `enable_user` | `user_id` (string, required) | Reactivates a previously disabled Kyriba user without affecting any other data | | `disable_user` | `user_id` (string, required) | Deactivates a Kyriba user without deleting them — the user record, their profile, and their access assignments are preserved and can be restored with `enable_user` | -The connector passes `user_id` to Kyriba unchanged. Kyriba's `/v1/users/{ref}` accepts either the user's UUID or their `code`, and C1's account selector supplies the UUID. +The connector passes `user_id` to Kyriba unchanged. Kyriba's `/v1/users/{ref}` accepts either the user's UUID or their `code`, and C1.ai's account selector supplies the UUID. ## Gather Kyriba credentials @@ -80,11 +80,11 @@ The connector authenticates using OAuth2 client credentials. You will need: - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -136,13 +136,13 @@ The connector authenticates using OAuth2 client credentials. You will need: - **Done.** Your Kyriba connector is now pulling access data into C1. + **Done.** Your Kyriba connector is now pulling access data into C1.ai. Follow these instructions to use the [Kyriba](https://github.com/conductorone/baton-kyriba) 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. + When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1.ai, automatically syncing and uploading data at regular intervals. ### Resources @@ -155,7 +155,7 @@ The connector authenticates using OAuth2 client credentials. You will need: - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -255,15 +255,15 @@ The connector authenticates using OAuth2 client credentials. You will need: - 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 C1.ai 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 Kyriba connector to. Kyriba data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the Kyriba connector to. Kyriba data should be found on the **Entitlements** and **Accounts** tabs. - **Done.** Your Kyriba connector is now pulling access data into C1. + **Done.** Your Kyriba connector is now pulling access data into C1.ai. diff --git a/baton/langfuse.mdx b/baton/langfuse.mdx index 5ef59030..74cc5071 100644 --- a/baton/langfuse.mdx +++ b/baton/langfuse.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Langfuse connector" og:title: "Set up a Langfuse connector" -description: "C1 provides identity governance for Langfuse. Integrate your Langfuse instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Langfuse. Integrate your Langfuse instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Langfuse. Integrate your Langfuse instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Langfuse. Integrate your Langfuse instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Langfuse" --- -C1 provides identity governance for Langfuse. Integrate your Langfuse -organization with C1 for unified visibility and governance over who can +C1.ai provides identity governance for Langfuse. Integrate your Langfuse +organization with C1.ai for unified visibility and governance over who can access your organization and its projects. ## Capabilities @@ -57,11 +57,11 @@ connector requires organization-scoped keys. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -108,7 +108,7 @@ connector requires organization-scoped keys. - **Done.** Your Langfuse connector is now pulling access data into C1. + **Done.** Your Langfuse connector is now pulling access data into C1.ai. @@ -134,6 +134,6 @@ connector requires organization-scoped keys. - **Done.** Your Langfuse connector is now pulling access data into C1. + **Done.** Your Langfuse connector is now pulling access data into C1.ai. diff --git a/baton/langsmith.mdx b/baton/langsmith.mdx index 5ca48364..2f23163c 100644 --- a/baton/langsmith.mdx +++ b/baton/langsmith.mdx @@ -1,8 +1,8 @@ --- title: "Set up a LangSmith connector" og:title: "Set up a LangSmith connector" -description: "C1 provides identity governance and just-in-time provisioning for LangSmith. Integrate your LangSmith 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 LangSmith. Integrate your LangSmith instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for LangSmith. Integrate your LangSmith instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for LangSmith. Integrate your LangSmith instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "LangSmith" --- @@ -19,7 +19,7 @@ sidebarTitle: "LangSmith" Use an organization-scoped LangSmith service key (`lsv2_sk_...`), not a -personal access token (`lsv2_pt_...`) or workspace-scoped key. C1 recommends a +personal access token (`lsv2_pt_...`) or workspace-scoped key. C1.ai recommends a service key with the Organization Admin role. @@ -61,11 +61,11 @@ service key with the Organization Admin role. ## Special notes -- Workspace role grants can be added and revoked from C1. +- Workspace role grants can be added and revoked from C1.ai. - Organization role grants are read-only because LangSmith replaces the single organization role on update rather than adding or removing independent grants. -- A user must already be a LangSmith organization member before C1 can assign +- A user must already be a LangSmith organization member before C1.ai can assign the user to a workspace role. - Personal and deleted workspaces are filtered out during sync. - The connector targets LangSmith Cloud. @@ -74,11 +74,11 @@ service key with the Organization Admin role. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -125,7 +125,7 @@ service key with the Organization Admin role. - **Done.** Your LangSmith connector is now pulling access data into C1. + **Done.** Your LangSmith connector is now pulling access data into C1.ai. @@ -134,7 +134,7 @@ service key with the Organization Admin role. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -152,7 +152,7 @@ service key with the Organization Admin role. - Configure C1 credentials and LangSmith credentials as environment + Configure C1.ai credentials and LangSmith credentials as environment variables: ```bash @@ -175,6 +175,6 @@ service key with the Organization Admin role. - **Done.** Your LangSmith connector is now pulling access data into C1. + **Done.** Your LangSmith connector is now pulling access data into C1.ai. diff --git a/baton/lastpass.mdx b/baton/lastpass.mdx index 25545336..20b93672 100644 --- a/baton/lastpass.mdx +++ b/baton/lastpass.mdx @@ -1,8 +1,8 @@ --- title: "Set up LastPass connector" og:title: "Set up LastPass connector" -description: "C1 provides identity governance for LastPass. Integrate your LastPass instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for LastPass. Integrate your LastPass instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for LastPass. Integrate your LastPass instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for LastPass. Integrate your LastPass instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "LastPass" --- @@ -36,17 +36,17 @@ See the LastPass docs for information on how to acquire credentials: [View the d To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of LastPass 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **LastPass** and click **Add**. @@ -79,23 +79,23 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your LastPass connector is now pulling access data into C1. +**Done.** Your LastPass connector is now pulling access data into C1.ai. **Follow these instructions to use the LastPass 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources -[Contact C1's support team](mailto:support@c1.ai) to download the latest version of the connector. +[Contact C1.ai's support team](mailto:support@c1.ai) to download the latest version of the connector. ### Step 1: Set up a new LastPass connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -187,14 +187,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 C1.ai 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 lastpass connector to. lastpass data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the lastpass connector to. lastpass data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your LastPass connector is now pulling access data into C1. +**Done.** Your LastPass connector is now pulling access data into C1.ai. diff --git a/baton/lattice.mdx b/baton/lattice.mdx index 0f172dc8..3704b8d6 100644 --- a/baton/lattice.mdx +++ b/baton/lattice.mdx @@ -1,15 +1,15 @@ --- title: "Set up a Lattice connector" og:title: "Set up a Lattice connector" -description: "C1 provides identity governance for Lattice. Integrate your Lattice instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Lattice. Integrate your Lattice instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Lattice. Integrate your Lattice instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Lattice. Integrate your Lattice instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Lattice" --- {/* stargate: cf-lattice-fullimpl-20260605 */} -C1 provides identity governance for Lattice. Integrate your Lattice instance -with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Lattice. Integrate your Lattice instance +with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -22,7 +22,7 @@ The connector syncs your Lattice users as identities. Each user carries their job title, department, and account status, so you can see who is active and where they sit in the organization. It also syncs your Lattice departments and who belongs to each one, so department membership is visible and reviewable in -C1. +C1.ai. ## Gather Lattice credentials @@ -52,11 +52,11 @@ a secret. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -100,7 +100,7 @@ a secret. - **Done.** Your Lattice connector is now pulling access data into C1. + **Done.** Your Lattice connector is now pulling access data into C1.ai. @@ -123,6 +123,6 @@ a secret. - **Done.** Your Lattice connector is now pulling access data into C1. + **Done.** Your Lattice connector is now pulling access data into C1.ai. diff --git a/baton/launchdarkly.mdx b/baton/launchdarkly.mdx index 7b4338b8..9a316e79 100644 --- a/baton/launchdarkly.mdx +++ b/baton/launchdarkly.mdx @@ -1,8 +1,8 @@ --- title: "Set up LaunchDarkly connector" og:title: "Set up LaunchDarkly connector" -description: "C1 provides identity governance for LaunchDarkly. Integrate your LaunchDarkly instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for LaunchDarkly. Integrate your LaunchDarkly instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for LaunchDarkly. Integrate your LaunchDarkly instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for LaunchDarkly. Integrate your LaunchDarkly instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "LaunchDarkly" --- @@ -52,17 +52,17 @@ This connector requires a LaunchDarkly **Enterprise** plan. A token's base role To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of LaunchDarkly 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **LaunchDarkly** and click **Add**. @@ -95,23 +95,23 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your LaunchDarkly connector is now pulling access data into C1. +**Done.** Your LaunchDarkly connector is now pulling access data into C1.ai. **Follow these instructions to use the LaunchDarkly 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai 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 C1.ai's support team](mailto:support@conductorone.com) to download the latest version of the connector. ### Step 1: Set up a new LaunchDarkly connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -204,13 +204,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 C1.ai 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 launchdarkly connector to. launchdarkly data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the launchdarkly connector to. launchdarkly data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your LaunchDarkly connector is now pulling access data into C1. +**Done.** Your LaunchDarkly connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/ldap.mdx b/baton/ldap.mdx index 0f870be6..aeb7a64c 100644 --- a/baton/ldap.mdx +++ b/baton/ldap.mdx @@ -1,8 +1,8 @@ --- title: "Set up an LDAP connector" og:title: "Set up an LDAP connector" -description: "C1 provides identity governance and just-in-time provisioning for LDAP. Integrate your LDAP server 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 LDAP. Integrate your LDAP server with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for LDAP. Integrate your LDAP server with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for LDAP. Integrate your LDAP server with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "LDAP" --- @@ -38,7 +38,7 @@ To use this feature, configure the following account provisioning mappings: ### 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 C1.ai 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. **Global actions** (connector-level): @@ -54,15 +54,15 @@ Connector actions are custom capabilities that extend C1 automations with app-sp | Action name | Additional fields | Description | | ----------- | ----------------- | ----------- | -| `update_profile` | `user_id` (account resource ID, required), `first_name` (string), `last_name` (string), `display_name` (string), `email` (string), `custom_attributes` (string map) | Set core profile fields (first name, last name, display name, email) and/or arbitrary custom LDAP attributes on an existing user. This action is scoped to the `user` resource type, which is what makes it discoverable and usable from C1's attribute-push-rule feature. It also backs C1's [attribute push rule](/product/admin/push-rules) flow for LDAP users. | +| `update_profile` | `user_id` (account resource ID, required), `first_name` (string), `last_name` (string), `display_name` (string), `email` (string), `custom_attributes` (string map) | Set core profile fields (first name, last name, display name, email) and/or arbitrary custom LDAP attributes on an existing user. This action is scoped to the `user` resource type, which is what makes it discoverable and usable from C1.ai's attribute-push-rule feature. It also backs C1.ai's [attribute push rule](/product/admin/push-rules) flow for LDAP users. | The `update_profile` action returns `success` (bool), `updated_user` (the modified user resource, re-fetched after the write; absent if the read-back failed, though the write itself still succeeded), `applied` (the number of attributes changed), and `skipped` (named fields or `custom_attributes` entries that were not written). `updated_user` carries the resource identity, `displayName`, and the user trait — not the entry's full attribute set. A value the action just wrote appears there only when it also feeds one of those: `display_name` through `displayName`, `email` through the trait's email list, and a `custom_attributes` key only when it maps to a trait field (`mail`, `displayName`, `sAMAccountName`, `userPrincipalName`, a non-RDN `uid` or `cn`, `lastLogonTimestamp`, `authTimestamp`). `first_name`, `last_name`, and every other `custom_attributes` key reach the directory but do not appear in `updated_user`. Use `applied` to confirm those. -Two requirements come from the C1 side rather than from LDAP: +Two requirements come from the C1.ai side rather than from LDAP: -- **`user_id` takes the C1 account identifier, not the LDAP DN.** C1 resolves the account to the connector's resource before dispatching the action. A DN fails inside C1 with `resource with type user was not found` and never reaches the connector, so it produces no connector log line and leaves the directory untouched. +- **`user_id` takes the C1.ai account identifier, not the LDAP DN.** C1.ai resolves the account to the connector's resource before dispatching the action. A DN fails inside C1.ai with `resource with type user was not found` and never reaches the connector, so it produces no connector log line and leaves the directory untouched. - **An attribute push rule must map from a single-valued attribute.** The connector's user profile carries only attributes that hold exactly one value on the entry, so a multi-valued source resolves to nothing: the rule saves and enables, and each push reports zero attributes applied. @@ -97,13 +97,13 @@ Here's the set of credentials you'll need when setting up the connector: To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of LDAP 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 C1.ai.** *Cloud-hosted connector not currently available.* @@ -111,7 +111,7 @@ To complete this task, you'll need: **Follow these instructions to use the LDAP 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -123,7 +123,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -218,13 +218,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 C1.ai 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 LDAP connector to. LDAP data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the LDAP connector to. LDAP data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your LDAP connector is now pulling access data into C1. +**Done.** Your LDAP connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/lever.mdx b/baton/lever.mdx index ef333e25..4ac766b2 100644 --- a/baton/lever.mdx +++ b/baton/lever.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Lever connector" og:title: "Set up a Lever connector" -description: "C1 provides identity governance for Lever. Integrate your Lever account with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Lever. Integrate your Lever account with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Lever. Integrate your Lever account with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Lever. Integrate your Lever account with C1.ai for unified visibility and governance over user access." sidebarTitle: "Lever" --- -C1 provides identity governance for Lever. Integrate your Lever account with -C1 for unified visibility and governance over who has access to your hiring +C1.ai provides identity governance for Lever. Integrate your Lever account with +C1.ai for unified visibility and governance over who has access to your hiring data. ## Capabilities @@ -48,11 +48,11 @@ your Lever account. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -96,7 +96,7 @@ your Lever account. - **Done.** Your Lever connector is now pulling access data into C1. + **Done.** Your Lever connector is now pulling access data into C1.ai. @@ -119,6 +119,6 @@ your Lever account. - **Done.** Your Lever connector is now pulling access data into C1. + **Done.** Your Lever connector is now pulling access data into C1.ai. diff --git a/baton/linear.mdx b/baton/linear.mdx index 2379bf83..eccc873b 100644 --- a/baton/linear.mdx +++ b/baton/linear.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Linear connector" og:title: "Set up a Linear connector" -description: "C1 provides identity governance and just-in-time provisioning for Linear. Integrate your Linear 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 Linear. Integrate your Linear instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Linear. Integrate your Linear instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Linear. Integrate your Linear instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Linear" --- @@ -37,7 +37,7 @@ In Linear, click your profile photo and select **Settings**. In the **Quick search** box, enter `Security & access`, then select the **Security & access** page. -In the **Personal API keys** section of the page, click **New API key**. Enter a label such as "C1", configure the key's permissions and team access, and click **Create**. +In the **Personal API keys** section of the page, click **New API key**. Enter a label such as "C1.ai", configure the key's permissions and team access, and click **Create**. The new API key is generated for you. Carefully copy and save the API key. @@ -51,17 +51,17 @@ The new API key is generated for you. Carefully copy and save the API key. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Linear 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Linear** and click **Add**. @@ -103,13 +103,13 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Linear connector is now pulling access data into C1. +**Done.** Your Linear connector is now pulling access data into C1.ai. **Follow these instructions to use the Linear 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -121,7 +121,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -221,13 +221,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 C1.ai 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 Linear connector to. Linear data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Linear connector to. Linear data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Linear connector is now pulling access data into C1. +**Done.** Your Linear connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/linode.mdx b/baton/linode.mdx index 987b427f..72cac602 100644 --- a/baton/linode.mdx +++ b/baton/linode.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Linode connector" og:title: "Set up a Linode connector" -description: "C1 provides identity governance for Linode. Integrate your Linode instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Linode. Integrate your Linode instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Linode. Integrate your Linode instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Linode. Integrate your Linode instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Linode" --- @@ -27,7 +27,7 @@ In Cloud Manager, navigate to your profile menu and select **API Tokens**. Click **Create a Personal Access Token**. -Give the new token a name, such as "C1", and set an expiration. +Give the new token a name, such as "C1.ai", and set an expiration. Select the **Read Only** permission for **Accounts**. @@ -44,17 +44,17 @@ Click **Create Token**. Carefully copy and save the new 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 C1.ai - Access to the set of Linode 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Linode** and click **Add**. @@ -90,23 +90,23 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Linode connector is now pulling access data into C1. +**Done.** Your Linode connector is now pulling access data into C1.ai. **Follow these instructions to use the Linode 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources -[Contact C1's support team](mailto:support@c1.ai) to download the latest version of the connector. +[Contact C1.ai's support team](mailto:support@c1.ai) to download the latest version of the connector. ### Step 1: Configure the Linode connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -197,14 +197,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 C1.ai 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 Linode connector to. Linode data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Linode connector to. Linode data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Linode connector is now pulling access data into C1. +**Done.** Your Linode connector is now pulling access data into C1.ai. diff --git a/baton/litmos.mdx b/baton/litmos.mdx index 41e8e20b..8a203a1a 100644 --- a/baton/litmos.mdx +++ b/baton/litmos.mdx @@ -1,8 +1,8 @@ --- title: "Set up an SAP Litmos connector" og:title: "Set up an SAP Litmos connector" -description: "C1 provides identity governance and just-in-time provisioning for SAP Litmos. Integrate your SAP Litmos 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 SAP Litmos. Integrate your SAP Litmos instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for SAP Litmos. Integrate your SAP Litmos instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for SAP Litmos. Integrate your SAP Litmos instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "SAP Litmos" --- @@ -43,17 +43,17 @@ Carefully copy and save the API key. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Litmos 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Litmos** and click **Add**. @@ -82,7 +82,7 @@ Enter the name of your Litmos account in the **Source** field. Paste the API key into the **API key** field. -**Optional.** In the **Course IDs** field, add the ID numbers of the courses you want to sync. If no course numbers are entered, C1 will sync all available courses. +**Optional.** In the **Course IDs** field, add the ID numbers of the courses you want to sync. If no course numbers are entered, C1.ai will sync all available courses. Click **Save**. @@ -92,13 +92,13 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Litmos connector is now pulling access data into C1. +**Done.** Your Litmos connector is now pulling access data into C1.ai. **Follow these instructions to use the Litmos 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -108,7 +108,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -203,14 +203,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 C1.ai 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 Litmos connector to. Litmos data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Litmos connector to. Litmos data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Litmos connector is now pulling access data into C1. +**Done.** Your Litmos connector is now pulling access data into C1.ai. diff --git a/baton/liveagent.mdx b/baton/liveagent.mdx index 41671685..9b9f170d 100644 --- a/baton/liveagent.mdx +++ b/baton/liveagent.mdx @@ -1,15 +1,15 @@ --- title: "Set up a LiveAgent connector" og:title: "Set up a LiveAgent connector" -description: "C1 provides identity governance for LiveAgent. Integrate your LiveAgent account with C1 for unified visibility and governance over agent access." -og:description: "C1 provides identity governance for LiveAgent. Integrate your LiveAgent account with C1 for unified visibility and governance over agent access." +description: "C1.ai provides identity governance for LiveAgent. Integrate your LiveAgent account with C1.ai for unified visibility and governance over agent access." +og:description: "C1.ai provides identity governance for LiveAgent. Integrate your LiveAgent account with C1.ai for unified visibility and governance over agent access." sidebarTitle: "LiveAgent" --- {/* stargate: cf-liveagent-20260605 */} -C1 provides identity governance for LiveAgent. Integrate your LiveAgent account -with C1 for unified visibility and governance over agent access. +C1.ai provides identity governance for LiveAgent. Integrate your LiveAgent account +with C1.ai for unified visibility and governance over agent access. ## Capabilities @@ -52,11 +52,11 @@ LiveAgent so the API key can read every agent and department. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -101,7 +101,7 @@ LiveAgent so the API key can read every agent and department. - **Done.** Your LiveAgent connector is now pulling access data into C1. + **Done.** Your LiveAgent connector is now pulling access data into C1.ai. @@ -125,6 +125,6 @@ LiveAgent so the API key can read every agent and department. - **Done.** Your LiveAgent connector is now pulling access data into C1. + **Done.** Your LiveAgent connector is now pulling access data into C1.ai. diff --git a/baton/logicmonitor.mdx b/baton/logicmonitor.mdx index 029fc9ca..7234f9f8 100644 --- a/baton/logicmonitor.mdx +++ b/baton/logicmonitor.mdx @@ -1,13 +1,13 @@ --- title: "Set up a LogicMonitor connector" og:title: "Set up a LogicMonitor connector" -description: "C1 provides identity governance for LogicMonitor. Integrate your LogicMonitor instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for LogicMonitor. Integrate your LogicMonitor instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for LogicMonitor. Integrate your LogicMonitor instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for LogicMonitor. Integrate your LogicMonitor instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "LogicMonitor" --- -C1 provides identity governance for LogicMonitor. Integrate your LogicMonitor -instance with C1 for unified visibility and governance over administrative and +C1.ai provides identity governance for LogicMonitor. Integrate your LogicMonitor +instance with C1.ai for unified visibility and governance over administrative and privileged access. ## Capabilities @@ -49,11 +49,11 @@ so the connector can list administrators and roles. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -98,7 +98,7 @@ so the connector can list administrators and roles. - **Done.** Your LogicMonitor connector is now pulling access data into C1. + **Done.** Your LogicMonitor connector is now pulling access data into C1.ai. @@ -120,6 +120,6 @@ so the connector can list administrators and roles. - **Done.** Your LogicMonitor connector is now pulling access data into C1. + **Done.** Your LogicMonitor connector is now pulling access data into C1.ai. diff --git a/baton/logto.mdx b/baton/logto.mdx index 4dcaad91..155b6578 100644 --- a/baton/logto.mdx +++ b/baton/logto.mdx @@ -1,12 +1,12 @@ --- title: "Set up a Logto connector" og:title: "Set up a Logto connector" -description: "C1 provides identity governance for Logto. Integrate your Logto tenant with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Logto. Integrate your Logto tenant with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Logto. Integrate your Logto tenant with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Logto. Integrate your Logto tenant with C1.ai for unified visibility and governance over user access." sidebarTitle: "Logto" --- -C1 provides identity governance for Logto. Integrate your Logto tenant with C1 +C1.ai provides identity governance for Logto. Integrate your Logto tenant with C1.ai for unified visibility and governance over user access across your organizations. @@ -58,11 +58,11 @@ Management API permission. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -110,7 +110,7 @@ Management API permission. - **Done.** Your Logto connector is now pulling access data into C1. + **Done.** Your Logto connector is now pulling access data into C1.ai. @@ -132,7 +132,7 @@ Management API permission. - **Done.** Your Logto connector is now pulling access data into C1. + **Done.** Your Logto connector is now pulling access data into C1.ai. diff --git a/baton/lokalise.mdx b/baton/lokalise.mdx index 144a51fa..36590430 100644 --- a/baton/lokalise.mdx +++ b/baton/lokalise.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Lokalise connector" og:title: "Set up a Lokalise connector" -description: "C1 provides identity governance for Lokalise. Integrate your Lokalise teams with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Lokalise. Integrate your Lokalise teams with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Lokalise. Integrate your Lokalise teams with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Lokalise. Integrate your Lokalise teams with C1.ai for unified visibility and governance over user access." sidebarTitle: "Lokalise" --- -C1 provides identity governance for Lokalise. Integrate your Lokalise -teams with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Lokalise. Integrate your Lokalise +teams with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -54,11 +54,11 @@ writes. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -106,7 +106,7 @@ writes. - **Done.** Your Lokalise connector is now pulling access data into C1. + **Done.** Your Lokalise connector is now pulling access data into C1.ai. @@ -132,7 +132,7 @@ writes. - **Done.** Your Lokalise connector is now pulling access data into C1. + **Done.** Your Lokalise connector is now pulling access data into C1.ai. diff --git a/baton/looker.mdx b/baton/looker.mdx index 057835a7..dbe7c9c9 100644 --- a/baton/looker.mdx +++ b/baton/looker.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Google Looker connector" og:title: "Set up a Google Looker connector" -description: "C1 provides identity governance for Looker. Integrate your Looker instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Looker. Integrate your Looker instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Looker. Integrate your Looker instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Looker. Integrate your Looker instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Google Looker" --- @@ -47,17 +47,17 @@ See the Looker docs for information on how to acquire credentials: [View the doc To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Looker 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Looker** and click **Add**. @@ -90,23 +90,23 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Looker connector is now pulling access data into C1. +**Done.** Your Looker connector is now pulling access data into C1.ai. **Follow these instructions to use the Looker 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources -[Contact C1's support team](mailto:support@c1.ai) to download the latest version of the connector. +[Contact C1.ai's support team](mailto:support@c1.ai) to download the latest version of the connector. ### Step 1: Set up a new Looker connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -202,14 +202,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 C1.ai 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 Looker connector to. Looker data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Looker connector to. Looker data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Looker connector is now pulling access data into C1. +**Done.** Your Looker connector is now pulling access data into C1.ai. diff --git a/baton/lucidchart.mdx b/baton/lucidchart.mdx index 31bfbb1a..168af6ce 100644 --- a/baton/lucidchart.mdx +++ b/baton/lucidchart.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Lucidchart connector" og:title: "Set up a Lucidchart connector" -description: "C1 provides identity governance and just-in-time provisioning for Lucidchart. Integrate your Lucidchart 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 Lucidchart. Integrate your Lucidchart instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Lucidchart. Integrate your Lucidchart instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Lucidchart. Integrate your Lucidchart instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Lucidchart" --- @@ -18,7 +18,7 @@ The Lucidchart connector supports [automatic account provisioning](/product/admi *Account provisioning is only available on Lucidchart accounts with Enterprise licenses. -When a new account is created by C1, the account's password will be sent to a [vault](/product/admin/vaults). +When a new account is created by C1.ai, the account's password will be sent to a [vault](/product/admin/vaults). This connector does not support account deprovisioning. You must deprovision accounts directly in Lucidchart. @@ -40,14 +40,14 @@ In the Lucidchart developer portal, navigate to **API Keys**. Click **+ Create API Key**. -Give the new key a name, such as "C1" and set an expiration, if desired. +Give the new key a name, such as "C1.ai" and set an expiration, if desired. Give the key the relevant set of grants: - - **To give C1 sync-only (READ) access:** `Documents - View` and `Folders - View` + - **To give C1.ai sync-only (READ) access:** `Documents - View` and `Folders - View` - - **To give C1 provisioning (READ/WRITE) access:** `Documents - Edit` and `Folders - Edit` + - **To give C1.ai provisioning (READ/WRITE) access:** `Documents - Edit` and `Folders - Edit` Click **Generate API key**. The new key is created. @@ -70,7 +70,7 @@ Give the new app a name, then click **Create**. Select the new app's **OAuth 2.0** tab. -Enter whichever redirect URI matches your C1 tenant's domain in the **Redirect URI** field: +Enter whichever redirect URI matches your C1.ai tenant's domain in the **Redirect URI** field: - Default instance: `https://accounts.conductor.one/oauth/callback` - EU data residency instance: `https://accounts.c1eu.ai/oauth/callback` @@ -108,17 +108,17 @@ Carefully copy and save the **refresh token** included in the token response. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Lucidchart 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Lucidchart** and click **Add**. @@ -158,23 +158,23 @@ Click **Save**. Click **Login with OAuth**. -Log into Lucidchart and authorize C1. +Log into Lucidchart and authorize C1.ai. -After authorizing, you'll be redirected back to the C1 integrations page, where an "Authorized as" message is now printed. +After authorizing, you'll be redirected back to the C1.ai integrations page, where an "Authorized as" message is now printed. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Lucidchart connector is now pulling access data into C1. +**Done.** Your Lucidchart connector is now pulling access data into C1.ai. **Follow these instructions to use the Lucidchart 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -184,7 +184,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -283,14 +283,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 C1.ai 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 Lucidchart connector to. Lucidchart data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Lucidchart connector to. Lucidchart data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Lucidchart connector is now pulling access data into C1. +**Done.** Your Lucidchart connector is now pulling access data into C1.ai. diff --git a/baton/mailchimp.mdx b/baton/mailchimp.mdx index c8ef7511..48ddd5d1 100644 --- a/baton/mailchimp.mdx +++ b/baton/mailchimp.mdx @@ -1,15 +1,15 @@ --- title: "Set up a Mailchimp connector" og:title: "Set up a Mailchimp connector" -description: "C1 provides identity governance for Mailchimp. Integrate your Mailchimp account with C1 for unified visibility and governance over who owns the connection." -og:description: "C1 provides identity governance for Mailchimp. Integrate your Mailchimp account with C1 for unified visibility and governance over who owns the connection." +description: "C1.ai provides identity governance for Mailchimp. Integrate your Mailchimp account with C1.ai for unified visibility and governance over who owns the connection." +og:description: "C1.ai provides identity governance for Mailchimp. Integrate your Mailchimp account with C1.ai for unified visibility and governance over who owns the connection." sidebarTitle: "Mailchimp" --- {/* stargate: cf-mailchimp-20260605 */} -C1 provides identity governance for Mailchimp. Integrate your Mailchimp account -with C1 for unified visibility and governance over the account behind the +C1.ai provides identity governance for Mailchimp. Integrate your Mailchimp account +with C1.ai for unified visibility and governance over the account behind the connection. ## Capabilities @@ -66,11 +66,11 @@ a suffix after a hyphen (for example `...-us19`). - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -115,7 +115,7 @@ a suffix after a hyphen (for example `...-us19`). - **Done.** Your Mailchimp connector is now pulling access data into C1. + **Done.** Your Mailchimp connector is now pulling access data into C1.ai. @@ -139,6 +139,6 @@ a suffix after a hyphen (for example `...-us19`). - **Done.** Your Mailchimp connector is now pulling access data into C1. + **Done.** Your Mailchimp connector is now pulling access data into C1.ai. diff --git a/baton/manage-connector.mdx b/baton/manage-connector.mdx index 21dcc9c1..4a073bbe 100644 --- a/baton/manage-connector.mdx +++ b/baton/manage-connector.mdx @@ -9,12 +9,12 @@ og:description: "Rename a connector or change connector owners." **Important** -This task requires the **Super Administrator** or **Connector Administrator** role in C1. +This task requires the **Super Administrator** or **Connector Administrator** role in C1.ai. ## Rename a connector -You can rename a connector to make it easier to identify in your C1 instance. +You can rename a connector to make it easier to identify in your C1.ai instance. @@ -50,7 +50,7 @@ Connector owners are responsible for managing and maintaining the connector. You On the connector's details page, find the **Details** section and click **Edit**. - Select one or more users from the list of C1 users. + Select one or more users from the list of C1.ai users. Click **Save**. diff --git a/baton/matomo.mdx b/baton/matomo.mdx index ca72a202..2dd40a3c 100644 --- a/baton/matomo.mdx +++ b/baton/matomo.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Matomo connector" og:title: "Set up a Matomo connector" -description: "C1 provides identity governance for Matomo. Integrate your Matomo instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Matomo. Integrate your Matomo instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Matomo. Integrate your Matomo instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Matomo. Integrate your Matomo instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Matomo" --- -C1 provides identity governance for Matomo. Integrate your Matomo -instance with C1 for unified visibility and governance over which users +C1.ai provides identity governance for Matomo. Integrate your Matomo +instance with C1.ai for unified visibility and governance over which users hold which level of access to each of your Matomo sites. ## Capabilities @@ -55,11 +55,11 @@ incomplete access graph. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -104,7 +104,7 @@ incomplete access graph. - **Done.** Your Matomo connector is now pulling access data into C1. + **Done.** Your Matomo connector is now pulling access data into C1.ai. @@ -128,6 +128,6 @@ incomplete access graph. - **Done.** Your Matomo connector is now pulling access data into C1. + **Done.** Your Matomo connector is now pulling access data into C1.ai. diff --git a/baton/mattermost.mdx b/baton/mattermost.mdx index 57bbfeca..93111c08 100644 --- a/baton/mattermost.mdx +++ b/baton/mattermost.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Mattermost connector" og:title: "Set up a Mattermost connector" -description: "C1 provides identity governance for Mattermost. Integrate your Mattermost instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Mattermost. Integrate your Mattermost instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Mattermost. Integrate your Mattermost instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Mattermost. Integrate your Mattermost instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Mattermost" --- -C1 provides identity governance for Mattermost. Integrate your Mattermost -instance with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Mattermost. Integrate your Mattermost +instance with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -75,11 +75,11 @@ when the token is not a System Admin. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -124,7 +124,7 @@ when the token is not a System Admin. - **Done.** Your Mattermost connector is now pulling access data into C1. + **Done.** Your Mattermost connector is now pulling access data into C1.ai. @@ -133,7 +133,7 @@ when the token is not a System Admin. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -151,7 +151,7 @@ when the token is not a System Admin. - Configure C1 credentials and Mattermost credentials as environment + Configure C1.ai credentials and Mattermost credentials as environment variables: ```bash @@ -168,6 +168,6 @@ when the token is not a System Admin. - **Done.** Your Mattermost connector is now pulling access data into C1. + **Done.** Your Mattermost connector is now pulling access data into C1.ai. diff --git a/baton/metabase.mdx b/baton/metabase.mdx index fe8b6b40..371c89f1 100644 --- a/baton/metabase.mdx +++ b/baton/metabase.mdx @@ -1,8 +1,8 @@ --- title: "Set up Metabase connector" og:title: "Set up Metabase connector" -description: "C1 provides identity governance and just-in-time provisioning for Metabase. Integrate your Metabase 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 Metabase. Integrate your Metabase instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Metabase. Integrate your Metabase instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Metabase. Integrate your Metabase instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Metabase" --- @@ -35,13 +35,13 @@ See the docs below for details on the capabilities of each version and instructi The Metabase connector supports [automatic account provisioning](/product/admin/account-provisioning). -When a new account is created by C1, the account's password will be sent to a [vault](/product/admin/vaults). +When a new account is created by C1.ai, the account's password will be sent to a [vault](/product/admin/vaults). The Metabase connector cannot fully deprovision accounts, but it can enable and disable existing accounts. #### 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 C1.ai 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 | |-------------|-------------------|-------------| @@ -58,13 +58,13 @@ Connector actions are custom capabilities that extend C1 automations with app-sp The Metabase v0.49 connector supports [automatic account provisioning](/product/admin/account-provisioning). -When a new account is created by C1, the account's password will be sent to a [vault](/product/admin/vaults). +When a new account is created by C1.ai, the account's password will be sent to a [vault](/product/admin/vaults). The Metabase v0.49 connector cannot fully deprovision accounts, but it can enable and disable existing accounts. #### 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 C1.ai 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 | |-------------|-------------------|-------------| @@ -81,13 +81,13 @@ Connector actions are custom capabilities that extend C1 automations with app-sp The Metabase v0.56 connector supports [automatic account provisioning](/product/admin/account-provisioning). -When a new account is created by C1, the account's password will be sent to a [vault](/product/admin/vaults). +When a new account is created by C1.ai, the account's password will be sent to a [vault](/product/admin/vaults). The Metabase v0.56 connector cannot fully deprovision accounts, but it can enable and disable existing accounts. #### 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 C1.ai 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 | |-------------|-------------------|-------------| @@ -118,17 +118,17 @@ This connector requires the following scopes: To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Metabase 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. As relevant, search for **Metabase**, **Metabase v0.49** or **Metabase v0.56** and click **Add**. @@ -161,13 +161,13 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Metabase connector is now pulling access data into C1. +**Done.** Your Metabase connector is now pulling access data into C1.ai. **Follow these instructions to use the Metabase 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -177,7 +177,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -391,13 +391,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 C1.ai 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 metabase connector to. metabase data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the metabase connector to. metabase data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Metabase connector is now pulling access data into C1. +**Done.** Your Metabase connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/microsoft-dynamic-365-business-central.mdx b/baton/microsoft-dynamic-365-business-central.mdx index ccfecb3d..4f4c1b38 100644 --- a/baton/microsoft-dynamic-365-business-central.mdx +++ b/baton/microsoft-dynamic-365-business-central.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Microsoft Dynamics 365 Business Central connector" og:title: "Set up a Microsoft Dynamics 365 Business Central connector" -description: "C1 provides identity governance for Microsoft Dynamics 365 Business Central. Integrate your Business Central environment with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Microsoft Dynamics 365 Business Central. Integrate your Business Central environment with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Microsoft Dynamics 365 Business Central. Integrate your Business Central environment with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Microsoft Dynamics 365 Business Central. Integrate your Business Central environment with C1.ai for unified visibility and governance over user access." sidebarTitle: "Microsoft Dynamics 365 Business Central" --- -C1 provides identity governance for Microsoft Dynamics 365 Business Central. Integrate your Business -Central environment with C1 for unified visibility and governance over who can access Business Central +C1.ai provides identity governance for Microsoft Dynamics 365 Business Central. Integrate your Business +Central environment with C1.ai for unified visibility and governance over who can access Business Central and which permission sets they hold. ## Capabilities @@ -75,11 +75,11 @@ Business Central API permissions. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -128,7 +128,7 @@ Business Central API permissions. - **Done.** Your Microsoft Dynamics 365 Business Central connector is now pulling access data into C1. + **Done.** Your Microsoft Dynamics 365 Business Central connector is now pulling access data into C1.ai. @@ -155,6 +155,6 @@ Business Central API permissions. - **Done.** Your Microsoft Dynamics 365 Business Central connector is now pulling access data into C1. + **Done.** Your Microsoft Dynamics 365 Business Central connector is now pulling access data into C1.ai. diff --git a/baton/microsoft-dynamics-fo.mdx b/baton/microsoft-dynamics-fo.mdx index 7327d39b..f5508fb2 100644 --- a/baton/microsoft-dynamics-fo.mdx +++ b/baton/microsoft-dynamics-fo.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Microsoft Dynamics 365 - Finance & Operations connector" og:title: "Set up a Microsoft Dynamics 365 - Finance & Operations connector" -description: "C1 provides identity governance and just-in-time provisioning for Microsoft Dynamics 365 - Finance & Operations. Integrate your Microsoft Dynamics 365 - Finance & Operations 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 Microsoft Dynamics 365 - Finance & Operations. Integrate your Microsoft Dynamics 365 - Finance & Operations instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Microsoft Dynamics 365 - Finance & Operations. Integrate your Microsoft Dynamics 365 - Finance & Operations instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Microsoft Dynamics 365 - Finance & Operations. Integrate your Microsoft Dynamics 365 - Finance & Operations instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Microsoft Dynamics 365 - Finance & Operations" --- @@ -25,7 +25,7 @@ This connector does not support full account deprovisioning. You can disable 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 C1.ai 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 | |-------------|-------------------|-------------| @@ -49,7 +49,7 @@ Log into the [Power Platform Admin Center](https://admin.powerplatform.microsoft On the left side of the screen, click **Manage** > **Environments**. -Click the name of the environment you want to integrate with C1. +Click the name of the environment you want to integrate with C1.ai. On the environment's details page, carefully copy and save the URL of the environment. @@ -64,7 +64,7 @@ In the Entra ID admin center, navigate to **App registrations**. Click **+ New registration**. -Give the application a name, such as "C1", and select the supported account type relevant to your Entra installation (typically **Accounts in this organizational directory only (Default Directory only - Single tenant)**). You do not need to set a redirect URL. +Give the application a name, such as "C1.ai", and select the supported account type relevant to your Entra installation (typically **Accounts in this organizational directory only (Default Directory only - Single tenant)**). You do not need to set a redirect URL. Click **Register**. @@ -131,7 +131,7 @@ Add a new register to the table, filling in: - The app's client ID - Your user ID - - A name that identifies this entry, such as "C1 integration" + - A name that identifies this entry, such as "C1.ai integration" Click **OK**. @@ -144,16 +144,16 @@ Click **OK**. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Microsoft Dynamics 365 - Finance & Operations 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Microsoft Dynamics 365 - Finance & Operations** and click **Add**. @@ -179,7 +179,7 @@ Find the **Settings** area of the page and click **Edit**. Enter the Microsoft Dynamics 365 - Finance & Operations credentials into the relevant fields. -**Optional.** If desired, click to enable **Sync only enabled role assignments**. When this option is enabled, C1 will ignore all roles that do not have the `enabled` status. +**Optional.** If desired, click to enable **Sync only enabled role assignments**. When this option is enabled, C1.ai will ignore all roles that do not have the `enabled` status. Click **Save**. @@ -188,22 +188,22 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Microsoft Dynamics 365 - Finance & Operations connector is now pulling access data into C1. +**Done.** Your Microsoft Dynamics 365 - Finance & Operations connector is now pulling access data into C1.ai. **Follow these instructions to use the Microsoft Dynamics 365 - Finance & Operations 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources -[Contact C1's support team](mailto:support@c1.ai) to download the latest version of the connector. +[Contact C1.ai's support team](mailto:support@c1.ai) to download the latest version of the connector. ### Step 1: Set up a new Microsoft Dynamics 365 - Finance & Operations connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -300,13 +300,13 @@ spec: ### 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. +Create a namespace in which to run C1.ai 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 Microsoft Dynamics 365 - Finance & Operations connector to. Microsoft Dynamics 365 - Finance & Operations data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Microsoft Dynamics 365 - Finance & Operations connector to. Microsoft Dynamics 365 - Finance & Operations data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Microsoft Dynamics 365 - Finance & Operations connector is now pulling access data into C1. +**Done.** Your Microsoft Dynamics 365 - Finance & Operations connector is now pulling access data into C1.ai. diff --git a/baton/microsoft-dynamics.mdx b/baton/microsoft-dynamics.mdx index d9b1d51b..08b54c11 100644 --- a/baton/microsoft-dynamics.mdx +++ b/baton/microsoft-dynamics.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Microsoft Dynamics 365 connector" og:title: "Set up a Microsoft Dynamics 365 connector" -description: "C1 provides identity governance and just-in-time provisioning for Microsoft Dynamics 365. Integrate your Microsoft Dynamics 365 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 Microsoft Dynamics 365. Integrate your Microsoft Dynamics 365 instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Microsoft Dynamics 365. Integrate your Microsoft Dynamics 365 instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Microsoft Dynamics 365. Integrate your Microsoft Dynamics 365 instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Microsoft Dynamics 365" --- @@ -34,7 +34,7 @@ Log into the [Power Platform Admin Center](https://admin.powerplatform.microsoft On the left side of the screen, click **Manage** > **Environments**. -Click the name of the environment you want to integrate with C1. +Click the name of the environment you want to integrate with C1.ai. On the environment's details page, carefully copy and save the URL of the environment. @@ -51,7 +51,7 @@ In the Entra ID admin center, navigate to **App registrations**. Click **+ New registration**. -Give the application a name, such as "C1", and select the supported account type relevant to your Entra installation (typically **Accounts in this organizational directory only (Default Directory only - Single tenant)**). You do not need to set a redirect URL. +Give the application a name, such as "C1.ai", and select the supported account type relevant to your Entra installation (typically **Accounts in this organizational directory only (Default Directory only - Single tenant)**). You do not need to set a redirect URL. Click **Register**. @@ -214,17 +214,17 @@ Click **OK**. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Microsoft Dynamics 365 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Microsoft Dynamics 365** and click **Add**. @@ -260,23 +260,23 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Microsoft Dynamics 365 connector is now pulling access data into C1. +**Done.** Your Microsoft Dynamics 365 connector is now pulling access data into C1.ai. **Follow these instructions to use the Microsoft Dynamics 365 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources -[Contact C1's support team](mailto:support@c1.ai) to download the latest version of the connector. +[Contact C1.ai's support team](mailto:support@c1.ai) to download the latest version of the connector. ### Step 1: Set up a new Microsoft Dynamics 365 connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -374,14 +374,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 C1.ai 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 Microsoft Dynamics 365 connector to. Microsoft Dynamics 365 data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Microsoft Dynamics 365 connector to. Microsoft Dynamics 365 data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Microsoft Dynamics 365 connector is now pulling access data into C1. +**Done.** Your Microsoft Dynamics 365 connector is now pulling access data into C1.ai. diff --git a/baton/microsoft-entra.mdx b/baton/microsoft-entra.mdx index 9dbd99bf..4b6fba21 100644 --- a/baton/microsoft-entra.mdx +++ b/baton/microsoft-entra.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Microsoft Entra ID connector" og:title: "Set up a Microsoft Entra ID connector" -og:description: "C1 provides identity governance and just-in-time provisioning for Entra ID. Integrate your Entra ID instance with C1 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 Entra ID. Integrate your Entra ID instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Entra ID. Integrate your Entra ID instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for Entra ID. Integrate your Entra ID instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "Microsoft Entra ID" --- -This page covers the Entra ID **connector**, which syncs and provisions access data for identity governance. It does not control how you sign in to C1. To set up signing in to C1 with your Entra ID account, see [Authenticate with Microsoft](/product/how-to/qs-set-up-c1#authenticate-with-microsoft). +This page covers the Entra ID **connector**, which syncs and provisions access data for identity governance. It does not control how you sign in to C1.ai. To set up signing in to C1.ai with your Entra ID account, see [Authenticate with Microsoft](/product/how-to/qs-set-up-c1#authenticate-with-microsoft). ## Capabilities @@ -24,7 +24,7 @@ This page covers the Entra ID **connector**, which syncs and provisions access d The Entra ID connector supports [automatic account provisioning and deprovisioning](/product/admin/account-provisioning). -When a new account is created by C1, the account's password will be sent to a [vault](/product/admin/vaults). +When a new account is created by C1.ai, the account's password will be sent to a [vault](/product/admin/vaults). #### Account creation fields @@ -59,7 +59,7 @@ The `additionalAttributes` field accepts a JSON string containing any writable [ ### 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 C1.ai 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 | |-------------|-------------------|-------------| @@ -94,7 +94,7 @@ In Entra admin center, navigate to **App registrations**. Click **+ New registration**. -Give the application a name, such as "C1", and select the supported account type relevant to your Entra installation. You do not need to set a redirect URL. +Give the application a name, such as "C1.ai", and select the supported account type relevant to your Entra installation. You do not need to set a redirect URL. Click **Register**. @@ -262,7 +262,7 @@ On the **Settings** tab, select **Active** as the **Assignment type**. Check **Permanently assigned** and add a justification, such as: - Required to allow the C1 connector to grant and revoke memberships for managed distribution lists and mail-enabled security groups, both managed by Exchange. + Required to allow the C1.ai connector to grant and revoke memberships for managed distribution lists and mail-enabled security groups, both managed by Exchange. Click **Assign**. @@ -275,16 +275,16 @@ Click **Assign**. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Entra ID 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Entra ID** and click **Add**. @@ -333,7 +333,7 @@ Paste the client secret into the **Entra client secret** field. The usage data feature requires a Microsoft Entra ID P1 or P2 license. Usage data collection is not supported on Microsoft Entra ID Free licenses. -**Optional.** Click to opt into **Schedule SCIM provisioning**, which forces an Entra SCIM sync when a new entitlement is provisioned for a user in C1. +**Optional.** Click to opt into **Schedule SCIM provisioning**, which forces an Entra SCIM sync when a new entitlement is provisioned for a user in C1.ai. **Optional.** Click to **Disable resource changed event feed**. These logs are enabled by default. @@ -346,7 +346,7 @@ Paste the client secret into the **Entra client secret** field. **Optional.** Click to enable **Skip enterprise applications without assignments** to exclude enterprise applications that have no app role assignments from the sync. This can substantially reduce sync output in tenants that have accumulated many auto-registered service principals. - Toggling this setting on an existing connection will cause C1 to add or remove previously-synced enterprise applications and their associated entitlements and grants on the next sync to reflect the new filter. + Toggling this setting on an existing connection will cause C1.ai to add or remove previously-synced enterprise applications and their associated entitlements and grants on the next sync to reflect the new filter. Click **Save**. @@ -355,16 +355,16 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Entra ID connector is now pulling access data into C1. +**Done.** Your Entra ID connector is now pulling access data into C1.ai. -**Follow these instructions to use a built-in, no-code connector hosted by C1 using certificate-based authentication.** +**Follow these instructions to use a built-in, no-code connector hosted by C1.ai using certificate-based authentication.** Certificate-based authentication is recommended for FedRAMP and other high-compliance environments where OAuth and client secrets are not permitted. -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Entra ID** and click **Add**. @@ -416,7 +416,7 @@ Upload your PEM-encoded private key file (.pem or .key) in the **Client Certific The usage data feature requires a Microsoft Entra ID P1 or P2 license. Usage data collection is not supported on Microsoft Entra ID Free licenses. -**Optional.** Click to opt into **Schedule SCIM provisioning**, which forces an Entra SCIM sync when a new entitlement is provisioned for a user in C1. +**Optional.** Click to opt into **Schedule SCIM provisioning**, which forces an Entra SCIM sync when a new entitlement is provisioned for a user in C1.ai. **Optional.** Click to **Disable resource changed event feed**. These logs are enabled by default. @@ -429,7 +429,7 @@ Upload your PEM-encoded private key file (.pem or .key) in the **Client Certific **Optional.** Click to enable **Skip enterprise applications without assignments** to exclude enterprise applications that have no app role assignments from the sync. This can substantially reduce sync output in tenants that have accumulated many auto-registered service principals. - Toggling this setting on an existing connection will cause C1 to add or remove previously-synced enterprise applications and their associated entitlements and grants on the next sync to reflect the new filter. + Toggling this setting on an existing connection will cause C1.ai to add or remove previously-synced enterprise applications and their associated entitlements and grants on the next sync to reflect the new filter. Click **Save**. @@ -438,16 +438,16 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Entra ID connector is now pulling access data into C1. +**Done.** Your Entra ID connector is now pulling access data into C1.ai. -**Follow these instructions to set up a built-in, no-code connector hosted by C1 using OAuth.** +**Follow these instructions to set up a built-in, no-code connector hosted by C1.ai using OAuth.** ### Step 1: Log in with OAuth -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Entra ID** and click **Add**. @@ -490,7 +490,7 @@ Specify the ID of the Entra tenant you're integrating in the **Entra tenant ID** The usage data feature requires a Microsoft Entra ID P1 or P2 license. Usage data collection is not supported on Microsoft Entra ID Free licenses. -**Optional.** Click to opt into **Schedule SCIM provisioning**, which forces an Entra SCIM sync when a new entitlement is provisioned for a user in C1. +**Optional.** Click to opt into **Schedule SCIM provisioning**, which forces an Entra SCIM sync when a new entitlement is provisioned for a user in C1.ai. **Optional.** Click to **Disable resource changed event feed**. These logs are enabled by default. @@ -503,28 +503,28 @@ Specify the ID of the Entra tenant you're integrating in the **Entra tenant ID** **Optional.** Click to enable **Skip enterprise applications without assignments** to exclude enterprise applications that have no app role assignments from the sync. This can substantially reduce sync output in tenants that have accumulated many auto-registered service principals. - Toggling this setting on an existing connection will cause C1 to add or remove previously-synced enterprise applications and their associated entitlements and grants on the next sync to reflect the new filter. + Toggling this setting on an existing connection will cause C1.ai to add or remove previously-synced enterprise applications and their associated entitlements and grants on the next sync to reflect the new filter. Click **Login with OAuth**. -Log in and authorize C1 with your Entra ID instance. +Log in and authorize C1.ai with your Entra ID instance. In order for the integration to work properly, you must consent to all permissions. -### Step 2: Grant permissions to the C1 app +### Step 2: Grant permissions to the C1.ai app In the Entra ID control panel, navigate to **Enterprise Applications**. -Click the **C1 Integration** app (not to be confused with the **C1 SSO** app, which is used to log into C1, not to synchronize your data). +Click the **C1 Integration** app (not to be confused with the **C1 SSO** app, which is used to log into C1.ai, not to synchronize your data). - If the C1 Integration app doesn't appear in the list of apps right away, wait a minute and click **Refresh**. + If the C1.ai Integration app doesn't appear in the list of apps right away, wait a minute and click **Refresh**. On the **C1 Integration** page, click **Permissions**. @@ -538,23 +538,23 @@ Click **Grant admin consent for ...** on the **C1 Integration** app permissions -Return to the Entra ID integration in C1 by clicking the **Entra ID** tile on the **Integrations** page. +Return to the Entra ID integration in C1.ai by clicking the **Entra ID** tile on the **Integrations** page. Click the **Entra ID** connector link that shows today's date in the **Connected on** column. -Click **Login with OAuth** a second time to complete the process and authorize C1 to obtain an access token with the permissions you've just granted. +Click **Login with OAuth** a second time to complete the process and authorize C1.ai to obtain an access token with the permissions you've just granted. -**Done.** Your Entra ID connector is now pulling access data into C1. +**Done.** Your Entra ID connector is now pulling access data into C1.ai. **Follow these instructions to use the Entra ID 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -563,7 +563,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an ### Step 1: Set up a new Entra ID connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -681,13 +681,13 @@ spec: ### 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. +Create a namespace in which to run C1.ai 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 Entra ID connector to. Entra ID data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Entra ID connector to. Entra ID data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Entra ID connector is now pulling access data into C1. +**Done.** Your Entra ID connector is now pulling access data into C1.ai. @@ -701,7 +701,7 @@ When enabled, the connector excludes groups that originate from on-premises Acti By default, this also filters out on-premises synced users from the membership lists of cloud groups. This means that if a cloud group contains both cloud-native and on-premises synced users, only the cloud-native members will appear as grants. -All users (both cloud-native and on-premises synced) are always synced to C1 regardless of this setting. This setting only affects groups and group memberships. +All users (both cloud-native and on-premises synced) are always synced to C1.ai regardless of this setting. This setting only affects groups and group memberships. ### Include on-premises users in cloud group memberships (`--include-on-prem-group-members` / `BATON_INCLUDE_ON_PREM_GROUP_MEMBERS`) @@ -718,7 +718,7 @@ This setting has no effect unless **Skip Active Directory Server groups** is als ### What's next? -If Entra ID 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 Entra ID 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.ai 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. diff --git a/baton/microsoft-intune.mdx b/baton/microsoft-intune.mdx index 75a03d56..6b8bf5f0 100644 --- a/baton/microsoft-intune.mdx +++ b/baton/microsoft-intune.mdx @@ -1,12 +1,12 @@ --- title: "Set up a Microsoft Intune connector" og:title: "Set up a Microsoft Intune connector" -description: "C1 provides identity governance for Microsoft Intune. Integrate your Microsoft Intune instance with C1 for unified visibility and governance over device and access data." -og:description: "C1 provides identity governance for Microsoft Intune. Integrate your Microsoft Intune instance with C1 for unified visibility and governance over device and access data." +description: "C1.ai provides identity governance for Microsoft Intune. Integrate your Microsoft Intune instance with C1.ai for unified visibility and governance over device and access data." +og:description: "C1.ai provides identity governance for Microsoft Intune. Integrate your Microsoft Intune instance with C1.ai for unified visibility and governance over device and access data." sidebarTitle: "Microsoft Intune" --- -C1 provides identity governance for Microsoft Intune. Integrate your Microsoft Intune instance with C1 for unified visibility and governance over managed devices and Intune role-based access. +C1.ai provides identity governance for Microsoft Intune. Integrate your Microsoft Intune instance with C1.ai for unified visibility and governance over managed devices and Intune role-based access. ## Capabilities @@ -20,7 +20,7 @@ C1 provides identity governance for Microsoft Intune. Integrate your Microsoft I The connector reads Intune-native objects through the Microsoft Graph device management API: managed devices (with their hardware, operating system, compliance, and management-state details), RBAC role definitions, scope tags, compliance policies, and configuration profiles. Each managed device is linked to its primary user, and roles, compliance policies, and configuration profiles are linked to the security groups they are assigned to. -Microsoft Intune does not own the identity directory. The users and groups that Intune references live in Microsoft Entra ID and are supplied by a separate Microsoft Entra connector. Add that connector so C1 can resolve device owners and assignment groups to the people and groups behind them. +Microsoft Intune does not own the identity directory. The users and groups that Intune references live in Microsoft Entra ID and are supplied by a separate Microsoft Entra connector. Add that connector so C1.ai can resolve device owners and assignment groups to the people and groups behind them. ## Prerequisites @@ -30,7 +30,7 @@ The connector uses application-only (client credentials) access to Microsoft Gra - In the Microsoft Entra admin center, register a new **application** dedicated to C1 (or reuse an existing one). + In the Microsoft Entra admin center, register a new **application** dedicated to C1.ai (or reuse an existing one). @@ -70,11 +70,11 @@ The connector uses application-only (client credentials) access to Microsoft Gra - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -122,7 +122,7 @@ The connector uses application-only (client credentials) access to Microsoft Gra - **Done.** Your Microsoft Intune connector is now pulling device and access data into C1. + **Done.** Your Microsoft Intune connector is now pulling device and access data into C1.ai. @@ -149,6 +149,6 @@ The connector uses application-only (client credentials) access to Microsoft Gra - **Done.** Your Microsoft Intune connector is now pulling device and access data into C1. + **Done.** Your Microsoft Intune connector is now pulling device and access data into C1.ai. diff --git a/baton/migration.mdx b/baton/migration.mdx index e64fd27d..4f999665 100644 --- a/baton/migration.mdx +++ b/baton/migration.mdx @@ -8,7 +8,7 @@ og:description: "Periodically we release a new version of a connector in order t ## Why are some connectors marked v2? -We’ve learned a lot since we started building connectors! One key advancement was the creation of the Baton framework for connector development, which C1 launched in December 2022. +We’ve learned a lot since we started building connectors! One key advancement was the creation of the Baton framework for connector development, which C1.ai launched in December 2022. Since then, we’ve rolled out updated versions of some connectors that were written pre-Baton in order to modernize the connectors’ architecture, improve their performance, and enable new capabilities. (See the table below for an overview of new capabilities in v2 connectors.) @@ -25,7 +25,7 @@ If we decide in the future to retire a v1 connector entirely, we’ll be in touc ## Migrate from a v1 to a v2 connector -**Important: Migrating from a v1 to a v2 connector replaces internal identifiers.** When you set up a v2 connector — whether in a new app or the same app as the v1 connector — C1 generates new app user IDs and entitlement IDs. Any existing tasks, access reviews, access review templates, or access profiles that reference the old v1 app’s users or entitlements will no longer resolve to the correct resources. Plan accordingly and review your tasks and access profiles after completing the migration. +**Important: Migrating from a v1 to a v2 connector replaces internal identifiers.** When you set up a v2 connector — whether in a new app or the same app as the v1 connector — C1.ai generates new app user IDs and entitlement IDs. Any existing tasks, access reviews, access review templates, or access profiles that reference the old v1 app’s users or entitlements will no longer resolve to the correct resources. Plan accordingly and review your tasks and access profiles after completing the migration. The basic process for migration is as follows (see the special note below about migrating IdP connectors): @@ -35,7 +35,7 @@ The basic process for migration is as follows (see the special note below about Leave the v1 connector running as-is. - Set up the v2 connector in a new C1 app. + Set up the v2 connector in a new C1.ai app. When you set up the v2 connector, select the **Create a new app** option. @@ -50,7 +50,7 @@ The basic process for migration is as follows (see the special note below about **This is a rip-and-replace process, not an in-place migration.** Because you are creating a new app for the v2 connector, app user IDs and entitlement IDs will change. Any existing tasks or access profiles that reference IDs from the v1 app will break and need to be reconfigured for the new v2 app. -Depending on the complexity of the connected software and how you’ve set it up in C1, this process might be quite simple, or a bit more complex. Our Customer Success team is always ready to talk through the process with you and provide advice and support. +Depending on the complexity of the connected software and how you’ve set it up in C1.ai, this process might be quite simple, or a bit more complex. Our Customer Success team is always ready to talk through the process with you and provide advice and support. **Thinking of migrating an IdP connector?** diff --git a/baton/miro.mdx b/baton/miro.mdx index 12d36b66..b1928466 100644 --- a/baton/miro.mdx +++ b/baton/miro.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Miro connector" og:title: "Set up a Miro connector" -description: "C1 provides identity governance and just-in-time provisioning for Miro. Integrate your Miro 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 Miro. Integrate your Miro instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Miro. Integrate your Miro instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Miro. Integrate your Miro instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Miro" --- @@ -39,7 +39,7 @@ Click the **Your apps** tab. Click **Create new app**. -Give the new app a name, such as "C1 integration" and select a developer team. You can leave the **Expire access token** box unchecked. +Give the new app a name, such as "C1.ai integration" and select a developer team. You can leave the **Expire access token** box unchecked. Click **Create app**. @@ -52,7 +52,7 @@ The newly created app's page opens. Scroll down to **Permissions** and select th - organizations:read - organizations:team:read - If you want to use C1 to provision access, also include: + If you want to use C1.ai to provision access, also include: - team:write - organizations:team:write @@ -70,7 +70,7 @@ Your app is installed, and the app's access token is shown. Carefully and copy a ### Optional: Generate a Miro SCIM access token -If you want to use C1 to provision accounts, you'll also need a SCIM access token. If you haven't already enabled SCIM for your Miro Enterprise account, [follow the Miro documentation](https://developers.miro.com/docs/how-to-enable-scim). +If you want to use C1.ai to provision accounts, you'll also need a SCIM access token. If you haven't already enabled SCIM for your Miro Enterprise account, [follow the Miro documentation](https://developers.miro.com/docs/how-to-enable-scim). To generate a new SCIM token: @@ -96,17 +96,17 @@ Carefully copy and save the SCIM 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 C1.ai - Access to the set of Miro 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Miro** and click **Add**. @@ -132,7 +132,7 @@ Find the **Settings** area of the page and click **Edit**. Paste the token into the **Access token** field. -**Optional.** If you want C1 to provision Miro accounts using this connector, paste the SCIM token into the **SCIM access token** field. +**Optional.** If you want C1.ai to provision Miro accounts using this connector, paste the SCIM token into the **SCIM access token** field. Click **Save**. @@ -142,13 +142,13 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Miro connector is now pulling access data into C1. +**Done.** Your Miro connector is now pulling access data into C1.ai. **Follow these instructions to use the Miro 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -160,7 +160,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -256,14 +256,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 C1.ai 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 Miro connector to. Miro data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Miro connector to. Miro data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Miro connector is now pulling access data into C1. +**Done.** Your Miro connector is now pulling access data into C1.ai. diff --git a/baton/mixpanel.mdx b/baton/mixpanel.mdx index 0cd838e6..5ea9229a 100644 --- a/baton/mixpanel.mdx +++ b/baton/mixpanel.mdx @@ -1,15 +1,15 @@ --- title: "Set up a Mixpanel connector" og:title: "Set up a Mixpanel connector" -description: "C1 provides identity governance for Mixpanel. Integrate your Mixpanel project with C1 for unified visibility and governance over who has access to your analytics data." -og:description: "C1 provides identity governance for Mixpanel. Integrate your Mixpanel project with C1 for unified visibility and governance over who has access to your analytics data." +description: "C1.ai provides identity governance for Mixpanel. Integrate your Mixpanel project with C1.ai for unified visibility and governance over who has access to your analytics data." +og:description: "C1.ai provides identity governance for Mixpanel. Integrate your Mixpanel project with C1.ai for unified visibility and governance over who has access to your analytics data." sidebarTitle: "Mixpanel" --- {/* stargate: cf-mixpanel-20260605 */} -C1 provides identity governance for Mixpanel. Integrate your Mixpanel project -with C1 for unified visibility and governance over who has access to your +C1.ai provides identity governance for Mixpanel. Integrate your Mixpanel project +with C1.ai for unified visibility and governance over who has access to your analytics data. ## Capabilities @@ -59,11 +59,11 @@ when the Service Account is created. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -112,7 +112,7 @@ when the Service Account is created. - **Done.** Your Mixpanel connector is now pulling access data into C1. + **Done.** Your Mixpanel connector is now pulling access data into C1.ai. @@ -140,6 +140,6 @@ when the Service Account is created. - **Done.** Your Mixpanel connector is now pulling access data into C1. + **Done.** Your Mixpanel connector is now pulling access data into C1.ai. diff --git a/baton/mode.mdx b/baton/mode.mdx index 434b3c6e..7f7b02ee 100644 --- a/baton/mode.mdx +++ b/baton/mode.mdx @@ -1,8 +1,8 @@ --- title: "Set up Mode connector" og:title: "Set up Mode connector" -description: "C1 provides identity governance for Mode. Integrate your Mode instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Mode. Integrate your Mode instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Mode. Integrate your Mode instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Mode. Integrate your Mode instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Mode" --- @@ -40,17 +40,17 @@ See the Mode docs for information on how to acquire credentials: [View the docum To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Mode configuration information gathered by following the instructions above -**Follow these instructions to use a built-in, no-code connector hosted by C1.** +**Follow these instructions to use a built-in, no-code connector hosted by C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Mode** and click **Add**. @@ -83,23 +83,23 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Mode connector is now pulling access data into C1. +**Done.** Your Mode connector is now pulling access data into C1.ai. **Follow these instructions to use the Mode connector, hosted and run in your own environment.** -When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources -[Contact C1's support team](mailto:support@c1.ai) to download the latest version of the connector. +[Contact C1.ai's support team](mailto:support@c1.ai) to download the latest version of the connector. ### Step 1: Set up a new Mode connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -192,14 +192,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 C1.ai 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 mode connector to. mode data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the mode connector to. mode data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Mode connector is now pulling access data into C1. +**Done.** Your Mode connector is now pulling access data into C1.ai. diff --git a/baton/monday.mdx b/baton/monday.mdx index 9491a805..0af82001 100644 --- a/baton/monday.mdx +++ b/baton/monday.mdx @@ -1,8 +1,8 @@ --- title: "Set up Monday.com connector" og:title: "Set up Monday.com connector" -description: "C1 provides identity governance and just-in-time provisioning for Monday.com. Integrate your Monday.com 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 Monday.com. Integrate your Monday.com instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Monday.com. Integrate your Monday.com instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Monday.com. Integrate your Monday.com instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Monday.com" --- @@ -39,11 +39,11 @@ sidebarTitle: "Monday.com" ### User states and provisioning -Monday.com users keep the same ID from invitation through deactivation. The connector maps each lifecycle state to a C1 account status and blocks unsupported operations with clear errors. +Monday.com users keep the same ID from invitation through deactivation. The connector maps each lifecycle state to a C1.ai account status and blocks unsupported operations with clear errors. -**How users appear in C1 after sync:** +**How users appear in C1.ai after sync:** -| User state | C1 account status | Included in sync | +| User state | C1.ai account status | Included in sync | | :--- | :--- | :--- | | Pending invite (not yet accepted) | Disabled | Yes | | Active member | Enabled | Yes | @@ -97,17 +97,17 @@ See the Monday.com docs for information on how to acquire credentials: [View the To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Monday.com 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Monday.com** and click **Add**. @@ -146,23 +146,23 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Monday.com connector is now pulling access data into C1. +**Done.** Your Monday.com connector is now pulling access data into C1.ai. **Follow these instructions to use the Monday.com 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai 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 C1.ai's support team](mailto:support@conductorone.com) to download the latest version of the connector. ### Step 1: Set up a new Monday.com connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -255,13 +255,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 C1.ai 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 Monday.com connector to. Monday.com data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Monday.com connector to. Monday.com data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Monday.com connector is now pulling access data into C1. +**Done.** Your Monday.com connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/mongodb-atlas.mdx b/baton/mongodb-atlas.mdx index 512831ce..241878de 100644 --- a/baton/mongodb-atlas.mdx +++ b/baton/mongodb-atlas.mdx @@ -1,8 +1,8 @@ --- title: "Set up a MongoDB Atlas connector" og:title: "Set up a MongoDB Atlas connector" -description: "C1 provides identity governance and just-in-time provisioning for MongoDB Atlas. Integrate your MongoDB Atlas 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 MongoDB Atlas. Integrate your MongoDB Atlas instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for MongoDB Atlas. Integrate your MongoDB Atlas instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for MongoDB Atlas. Integrate your MongoDB Atlas instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "MongoDB Atlas" --- @@ -25,7 +25,7 @@ When a new account is created using the default `SCRAM-SHA` authentication type, ## Account provisioning -When C1 provisions a new account through the MongoDB Atlas connector, the connector creates a **database user** in the specified MongoDB Atlas project. By default, the connector also sends an **organization invitation** to the user's email address, granting them access to the MongoDB Atlas console. You can disable this behavior by turning off the **Create invite** setting on the connector. +When C1.ai provisions a new account through the MongoDB Atlas connector, the connector creates a **database user** in the specified MongoDB Atlas project. By default, the connector also sends an **organization invitation** to the user's email address, granting them access to the MongoDB Atlas console. You can disable this behavior by turning off the **Create invite** setting on the connector. ### Provisioning fields @@ -45,7 +45,7 @@ The **Authentication Type** field determines how the provisioned database user a | Authentication type | Description | Username format | | :--- | :--- | :--- | -| `SCRAM-SHA` | Password-based authentication (default). A random password is generated and stored in a C1 [vault](/product/admin/vaults). | Alphanumeric string (special characters such as `@` are not supported; email addresses are invalid) | +| `SCRAM-SHA` | Password-based authentication (default). A random password is generated and stored in a C1.ai [vault](/product/admin/vaults). | Alphanumeric string (special characters such as `@` are not supported; email addresses are invalid) | | `AWS_IAM_USER` | AWS IAM user authentication. | AWS user ARN | | `X509_CUSTOMER` | Customer-managed X.509 certificate authentication. | RFC 2253 Distinguished Name | | `X509_MANAGED` | MongoDB Atlas-managed X.509 certificate authentication. | RFC 2253 Distinguished Name | @@ -53,7 +53,7 @@ The **Authentication Type** field determines how the provisioned database user a | `OIDC_WORKLOAD` | OIDC workload identity authentication. | `/` | -When using `SCRAM-SHA`, the provisioned user retrieves their database password from the C1 [vault](/product/admin/vaults). For all other authentication types, no password is generated. Instead, the database user is created in the `$external` database, and the user authenticates using their external identity provider. +When using `SCRAM-SHA`, the provisioned user retrieves their database password from the C1.ai [vault](/product/admin/vaults). For all other authentication types, no password is generated. Instead, the database user is created in the `$external` database, and the user authenticates using their external identity provider. ### How provisioning works @@ -62,7 +62,7 @@ When account provisioning runs, the connector performs these steps: 1. **Organization invitation** (optional): If **Create invite** is enabled (the default), the connector invites the user to the MongoDB Atlas organization. If the user already exists in the organization, this step is skipped. -2. **Database user creation**: The connector creates a database user in the specified project with the chosen authentication type. The new database user is assigned a default `read` role on the `admin` database. You can grant additional database roles (such as `readWrite` or `dbAdmin`) through C1 entitlements after the account is provisioned. +2. **Database user creation**: The connector creates a database user in the specified project with the chosen authentication type. The new database user is assigned a default `read` role on the `admin` database. You can grant additional database roles (such as `readWrite` or `dbAdmin`) through C1.ai entitlements after the account is provisioned. ## Gather MongoDB Atlas credentials @@ -82,7 +82,7 @@ Navigate to the MongoDB Atlas organization you wish to integrate and click **App Click **Add new** and then select **API Key**. -Give the new API key a description, such as "C1 integration". +Give the new API key a description, such as "C1.ai integration". In the **Organization Permissions** area, select the relevant permissions: @@ -97,14 +97,14 @@ In the **Organization Permissions** area, select the relevant permissions: Click **Next**. -Under **API Access List**, click **Add Access List Entry**. Add the IP addresses listed on the [C1 Baton FAQ page](/baton/faq#which-ip-addresses-does-conductorone-use-for-connectors), then click **Save**. +Under **API Access List**, click **Add Access List Entry**. Add the IP addresses listed on the [C1.ai Baton FAQ page](/baton/faq#which-ip-addresses-does-conductorone-use-for-connectors), then click **Save**. If you're using a self-hosted connector, add the IP address of your connector host instead. -**Optional.** To sync databases and collections, for each project, add the IP addresses listed on the [C1 Baton FAQ page](/baton/faq#which-ip-addresses-does-conductorone-use-for-connectors) to **Database & Network Access** > **IP Access List**. See the **Sync databases** and **Enable Mongo driver** configuration options below. +**Optional.** To sync databases and collections, for each project, add the IP addresses listed on the [C1.ai Baton FAQ page](/baton/faq#which-ip-addresses-does-conductorone-use-for-connectors) to **Database & Network Access** > **IP Access List**. See the **Sync databases** and **Enable Mongo driver** configuration options below. Carefully copy and save the public key and private key. @@ -118,17 +118,17 @@ Carefully copy and save the public key and private key. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of MongoDB Atlas 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **MongoDB Atlas** and click **Add**. @@ -157,7 +157,7 @@ Paste the public key into the **Public key** field. Paste the private key into the **Private key** field. -**Optional.** If desired, click to enable **Create invite**, which will create email invitations for new MongoDB accounts provisioned by C1. +**Optional.** If desired, click to enable **Create invite**, which will create email invitations for new MongoDB accounts provisioned by C1.ai. **Optional.** If desired, click to enable **Sync databases** and **Enable Mongo driver**. The combination of these two settings allows the connector to discover and sync databases and collections from MongoDB Atlas clusters. @@ -173,13 +173,13 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your MongoDB Atlas connector is now pulling access data into C1. +**Done.** Your MongoDB Atlas connector is now pulling access data into C1.ai. **Follow these instructions to use the MongoDB 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -191,7 +191,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -295,14 +295,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 C1.ai 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 MongoDB Atlas connector to. MongoDB Atlas data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the MongoDB Atlas connector to. MongoDB Atlas data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your MongoDB Atlas connector is now pulling access data into C1. +**Done.** Your MongoDB Atlas connector is now pulling access data into C1.ai. diff --git a/baton/mulesoft.mdx b/baton/mulesoft.mdx index 366f3431..3c6dd665 100644 --- a/baton/mulesoft.mdx +++ b/baton/mulesoft.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Mulesoft connector" og:title: "Set up a Mulesoft connector" -description: "C1 provides identity governance for Mulesoft. Integrate your Mulesoft instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Mulesoft. Integrate your Mulesoft instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Mulesoft. Integrate your Mulesoft instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Mulesoft. Integrate your Mulesoft instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Salesforce Mulesoft" --- -C1 provides identity governance for Mulesoft Anypoint Platform. Integrate your -Anypoint organization with C1 for unified visibility and governance over user, +C1.ai provides identity governance for Mulesoft Anypoint Platform. Integrate your +Anypoint organization with C1.ai for unified visibility and governance over user, team, and role group access. ## Capabilities @@ -52,11 +52,11 @@ and read organization members, teams, and role groups in Access Management. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -103,7 +103,7 @@ and read organization members, teams, and role groups in Access Management. - **Done.** Your Mulesoft connector is now pulling access data into C1. + **Done.** Your Mulesoft connector is now pulling access data into C1.ai. @@ -125,6 +125,6 @@ and read organization members, teams, and role groups in Access Management. - **Done.** Your Mulesoft connector is now pulling access data into C1. + **Done.** Your Mulesoft connector is now pulling access data into C1.ai. diff --git a/baton/mural.mdx b/baton/mural.mdx index 3c1c40ee..6c51e241 100644 --- a/baton/mural.mdx +++ b/baton/mural.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Mural connector" og:title: "Set up a Mural connector" -description: "C1 provides identity governance for Mural. Integrate your Mural workspace with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Mural. Integrate your Mural workspace with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Mural. Integrate your Mural workspace with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Mural. Integrate your Mural workspace with C1.ai for unified visibility and governance over user access." sidebarTitle: "Mural" --- -C1 provides identity governance for Mural. Integrate your Mural -workspace with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Mural. Integrate your Mural +workspace with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -50,11 +50,11 @@ the id of the workspace you want to sync. Treat the token as a secret. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -99,7 +99,7 @@ the id of the workspace you want to sync. Treat the token as a secret. - **Done.** Your Mural connector is now pulling access data into C1. + **Done.** Your Mural connector is now pulling access data into C1.ai. @@ -123,6 +123,6 @@ the id of the workspace you want to sync. Treat the token as a secret. - **Done.** Your Mural connector is now pulling access data into C1. + **Done.** Your Mural connector is now pulling access data into C1.ai. diff --git a/baton/mysql.mdx b/baton/mysql.mdx index 2894cc11..aee51369 100644 --- a/baton/mysql.mdx +++ b/baton/mysql.mdx @@ -116,7 +116,7 @@ That's it! You now have the credentials needed to configure the connector. You must have the **Connector Administrator** or **Super Administrator** role in ConductorOne to add a connector. MySQL is a self-hosted connector — you run the Baton binary in your own infrastructure. You will need: - MySQL connection string (`user:password@tcp(host:port)/`) - - A C1 Client ID and Client Secret (obtained in Step 1 below) + - A C1.ai Client ID and Client Secret (obtained in Step 1 below) ### Resources @@ -126,7 +126,7 @@ That's it! You now have the credentials needed to configure the connector. ### Step 1 -Add a Baton connector in ConductorOne and rotate credentials to get a C1 Client ID and Client Secret. +Add a Baton connector in ConductorOne and rotate credentials to get a C1.ai Client ID and Client Secret. diff --git a/baton/n8n.mdx b/baton/n8n.mdx index bab88ec0..d2603248 100644 --- a/baton/n8n.mdx +++ b/baton/n8n.mdx @@ -1,8 +1,8 @@ --- title: "Set up a n8n connector" og:title: "Set up a n8n connector" -description: "C1 provides identity governance and just-in-time provisioning for n8n. Integrate your n8n instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision global roles and project membership." -og:description: "C1 provides identity governance and just-in-time provisioning for n8n. Integrate your n8n instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision global roles and project membership." +description: "C1.ai provides identity governance and just-in-time provisioning for n8n. Integrate your n8n instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision global roles and project membership." +og:description: "C1.ai provides identity governance and just-in-time provisioning for n8n. Integrate your n8n instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision global roles and project membership." sidebarTitle: "n8n" --- @@ -24,8 +24,8 @@ The n8n connector syncs the following resources: **Known limitations:** -- n8n does not support disabling or suspending users — only inviting or deleting them. C1 cannot suspend n8n users. -- Project membership provisioning is blocked by n8n (returns 403) when SSO-based provisioning is enabled on the instance. C1 will report the error if this occurs. +- n8n does not support disabling or suspending users — only inviting or deleting them. C1.ai cannot suspend n8n users. +- Project membership provisioning is blocked by n8n (returns 403) when SSO-based provisioning is enabled on the instance. C1.ai will report the error if this occurs. - Revoking the `global:member` role is a no-op — it is the base instance role. To remove a user entirely, use the delete user action. - There is no SCIM support in n8n. @@ -62,11 +62,11 @@ To configure the n8n connector, you need **Owner** or **Admin** permissions in y - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -116,19 +116,19 @@ To configure the n8n connector, you need **Owner** or **Admin** permissions in y - **Done.** Your n8n connector is now pulling access data into C1. + **Done.** Your n8n connector is now pulling access data into C1.ai. Follow these instructions to use the [n8n](https://github.com/ConductorOne/baton-n8n) 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. + When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1.ai, automatically syncing and uploading data at regular intervals. ### Step 1: Set up a new n8n connector - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -226,15 +226,15 @@ To configure the n8n connector, you need **Owner** or **Admin** permissions in y - 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 C1.ai 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 n8n connector to. n8n data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the n8n connector to. n8n data should be found on the **Entitlements** and **Accounts** tabs. - **Done.** Your n8n connector is now pulling access data into C1. + **Done.** Your n8n connector is now pulling access data into C1.ai. diff --git a/baton/navan.mdx b/baton/navan.mdx index 3e5a4800..83199947 100644 --- a/baton/navan.mdx +++ b/baton/navan.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Navan connector" og:title: "Set up a Navan connector" -description: "C1 provides identity governance for Navan. Integrate your Navan instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Navan. Integrate your Navan instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Navan. Integrate your Navan instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Navan. Integrate your Navan instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Navan" --- -C1 provides identity governance for Navan. Integrate your Navan instance with -C1 for unified visibility and governance over who has access in Navan, which +C1.ai provides identity governance for Navan. Integrate your Navan instance with +C1.ai for unified visibility and governance over who has access in Navan, which department and cost center each person belongs to, and what role they hold. ## Capabilities @@ -50,11 +50,11 @@ credentials. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -99,7 +99,7 @@ credentials. - **Done.** Your Navan connector is now pulling access data into C1. + **Done.** Your Navan connector is now pulling access data into C1.ai. @@ -123,6 +123,6 @@ credentials. - **Done.** Your Navan connector is now pulling access data into C1. + **Done.** Your Navan connector is now pulling access data into C1.ai. diff --git a/baton/ncino.mdx b/baton/ncino.mdx index 4d1a63de..d958c769 100644 --- a/baton/ncino.mdx +++ b/baton/ncino.mdx @@ -1,8 +1,8 @@ --- title: "Set up an nCino connector" og:title: "Set up an nCino connector" -description: "C1 provides identity governance for nCino. Integrate your nCino instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for nCino. Integrate your nCino instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for nCino. Integrate your nCino instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for nCino. Integrate your nCino instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "nCino" --- @@ -64,17 +64,17 @@ Enable **GET** on the API endpoints that display info on team members, loan offi To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of nCino 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **nCino** and click **Add**. @@ -107,23 +107,23 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your nCino connector is now pulling access data into C1. +**Done.** Your nCino connector is now pulling access data into C1.ai. **Follow these instructions to use the nCino 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai 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 C1.ai's support team](mailto:support@conductorone.com) to download the latest version of the connector. ### Step 1: Set up a new nCino connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -215,14 +215,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 C1.ai 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 nCino connector to. nCino data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the nCino connector to. nCino data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your nCino connector is now pulling access data into C1. +**Done.** Your nCino connector is now pulling access data into C1.ai. diff --git a/baton/netlify.mdx b/baton/netlify.mdx index 0a165dd1..a65e6700 100644 --- a/baton/netlify.mdx +++ b/baton/netlify.mdx @@ -1,8 +1,8 @@ --- title: "Set up Netlify connector" og:title: "Set up Netlify connector" -description: "C1 provides identity governance for Netlify. Integrate your Netlify instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Netlify. Integrate your Netlify instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Netlify. Integrate your Netlify instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Netlify. Integrate your Netlify instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Netlify" --- @@ -38,17 +38,17 @@ See the Netlify docs for information on how to acquire credentials: [View the do To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Netlify 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Netlify** and click **Add**. @@ -81,23 +81,23 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Netlify connector is now pulling access data into C1. +**Done.** Your Netlify connector is now pulling access data into C1.ai. **Follow these instructions to use the Netlify 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources -[Contact C1's support team](mailto:support@c1.ai) to download the latest version of the connector. +[Contact C1.ai's support team](mailto:support@c1.ai) to download the latest version of the connector. ### Step 1: Set up a new Netlify connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -188,14 +188,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 C1.ai 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 netlify connector to. netlify data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the netlify connector to. netlify data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Netlify connector is now pulling access data into C1. +**Done.** Your Netlify connector is now pulling access data into C1.ai. diff --git a/baton/netsuite.mdx b/baton/netsuite.mdx index 2cbb65b5..e4a7decf 100644 --- a/baton/netsuite.mdx +++ b/baton/netsuite.mdx @@ -1,8 +1,8 @@ --- title: "Set up an Oracle NetSuite connector" og:title: "Set up an Oracle NetSuite connector" -description: "C1 provides identity governance for Oracle NetSuite. Integrate your Oracle NetSuite instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." -og:description: "C1 provides identity governance for Oracle NetSuite. Integrate your Oracle NetSuite instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance for Oracle NetSuite. Integrate your Oracle NetSuite instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance for Oracle NetSuite. Integrate your Oracle NetSuite instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Oracle NetSuite" --- @@ -21,7 +21,7 @@ This connector does not support account deprovisioning. You must deprovision acc ## Account provisioning -The NetSuite connector supports creating new employee accounts directly from C1. When configuring an account provisioning policy, you can map the following fields. +The NetSuite connector supports creating new employee accounts directly from C1.ai. When configuring an account provisioning policy, you can map the following fields. ### Required fields @@ -58,7 +58,7 @@ To add `giveAccess` or `skipDefaultRole` to your mapping, click **Add mapping** -**Administrator roles cannot be granted or revoked via the connector.** NetSuite's API does not allow modifications to employee records that have the Administrator role assigned, regardless of the permissions granted to the integration. Attempting to grant or revoke the Administrator role through C1 will result in an error. To assign or remove the Administrator role, make the change directly in NetSuite. +**Administrator roles cannot be granted or revoked via the connector.** NetSuite's API does not allow modifications to employee records that have the Administrator role assigned, regardless of the permissions granted to the integration. Attempting to grant or revoke the Administrator role through C1.ai will result in an error. To assign or remove the Administrator role, make the change directly in NetSuite. ## Login Access @@ -133,13 +133,13 @@ Find the **ACCOUNT ID** field on the page. Make a note of your account ID. We'll In NetSuite, navigate to **Setup** > **Integrations** > **Manage Integrations**. Click **New** to create a new integration. -Give the new integration a name, such as "C1". +Give the new integration a name, such as "C1.ai". Check the box for **TOKEN-BASED AUTHENTICATION**. -Make sure **OAuth 2.0 Authorization Code Grant** is unchecked on the Authentication tab. NetSuite may enable this by default, which requires a Redirect URI that is not needed for the C1 connector. The C1 NetSuite connector uses Token-Based Authentication only. +Make sure **OAuth 2.0 Authorization Code Grant** is unchecked on the Authentication tab. NetSuite may enable this by default, which requires a Redirect URI that is not needed for the C1.ai connector. The C1.ai NetSuite connector uses Token-Based Authentication only. @@ -157,7 +157,7 @@ Make a careful note of these credentials (they won't be shown again). Still in NetSuite, navigate to **Setup** > **Users/Roles** > **Manage Roles**. Click **New** to create a new role. -Give the new role a name, such as "C1 integration". +Give the new role a name, such as "C1.ai integration". Assign the following permissions to the role: @@ -220,17 +220,17 @@ Make a careful note of these credentials (they won't be shown again). To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of NetSuite 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **NetSuite** and click **Add**. @@ -272,13 +272,13 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your NetSuite connector is now pulling access data into C1. +**Done.** Your NetSuite connector is now pulling access data into C1.ai. **Follow these instructions to use the NetSuite 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -288,7 +288,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -391,20 +391,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 C1.ai 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 NetSuite connector to. NetSuite data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the NetSuite connector to. NetSuite data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your NetSuite connector is now pulling access data into C1. +**Done.** Your NetSuite connector is now pulling access data into C1.ai. ## Custom Fields -The NetSuite connector supports syncing custom employee fields. Custom field values are added to the user profile attributes in C1, making them available for access reviews and reporting. +The NetSuite connector supports syncing custom employee fields. Custom field values are added to the user profile attributes in C1.ai, making them available for access reviews and reporting. ### Finding custom field IDs diff --git a/baton/newrelic.mdx b/baton/newrelic.mdx index 86cc2783..5efbe493 100644 --- a/baton/newrelic.mdx +++ b/baton/newrelic.mdx @@ -1,8 +1,8 @@ --- title: "Set up a New Relic connector" og:title: "Set up a New Relic connector" -description: "C1 provides identity governance and just-in-time provisioning for New Relic. Integrate your New Relic 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 New Relic. Integrate your New Relic instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for New Relic. Integrate your New Relic instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for New Relic. Integrate your New Relic instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "New Relic" --- @@ -19,7 +19,7 @@ The New Relic connector supports account provisioning: creating and deleting use ### 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 C1.ai 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 | |-------------|-------------------|-------------| @@ -27,7 +27,7 @@ Connector actions are custom capabilities that extend C1 automations with app-sp ### Find your authentication domain ID -New Relic organizes users into authentication domains, and every new user must be created within one. C1 needs this domain's ID before it can create New Relic accounts. +New Relic organizes users into authentication domains, and every new user must be created within one. C1.ai needs this domain's ID before it can create New Relic accounts. @@ -45,7 +45,7 @@ See New Relic's [authentication domains documentation](https://docs.newrelic.com ### Set up account provisioning mappings -C1 creates a New Relic account when a user requests access to this app. The account details come from the app's provisioning mappings, which you set up on the app's **Overview** page — see [Configure account provisioning](/product/admin/account-provisioning) for the full procedure. +C1.ai creates a New Relic account when a user requests access to this app. The account details come from the app's provisioning mappings, which you set up on the app's **Overview** page — see [Configure account provisioning](/product/admin/account-provisioning) for the full procedure. The New Relic connector requires four mappings: @@ -86,7 +86,7 @@ Click **Create a key**. The **Create an API key** drawer opens. Select **User** as the **Key type**. -Enter a name for the new API key, such as "C1", and add any notes you or your colleagues might need about this key. +Enter a name for the new API key, such as "C1.ai", and add any notes you or your colleagues might need about this key. Click **Create a key**. @@ -106,17 +106,17 @@ Click the **...** menu and select **Copy key**. Carefully save the API key. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of New Relic 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **New Relic** and click **Add**. @@ -149,23 +149,23 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**That's it!** Your New Relic connector is now pulling access data into C1. +**That's it!** Your New Relic connector is now pulling access data into C1.ai. **Follow these instructions to use the New Relic 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai 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 C1.ai's support team](mailto:support@conductorone.com) to download the latest version of the connector. ### Step 1: Set up a new New Relic connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -258,13 +258,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 C1.ai 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 New Relic connector to. New Relic data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the New Relic connector to. New Relic data should be found on the **Entitlements** and **Accounts** tabs. -**That's it!** Your New Relic connector is now pulling access data into C1. +**That's it!** Your New Relic connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/ninja-one.mdx b/baton/ninja-one.mdx index c68df556..3bbe3051 100644 --- a/baton/ninja-one.mdx +++ b/baton/ninja-one.mdx @@ -1,8 +1,8 @@ --- title: "Set up NinjaOne connector" og:title: "Set up NinjaOne connector" -description: "C1 provides identity governance and just-in-time provisioning for NinjaOne. Integrate your NinjaOne 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 NinjaOne. Integrate your NinjaOne instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for NinjaOne. Integrate your NinjaOne instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for NinjaOne. Integrate your NinjaOne instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "NinjaOne" --- @@ -79,17 +79,17 @@ After saving, carefully copy and save the client ID and client secret. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of NinjaOne 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **NinjaOne** and click **Add**. @@ -122,13 +122,13 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your NinjaOne connector is now pulling access data into C1. +**Done.** Your NinjaOne connector is now pulling access data into C1.ai. **Follow these instructions to use the NinjaOne 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -138,7 +138,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -234,14 +234,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 C1.ai 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 ninja-one connector to. ninja-one data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the ninja-one connector to. ninja-one data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your NinjaOne connector is now pulling access data into C1. +**Done.** Your NinjaOne connector is now pulling access data into C1.ai. diff --git a/baton/ninjio.mdx b/baton/ninjio.mdx index c792d760..a62ac8aa 100644 --- a/baton/ninjio.mdx +++ b/baton/ninjio.mdx @@ -1,8 +1,8 @@ --- title: "Set up a NINJIO connector" og:title: "Set up a NINJIO connector" -description: "C1 provides identity governance for NINJIO. Integrate your NINJIO instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for NINJIO. Integrate your NINJIO instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for NINJIO. Integrate your NINJIO instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for NINJIO. Integrate your NINJIO instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "NINJIO" --- @@ -45,11 +45,11 @@ To configure the NINJIO connector, you need administrator permissions in NINJIO. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -98,19 +98,19 @@ To configure the NINJIO connector, you need administrator permissions in NINJIO. - **Done.** Your NINJIO connector is now pulling access data into C1. + **Done.** Your NINJIO connector is now pulling access data into C1.ai. Follow these instructions to use the [NINJIO](https://github.com/conductorone/baton-ninjio) 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. + When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1.ai, automatically syncing and uploading data at regular intervals. ### Step 1: Set up a new NINJIO connector - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -207,15 +207,15 @@ To configure the NINJIO connector, you need administrator permissions in NINJIO. - 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 C1.ai 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 NINJIO connector to. NINJIO data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the NINJIO connector to. NINJIO data should be found on the **Entitlements** and **Accounts** tabs. - **Done.** Your NINJIO connector is now pulling access data into C1. + **Done.** Your NINJIO connector is now pulling access data into C1.ai. diff --git a/baton/northflank.mdx b/baton/northflank.mdx index 3e73004f..8e52eaf4 100644 --- a/baton/northflank.mdx +++ b/baton/northflank.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Northflank connector" og:title: "Set up a Northflank connector" -description: "C1 provides identity governance for Northflank. Integrate your Northflank organization with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Northflank. Integrate your Northflank organization with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Northflank. Integrate your Northflank organization with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Northflank. Integrate your Northflank organization with C1.ai for unified visibility and governance over user access." sidebarTitle: "Northflank" --- -C1 provides identity governance for Northflank. Integrate your Northflank -organization with C1 for unified visibility and governance over who has access +C1.ai provides identity governance for Northflank. Integrate your Northflank +organization with C1.ai for unified visibility and governance over who has access through organization roles and directory groups. ## Capabilities @@ -53,11 +53,11 @@ from, and the token is scoped to a single organization. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -102,7 +102,7 @@ from, and the token is scoped to a single organization. - **Done.** Your Northflank connector is now pulling access data into C1. + **Done.** Your Northflank connector is now pulling access data into C1.ai. @@ -126,6 +126,6 @@ from, and the token is scoped to a single organization. - **Done.** Your Northflank connector is now pulling access data into C1. + **Done.** Your Northflank connector is now pulling access data into C1.ai. diff --git a/baton/notion.mdx b/baton/notion.mdx index 671041f4..d8a02b86 100644 --- a/baton/notion.mdx +++ b/baton/notion.mdx @@ -1,14 +1,14 @@ --- title: "Set up a Notion connector" og:title: "Set up a Notion connector" -description: "C1 provides identity governance and just-in-time provisioning for Notion. Integrate your Notion 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 Notion. Integrate your Notion instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Notion. Integrate your Notion instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Notion. Integrate your Notion instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Notion" --- ## Availability -C1 currently only integrates with Notion Enterprise. You cannot use this connector successfully with the Free, Plus, or Business editions of Notion. +C1.ai currently only integrates with Notion Enterprise. You cannot use this connector successfully with the Free, Plus, or Business editions of Notion. ## Capabilities @@ -64,17 +64,17 @@ For more information, see [Provision users & groups with SCIM](https://www.notio To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Notion 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Notion** and click **Add**. @@ -107,13 +107,13 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Notion connector is now pulling access data into C1. +**Done.** Your Notion connector is now pulling access data into C1.ai. **Follow these instructions to use the Notion 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -123,7 +123,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -222,13 +222,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 C1.ai 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 Notion connector to. Notion data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Notion connector to. Notion data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Notion connector is now pulling access data into C1. +**Done.** Your Notion connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/npm.mdx b/baton/npm.mdx index 7fdee14c..72a5e06e 100644 --- a/baton/npm.mdx +++ b/baton/npm.mdx @@ -1,12 +1,12 @@ --- title: "Set up an npm connector" og:title: "Set up an npm connector" -description: "C1 provides identity governance for npm. Integrate your npm organization with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for npm. Integrate your npm organization with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for npm. Integrate your npm organization with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for npm. Integrate your npm organization with C1.ai for unified visibility and governance over user access." sidebarTitle: "npm" --- -C1 provides identity governance for npm. Integrate your npm organization with C1 +C1.ai provides identity governance for npm. Integrate your npm organization with C1.ai for unified visibility and governance over who belongs to the organization, what role they hold, and which teams they are members of. @@ -54,11 +54,11 @@ and you need an npm access token with organization read access. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -103,7 +103,7 @@ and you need an npm access token with organization read access. - **Done.** Your npm connector is now pulling access data into C1. + **Done.** Your npm connector is now pulling access data into C1.ai. @@ -126,7 +126,7 @@ and you need an npm access token with organization read access. - **Done.** Your npm connector is now pulling access data into C1. + **Done.** Your npm connector is now pulling access data into C1.ai. diff --git a/baton/octopus.mdx b/baton/octopus.mdx index ec7c3eb4..f031198a 100644 --- a/baton/octopus.mdx +++ b/baton/octopus.mdx @@ -1,13 +1,13 @@ --- title: "Set up an Octopus connector" og:title: "Set up an Octopus connector" -description: "C1 provides identity governance for Octopus Deploy. Integrate your Octopus instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Octopus Deploy. Integrate your Octopus instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Octopus Deploy. Integrate your Octopus instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Octopus Deploy. Integrate your Octopus instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Octopus" --- -C1 provides identity governance for Octopus Deploy. Integrate your Octopus -instance with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Octopus Deploy. Integrate your Octopus +instance with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -65,11 +65,11 @@ connector. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -116,7 +116,7 @@ connector. - **Done.** Your Octopus connector is now pulling access data into C1. + **Done.** Your Octopus connector is now pulling access data into C1.ai. @@ -142,6 +142,6 @@ connector. - **Done.** Your Octopus connector is now pulling access data into C1. + **Done.** Your Octopus connector is now pulling access data into C1.ai. diff --git a/baton/okta-aws-federation.mdx b/baton/okta-aws-federation.mdx index e7316bdb..a34117f2 100644 --- a/baton/okta-aws-federation.mdx +++ b/baton/okta-aws-federation.mdx @@ -1,8 +1,8 @@ --- title: "Set up an Okta AWS Federation connector" og:title: "Set up an Okta AWS Federation connector" -description: "C1 provides identity governance and just-in-time provisioning for Okta for AWS federation. Integrate your Okta 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 Okta for AWS federation. Integrate your Okta instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for Okta for AWS federation. Integrate your Okta instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Okta for AWS federation. Integrate your Okta instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "Okta AWS Federation" --- @@ -30,11 +30,11 @@ The groups and their membership are imported from the paired Okta connector, not Configuring the connector requires you to pass in credentials generated in Okta. Gather these credentials before you move on. -### API token permissions and C1 capabilities +### API token permissions and C1.ai capabilities -C1's capabilities depend on the permissions of the API token used to set up the connector: +C1.ai's capabilities depend on the permissions of the API token used to set up the connector: -| C1 capability | Custom read-only token | Read-only + app admin + group admin token | Super admin token | +| C1.ai capability | Custom read-only token | Read-only + app admin + group admin token | Super admin token | | :--- | :--- | :--- | :--- | | Review application assignment | | | | | Provision application assignment | | | | @@ -47,7 +47,7 @@ Instead of generating a new API token, you can use an existing API token generat ### (Optional) Create a custom read-only admin role -To give the C1 integration limited read-only admin permissions, you'll need to create a custom Okta admin role and resource set and assign them to the admin you'll use to generate the API key. +To give the C1.ai integration limited read-only admin permissions, you'll need to create a custom Okta admin role and resource set and assign them to the admin you'll use to generate the API key. @@ -57,7 +57,7 @@ In Okta, log in to the Admin Dashboards and navigate to **Security** > **Adminis Click **Create new role**. -Give the new role a name and description, such as "C1 integration read-only admin". +Give the new role a name and description, such as "C1.ai integration read-only admin". Give the role the **View roles, resources, and admin assignments** permission (this is found in the **Identity and access management permissions** section). @@ -72,7 +72,7 @@ Next, navigate to **Security** > **Administrators** > **Resources**. Click **Create new resource set**. -Give the new resource set a name and description, such as "Read-only admin for C1 integration". +Give the new resource set a name and description, such as "Read-only admin for C1.ai integration". Click **Add resources**. @@ -140,7 +140,7 @@ When **creating** an API token, Okta assigns the permissions of the _currently l Log into Okta with the account you'll use to generate the API token. - The account must have **Super Administrator,** the custom read-only role you created above, or a combination of **Read Only/App Admin/Group Admin** privileges. The permissions on the API token affects what features and functionality are available from C1. Before you begin, review the chart in [API permissions and C1 capabilities](/baton/okta#api-token-permissions-and-conductorone-capabilities) to make sure you're creating a token with the right permissions for your needs. + The account must have **Super Administrator,** the custom read-only role you created above, or a combination of **Read Only/App Admin/Group Admin** privileges. The permissions on the API token affects what features and functionality are available from C1.ai. Before you begin, review the chart in [API permissions and C1.ai capabilities](/baton/okta#api-token-permissions-and-conductorone-capabilities) to make sure you're creating a token with the right permissions for your needs. In the Okta console, navigate to **Security** > **API** and click **Tokens**. @@ -163,17 +163,17 @@ Copy and save the new API 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 C1.ai - Access to the set of Okta 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Okta AWS Federation** and click **Add**. @@ -207,7 +207,7 @@ Enter your AWS Okta app ID in the **AWS Okta app ID** field. **Optional.** If desired, click the checkbox to **Allow group to direct assignment conversion for provisioning**. - When this setting is enabled, when AWS roles are requested directly and the user is assigned to the AWS app in Okta via group membership, C1 will convert the user assignment to a direct assignment. + When this setting is enabled, when AWS roles are requested directly and the user is assigned to the AWS app in Okta via group membership, C1.ai will convert the user assignment to a direct assignment. Click **Save**. @@ -226,7 +226,7 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Okta AWS Federation connector is now pulling access data into C1. +**Done.** Your Okta AWS Federation connector is now pulling access data into C1.ai. diff --git a/baton/okta-ciam-workforce.mdx b/baton/okta-ciam-workforce.mdx index 29c6c70b..b7d97471 100644 --- a/baton/okta-ciam-workforce.mdx +++ b/baton/okta-ciam-workforce.mdx @@ -1,8 +1,8 @@ --- title: "Set up an Okta CIAM Workforce connector" og:title: "Set up an Okta CIAM Workforce connector" -description: "C1 provides identity governance and just-in-time provisioning for Okta CIAM for Workforce. Integrate your Okta CIAM instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision group membership." -og:description: "C1 provides identity governance and just-in-time provisioning for Okta CIAM for Workforce. Integrate your Okta CIAM instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision group membership." +description: "C1.ai provides identity governance and just-in-time provisioning for Okta CIAM for Workforce. Integrate your Okta CIAM instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision group membership." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Okta CIAM for Workforce. Integrate your Okta CIAM instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision group membership." sidebarTitle: "Okta CIAM Workforce" --- @@ -19,7 +19,7 @@ sidebarTitle: "Okta CIAM Workforce" | Roles | | | | Custom roles | | | -The Okta CIAM Workforce connector supports provisioning for group membership only. You can grant and revoke user access to groups through C1. +The Okta CIAM Workforce connector supports provisioning for group membership only. You can grant and revoke user access to groups through C1.ai. This connector does not support user provisioning or deprovisioning. User management must be handled directly in Okta CIAM. @@ -49,7 +49,7 @@ Navigate to **Security** > **API** and click **Tokens**. Click **Create Token**. -Give your token a name, such as "C1 Integration", and click **Create Token**. +Give your token a name, such as "C1.ai Integration", and click **Create Token**. Copy and save the new API token securely. You won't be able to view it again. @@ -75,17 +75,17 @@ For example, if you want to sync only users with `@example.com` and `@company.co To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the Okta CIAM 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Okta CIAM Workforce** and click **Add**. @@ -127,13 +127,13 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Okta CIAM Workforce connector is now pulling access data into C1. +**Done.** Your Okta CIAM Workforce connector is now pulling access data into C1.ai. **Follow these instructions to use the Okta CIAM Workforce 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -145,7 +145,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -243,13 +243,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 C1.ai 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 Okta CIAM Workforce connector to. Okta CIAM data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Okta CIAM Workforce connector to. Okta CIAM data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Okta CIAM Workforce connector is now pulling access data into C1. +**Done.** Your Okta CIAM Workforce connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/okta.mdx b/baton/okta.mdx index 0e4714b7..68d26ff8 100644 --- a/baton/okta.mdx +++ b/baton/okta.mdx @@ -1,17 +1,17 @@ --- title: "Set up an Okta connector" og:title: "Set up an Okta connector" -description: "C1 provides identity governance and just-in-time provisioning for Okta. Integrate your Okta 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 Okta. Integrate your Okta instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for Okta. Integrate your Okta instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Okta. Integrate your Okta instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "Okta" --- -**This is an updated and improved version of the Okta connector!** If you're setting up Okta with C1 for the first time, you're in the right place. +**This is an updated and improved version of the Okta connector!** If you're setting up Okta with C1.ai for the first time, you're in the right place. -This page covers the Okta **connector**, which syncs and provisions access data for identity governance. It does not control how you sign in to C1. To set up signing in to C1 with your Okta account, see [Authenticate with Okta](/product/how-to/qs-set-up-c1#authenticate-with-okta). +This page covers the Okta **connector**, which syncs and provisions access data for identity governance. It does not control how you sign in to C1.ai. To set up signing in to C1.ai with your Okta account, see [Authenticate with Okta](/product/how-to/qs-set-up-c1#authenticate-with-okta). ## Capabilities @@ -37,7 +37,7 @@ This page covers the Okta **connector**, which syncs and provisions access data -The standard roles **Workflows Administrator**, **Access Certifications Administrator**, and **Access Requests Administrator** appear as Custom Roles in C1. Enable **Sync Custom Roles** to see them. The Okta API returns these roles through the same endpoint as custom roles. +The standard roles **Workflows Administrator**, **Access Certifications Administrator**, and **Access Requests Administrator** appear as Custom Roles in C1.ai. Enable **Sync Custom Roles** to see them. The Okta API returns these roles through the same endpoint as custom roles. @@ -64,7 +64,7 @@ Use this attribute in policies and access profiles to verify that bindings and g -**Skip app groups changes how app access is attributed.** When a group is assigned to an app, C1 records that group as the source of each member's access. Skipping `APP_GROUP` groups means they are never synced, so access conferred by one has no group to point at. Rather than dropping that access, the connector reports it as a direct assignment on the app. +**Skip app groups changes how app access is attributed.** When a group is assigned to an app, C1.ai records that group as the source of each member's access. Skipping `APP_GROUP` groups means they are never synced, so access conferred by one has no group to point at. Rather than dropping that access, the connector reports it as a direct assignment on the app. Two things this does *not* do: @@ -76,17 +76,17 @@ On such an app, the direct assignments produced this way are marked immutable, b The Okta connector supports [automatic account provisioning](/product/admin/account-provisioning). -The Okta connector supports account deprovisioning through C1 resource deletion. It first deactivates the user to the `DEPROVISIONED` state and then permanently deletes the user. The same operations are available separately through the `deactivate_user` and `delete_user` connector actions. These operations require an API token or OAuth app with `okta.users.manage` scope. +The Okta connector supports account deprovisioning through C1.ai resource deletion. It first deactivates the user to the `DEPROVISIONED` state and then permanently deletes the user. The same operations are available separately through the `deactivate_user` and `delete_user` connector actions. These operations require an API token or OAuth app with `okta.users.manage` scope. #### Account creation profile fields -When you configure account provisioning for Okta, C1 shows the following optional fields on the account creation form (in addition to first name, last name, email, and login): +When you configure account provisioning for Okta, C1.ai shows the following optional fields on the account creation form (in addition to first name, last name, email, and login): | Field | Values | Default | What it does | | :--- | :--- | :--- | :--- | | **Password Change Required on Login** | `True` / `False` | Off | When creating an account with a random password, requires the user to change that password on first login. | | **Create Inactive** | `True` / `False` | Off | Creates the user in Okta as staged (inactive) without activating them. | -| **Send Activation Email** | `True` / `False` | `True` | When set to `False`, activates the user without sending Okta's activation email. Use this when C1 (or another system) owns user communication. | +| **Send Activation Email** | `True` / `False` | `True` | When set to `False`, activates the user without sending Okta's activation email. Use this when C1.ai (or another system) owns user communication. | | **Provider Type** | `OKTA` / `FEDERATION` | Okta's default (local) provider | Set to `FEDERATION` to create a federated user with no local Okta password. Common in hub-and-spoke / Org2Org designs where the hub IdP owns credentials. | | **Additional Attributes** | Map of Okta profile keys | — | Extra Okta profile attributes (standard or custom schema) to set on the user. | @@ -95,7 +95,7 @@ When you configure account provisioning for Okta, C1 shows the following optiona -**Okta Staged status (sign-in to Okta, not C1).** In Okta, **Staged** means the account was created but not activated yet, so the user cannot sign in to Okta. That is an Okta lifecycle state — it is not about signing in to ConductorOne. Staged users sync as **disabled** in C1 so sync matches the lifecycle actions: `disable_user` is a no-op on staged accounts, and `enable_user` activates them (`/lifecycle/activate` without sending another activation email). After activation the account becomes **Active** or **Provisioned** (Provisioned only means they have not completed first login yet). +**Okta Staged status (sign-in to Okta, not C1.ai).** In Okta, **Staged** means the account was created but not activated yet, so the user cannot sign in to Okta. That is an Okta lifecycle state — it is not about signing in to ConductorOne. Staged users sync as **disabled** in C1.ai so sync matches the lifecycle actions: `disable_user` is a no-op on staged accounts, and `enable_user` activates them (`/lifecycle/activate` without sending another activation email). After activation the account becomes **Active** or **Provisioned** (Provisioned only means they have not completed first login yet). Default **Create Account** does not leave users staged: the connector activates them or sends Okta's activation email. Users stay staged only when **Create Inactive** is `True`, an Okta admin created them without activating, or an incomplete create left them there. The raw Okta status string stays on the resource details, so Staged remains distinguishable from Suspended or Deprovisioned. After you upgrade a connector that previously reported staged users as enabled, the next sync flips those resources to disabled — review any automations that key off user enabled/disabled status. @@ -124,7 +124,7 @@ Syncing standard and custom admin roles requires a super admin token. ### Connector actions -Connector actions are custom capabilities that extend C1 automations with app-specific operations. The Okta connector's actions are reached from **two different automation steps**, and which step offers an action is determined by the action itself — you cannot choose: +Connector actions are custom capabilities that extend C1.ai automations with app-specific operations. The Okta connector's actions are reached from **two different automation steps**, and which step offers an action is determined by the action itself — you cannot choose: | Automation step | Actions offered | How the target is selected | |-----------------|-----------------|----------------------------| @@ -133,7 +133,7 @@ Connector actions are custom capabilities that extend C1 automations with app-sp In the Perform connector action step, actions are listed under their resource type and display name rather than their raw action name: `deactivate_user`, `delete_user`, and `update_profile` appear as **`user - Deactivate User`**, **`user - Delete User`**, and **`user - Update User Profile`**, and `modify_group` as **`group - Modify Group`**. An action with no display name registered falls back to its raw name, so `create` appears as **`group - create`**. -`enable_user`, `disable_user` and `update_user` take `user_id` as a plain string, and `modify_group` takes `group_id` the same way. Pass the raw Okta ID (for example `00u1abc2def3GHI4jk5`), not the C1 resource ID — the connector sends the value to Okta unchanged, and a C1 resource ID returns a not-found error. `deactivate_user`, `delete_user`, and `update_profile` take a resource selector instead, so the Okta ID is resolved for you. +`enable_user`, `disable_user` and `update_user` take `user_id` as a plain string, and `modify_group` takes `group_id` the same way. Pass the raw Okta ID (for example `00u1abc2def3GHI4jk5`), not the C1.ai resource ID — the connector sends the value to Okta unchanged, and a C1.ai resource ID returns a not-found error. `deactivate_user`, `delete_user`, and `update_profile` take a resource selector instead, so the Okta ID is resolved for you. | Action name | Additional fields | Description | |-------------|-------------------|-------------| @@ -142,12 +142,12 @@ In the Perform connector action step, actions are listed under their resource ty | deactivate_user | `user_id` (Okta user resource, required) | Destructively deprovisions the selected user from assigned applications and leaves the Okta user record in `DEPROVISIONED`. A user already in that state succeeds without another mutation. | | delete_user | `user_id` (Okta user resource, required) | Ensures the selected user is deactivated, then permanently deletes the user. A user that is already absent succeeds so workflow retries are safe. | | update_profile | `user_id` (resource ID, required), 18 optional profile fields (`login`, `email`, `secondEmail`, `firstName`, `lastName`, `middleName`, `displayName`, `title`, `department`, `division`, `organization`, `employeeNumber`, `costCenter`, `userType`, `primaryPhone`, `mobilePhone`, `countryCode`, `managerId`), `additionalAttributes` (map) | Updates an existing Okta user's profile attributes. At least one profile field must be provided. | -| update_user | `user_id` (string, required), `user_profile` (JSON object, required) | Updates a user's profile from a JSON object of Okta profile attributes — accepts any attribute, not limited to update_profile's curated list. This is the action C1's automated profile-push pipeline uses. | +| update_user | `user_id` (string, required), `user_profile` (JSON object, required) | Updates a user's profile from a JSON object of Okta profile attributes — accepts any attribute, not limited to update_profile's curated list. This is the action C1.ai's automated profile-push pipeline uses. | | create | `name` (string, required), `description` (string), `userMembers` (resource ID list) | Creates a new Okta group with optional initial members | | modify_group | `group_id` (string, required), `name` (string), `description` (string) | Updates the name and/or description of an existing Okta group. Returns success without calling the Okta API if the supplied values already match the group's current name and description (idempotent). | -`deactivate_user`, `delete_user`, and C1 account deprovisioning are destructive. Deactivation removes the user's assigned-app provisioning and can destroy downstream data such as email or files. Deletion permanently removes the Okta user and cannot be recovered. Use workflow approval gates where appropriate. +`deactivate_user`, `delete_user`, and C1.ai account deprovisioning are destructive. Deactivation removes the user's assigned-app provisioning and can destroy downstream data such as email or files. Deletion permanently removes the Okta user and cannot be recovered. Use workflow approval gates where appropriate. @@ -171,7 +171,7 @@ Group deletion is available via the CLI using the `--delete-resource` flag. To d baton-okta --api-token $BATON_API_TOKEN --domain $BATON_DOMAIN --delete-resource "" --delete-resource-type "group" ``` -Use the raw Okta external ID (e.g. `00g1abc2def3GHI4jk5`), not the C1 resource ID. Group deletion is not available through the C1 UI or the Automations tab. +Use the raw Okta external ID (e.g. `00g1abc2def3GHI4jk5`), not the C1.ai resource ID. Group deletion is not available through the C1.ai UI or the Automations tab. ## Authentication methods @@ -189,11 +189,11 @@ The **OAuth 2.0 Private Key** method is recommended for production environments Configuring the connector requires you to pass in credentials generated in Okta. Gather these credentials before you move on. -### API token permissions and C1 capabilities +### API token permissions and C1.ai capabilities -C1's capabilities depend on the permissions of the API token used to set up the connector: +C1.ai's capabilities depend on the permissions of the API token used to set up the connector: -| C1 capability | Custom read-only token | Read-only + app admin + group admin token | Super admin token | +| C1.ai capability | Custom read-only token | Read-only + app admin + group admin token | Super admin token | | :--- | :--- | :--- | :--- | | Review group membership | | | | | Provision group membership | | | | @@ -213,7 +213,7 @@ This role is necessary when admin roles are assigned to Okta groups. Without it, ### (Optional) Create a custom read-only admin role -To give the C1 integration limited read-only admin permissions, create a custom Okta admin role and resource set and assign them to the admin you'll use to generate the API key. +To give the C1.ai integration limited read-only admin permissions, create a custom Okta admin role and resource set and assign them to the admin you'll use to generate the API key. @@ -223,7 +223,7 @@ In Okta, log in to the Admin Dashboards and navigate to **Security** > **Adminis Click **Create new role**. -Give the new role a name and description, such as "C1 integration read-only admin". +Give the new role a name and description, such as "C1.ai integration read-only admin". Give the role the **View roles, resources, and admin assignments** permission (this is found in the **Identity and access management permissions** section). @@ -238,7 +238,7 @@ Next, navigate to **Security** > **Administrators** > **Resources**. Click **Create new resource set**. -Give the new resource set a name and description, such as "Read-only admin for C1 integration". +Give the new resource set a name and description, such as "Read-only admin for C1.ai integration". Click **Add resources**. @@ -299,7 +299,7 @@ Click **Add Administrator**. ### Create an API token -We strongly recommend creating a dedicated token for the C1 integration so you can manage the token's lifespan and control per-token rate limits. +We strongly recommend creating a dedicated token for the C1.ai integration so you can manage the token's lifespan and control per-token rate limits. When **creating** an API token, Okta assigns the permissions of the _currently logged-in user_ to the token. If, for example, you wish to use a Read Only Admin-scoped API token, you must log in to Okta as a user with the Read Only Admin role assigned. @@ -309,7 +309,7 @@ When **creating** an API token, Okta assigns the permissions of the _currently l Log into Okta with the account you'll use to generate the API token. - The account must have **Super Administrator,** the custom read-only role you created above, or a combination of **Read Only/App Admin/Group Admin** privileges. The permissions on the API token affects what features and functionality are available from C1. Before you begin, review the chart in [API permissions and C1 capabilities](/baton/okta#api-token-permissions-and-conductorone-capabilities) to make sure you're creating a token with the right permissions for your needs. + The account must have **Super Administrator,** the custom read-only role you created above, or a combination of **Read Only/App Admin/Group Admin** privileges. The permissions on the API token affects what features and functionality are available from C1.ai. Before you begin, review the chart in [API permissions and C1.ai capabilities](/baton/okta#api-token-permissions-and-conductorone-capabilities) to make sure you're creating a token with the right permissions for your needs. In the Okta console, navigate to **Security > API** and click **Tokens**. @@ -339,7 +339,7 @@ In Okta, navigate to **Applications** > **Applications** and click **Create App Select **API Services** and click **Next**. -Give the app a name (e.g., "C1 Integration") and click **Save**. +Give the app a name (e.g., "C1.ai Integration") and click **Save**. On the app's **General** tab, note the **Client ID**. @@ -394,7 +394,7 @@ If a sync finishes cleanly with no accounts, check the app's **Admin Roles** tab You'll need the **Client ID**, **Private Key**, and **Private Key ID** when configuring the connector. -**Private key format.** The **Okta Private Key** field in the C1 connector form holds a single line. Pasting a multi-line PEM into it replaces the line breaks with spaces, and the connector rejects the result with `oktaauth: parse private key: no PEM block found`. +**Private key format.** The **Okta Private Key** field in the C1.ai connector form holds a single line. Pasting a multi-line PEM into it replaces the line breaks with spaces, and the connector rejects the result with `oktaauth: parse private key: no PEM block found`. Enter the key on one line, writing each line break as a literal `\n`: @@ -423,17 +423,17 @@ The key must be RSA. Okta's DPoP implementation does not accept elliptic-curve k To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Okta 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Okta v2** and click **Add**. @@ -497,13 +497,13 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Okta connector is now pulling access data into C1. +**Done.** Your Okta connector is now pulling access data into C1.ai. **Follow these instructions to use the Okta 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -515,7 +515,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -616,17 +616,17 @@ 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 C1.ai 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 Okta connector to. Okta data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Okta connector to. Okta data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Okta connector is now pulling access data into C1. +**Done.** Your Okta connector is now pulling access data into C1.ai. ### What's next? -If Okta is your company's identity provider (meaning that it is used to SSO into other software), the connector 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 connectors for the SCIMed apps. +If Okta is your company's identity provider (meaning that it is used to SSO into other software), the connector sync will automatically create applications in C1.ai 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 connectors for the SCIMed apps. diff --git a/baton/onelogin.mdx b/baton/onelogin.mdx index eac63561..b020f255 100644 --- a/baton/onelogin.mdx +++ b/baton/onelogin.mdx @@ -1,17 +1,17 @@ --- title: "Set up an OneLogin connector" og:title: "Set up an OneLogin connector" -description: "C1 provides identity governance and just-in-time provisioning for OneLogin. Integrate your OneLogin 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 OneLogin. Integrate your OneLogin instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for OneLogin. Integrate your OneLogin instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for OneLogin. Integrate your OneLogin instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "OneLogin" --- -**This is an updated and improved version of the OneLogin connector!** If you're setting up OneLogin with C1 for the first time, you're in the right place. +**This is an updated and improved version of the OneLogin connector!** If you're setting up OneLogin with C1.ai for the first time, you're in the right place. -This page covers the OneLogin **connector**, which syncs and provisions access data for identity governance. It does not control how you sign in to C1. To set up signing in to C1 with your OneLogin account, see [Authenticate with OneLogin](/product/how-to/qs-set-up-c1#authenticate-with-onelogin). +This page covers the OneLogin **connector**, which syncs and provisions access data for identity governance. It does not control how you sign in to C1.ai. To set up signing in to C1.ai with your OneLogin account, see [Authenticate with OneLogin](/product/how-to/qs-set-up-c1#authenticate-with-onelogin). ## Capabilities @@ -70,7 +70,7 @@ When the new API credential is created, carefully copy and save the **Client ID* ## Enable automatic user mapping sync (optional) -When C1 grants or revokes a role, OneLogin's user mapping rules are not automatically re-evaluated. If you have mapping rules that should take effect immediately after a role change, you can enable **Apply user mappings**. When enabled, the connector instructs OneLogin to re-evaluate and apply all user mapping rules immediately after every role grant or revoke. +When C1.ai grants or revokes a role, OneLogin's user mapping rules are not automatically re-evaluated. If you have mapping rules that should take effect immediately after a role change, you can enable **Apply user mappings**. When enabled, the connector instructs OneLogin to re-evaluate and apply all user mapping rules immediately after every role grant or revoke. This feature requires a custom user field named `c1_last_action` to exist in your OneLogin account before you enable it. @@ -105,17 +105,17 @@ Once the field exists, enable the **Apply user mappings** option when configurin To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of OneLogin 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **OneLogin v2** and click **Add**. @@ -157,13 +157,13 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your OneLogin connector is now pulling access data into C1. +**Done.** Your OneLogin connector is now pulling access data into C1.ai. **Follow these instructions to use the OneLogin 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -175,7 +175,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -273,18 +273,18 @@ 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 C1.ai 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 OneLogin connector to. OneLogin data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the OneLogin connector to. OneLogin data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your OneLogin connector is now pulling access data into C1. +**Done.** Your OneLogin connector is now pulling access data into C1.ai. ### What's next? -If OneLogin is your company's identity provider (meaning that it is used to SSO into other software), the connector 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 connectors for the SCIMed apps. +If OneLogin is your company's identity provider (meaning that it is used to SSO into other software), the connector sync will automatically create applications in C1.ai 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 connectors for the SCIMed apps. diff --git a/baton/openai.mdx b/baton/openai.mdx index 26490d3b..a2d690e9 100644 --- a/baton/openai.mdx +++ b/baton/openai.mdx @@ -1,8 +1,8 @@ --- title: "Set up OpenAI connector" og:title: "Set up OpenAI connector" -description: "C1 provides identity governance and just-in-time provisioning for OpenAI. Integrate your OpenAI 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 OpenAI. Integrate your OpenAI instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for OpenAI. Integrate your OpenAI instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for OpenAI. Integrate your OpenAI instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "OpenAI" --- @@ -38,7 +38,7 @@ sidebarTitle: "OpenAI" -**Archived projects are not synced.** The connector only syncs active (non-archived) projects. Service accounts, groups, and role assignments that exist only under an archived project will not appear in C1. +**Archived projects are not synced.** The connector only syncs active (non-archived) projects. Service accounts, groups, and role assignments that exist only under an archived project will not appear in C1.ai. @@ -70,7 +70,7 @@ sidebarTitle: "OpenAI" -**Invitation counts fluctuate between syncs.** Pending and disabled invitations naturally come and go as users accept, expire, or are revoked. C1 skips sync anomaly detection on the Invitation resource type to avoid false-positive alerts from these expected changes. +**Invitation counts fluctuate between syncs.** Pending and disabled invitations naturally come and go as users accept, expire, or are revoked. C1.ai skips sync anomaly detection on the Invitation resource type to avoid false-positive alerts from these expected changes. **Additional functionality:** @@ -118,11 +118,11 @@ The key endpoints are: - **Modify project user role**: `POST /v1/organization/projects/{project_id}/users/{user_id}` — update a user's project role - **Remove user from project**: `DELETE /v1/organization/projects/{project_id}/users/{user_id}` -The C1 OpenAI connector uses the Admin API to manage project memberships. When you configure C1 to provision access to OpenAI projects, C1 handles these API calls for you, filling the gap that SCIM leaves for project-level access. +The C1.ai OpenAI connector uses the Admin API to manage project memberships. When you configure C1.ai to provision access to OpenAI projects, C1.ai handles these API calls for you, filling the gap that SCIM leaves for project-level access. ### What SCIM provides vs. what requires the Admin API -| Capability | SCIM | Admin API (via C1) | +| Capability | SCIM | Admin API (via C1.ai) | | :--- | :--- | :--- | | Provision user into organization | | | | Deprovision user from organization | | | @@ -132,7 +132,7 @@ The C1 OpenAI connector uses the Admin API to manage project memberships. When y | Map IdP groups to projects | | | -Neither SCIM nor the Admin API currently supports automatically mapping IdP groups to OpenAI projects. To assign users to projects, use C1's provisioning capabilities with the OpenAI connector, which calls the Admin API on your behalf. +Neither SCIM nor the Admin API currently supports automatically mapping IdP groups to OpenAI projects. To assign users to projects, use C1.ai's provisioning capabilities with the OpenAI connector, which calls the Admin API on your behalf. ## Gather OpenAI configuration information @@ -162,18 +162,18 @@ See the OpenAI docs for more information: [Admin API Keys documentation](https:/ To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of OpenAI 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **OpenAI** and click **Add**. @@ -206,14 +206,14 @@ To complete this task, you'll need: -**Done.** Your OpenAI connector is now pulling access data into C1. +**Done.** Your OpenAI connector is now pulling access data into C1.ai. **Follow these instructions to use the OpenAI 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -223,7 +223,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -315,14 +315,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 C1.ai 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 OpenAI connector to. OpenAI data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the OpenAI connector to. OpenAI data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your OpenAI connector is now pulling access data into C1. +**Done.** Your OpenAI connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/opensearch.mdx b/baton/opensearch.mdx index f555e4e7..3ea24284 100644 --- a/baton/opensearch.mdx +++ b/baton/opensearch.mdx @@ -1,8 +1,8 @@ --- title: "Set up an OpenSearch connector" og:title: "Set up an OpenSearch connector" -description: "C1 provides identity governance for OpenSearch. Integrate your OpenSearch instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." -og:description: "C1 provides identity governance for OpenSearch. Integrate your OpenSearch instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance for OpenSearch. Integrate your OpenSearch instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance for OpenSearch. Integrate your OpenSearch instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "OpenSearch" --- @@ -51,17 +51,17 @@ If your OpenSearch cluster uses a custom certificate, you'll also need: To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of OpenSearch 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **OpenSearch** and click **Add**. @@ -122,13 +122,13 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your OpenSearch connector is now pulling access data into C1. +**Done.** Your OpenSearch connector is now pulling access data into C1.ai. **Follow these instructions to use the OpenSearch 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -138,7 +138,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -235,14 +235,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 C1.ai 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 OpenSearch connector to. OpenSearch data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the OpenSearch connector to. OpenSearch data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your OpenSearch connector is now pulling access data into C1. +**Done.** Your OpenSearch connector is now pulling access data into C1.ai. diff --git a/baton/opsgenie.mdx b/baton/opsgenie.mdx index 19076ccd..fab4cfca 100644 --- a/baton/opsgenie.mdx +++ b/baton/opsgenie.mdx @@ -1,13 +1,13 @@ --- title: "Set up an Atlassian Opsgenie connector" -description: "C1 provides identity governance for Opsgenie. Integrate your Opsgenie instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance for Opsgenie. Integrate your Opsgenie instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." og:title: "Set up an Atlassian Opsgenie connector" -og:description: "C1 provides identity governance for Opsgenie. Integrate your Opsgenie instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance for Opsgenie. Integrate your Opsgenie instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Atlassian Opsgenie" --- -**This is an updated and improved version of the Opsgenie integration!** If you're setting up an Opsgenie connector with C1 for the first time, you're in the right place. +**This is an updated and improved version of the Opsgenie integration!** If you're setting up an Opsgenie connector with C1.ai for the first time, you're in the right place. ## Capabilities @@ -59,17 +59,17 @@ A user with the **Owner** or **Admin** role (or a custom user role with the **Ed **To complete this task, you'll need:** -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Opsgenie 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Opsgenie** and click **Add**. @@ -102,12 +102,12 @@ A user with the **Owner** or **Admin** role (or a custom user role with the **Ed -**Done.** Your Opsgenie connector is now pulling access data into C1. +**Done.** Your Opsgenie connector is now pulling access data into C1.ai. **Follow these instructions to use the Opsgenie 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -117,7 +117,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -206,14 +206,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 C1.ai 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 Opsgenie connector to. Opsgenie data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Opsgenie connector to. Opsgenie data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Opsgenie connector is now pulling access data into C1. +**Done.** Your Opsgenie connector is now pulling access data into C1.ai. diff --git a/baton/oracle-cloud-infrastructure.mdx b/baton/oracle-cloud-infrastructure.mdx index fda3fb1d..ff879ab5 100644 --- a/baton/oracle-cloud-infrastructure.mdx +++ b/baton/oracle-cloud-infrastructure.mdx @@ -1,8 +1,8 @@ --- title: "Set up an Oracle Cloud Infrastructure connector" og:title: "Set up an Oracle Cloud Infrastructure connector" -description: "C1 provides identity governance for Oracle Cloud Infrastructure. Integrate your Oracle Cloud Infrastructure instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." -og:description: "C1 provides identity governance for Oracle Cloud Infrastructure. Integrate your Oracle Cloud Infrastructure instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance for Oracle Cloud Infrastructure. Integrate your Oracle Cloud Infrastructure instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance for Oracle Cloud Infrastructure. Integrate your Oracle Cloud Infrastructure instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Oracle Cloud Infrastructure" --- @@ -79,17 +79,17 @@ Download the public and private key files that are generated for you. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Oracle Cloud Infrastructure 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Oracle Cloud Infrastructure** and click **Add**. @@ -128,23 +128,23 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Oracle Cloud Infrastructure connector is now pulling access data into C1. +**Done.** Your Oracle Cloud Infrastructure connector is now pulling access data into C1.ai. **Follow these instructions to use the Oracle Cloud Infrastructure 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources -[Contact C1's support team](mailto:support@c1.ai) to download the latest version of the connector. +[Contact C1.ai's support team](mailto:support@c1.ai) to download the latest version of the connector. ### Step 1: Set up a new Oracle Cloud Infrastructure connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -241,14 +241,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 C1.ai 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 Cloud Infrastructure connector to. Oracle Cloud Infrastructure data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Oracle Cloud Infrastructure connector to. Oracle Cloud Infrastructure data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Oracle Cloud Infrastructure connector is now pulling access data into C1. +**Done.** Your Oracle Cloud Infrastructure connector is now pulling access data into C1.ai. diff --git a/baton/oracle-field-service.mdx b/baton/oracle-field-service.mdx index 97d322ff..8dc4b596 100644 --- a/baton/oracle-field-service.mdx +++ b/baton/oracle-field-service.mdx @@ -1,8 +1,8 @@ --- title: "Set up an Oracle Field Service connector" og:title: "Set up an Oracle Field Service connector" -description: "C1 provides identity governance for Oracle Field Service. Integrate your Oracle Field Service instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." -og:description: "C1 provides identity governance for Oracle Field Service. Integrate your Oracle Field Service instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance for Oracle Field Service. Integrate your Oracle Field Service instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance for Oracle Field Service. Integrate your Oracle Field Service instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Oracle Field Service" --- @@ -17,7 +17,7 @@ sidebarTitle: "Oracle Field Service" The Oracle Field Service connector supports [automatic account provisioning and deprovisioning](/product/admin/account-provisioning). -When a new account is created by C1, the account's password will be sent to a [vault](/product/admin/vaults). +When a new account is created by C1.ai, the account's password will be sent to a [vault](/product/admin/vaults). ### Entitlement provisioning @@ -46,7 +46,7 @@ In the left pane, click the **+** icon to add a new application. In the **New application** window, provide the following details: - * Application Name: A descriptive name you can easily recognize (for example, "C1 Connector"). + * Application Name: A descriptive name you can easily recognize (for example, "C1.ai Connector"). * Application ID: A unique identifier (for example, "c1-connector"). @@ -92,7 +92,7 @@ A window will appear with a list of available APIs. Select the following API: After adding this API, you must grant specific permissions for it. Navigate to the API's **Available entities** and select the following entities: - **Core API** - - User entity: Read/write (or Read if you do not want C1 to provision access) + - User entity: Read/write (or Read if you do not want C1.ai to provision access) - Resource entity: Read @@ -112,17 +112,17 @@ Once you have set the permissions for both APIs, click **Save** on the main appl To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Oracle Field Service 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Oracle Field Service** and click **Add**. @@ -161,13 +161,13 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Oracle Field Service connector is now pulling access data into C1. +**Done.** Your Oracle Field Service connector is now pulling access data into C1.ai. **Follow these instructions to use the Oracle Field Service 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -177,7 +177,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -275,14 +275,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 C1.ai 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 Field Service connector to. Oracle Field Service data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Oracle Field Service connector to. Oracle Field Service data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Oracle Field Service connector is now pulling access data into C1. +**Done.** Your Oracle Field Service connector is now pulling access data into C1.ai. diff --git a/baton/oracle-fusion-cloud-hcm.mdx b/baton/oracle-fusion-cloud-hcm.mdx index 12948c97..f7203ce2 100644 --- a/baton/oracle-fusion-cloud-hcm.mdx +++ b/baton/oracle-fusion-cloud-hcm.mdx @@ -1,8 +1,8 @@ --- title: "Set up an Oracle Fusion Cloud HCM connector" og:title: "Set up an Oracle Fusion Cloud HCM connector" -description: "C1 provides identity governance for Oracle Fusion Cloud HCM. Integrate your Oracle Fusion Cloud HCM instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." -og:description: "C1 provides identity governance for Oracle Fusion Cloud HCM. Integrate your Oracle Fusion Cloud HCM instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance for Oracle Fusion Cloud HCM. Integrate your Oracle Fusion Cloud HCM instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance for Oracle Fusion Cloud HCM. Integrate your Oracle Fusion Cloud HCM instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Oracle Fusion Cloud HCM" --- @@ -75,17 +75,17 @@ The **Human Capital Management Integration Specialist** role on its own only inc To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Oracle Fusion Cloud HCM 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Oracle Fusion Cloud HCM** and click **Add**. @@ -118,23 +118,23 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Oracle Fusion Cloud HCM connector is now pulling access data into C1. +**Done.** Your Oracle Fusion Cloud HCM connector is now pulling access data into C1.ai. **Follow these instructions to use the Oracle Fusion Cloud HCM 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources -[Contact C1's support team](mailto:support@c1.ai) to download the latest version of the connector. +[Contact C1.ai's support team](mailto:support@c1.ai) to download the latest version of the connector. ### Step 1: Set up a new Oracle Fusion Cloud HCM connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -229,14 +229,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 C1.ai 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 Fusion Cloud HCM connector to. Oracle Fusion Cloud HCM data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Oracle Fusion Cloud HCM connector to. Oracle Fusion Cloud HCM data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Oracle Fusion Cloud HCM connector is now pulling access data into C1. +**Done.** Your Oracle Fusion Cloud HCM connector is now pulling access data into C1.ai. diff --git a/baton/oracle-idcs.mdx b/baton/oracle-idcs.mdx index c53bad16..2a1cb3b5 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: "C1.ai provides identity governance for Oracle Identity Cloud Service (IDCS). Integrate your Oracle IDCS instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance for Oracle Identity Cloud Service (IDCS). Integrate your Oracle IDCS instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Oracle Identity Cloud Service" --- @@ -21,11 +21,11 @@ sidebarTitle: "Oracle Identity Cloud Service" The Oracle IDCS connector supports [automatic account provisioning and deprovisioning](/product/admin/account-provisioning). -The connector also supports **account lifecycle actions** (enable and disable account) and **attribute push** to update user profile fields directly from C1. +The connector also supports **account lifecycle actions** (enable and disable account) and **attribute push** to update user profile fields directly from C1.ai. *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 C1.ai. ## Actions @@ -37,7 +37,7 @@ The OAuth2 confidential application in Oracle IDCS must have the **Identity Doma ### Account lifecycle actions -Use the **Automation** tab on the Oracle IDCS connector page in C1 to enable or disable user accounts: +Use the **Automation** tab on the Oracle IDCS connector page in C1.ai to enable or disable user accounts: | Action | Description | | :--- | :--- | @@ -48,14 +48,14 @@ Both actions use SCIM PATCH to toggle the `active` field on the target user. ### Attribute push -The connector supports pushing updates to the following user profile fields directly from a user's profile page in C1: +The connector supports pushing updates to the following user profile fields directly from a user's profile page in C1.ai: - First Name - Last Name - Display Name - Email -To push an attribute, navigate to an Oracle IDCS user's profile in C1 and use the **Push Attribute** option. Updates are applied via SCIM PATCH. +To push an attribute, navigate to an Oracle IDCS user's profile in C1.ai and use the **Push Attribute** option. Updates are applied via SCIM PATCH. Email updates append the new address as a work email rather than replacing the existing emails array. @@ -93,7 +93,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 "C1.ai", then click **Next**. On the **OAuth Configuration** page, click **Edit OAuth configuration** and select **Configure this application as a client**. @@ -127,17 +127,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 C1.ai - 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Oracle IDCS** and click **Add**. @@ -178,23 +178,23 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Oracle IDCS connector is now pulling access data into C1. +**Done.** Your Oracle IDCS connector is now pulling access data into C1.ai. **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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources -[Contact C1's support team](mailto:support@c1.ai) to download the latest version of the connector. +[Contact C1.ai's support team](mailto:support@c1.ai) to download the latest version of the connector. ### Step 1: Set up a new Oracle IDCS connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -292,13 +292,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 C1.ai 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 C1.ai, 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. -**Done.** Your Oracle IDCS connector is now pulling access data into C1. +**Done.** Your Oracle IDCS connector is now pulling access data into C1.ai. diff --git a/baton/ory.mdx b/baton/ory.mdx index 249ea7ea..fa5f2580 100644 --- a/baton/ory.mdx +++ b/baton/ory.mdx @@ -1,12 +1,12 @@ --- title: "Set up an Ory connector" og:title: "Set up an Ory connector" -description: "C1 provides identity governance for Ory. Integrate your Ory project with C1 for unified visibility over user identities." -og:description: "C1 provides identity governance for Ory. Integrate your Ory project with C1 for unified visibility over user identities." +description: "C1.ai provides identity governance for Ory. Integrate your Ory project with C1.ai for unified visibility over user identities." +og:description: "C1.ai provides identity governance for Ory. Integrate your Ory project with C1.ai for unified visibility over user identities." sidebarTitle: "Ory" --- -C1 provides identity governance for Ory. Integrate your Ory project with C1 +C1.ai provides identity governance for Ory. Integrate your Ory project with C1.ai for unified visibility over user identities synced from the Ory Admin API. ## Capabilities @@ -55,11 +55,11 @@ keys are not authorized for the project's `/admin/identities` endpoint. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -105,7 +105,7 @@ keys are not authorized for the project's `/admin/identities` endpoint. - **Done.** Your Ory connector is now pulling identity data into C1. + **Done.** Your Ory connector is now pulling identity data into C1.ai. @@ -132,7 +132,7 @@ keys are not authorized for the project's `/admin/identities` endpoint. - **Done.** Your Ory connector is now pulling identity data into C1. + **Done.** Your Ory connector is now pulling identity data into C1.ai. diff --git a/baton/outline.mdx b/baton/outline.mdx index 2ba3ad1f..8eb53c26 100644 --- a/baton/outline.mdx +++ b/baton/outline.mdx @@ -1,13 +1,13 @@ --- title: "Set up an Outline connector" og:title: "Set up an Outline connector" -description: "C1 provides identity governance for Outline. Integrate your Outline instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Outline. Integrate your Outline instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Outline. Integrate your Outline instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Outline. Integrate your Outline instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Outline" --- -C1 provides identity governance for Outline. Integrate your Outline -instance with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Outline. Integrate your Outline +instance with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -70,17 +70,17 @@ and `groups.memberships`. identity and group membership. - The connector requests users of every status. If your Outline server excludes suspended or invited users from those listings, those users will - not appear in C1 until they are active. + not appear in C1.ai until they are active. ## Configure the Outline connector - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -125,7 +125,7 @@ and `groups.memberships`. - **Done.** Your Outline connector is now pulling access data into C1. + **Done.** Your Outline connector is now pulling access data into C1.ai. @@ -149,6 +149,6 @@ and `groups.memberships`. - **Done.** Your Outline connector is now pulling access data into C1. + **Done.** Your Outline connector is now pulling access data into C1.ai. diff --git a/baton/outreach.mdx b/baton/outreach.mdx index f241a9c1..ce74eaa3 100644 --- a/baton/outreach.mdx +++ b/baton/outreach.mdx @@ -1,8 +1,8 @@ --- title: "Set up an Outreach connector" og:title: "Set up an Outreach connector" -description: "C1 provides identity governance and just-in-time provisioning for Outreach. Integrate your Outreach 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 Outreach. Integrate your Outreach instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Outreach. Integrate your Outreach instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Outreach. Integrate your Outreach instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Outreach" --- @@ -18,7 +18,7 @@ The Outreach connector supports [automatic account provisioning and deprovisioni ### 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 C1.ai 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 | |-------------|-------------------|-------------| @@ -44,7 +44,7 @@ A user who is an **admin** in Outreach must perform this task. Click **Create app**. - Give the new app a name, such as "C1", then click **Create**. + Give the new app a name, such as "C1.ai", then click **Create**. The new app's details view opens. Click **Feature selection**. @@ -90,16 +90,16 @@ Save the app. If desired, create a release. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Outreach 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Outreach** and click **Add**. @@ -128,9 +128,9 @@ Paste the the OAuth application ID and application secret into the **Client ID** Click **Login with OAuth**. -Log into Outreach and authorize C1. +Log into Outreach and authorize C1.ai. - After authorizing, you'll be redirected back to the C1 integrations page, where an "Authorized as" message is now printed. + After authorizing, you'll be redirected back to the C1.ai integrations page, where an "Authorized as" message is now printed. **Remember:** Reauthorize the connector if you change the permissions that are granted to the Outreach OAuth app. @@ -143,12 +143,12 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Outreach connector is now pulling access data into C1. +**Done.** Your Outreach connector is now pulling access data into C1.ai. **Follow these instructions to use the Outreach 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -159,7 +159,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an ### Step 1: Set up a new Outreach connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -251,14 +251,14 @@ spec: ### 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. +Create a namespace in which to run C1.ai 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 Outreach connector to. Outreach data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Outreach connector to. Outreach data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Outreach connector is now pulling access data into C1. +**Done.** Your Outreach connector is now pulling access data into C1.ai. diff --git a/baton/pagerduty.mdx b/baton/pagerduty.mdx index 8bf57c88..7e2da83b 100644 --- a/baton/pagerduty.mdx +++ b/baton/pagerduty.mdx @@ -1,8 +1,8 @@ --- title: Set up a PagerDuty connector -og:title: Set up a PagerDuty connector - C1 docs -og:description: Integrate your PagerDuty 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 PagerDuty. Integrate your PagerDuty instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a PagerDuty connector - C1.ai docs +og:description: Integrate your PagerDuty instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance for PagerDuty. Integrate your PagerDuty instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: PagerDuty --- @@ -39,7 +39,7 @@ Sign into PagerDuty and navigate to **Developer Tools > Integrations > API Acces Click **Create New API Key**. -Enter a description for the key, such as "C1 integration". +Enter a description for the key, such as "C1.ai integration". Click **Create Key**. @@ -56,17 +56,17 @@ Carefully save the newly generated API key. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of PagerDuty 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **PagerDuty** and click **Add**. @@ -98,12 +98,12 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your PagerDuty connector is now pulling access data into C1. +**Done.** Your PagerDuty connector is now pulling access data into C1.ai. **Follow these instructions to use the PagerDuty 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -113,7 +113,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -205,13 +205,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 C1.ai 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 PagerDuty connector to. PagerDuty data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the PagerDuty connector to. PagerDuty data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your PagerDuty connector is now pulling access data into C1. +**Done.** Your PagerDuty connector is now pulling access data into C1.ai. diff --git a/baton/pagertree.mdx b/baton/pagertree.mdx index 49af3602..903670b2 100644 --- a/baton/pagertree.mdx +++ b/baton/pagertree.mdx @@ -1,15 +1,15 @@ --- title: "Set up a PagerTree connector" og:title: "Set up a PagerTree connector" -description: "C1 provides identity governance for PagerTree. Integrate your PagerTree account with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for PagerTree. Integrate your PagerTree account with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for PagerTree. Integrate your PagerTree account with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for PagerTree. Integrate your PagerTree account with C1.ai for unified visibility and governance over user access." sidebarTitle: "PagerTree" --- {/* stargate */} -C1 provides identity governance for PagerTree. Integrate your PagerTree account -with C1 for unified visibility and governance over the users who can access +C1.ai provides identity governance for PagerTree. Integrate your PagerTree account +with C1.ai for unified visibility and governance over the users who can access your PagerTree account. ## Capabilities @@ -50,11 +50,11 @@ permissions in PagerTree. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -98,7 +98,7 @@ permissions in PagerTree. - **Done.** Your PagerTree connector is now pulling access data into C1. + **Done.** Your PagerTree connector is now pulling access data into C1.ai. @@ -121,6 +121,6 @@ permissions in PagerTree. - **Done.** Your PagerTree connector is now pulling access data into C1. + **Done.** Your PagerTree connector is now pulling access data into C1.ai. diff --git a/baton/palantir.mdx b/baton/palantir.mdx index 5af392cb..f43006b0 100644 --- a/baton/palantir.mdx +++ b/baton/palantir.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Palantir connector" og:title: "Set up a Palantir connector" -description: "C1 provides identity governance for Palantir Foundry. Integrate your Foundry stack with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Palantir Foundry. Integrate your Foundry stack with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Palantir Foundry. Integrate your Foundry stack with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Palantir Foundry. Integrate your Foundry stack with C1.ai for unified visibility and governance over user access." sidebarTitle: "Palantir" --- -C1 provides identity governance for Palantir Foundry. Integrate your Foundry -stack with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Palantir Foundry. Integrate your Foundry +stack with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -23,12 +23,12 @@ provisioning is deprovisioning only: Foundry has no create-user API, so the connector cannot create accounts. Deleting a user calls Foundry's delete-user endpoint. What happens next depends on your Foundry configuration: if Foundry hard-deletes the account, it no longer appears in the sync; if Foundry marks the -account deleted instead, it keeps syncing into C1 as a disabled account. +account deleted instead, it keeps syncing into C1.ai as a disabled account. **A group can contain both users and other groups.** Nested-group members are surfaced as expandable grants, so a user who reaches a group only through a -nested group still shows that access in C1. +nested group still shows that access in C1.ai. ## Gather Palantir credentials @@ -65,11 +65,11 @@ requires Foundry administrator access. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -108,7 +108,7 @@ requires Foundry administrator access. - **Done.** Your Palantir connector is now pulling access data into C1. + **Done.** Your Palantir connector is now pulling access data into C1.ai. @@ -132,6 +132,6 @@ requires Foundry administrator access. - **Done.** Your Palantir connector is now pulling access data into C1. + **Done.** Your Palantir connector is now pulling access data into C1.ai. diff --git a/baton/palo-alto-cortex.mdx b/baton/palo-alto-cortex.mdx index ccff5853..7be65311 100644 --- a/baton/palo-alto-cortex.mdx +++ b/baton/palo-alto-cortex.mdx @@ -1,8 +1,8 @@ --- title: Set up a Palo Alto Networks Cortex XDR connector -og:title: Set up a Palo Alto Networks Cortex XDR connector - C1 docs -og:description: Integrate your Cortex XDR 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 Cortex XDR. Integrate your Cortex XDR instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a Palo Alto Networks Cortex XDR connector - C1.ai docs +og:description: Integrate your Cortex XDR instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance and just-in-time provisioning for Cortex XDR. Integrate your Cortex XDR instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: "Palo Alto Networks Cortex XDR" --- @@ -67,18 +67,18 @@ Find and copy the key's **ID**. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Cortex XDR 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Cortex XDR** and click **Add**. @@ -110,14 +110,14 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Cortex XDR connector is now pulling access data into C1. +**Done.** Your Cortex XDR connector is now pulling access data into C1.ai. **Follow these instructions to use the Cortex XDR 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -127,7 +127,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -224,13 +224,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 C1.ai 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 Cortex XDR connector to. Cortex XDR data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Cortex XDR connector to. Cortex XDR data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Cortex XDR connector is now pulling access data into C1. +**Done.** Your Cortex XDR connector is now pulling access data into C1.ai. diff --git a/baton/panda-doc.mdx b/baton/panda-doc.mdx index b726ca53..c9aeddcd 100644 --- a/baton/panda-doc.mdx +++ b/baton/panda-doc.mdx @@ -1,8 +1,8 @@ --- title: Set up a PandaDoc connector -og:title: Set up a PandaDoc connector - C1 docs -og:description: "C1 provides identity governance for PandaDoc. Integrate your PandaDoc instance with C1 for unified visibility and governance over user access." -description: "C1 provides identity governance for PandaDoc. Integrate your PandaDoc instance with C1 for unified visibility and governance over user access." +og:title: Set up a PandaDoc connector - C1.ai docs +og:description: "C1.ai provides identity governance for PandaDoc. Integrate your PandaDoc instance with C1.ai for unified visibility and governance over user access." +description: "C1.ai provides identity governance for PandaDoc. Integrate your PandaDoc instance with C1.ai for unified visibility and governance over user access." sidebarTitle: PandaDoc --- @@ -62,17 +62,17 @@ If **Dev Center** doesn't appear in your PandaDoc navigation: To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of PandaDoc 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **PandaDoc** and click **Add**. @@ -108,12 +108,12 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your PandaDoc connector is now pulling access data into C1. +**Done.** Your PandaDoc connector is now pulling access data into C1.ai. **Follow these instructions to use the PandaDoc 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -123,7 +123,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -215,13 +215,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 C1.ai 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 PandaDoc connector to. PandaDoc data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the PandaDoc connector to. PandaDoc data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your PandaDoc connector is now pulling access data into C1. +**Done.** Your PandaDoc connector is now pulling access data into C1.ai. diff --git a/baton/panther.mdx b/baton/panther.mdx index b029f243..db793bde 100644 --- a/baton/panther.mdx +++ b/baton/panther.mdx @@ -1,8 +1,8 @@ --- title: Set up a Panther connector -og:title: Set up a Panther connector - C1 docs -og:description: Integrate your Panther 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 Panther. Integrate your Panther instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a Panther connector - C1.ai docs +og:description: Integrate your Panther instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance for Panther. Integrate your Panther instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: Panther --- @@ -37,14 +37,14 @@ The GraphQL API URL format depends on your deployment type: - **SaaS**: `https://api.{your-tenant}.runpanther.net/public/graphql` - **Self-hosted**: `https://{your-domain}/v1/public/graphql` -The C1 connector requires this URL to authenticate and sync data. +The C1.ai connector requires this URL to authenticate and sync data. Click **Create New Token**. -Give the API token a name, such as "C1". +Give the API token a name, such as "C1.ai". @@ -69,19 +69,19 @@ Carefully copy and save the 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 C1.ai - Access to the set of Panther 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 C1.ai.** -**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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Panther** and click **Add**. @@ -113,12 +113,12 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Panther connector is now pulling access data into C1. +**Done.** Your Panther connector is now pulling access data into C1.ai. **Follow these instructions to use the Panther 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -128,7 +128,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -218,14 +218,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 C1.ai 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 Panther connector to. Panther data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Panther connector to. Panther data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Panther connector is now pulling access data into C1. +**Done.** Your Panther connector is now pulling access data into C1.ai. diff --git a/baton/paycom.mdx b/baton/paycom.mdx index fd06cc49..918c5e02 100644 --- a/baton/paycom.mdx +++ b/baton/paycom.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Paycom connector" og:title: "Set up a Paycom connector" -description: "C1 provides identity governance for Paycom. Integrate your Paycom instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Paycom. Integrate your Paycom instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Paycom. Integrate your Paycom instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Paycom. Integrate your Paycom instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Paycom" --- -C1 provides identity governance for Paycom. Integrate your Paycom -instance with C1 for unified visibility and governance over employee access. +C1.ai provides identity governance for Paycom. Integrate your Paycom +instance with C1.ai for unified visibility and governance over employee access. The Paycom connector is read-only: it syncs employees as identities. Paycom's API exposes no write endpoints for employee accounts or assignments, so the @@ -58,11 +58,11 @@ the automation team. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -110,7 +110,7 @@ the automation team. - **Done.** Your Paycom connector is now pulling access data into C1. + **Done.** Your Paycom connector is now pulling access data into C1.ai. @@ -139,6 +139,6 @@ the automation team. - **Done.** Your Paycom connector is now pulling access data into C1. + **Done.** Your Paycom connector is now pulling access data into C1.ai. diff --git a/baton/paylocity-weblink.mdx b/baton/paylocity-weblink.mdx index 5f05a036..2425e82b 100644 --- a/baton/paylocity-weblink.mdx +++ b/baton/paylocity-weblink.mdx @@ -1,15 +1,15 @@ --- title: "Set up a Paylocity Weblink connector" -og:title: "Set up a Paylocity Weblink connector - C1 docs" -og:description: "Integrate your Paylocity Weblink instance with C1 to run user access reviews, enable just-in-time access requests, and automatically provision and deprovision access." -description: "C1 provides identity governance for Paylocity Weblink. Integrate your Paylocity Weblink instance with C1 to run user access reviews (UARs) and sync employee data." +og:title: "Set up a Paylocity Weblink connector - C1.ai docs" +og:description: "Integrate your Paylocity Weblink instance with C1.ai to run user access reviews, enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance for Paylocity Weblink. Integrate your Paylocity Weblink instance with C1.ai to run user access reviews (UARs) and sync employee data." sidebarTitle: "Paylocity Weblink" --- **Paylocity has two separate API systems.** This connector uses the **Weblink (legacy) API v2**, which does not return sensitive PII fields (SSN, DOB, ethnicity). There is a separate [Paylocity connector](/baton/paylocity) that uses the NextGen API. -Use this connector if you need to avoid transmitting sensitive PII data to C1. +Use this connector if you need to avoid transmitting sensitive PII data to C1.ai. {/* AUTO-GENERATED:START - capabilities @@ -27,7 +27,7 @@ The Paylocity Weblink connector syncs the following resources: ### 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 C1.ai 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 | | ----------- | ------------------ | ----------- | @@ -36,9 +36,9 @@ Connector actions are custom capabilities that extend C1 automations with app-sp The `create_user` action mirrors the [Paylocity Add Employee](https://developer.paylocity.com/integrations/reference/add-employee) endpoint. Only `first_name` and `last_name` are required by the API; all other fields are optional. If `employee_status` is not provided, the action always defaults it to `A` (Active) so the new employee lands as a usable record. -The action uses the v2 direct-create endpoint rather than the v1 `/onboarding/employees` flow. The v1 flow stages an employee that requires manual graduation in the Paylocity admin UI; the goal here is to produce a fully-usable employee from a single C1 automation step, not a draft awaiting human review. +The action uses the v2 direct-create endpoint rather than the v1 `/onboarding/employees` flow. The v1 flow stages an employee that requires manual graduation in the Paylocity admin UI; the goal here is to produce a fully-usable employee from a single C1.ai automation step, not a draft awaiting human review. -Compensation fields (pay rate, salary, pay type) are intentionally not exposed here. Those changes go through HR/payroll approval workflows in Paylocity and should be set in the Paylocity admin UI rather than provisioned through C1. +Compensation fields (pay rate, salary, pay type) are intentionally not exposed here. Those changes go through HR/payroll approval workflows in Paylocity and should be set in the Paylocity admin UI rather than provisioned through C1.ai. Reactivation (Terminated → Active) is not supported. The Paylocity Weblink API rejects that transition; customers who need to re-enable a terminated employee must do so through the Paylocity admin portal. @@ -86,17 +86,17 @@ The **Company ID** must include the full alphanumeric value with its suffix (e.g To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Paylocity Weblink 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -148,13 +148,13 @@ To complete this task, you'll need: - **Done.** Your Paylocity Weblink connector is now pulling access data into C1. + **Done.** Your Paylocity Weblink connector is now pulling access data into C1.ai. **Follow these instructions to use the [Paylocity Weblink](https://github.com/ConductorOne/baton-paylocity-weblink) 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. + When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1.ai, automatically syncing and uploading data at regular intervals. ### Resources @@ -166,7 +166,7 @@ To complete this task, you'll need: - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -266,15 +266,15 @@ To complete this task, you'll need: - 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 C1.ai 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 Paylocity Weblink connector to. Paylocity Weblink data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Paylocity Weblink connector to. Paylocity Weblink data should be found on the **Entitlements** and **Accounts** tabs. - **Done.** Your Paylocity Weblink connector is now pulling access data into C1. + **Done.** Your Paylocity Weblink connector is now pulling access data into C1.ai. diff --git a/baton/paylocity.mdx b/baton/paylocity.mdx index e699282e..5bbce3df 100644 --- a/baton/paylocity.mdx +++ b/baton/paylocity.mdx @@ -1,8 +1,8 @@ --- title: Set up a Paylocity connector -og:title: Set up a Paylocity connector - C1 docs -og:description: "C1 provides identity governance for Paylocity. Integrate your Paylocity instance with C1 for unified visibility and governance over user access." -description: "C1 provides identity governance for Paylocity. Integrate your Paylocity instance with C1 for unified visibility and governance over user access." +og:title: Set up a Paylocity connector - C1.ai docs +og:description: "C1.ai provides identity governance for Paylocity. Integrate your Paylocity instance with C1.ai for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Paylocity. Integrate your Paylocity instance with C1.ai for unified visibility and governance over user access." sidebarTitle: Paylocity --- @@ -26,7 +26,7 @@ Configuring the connector requires you to pass in credentials generated in Paylo To set up the Paylocity connector, you'll need: * Client ID and client secret, which are issued by Paylocity when you request API access -* Company ID for the Paylocity entity you want to integrate with C1 +* Company ID for the Paylocity entity you want to integrate with C1.ai * Base API gateway URL of your Paylocity API environment **Done.** Next, move on to the connector configuration instructions. @@ -36,17 +36,17 @@ To set up the Paylocity connector, you'll need: To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Paylocity 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Paylocity** and click **Add**. @@ -78,13 +78,13 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Paylocity connector is now pulling access data into C1. +**Done.** Your Paylocity connector is now pulling access data into C1.ai. **Follow these instructions to use the Paylocity connector 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -94,7 +94,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -187,13 +187,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 C1.ai 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 Paylocity connector to. Paylocity data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Paylocity connector to. Paylocity data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Paylocity connector is now pulling access data into C1. +**Done.** Your Paylocity connector is now pulling access data into C1.ai. diff --git a/baton/percipio.mdx b/baton/percipio.mdx index 5d375bdc..639780c0 100644 --- a/baton/percipio.mdx +++ b/baton/percipio.mdx @@ -1,8 +1,8 @@ --- title: Set up a Percipio connector -og:title: Set up a Percipio connector - C1 docs -og:description: "C1 provides identity governance for Percipio. Integrate your Percipio instance with C1 for unified visibility and governance over user access." -description: "C1 provides identity governance for Percipio. Integrate your Percipio instance with C1 for unified visibility and governance over user access." +og:title: Set up a Percipio connector - C1.ai docs +og:description: "C1.ai provides identity governance for Percipio. Integrate your Percipio instance with C1.ai for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Percipio. Integrate your Percipio instance with C1.ai for unified visibility and governance over user access." sidebarTitle: Percipio --- @@ -17,13 +17,13 @@ sidebarTitle: Percipio Configuring the connector requires you to pass in credentials generated in Percipio. Gather these credentials before you move on. -To set up the integration with C1, you'll need: +To set up the integration with C1.ai, you'll need: - Your Percipio organization UUID - The API bearer token associated with a [Percipio service account](https://documentation.skillsoft.com/en_us/pes/Integration/int_api_rest_authentication.htm) -Please work with your Skillsoft Account Team to set up a service account for the C1 integration and gather these credentials. +Please work with your Skillsoft Account Team to set up a service account for the C1.ai integration and gather these credentials. **Done.** Next, move on to the connector configuration instructions. @@ -32,18 +32,18 @@ Please work with your Skillsoft Account Team to set up a service account for the To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Percipio 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Percipio** and click **Add**. @@ -72,7 +72,7 @@ In the **Organization ID** field, enter your Percipio organization UUID. In the **API Token** field, enter the token associated with the Percipio service account set up for this integration. -**Optional.** In the **Course IDs** field, add the ID numbers of the courses you want to sync. If no course numbers are entered, C1 will sync all available courses. +**Optional.** In the **Course IDs** field, add the ID numbers of the courses you want to sync. If no course numbers are entered, C1.ai will sync all available courses. Click **Save**. @@ -81,13 +81,13 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Percipio connector is now pulling access data into C1. +**Done.** Your Percipio connector is now pulling access data into C1.ai. **Follow these instructions to use the Percipio 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -97,7 +97,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -188,13 +188,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 C1.ai 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 Percipio connector to. Percipio data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Percipio connector to. Percipio data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Percipio connector is now pulling access data into C1. +**Done.** Your Percipio connector is now pulling access data into C1.ai. diff --git a/baton/perplexity.mdx b/baton/perplexity.mdx index 4358c486..b1874a4d 100644 --- a/baton/perplexity.mdx +++ b/baton/perplexity.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Perplexity connector" og:title: "Set up a Perplexity connector" -description: "C1 provides identity governance and just-in-time provisioning for Perplexity. Integrate your Perplexity 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 Perplexity. Integrate your Perplexity Enterprise instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for Perplexity. Integrate your Perplexity Enterprise instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Perplexity. Integrate your Perplexity Enterprise instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "Perplexity" --- @@ -30,17 +30,17 @@ The Perplexity connector syncs the following resources: #### Account creation fields -When provisioning a new Perplexity user account, C1 prompts for the following field: +When provisioning a new Perplexity user account, C1.ai 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. Enter names in "First Last" order — the connector does not detect locale-native orderings such as family-name-first. | -The user's email address is provided automatically by C1 and is used as the SCIM username. No password is required — Perplexity Enterprise authenticates users through SSO, so accounts are created without credentials. +The user's email address is provided automatically by C1.ai and is used as the SCIM username. No password is required — Perplexity Enterprise authenticates users through SSO, so accounts are created without credentials. ### 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 C1.ai 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 | |-------------|-------------------|-------------| @@ -56,7 +56,7 @@ Perplexity Enterprise uses a two-tier role model: Role assignment is driven entirely through your identity provider (IdP). In your IdP (Okta, Microsoft Entra ID, or OneLogin), you create two groups — one mapped to the Admin role and one mapped to the Member role — and then add or remove users from those groups to grant or revoke their Perplexity role. -In C1, these IdP-pushed groups appear as the syncable, grantable resources. Granting a Perplexity user the "member" entitlement on the Admin group makes them a Perplexity Admin; revoking that entitlement (or moving them to the Member group) downgrades them to a Member. +In C1.ai, these IdP-pushed groups appear as the syncable, grantable resources. Granting a Perplexity user the "member" entitlement on the Admin group makes them a Perplexity Admin; revoking that entitlement (or moving them to the Member group) downgrades them to a Member. ## SCIM-only connector @@ -109,7 +109,7 @@ A Perplexity Enterprise administrator must perform this task. SCIM credentials a - In your identity provider, create two groups — one to map to the Perplexity **Admin** role and one to map to the **Member** role — and assign users to the appropriate group. These groups will be pushed to Perplexity via SCIM and will appear as syncable resources in C1. + In your identity provider, create two groups — one to map to the Perplexity **Admin** role and one to map to the **Member** role — and assign users to the appropriate group. These groups will be pushed to Perplexity via SCIM and will appear as syncable resources in C1.ai. @@ -126,18 +126,18 @@ For more information, see the [Perplexity SCIM documentation](https://www.perple To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the Perplexity SCIM 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -187,7 +187,7 @@ To complete this task, you'll need: - **Done.** Your Perplexity connector is now pulling access data into C1. + **Done.** Your Perplexity connector is now pulling access data into C1.ai. @@ -195,7 +195,7 @@ To complete this task, you'll need: **Follow these instructions to use the [Perplexity](https://github.com/ConductorOne/baton-perplexity) 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -207,7 +207,7 @@ To complete this task, you'll need: - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -308,15 +308,15 @@ To complete this task, you'll need: - 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 C1.ai 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 Perplexity connector to. Perplexity data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Perplexity connector to. Perplexity data should be found on the **Entitlements** and **Accounts** tabs. - **Done.** Your Perplexity connector is now pulling access data into C1. + **Done.** Your Perplexity connector is now pulling access data into C1.ai. diff --git a/baton/personio.mdx b/baton/personio.mdx index a98451cd..834a1d81 100644 --- a/baton/personio.mdx +++ b/baton/personio.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Personio connector" og:title: "Set up a Personio connector" -description: "C1 provides identity governance for Personio. Integrate your Personio instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Personio. Integrate your Personio instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Personio. Integrate your Personio instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Personio. Integrate your Personio instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Personio" --- @@ -24,7 +24,7 @@ role permissions. In Personio, open **Marketplace** > **Connected integrations** and create - or select a custom integration for C1. + or select a custom integration for C1.ai. @@ -41,7 +41,7 @@ role permissions. - Select the readable employee attributes that C1 should sync. Personio only + Select the readable employee attributes that C1.ai should sync. Personio only returns attributes allowed on the API credential. @@ -69,7 +69,7 @@ role permissions. ## Synced resource types -- **Persons**: Personio persons mapped as C1 users. Primary employment details +- **Persons**: Personio persons mapped as C1.ai users. Primary employment details are joined from the person's employments endpoint and added to the user profile. @@ -107,11 +107,11 @@ role permissions. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -159,7 +159,7 @@ role permissions. - **Done.** Your Personio connector is now pulling identity data into C1. + **Done.** Your Personio connector is now pulling identity data into C1.ai. @@ -168,7 +168,7 @@ role permissions. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -186,7 +186,7 @@ role permissions. - Configure C1 credentials and Personio credentials as environment + Configure C1.ai credentials and Personio credentials as environment variables: ```bash @@ -210,6 +210,6 @@ role permissions. - **Done.** Your Personio connector is now pulling identity data into C1. + **Done.** Your Personio connector is now pulling identity data into C1.ai. diff --git a/baton/ping-one.mdx b/baton/ping-one.mdx index 265700ea..d66d390f 100644 --- a/baton/ping-one.mdx +++ b/baton/ping-one.mdx @@ -1,8 +1,8 @@ --- title: Set up PingOne connector -og:title: Set up PingOne connector - C1 docs -og:description: Integrate your PingOne 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 PingOne. Integrate your PingOne instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up PingOne connector - C1.ai docs +og:description: Integrate your PingOne instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance and just-in-time provisioning for PingOne. Integrate your PingOne instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: PingOne --- @@ -13,7 +13,7 @@ We recommend closely monitoring workflows that use this connector and contacting -This page covers the PingOne **connector**, which syncs and provisions access data for identity governance. It does not control how you sign in to C1. To set up signing in to C1 with your PingOne account, see [Authenticate with PingOne](/product/how-to/qs-set-up-c1#authenticate-with-pingone). +This page covers the PingOne **connector**, which syncs and provisions access data for identity governance. It does not control how you sign in to C1.ai. To set up signing in to C1.ai with your PingOne account, see [Authenticate with PingOne](/product/how-to/qs-set-up-c1#authenticate-with-pingone). ## Capabilities @@ -58,18 +58,18 @@ This connector requires the following scopes: To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of PingOne 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **PingOne** and click **Add**. @@ -101,23 +101,23 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your PingOne connector is now pulling access data into C1. +**Done.** Your PingOne connector is now pulling access data into C1.ai. **Follow these instructions to use the PingOne 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources -[Contact C1's support team](mailto:support@c1.ai) to download the latest version of the connector. +[Contact C1.ai's support team](mailto:support@c1.ai) to download the latest version of the connector. ### Step 1: Set up a new PingOne connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -211,13 +211,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 C1.ai 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 ping-one connector to. ping-one data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the ping-one connector to. ping-one data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your PingOne connector is now pulling access data into C1. +**Done.** Your PingOne connector is now pulling access data into C1.ai. diff --git a/baton/pingboard.mdx b/baton/pingboard.mdx index fc20876c..3ebb53a1 100644 --- a/baton/pingboard.mdx +++ b/baton/pingboard.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Pingboard connector" og:title: "Set up a Pingboard connector" -description: "C1 provides identity governance for Pingboard. Integrate your Pingboard instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Pingboard. Integrate your Pingboard instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Pingboard. Integrate your Pingboard instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Pingboard. Integrate your Pingboard instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Pingboard" --- -C1 provides identity governance for Pingboard. Integrate your Pingboard -instance with C1 for unified visibility and governance over user access. The +C1.ai provides identity governance for Pingboard. Integrate your Pingboard +instance with C1.ai for unified visibility and governance over user access. The connector is read-only: it syncs users and groups and reports group membership, and never writes back to Pingboard. @@ -19,7 +19,7 @@ membership, and never writes back to Pingboard. |Groups||| Each group exposes a **member** entitlement, and the connector grants it to the -users in that group, so group membership is visible and reviewable in C1. +users in that group, so group membership is visible and reviewable in C1.ai. ## Gather Pingboard credentials @@ -53,11 +53,11 @@ pair. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -103,7 +103,7 @@ pair. - **Done.** Your Pingboard connector is now pulling access data into C1. + **Done.** Your Pingboard connector is now pulling access data into C1.ai. @@ -128,6 +128,6 @@ pair. - **Done.** Your Pingboard connector is now pulling access data into C1. + **Done.** Your Pingboard connector is now pulling access data into C1.ai. diff --git a/baton/pingfed.mdx b/baton/pingfed.mdx index cec8b1a2..392d26ce 100644 --- a/baton/pingfed.mdx +++ b/baton/pingfed.mdx @@ -1,8 +1,8 @@ --- title: Set up a PingFederate connector -og:title: Set up a PingFederate connector - C1 docs -og:description: Integrate your PingFederate 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 PingFederate. Integrate your PingFederate instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a PingFederate connector - C1.ai docs +og:description: Integrate your PingFederate instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance and just-in-time provisioning for PingFederate. Integrate your PingFederate instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: PingFederate --- @@ -35,18 +35,18 @@ To set up the PingFederate connector, you'll need: To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of PingFederate 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **PingFederate** and click **Add**. @@ -81,13 +81,13 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your PingFederate connector is now pulling access data into C1. +**Done.** Your PingFederate connector is now pulling access data into C1.ai. **Follow these instructions to use the PingFederate 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -97,7 +97,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -191,13 +191,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 C1.ai 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 PingFederate connector to. PingFederate data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the PingFederate connector to. PingFederate data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your PingFederate connector is now pulling access data into C1. +**Done.** Your PingFederate connector is now pulling access data into C1.ai. diff --git a/baton/pipedrive.mdx b/baton/pipedrive.mdx index 16ded8c8..62ed7ec7 100644 --- a/baton/pipedrive.mdx +++ b/baton/pipedrive.mdx @@ -1,9 +1,9 @@ --- title: Set up Pipedrive connector -og:title: Set up Pipedrive connector - C1 docs -og:description: "C1 provides identity governance for Pipedrive. Integrate your Pipedrive instance with C1 for unified visibility and governance over user access." +og:title: Set up Pipedrive connector - C1.ai docs +og:description: "C1.ai provides identity governance for Pipedrive. Integrate your Pipedrive instance with C1.ai for unified visibility and governance over user access." sidebarTitle: Pipedrive -description: "C1 provides identity governance for Pipedrive. Integrate your Pipedrive instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Pipedrive. Integrate your Pipedrive instance with C1.ai for unified visibility and governance over user access." --- @@ -42,18 +42,18 @@ See the Pipedrive docs for information on how to acquire credentials: [View the To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Pipedrive 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Pipedrive** and click **Add**. @@ -85,23 +85,23 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Pipedrive connector is now pulling access data into C1. +**Done.** Your Pipedrive connector is now pulling access data into C1.ai. **Follow these instructions to use the Pipedrive 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources -[Contact C1's support team](mailto:support@c1.ai) to download the latest version of the connector. +[Contact C1.ai's support team](mailto:support@c1.ai) to download the latest version of the connector. ### Step 1: Set up a new Pipedrive connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -191,13 +191,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 C1.ai 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 pipedrive connector to. pipedrive data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the pipedrive connector to. pipedrive data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Pipedrive connector is now pulling access data into C1. +**Done.** Your Pipedrive connector is now pulling access data into C1.ai. diff --git a/baton/plane.mdx b/baton/plane.mdx index d5ff7f6c..1abc67a5 100644 --- a/baton/plane.mdx +++ b/baton/plane.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Plane connector" og:title: "Set up a Plane connector" -description: "C1 provides identity governance for Plane. Integrate your Plane instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Plane. Integrate your Plane instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Plane. Integrate your Plane instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Plane. Integrate your Plane instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Plane" --- -C1 provides identity governance for Plane. Integrate your Plane workspace with -C1 for unified visibility and governance over who can access your workspace and +C1.ai provides identity governance for Plane. Integrate your Plane workspace with +C1.ai for unified visibility and governance over who can access your workspace and projects. ## Capabilities @@ -28,7 +28,7 @@ Guest). You need a Plane account with access to the workspace you want to govern. The personal access token you create can see every workspace your account belongs -to, so make sure you note the slug of the specific workspace you want C1 to +to, so make sure you note the slug of the specific workspace you want C1.ai to sync. @@ -55,11 +55,11 @@ sync. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -107,7 +107,7 @@ sync. - **Done.** Your Plane connector is now pulling access data into C1. + **Done.** Your Plane connector is now pulling access data into C1.ai. @@ -133,6 +133,6 @@ sync. - **Done.** Your Plane connector is now pulling access data into C1. + **Done.** Your Plane connector is now pulling access data into C1.ai. diff --git a/baton/planetscale.mdx b/baton/planetscale.mdx index 4c83c45e..ed8a8f12 100644 --- a/baton/planetscale.mdx +++ b/baton/planetscale.mdx @@ -1,13 +1,13 @@ --- title: "Set up a PlanetScale connector" og:title: "Set up a PlanetScale connector" -description: "C1 provides identity governance for PlanetScale. Integrate your PlanetScale organization with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for PlanetScale. Integrate your PlanetScale organization with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for PlanetScale. Integrate your PlanetScale organization with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for PlanetScale. Integrate your PlanetScale organization with C1.ai for unified visibility and governance over user access." sidebarTitle: "PlanetScale" --- -C1 provides identity governance for PlanetScale. Integrate your PlanetScale -organization with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for PlanetScale. Integrate your PlanetScale +organization with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -36,7 +36,7 @@ organization-wide read access. The connector is read-only and needs the Grant the service token the **`read_organization`** access on the - organizations you want C1 to govern. + organizations you want C1.ai to govern. @@ -73,11 +73,11 @@ organization-wide read access. The connector is read-only and needs the - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -122,7 +122,7 @@ organization-wide read access. The connector is read-only and needs the - **Done.** Your PlanetScale connector is now pulling access data into C1. + **Done.** Your PlanetScale connector is now pulling access data into C1.ai. @@ -131,7 +131,7 @@ organization-wide read access. The connector is read-only and needs the - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -139,7 +139,7 @@ organization-wide read access. The connector is read-only and needs the - Configure C1 credentials and PlanetScale credentials as environment + Configure C1.ai credentials and PlanetScale credentials as environment variables: ```bash @@ -156,6 +156,6 @@ organization-wide read access. The connector is read-only and needs the - **Done.** Your PlanetScale connector is now pulling access data into C1. + **Done.** Your PlanetScale connector is now pulling access data into C1.ai. diff --git a/baton/pluralsight.mdx b/baton/pluralsight.mdx index ee369121..ee4efdad 100644 --- a/baton/pluralsight.mdx +++ b/baton/pluralsight.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Pluralsight connector" og:title: "Set up a Pluralsight connector" -description: "C1 provides identity governance for Pluralsight. Integrate your Pluralsight account with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Pluralsight. Integrate your Pluralsight account with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Pluralsight. Integrate your Pluralsight account with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Pluralsight. Integrate your Pluralsight account with C1.ai for unified visibility and governance over user access." sidebarTitle: "Pluralsight" --- -C1 provides identity governance for Pluralsight. Integrate your Pluralsight -account with C1 for unified visibility and governance over users and team +C1.ai provides identity governance for Pluralsight. Integrate your Pluralsight +account with C1.ai for unified visibility and governance over users and team membership. ## Capabilities @@ -44,9 +44,9 @@ generate an API key. ## Synced resource types -- **Users**: the account's Pluralsight users, mapped as C1 users. Each user +- **Users**: the account's Pluralsight users, mapped as C1.ai users. Each user carries `id` (stable external id), `email`, and name. -- **Teams**: Pluralsight teams, mapped as C1 groups. Each team exposes a +- **Teams**: Pluralsight teams, mapped as C1.ai groups. Each team exposes a `member` entitlement (and an `admin` entitlement for team managers). Team membership grants are derived from the authoritative `teams` connection on each user node. diff --git a/baton/postgresql.mdx b/baton/postgresql.mdx index b3bb3bde..3fd96472 100644 --- a/baton/postgresql.mdx +++ b/baton/postgresql.mdx @@ -1,9 +1,9 @@ --- title: Set up a PostgreSQL connector -og:title: Set up a PostgreSQL connector - C1 docs -og:description: Integrate your PostgreSQL instance with C1 to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +og:title: Set up a PostgreSQL connector - C1.ai docs +og:description: Integrate your PostgreSQL instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. sidebarTitle: PostgreSQL -description: C1 provides identity governance and just-in-time provisioning for PostgreSQL. Integrate your PostgreSQL instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +description: C1.ai provides identity governance and just-in-time provisioning for PostgreSQL. Integrate your PostgreSQL instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. --- ## Capabilities @@ -24,7 +24,7 @@ description: C1 provides identity governance and just-in-time provisioning for P The PostgreSQL connector supports [automatic account provisioning and deprovisioning](/product/admin/account-provisioning). -When a new account is created by C1, the account's password will be sent to a [vault](/product/admin/vaults). +When a new account is created by C1.ai, the account's password will be sent to a [vault](/product/admin/vaults). ## Gather PostgreSQL credentials @@ -39,14 +39,14 @@ Configuring the connector requires you to pass in credentials generated in Postg To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of PostgreSQL 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 C1.ai.** *Cloud-hosted connector not currently available.* @@ -54,7 +54,7 @@ To complete this task, you'll need: **Follow these instructions to use the PostgreSQL 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -66,7 +66,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -163,13 +163,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 C1.ai 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 PostgreSQL connector to. PostgreSQL data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the PostgreSQL connector to. PostgreSQL data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your PostgreSQL connector is now pulling access data into C1. +**Done.** Your PostgreSQL connector is now pulling access data into C1.ai. diff --git a/baton/posthog.mdx b/baton/posthog.mdx index a4e3d039..9af8dd9d 100644 --- a/baton/posthog.mdx +++ b/baton/posthog.mdx @@ -1,13 +1,13 @@ --- title: "Set up a PostHog connector" og:title: "Set up a PostHog connector" -description: "C1 provides identity governance for PostHog. Integrate your PostHog organization with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for PostHog. Integrate your PostHog organization with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for PostHog. Integrate your PostHog organization with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for PostHog. Integrate your PostHog organization with C1.ai for unified visibility and governance over user access." sidebarTitle: "PostHog" --- -C1 provides identity governance for PostHog. Integrate your PostHog -organization with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for PostHog. Integrate your PostHog +organization with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -71,11 +71,11 @@ roles. The key must belong to a member of the organization you want to sync. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -123,7 +123,7 @@ roles. The key must belong to a member of the organization you want to sync. - **Done.** Your PostHog connector is now pulling access data into C1. + **Done.** Your PostHog connector is now pulling access data into C1.ai. @@ -132,7 +132,7 @@ roles. The key must belong to a member of the organization you want to sync. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -141,7 +141,7 @@ roles. The key must belong to a member of the organization you want to sync. - Configure C1 credentials and PostHog credentials as environment + Configure C1.ai credentials and PostHog credentials as environment variables: ```bash @@ -158,6 +158,6 @@ roles. The key must belong to a member of the organization you want to sync. - **Done.** Your PostHog connector is now pulling access data into C1. + **Done.** Your PostHog connector is now pulling access data into C1.ai. diff --git a/baton/postman.mdx b/baton/postman.mdx index ee57cde1..93e33bfb 100644 --- a/baton/postman.mdx +++ b/baton/postman.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Postman connector" og:title: "Set up a Postman connector" -description: "C1 provides identity governance for Postman. Integrate your Postman instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Postman. Integrate your Postman instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Postman. Integrate your Postman instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Postman. Integrate your Postman instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Postman" --- -C1 provides identity governance for Postman. Integrate your Postman team -with C1 for unified visibility and governance over who belongs to which +C1.ai provides identity governance for Postman. Integrate your Postman team +with C1.ai for unified visibility and governance over who belongs to which workspaces and which roles they hold. ## Capabilities @@ -53,11 +53,11 @@ and Solo accounts do not have a team user list and cannot be synced. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -102,7 +102,7 @@ and Solo accounts do not have a team user list and cannot be synced. - **Done.** Your Postman connector is now pulling access data into C1. + **Done.** Your Postman connector is now pulling access data into C1.ai. @@ -126,6 +126,6 @@ and Solo accounts do not have a team user list and cannot be synced. - **Done.** Your Postman connector is now pulling access data into C1. + **Done.** Your Postman connector is now pulling access data into C1.ai. diff --git a/baton/prismhr.mdx b/baton/prismhr.mdx index 07fa30d1..f6eeb422 100644 --- a/baton/prismhr.mdx +++ b/baton/prismhr.mdx @@ -1,9 +1,9 @@ --- title: Set up a PrismHR connector -og:title: Set up a PrismHR connector - C1 docs -og:description: Integrate your PrismHR instance with C1 to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +og:title: Set up a PrismHR connector - C1.ai docs +og:description: Integrate your PrismHR instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. sidebarTitle: PrismHR -description: C1 provides identity governance for PrismHR. Integrate your PrismHR instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +description: C1.ai provides identity governance for PrismHR. Integrate your PrismHR instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. --- ## Capabilities @@ -15,7 +15,7 @@ description: C1 provides identity governance for PrismHR. Integrate your PrismHR ### 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 C1.ai 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 | | -------------------------- | ----------------------------------------------------------------------------------------------------------- | -------------------------------------------- | @@ -91,18 +91,18 @@ Click **Save**. Make a note of the web service user's username, password, and Pe To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of PrismHR 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **PrismHR** and click **Add**. @@ -138,13 +138,13 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your PrismHR connector is now pulling access data into C1. +**Done.** Your PrismHR connector is now pulling access data into C1.ai. **Follow these instructions to use the PrismHR 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -154,7 +154,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -246,13 +246,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 C1.ai 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 PrismHR connector to. PrismHR data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the PrismHR connector to. PrismHR data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your PrismHR connector is now pulling access data into C1. +**Done.** Your PrismHR connector is now pulling access data into C1.ai. diff --git a/baton/privx.mdx b/baton/privx.mdx index ebde9c39..78b95c23 100644 --- a/baton/privx.mdx +++ b/baton/privx.mdx @@ -1,8 +1,8 @@ --- title: Set up a PrivX connector -og:title: Set up a PrivX connector - C1 docs -og:description: "C1 provides identity governance for PrivX. Integrate your PrivX instance with C1 for unified visibility and governance over user access." -description: "C1 provides identity governance for PrivX. Integrate your PrivX instance with C1 for unified visibility and governance over user access." +og:title: Set up a PrivX connector - C1.ai docs +og:description: "C1.ai provides identity governance for PrivX. Integrate your PrivX instance with C1.ai for unified visibility and governance over user access." +description: "C1.ai provides identity governance for PrivX. Integrate your PrivX instance with C1.ai for unified visibility and governance over user access." sidebarTitle: PrivX --- @@ -29,7 +29,7 @@ A user with the **Admin** role in PrivX must perform this task. ### Set up a PrivX role -First, create a PrivX role that will be used to grant permissions to the API client you'll use to integrate with C1. +First, create a PrivX role that will be used to grant permissions to the API client you'll use to integrate with C1.ai. @@ -72,18 +72,18 @@ Scroll down to the **Credentials** section of the page. Carefully copy and save To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of PrivX 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **PrivX** and click **Add**. @@ -119,13 +119,13 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your PrivX connector is now pulling access data into C1. +**Done.** Your PrivX connector is now pulling access data into C1.ai. **Follow these instructions to use the Privx 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -137,7 +137,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -232,14 +232,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 C1.ai 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 PrivX connector to. PrivX data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the PrivX connector to. PrivX data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your PrivX connector is now pulling access data into C1. +**Done.** Your PrivX connector is now pulling access data into C1.ai. diff --git a/baton/procore.mdx b/baton/procore.mdx index a2544a73..f1d0387b 100644 --- a/baton/procore.mdx +++ b/baton/procore.mdx @@ -1,8 +1,8 @@ --- title: Set up a Procore connector -og:title: Set up a Procore connector - C1 docs -og:description: Integrate your Procore 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 Procore. Integrate your Procore instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a Procore connector - C1.ai docs +og:description: Integrate your Procore instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance for Procore. Integrate your Procore instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: Procore --- @@ -45,7 +45,7 @@ A user with the permission to create apps in Procore must perform this task. In the Procore Developer Portal, navigate to **My Apps** > **Create a New App**. -Give the new app a name, such as "C1". +Give the new app a name, such as "C1.ai". Click **Create**. @@ -90,7 +90,7 @@ Click **Add**. ### Enable project directories -For each Procore project you want to provision using C1: +For each Procore project you want to provision using C1.ai: @@ -108,17 +108,17 @@ Enable the project directory. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Procore 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Procore** and click **Add**. @@ -151,13 +151,13 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Procore connector is now pulling access data into C1. +**Done.** Your Procore connector is now pulling access data into C1.ai. **Follow these instructions to use the Procore 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai 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 C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -262,14 +262,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 C1.ai 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 Procore connector to. Procore data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Procore connector to. Procore data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Procore connector is now pulling access data into C1. +**Done.** Your Procore connector is now pulling access data into C1.ai. diff --git a/baton/productboard.mdx b/baton/productboard.mdx index afc1ceeb..21047b01 100644 --- a/baton/productboard.mdx +++ b/baton/productboard.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Productboard connector" og:title: "Set up a Productboard connector" -description: "C1 provides identity governance for Productboard. Integrate your Productboard instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Productboard. Integrate your Productboard instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Productboard. Integrate your Productboard instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Productboard. Integrate your Productboard instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Productboard" --- -C1 provides identity governance for Productboard. Integrate your Productboard -instance with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Productboard. Integrate your Productboard +instance with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -55,11 +55,11 @@ token. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -103,7 +103,7 @@ token. - **Done.** Your Productboard connector is now pulling access data into C1. + **Done.** Your Productboard connector is now pulling access data into C1.ai. @@ -126,6 +126,6 @@ token. - **Done.** Your Productboard connector is now pulling access data into C1. + **Done.** Your Productboard connector is now pulling access data into C1.ai. diff --git a/baton/propelauth.mdx b/baton/propelauth.mdx index dd6e68c4..4ef6fb42 100644 --- a/baton/propelauth.mdx +++ b/baton/propelauth.mdx @@ -1,13 +1,13 @@ --- title: "Set up a PropelAuth connector" og:title: "Set up a PropelAuth connector" -description: "C1 provides identity governance for PropelAuth. Integrate your PropelAuth environment with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for PropelAuth. Integrate your PropelAuth environment with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for PropelAuth. Integrate your PropelAuth environment with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for PropelAuth. Integrate your PropelAuth environment with C1.ai for unified visibility and governance over user access." sidebarTitle: "PropelAuth" --- -C1 provides identity governance for PropelAuth. Integrate your PropelAuth -environment with C1 for unified visibility and governance over the users in +C1.ai provides identity governance for PropelAuth. Integrate your PropelAuth +environment with C1.ai for unified visibility and governance over the users in your project, the organizations they belong to, and the role each user holds in each organization. The connector is read-only — it never writes to PropelAuth. @@ -56,11 +56,11 @@ its own Auth URL and its own API keys. Configure one connector per environment. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -105,7 +105,7 @@ its own Auth URL and its own API keys. Configure one connector per environment. - **Done.** Your PropelAuth connector is now pulling access data into C1. + **Done.** Your PropelAuth connector is now pulling access data into C1.ai. @@ -129,6 +129,6 @@ its own Auth URL and its own API keys. Configure one connector per environment. - **Done.** Your PropelAuth connector is now pulling access data into C1. + **Done.** Your PropelAuth connector is now pulling access data into C1.ai. diff --git a/baton/pumble.mdx b/baton/pumble.mdx index 4f54e158..ba7bba9a 100644 --- a/baton/pumble.mdx +++ b/baton/pumble.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Pumble connector" og:title: "Set up a Pumble connector" -description: "C1 provides identity governance for Pumble. Integrate your Pumble instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Pumble. Integrate your Pumble instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Pumble. Integrate your Pumble instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Pumble. Integrate your Pumble instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Pumble" --- -C1 provides identity governance for Pumble. Integrate your Pumble -workspace with C1 for unified visibility and governance over who can access +C1.ai provides identity governance for Pumble. Integrate your Pumble +workspace with C1.ai for unified visibility and governance over who can access your team chat. ## Capabilities @@ -20,7 +20,7 @@ your team chat. The connector syncs every workspace member, every user group, and each group's membership. Members keep their workspace role (Owner, Admin, User, or Guest) and their active or deactivated state, so deactivated members -remain visible in C1 rather than disappearing. +remain visible in C1.ai rather than disappearing. ## Gather Pumble credentials @@ -50,11 +50,11 @@ workspace members or groups. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -99,7 +99,7 @@ workspace members or groups. - **Done.** Your Pumble connector is now pulling access data into C1. + **Done.** Your Pumble connector is now pulling access data into C1.ai. @@ -123,6 +123,6 @@ workspace members or groups. - **Done.** Your Pumble connector is now pulling access data into C1. + **Done.** Your Pumble connector is now pulling access data into C1.ai. diff --git a/baton/railway.mdx b/baton/railway.mdx index d4aa7d36..85e7c3a2 100644 --- a/baton/railway.mdx +++ b/baton/railway.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Railway connector" og:title: "Set up a Railway connector" -description: "C1 provides identity governance for Railway. Integrate your Railway instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Railway. Integrate your Railway instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Railway. Integrate your Railway instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Railway. Integrate your Railway instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Railway" --- -C1 provides identity governance for Railway. Integrate your Railway workspaces -with C1 for unified visibility and governance over who can access your projects +C1.ai provides identity governance for Railway. Integrate your Railway workspaces +with C1.ai for unified visibility and governance over who can access your projects and at what role. ## Capabilities @@ -49,11 +49,11 @@ provides the broadest visibility. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -97,7 +97,7 @@ provides the broadest visibility. - **Done.** Your Railway connector is now pulling access data into C1. + **Done.** Your Railway connector is now pulling access data into C1.ai. @@ -120,6 +120,6 @@ provides the broadest visibility. - **Done.** Your Railway connector is now pulling access data into C1. + **Done.** Your Railway connector is now pulling access data into C1.ai. diff --git a/baton/ramp.mdx b/baton/ramp.mdx index 679fb74e..b5ec4181 100644 --- a/baton/ramp.mdx +++ b/baton/ramp.mdx @@ -1,13 +1,13 @@ --- title: Set up a Ramp connector og:title: Set up a Ramp connector -description: C1 provides identity governance and just-in-time provisioning for Ramp. Integrate your Ramp 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 Ramp. Integrate your Ramp instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access. +description: C1.ai provides identity governance and just-in-time provisioning for Ramp. Integrate your Ramp instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access. +og:description: C1.ai provides identity governance and just-in-time provisioning for Ramp. Integrate your Ramp instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access. sidebarTitle: Ramp --- -**This is an updated and improved version of the Ramp connector!** If you're setting up Ramp with C1 for the first time, you're in the right place. +**This is an updated and improved version of the Ramp connector!** If you're setting up Ramp with C1.ai for the first time, you're in the right place. ## Capabilities @@ -28,13 +28,13 @@ sidebarTitle: Ramp **Vendor owner is single-assignee.** Each Ramp vendor can have only one owner at a time. Granting the vendor owner entitlement to a new user overwrites the previous owner in Ramp — the prior owner is silently removed. Revoking the entitlement clears the owner only when the principal being revoked is the current owner. -Synced Ramp vendors are emitted as C1 vendor resources with Ramp vendor identity metadata. Vendor owner access is represented as the `owner` entitlement on each vendor. Vendor agreements are available as an opt-in resource type and use the same Ramp `vendors:read` scope as vendors. +Synced Ramp vendors are emitted as C1.ai vendor resources with Ramp vendor identity metadata. Vendor owner access is represented as the `owner` entitlement on each vendor. Vendor agreements are available as an opt-in resource type and use the same Ramp `vendors:read` scope as vendors. The Ramp connector supports [automatic account provisioning](/product/admin/account-provisioning). ### 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 C1.ai 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 | |-------------|-------------------|-------------| @@ -71,7 +71,7 @@ The Ramp connector supports two authentication methods. Choose the one that fits - `audit_logs:read` — read Ramp audit-log events for incremental sync - The **users:write** and **vendors:write** scopes are used only when C1 provisions and deprovisions access. **If you do not want C1 to perform these tasks, do not grant these scopes.** + The **users:write** and **vendors:write** scopes are used only when C1.ai provisions and deprovisions access. **If you do not want C1.ai to perform these tasks, do not grant these scopes.** @@ -107,7 +107,7 @@ For more information, see the [Ramp API token documentation](https://docs.ramp.c - `audit_logs:read` — read Ramp audit-log events for incremental sync - The **users:write** and **vendors:write** scopes are used only when C1 provisions and deprovisions access. **If you do not want C1 to perform these tasks, do not grant these scopes.** + The **users:write** and **vendors:write** scopes are used only when C1.ai provisions and deprovisions access. **If you do not want C1.ai to perform these tasks, do not grant these scopes.** 4. Click **Create** @@ -124,17 +124,17 @@ For more information, see the [Ramp authorization documentation](https://docs.ra To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - The **Administrator** role in Ramp -**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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Ramp** and click **Add**. @@ -170,13 +170,13 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Ramp connector is now pulling access data into C1. +**Done.** Your Ramp connector is now pulling access data into C1.ai. **Follow these instructions to use the Ramp 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -186,7 +186,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -234,11 +234,11 @@ The connector points at `https://api.ramp.com` by default. Set `BATON_RAMP_BASE_ ### Optional resources and events -The connector ships with an opt-in `vendor_agreement` resource type. When enabled in C1 resource-type settings, the connector syncs Ramp vendor agreements as their own resources, including term, renewal status, total contract value, and contract owners. Vendor agreements use the existing `vendors:read` scope; Ramp does not require a separate vendor-agreement scope. +The connector ships with an opt-in `vendor_agreement` resource type. When enabled in C1.ai resource-type settings, the connector syncs Ramp vendor agreements as their own resources, including term, renewal status, total contract value, and contract owners. Vendor agreements use the existing `vendors:read` scope; Ramp does not require a separate vendor-agreement scope. Ramp vendors are always decorated with cross-system identity and pre-aggregated trailing-window spend when those fields are returned by Ramp. -Set `BATON_AUDIT_LOG_EVENTS=true` to expose Ramp's audit-log API as an event feed so vendor and agreement changes can flow into C1 incrementally between full syncs. This setting is independent from vendor-agreement resource enablement and requires Ramp audit-log API availability, such as Ramp Plus, plus the `audit_logs:read` scope. When the flag is unset (the default), the audit-log API is not called. +Set `BATON_AUDIT_LOG_EVENTS=true` to expose Ramp's audit-log API as an event feed so vendor and agreement changes can flow into C1.ai incrementally between full syncs. This setting is independent from vendor-agreement resource enablement and requires Ramp audit-log API availability, such as Ramp Plus, plus the `audit_logs:read` scope. When the flag is unset (the default), the audit-log API is not called. #### Secrets configuration @@ -333,13 +333,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 C1.ai 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 Ramp connector to. Ramp data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Ramp connector to. Ramp data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Ramp connector is now pulling access data into C1. +**Done.** Your Ramp connector is now pulling access data into C1.ai. diff --git a/baton/rapid7.mdx b/baton/rapid7.mdx index a5aaa041..b6652088 100644 --- a/baton/rapid7.mdx +++ b/baton/rapid7.mdx @@ -1,8 +1,8 @@ --- title: Set up Rapid7 connector -og:title: Set up Rapid7 connector - C1 docs -og:description: "C1 provides identity governance for Rapid7. Integrate your Rapid7 instance with C1 for unified visibility and governance over user access." -description: "C1 provides identity governance for Rapid7. Integrate your Rapid7 instance with C1 for unified visibility and governance over user access." +og:title: Set up Rapid7 connector - C1.ai docs +og:description: "C1.ai provides identity governance for Rapid7. Integrate your Rapid7 instance with C1.ai for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Rapid7. Integrate your Rapid7 instance with C1.ai for unified visibility and governance over user access." sidebarTitle: Rapid7 --- @@ -22,16 +22,16 @@ This connector works with Rapid7 products available on the Command Platform API The Rapid7 connector supports [automatic account provisioning](/product/admin/account-provisioning) on the Command Platform. New accounts receive an invitation email and set their own password. -**Role sync includes Rapid7's shared roles even when they don't appear in your account's role list.** The shared Administrator, View and Change, and View Only roles are assignable across your whole account, but Rapid7 only lists them in the role catalog for organizations subscribed to certain products. C1 always includes these three roles so any assignment referencing one still syncs correctly. +**Role sync includes Rapid7's shared roles even when they don't appear in your account's role list.** The shared Administrator, View and Change, and View Only roles are assignable across your whole account, but Rapid7 only lists them in the role catalog for organizations subscribed to certain products. C1.ai always includes these three roles so any assignment referencing one still syncs correctly. -**Role and group assignments sync across every organization in your account.** If your account has more than one organization, a user or group can hold different role assignments in each. C1 collects assignments from every organization, not just one. +**Role and group assignments sync across every organization in your account.** If your account has more than one organization, a user or group can hold different role assignments in each. C1.ai collects assignments from every organization, not just one. ### 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 C1.ai 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 | |-------------|-------------------|-------------| @@ -67,16 +67,16 @@ See the Rapid7 docs for information on how to acquire credentials: [View the doc To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Rapid7 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Rapid7** and click **Add**. @@ -108,23 +108,23 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Rapid7 connector is now pulling access data into C1. +**Done.** Your Rapid7 connector is now pulling access data into C1.ai. **Follow these instructions to use the Rapid7 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai 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 C1.ai's support team](mailto:support@conductorone.com) to download the latest version of the connector. ### Step 1: Set up a new Rapid7 connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -216,13 +216,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 C1.ai 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 rapid7 connector to. rapid7 data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the rapid7 connector to. rapid7 data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Rapid7 connector is now pulling access data into C1. +**Done.** Your Rapid7 connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/reamaze.mdx b/baton/reamaze.mdx index e215d49a..8178d31e 100644 --- a/baton/reamaze.mdx +++ b/baton/reamaze.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Re:amaze connector" og:title: "Set up a Re:amaze connector" -description: "C1 provides identity governance for Re:amaze. Integrate your Re:amaze account with C1 for unified visibility and governance over staff access." -og:description: "C1 provides identity governance for Re:amaze. Integrate your Re:amaze account with C1 for unified visibility and governance over staff access." +description: "C1.ai provides identity governance for Re:amaze. Integrate your Re:amaze account with C1.ai for unified visibility and governance over staff access." +og:description: "C1.ai provides identity governance for Re:amaze. Integrate your Re:amaze account with C1.ai for unified visibility and governance over staff access." sidebarTitle: "Re:amaze" --- -C1 provides identity governance for Re:amaze. Integrate your Re:amaze account -with C1 for unified visibility and governance over the staff who can access +C1.ai provides identity governance for Re:amaze. Integrate your Re:amaze account +with C1.ai for unified visibility and governance over the staff who can access your customer-support helpdesk. ## Capabilities @@ -48,11 +48,11 @@ token. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -98,7 +98,7 @@ token. - **Done.** Your Re:amaze connector is now pulling access data into C1. + **Done.** Your Re:amaze connector is now pulling access data into C1.ai. @@ -123,6 +123,6 @@ token. - **Done.** Your Re:amaze connector is now pulling access data into C1. + **Done.** Your Re:amaze connector is now pulling access data into C1.ai. diff --git a/baton/recruitee.mdx b/baton/recruitee.mdx index 93ece1b6..81a6b2a3 100644 --- a/baton/recruitee.mdx +++ b/baton/recruitee.mdx @@ -1,15 +1,15 @@ --- title: "Set up a Recruitee connector" og:title: "Set up a Recruitee connector" -description: "C1 provides identity governance for Recruitee. Integrate your Recruitee instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Recruitee. Integrate your Recruitee instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Recruitee. Integrate your Recruitee instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Recruitee. Integrate your Recruitee instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Recruitee" --- {/* stargate */} -C1 provides identity governance for Recruitee. Integrate your Recruitee account -with C1 for unified visibility and governance over the admins who can access +C1.ai provides identity governance for Recruitee. Integrate your Recruitee account +with C1.ai for unified visibility and governance over the admins who can access your Recruitee account. ## Capabilities @@ -56,11 +56,11 @@ Recruitee. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -105,7 +105,7 @@ Recruitee. - **Done.** Your Recruitee connector is now pulling access data into C1. + **Done.** Your Recruitee connector is now pulling access data into C1.ai. @@ -129,6 +129,6 @@ Recruitee. - **Done.** Your Recruitee connector is now pulling access data into C1. + **Done.** Your Recruitee connector is now pulling access data into C1.ai. diff --git a/baton/redis.mdx b/baton/redis.mdx index 04b25222..5b9e5ca2 100644 --- a/baton/redis.mdx +++ b/baton/redis.mdx @@ -1,8 +1,8 @@ --- title: Set up a Redis connector -og:title: Set up a Redis connector - C1 docs -og:description: "C1 provides identity governance for Redis. Integrate your Redis instance with C1 for unified visibility and governance over user access." -description: "C1 provides identity governance for Redis. Integrate your Redis instance with C1 for unified visibility and governance over user access." +og:title: Set up a Redis connector - C1.ai docs +og:description: "C1.ai provides identity governance for Redis. Integrate your Redis instance with C1.ai for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Redis. Integrate your Redis instance with C1.ai for unified visibility and governance over user access." sidebarTitle: Redis --- @@ -17,7 +17,7 @@ sidebarTitle: Redis Configuring the connector requires you to pass in credentials generated in Redis. Gather these credentials before you move on. -To set up the integration with C1, you'll need: +To set up the integration with C1.ai, you'll need: - Your Redis Enterprise Service cluster host and port @@ -30,17 +30,17 @@ To set up the integration with C1, you'll need: To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Redis 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Redis Enterprise** and click **Add**. @@ -78,12 +78,12 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Redis connector is now pulling access data into C1. +**Done.** Your Redis connector is now pulling access data into C1.ai. **Follow these instructions to use the Redis 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -93,7 +93,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -185,14 +185,14 @@ spec: -1. Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files. +1. Create a namespace in which to run C1.ai 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 Redis connector to. Redis data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Redis connector to. Redis data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Redis connector is now pulling access data into C1. +**Done.** Your Redis connector is now pulling access data into C1.ai. diff --git a/baton/render.mdx b/baton/render.mdx index aee87179..dd52ca18 100644 --- a/baton/render.mdx +++ b/baton/render.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Render connector" og:title: "Set up a Render connector" -description: "C1 provides identity governance for Render. Integrate your Render workspace with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Render. Integrate your Render workspace with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Render. Integrate your Render workspace with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Render. Integrate your Render workspace with C1.ai for unified visibility and governance over user access." sidebarTitle: "Render" --- -C1 provides identity governance for Render. Integrate your Render workspace -with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Render. Integrate your Render workspace +with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -51,11 +51,11 @@ of the workspace you are syncing. A non-admin key sees only a partial roster. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -102,7 +102,7 @@ of the workspace you are syncing. A non-admin key sees only a partial roster. - **Done.** Your Render connector is now pulling access data into C1. + **Done.** Your Render connector is now pulling access data into C1.ai. @@ -128,6 +128,6 @@ of the workspace you are syncing. A non-admin key sees only a partial roster. - **Done.** Your Render connector is now pulling access data into C1. + **Done.** Your Render connector is now pulling access data into C1.ai. diff --git a/baton/retool.mdx b/baton/retool.mdx index 222627f2..05fc7838 100644 --- a/baton/retool.mdx +++ b/baton/retool.mdx @@ -1,8 +1,8 @@ --- title: Set up Retool connector -og:title: Set up Retool connector - C1 docs -og:description: Integrate your Retool instance with C1 to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. -description: C1 provides identity governance and just-in-time provisioning for Retool. Integrate your Retool instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up Retool connector - C1.ai docs +og:description: Integrate your Retool instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance and just-in-time provisioning for Retool. Integrate your Retool instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: Retool --- @@ -90,21 +90,21 @@ Copy and save the token, and note your Retool base URL (for example `https:// To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Retool 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 C1.ai.** *Cloud-hosted connector not currently available.* **Follow these instructions to use the Retool connector, hosted and run in your own environment.** -When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -114,7 +114,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -210,13 +210,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 C1.ai 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 Retool connector to. Retool data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Retool connector to. Retool data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Retool connector is now pulling access data into C1. +**Done.** Your Retool connector is now pulling access data into C1.ai. diff --git a/baton/revpro.mdx b/baton/revpro.mdx index b09fcd8e..6f7a90fe 100644 --- a/baton/revpro.mdx +++ b/baton/revpro.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Zuora RevPro connector" og:title: "Set up a Zuora RevPro connector" -description: "C1 provides identity governance for Zuora RevPro. Integrate your Zuora tenant with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Zuora RevPro. Integrate your Zuora tenant with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Zuora RevPro. Integrate your Zuora tenant with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Zuora RevPro. Integrate your Zuora tenant with C1.ai for unified visibility and governance over user access." sidebarTitle: "Zuora RevPro" --- -C1 provides identity governance for Zuora RevPro (Zuora Revenue). Integrate -your Zuora tenant with C1 for unified visibility and governance over user +C1.ai provides identity governance for Zuora RevPro (Zuora Revenue). Integrate +your Zuora tenant with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -77,11 +77,11 @@ created for a Zuora platform user. It performs read-only API calls. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -127,7 +127,7 @@ created for a Zuora platform user. It performs read-only API calls. - **Done.** Your Zuora RevPro connector is now pulling access data into C1. + **Done.** Your Zuora RevPro connector is now pulling access data into C1.ai. @@ -151,6 +151,6 @@ created for a Zuora platform user. It performs read-only API calls. - **Done.** Your Zuora RevPro connector is now pulling access data into C1. + **Done.** Your Zuora RevPro connector is now pulling access data into C1.ai. diff --git a/baton/ringcentral.mdx b/baton/ringcentral.mdx index 1a52ca09..42ff6345 100644 --- a/baton/ringcentral.mdx +++ b/baton/ringcentral.mdx @@ -1,8 +1,8 @@ --- title: Set up a RingCentral connector -og:title: Set up a RingCentral connector - C1 docs -og:description: Integrate your RingCentral instance with C1 to run user access reviews, enable just-in-time access requests, and easily provision and deprovision role access. -description: C1 provides identity governance and just-in-time provisioning for RingCentral. Integrate your RingCentral instance with C1 to run user access reviews (UARs) and provision or deprovision role assignments. +og:title: Set up a RingCentral connector - C1.ai docs +og:description: Integrate your RingCentral instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision role access. +description: C1.ai provides identity governance and just-in-time provisioning for RingCentral. Integrate your RingCentral instance with C1.ai to run user access reviews (UARs) and provision or deprovision role assignments. sidebarTitle: RingCentral --- @@ -68,7 +68,7 @@ In the upper right corner of the screen, click your name and select **Credential Click **Create JWT**. -Give the JWT a name, such as "C1" and select the environment where it will be used. +Give the JWT a name, such as "C1.ai" and select the environment where it will be used. Select the **Only specific apps of my choice** option and enter the client ID of your newly created app. @@ -84,17 +84,17 @@ Click **Create**. Carefully copy and save the JWT 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 C1.ai - Access to the set of RingCentral 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **RingCentral** and click **Add**. @@ -131,12 +131,12 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your RingCentral connector is now pulling access data into C1. +**Done.** Your RingCentral connector is now pulling access data into C1.ai. **Follow these instructions to use the RingCentral 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -146,7 +146,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -240,15 +240,15 @@ 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 C1.ai 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 RingCentral connector to. RingCentral data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the RingCentral connector to. RingCentral data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your RingCentral connector is now pulling access data into C1. +**Done.** Your RingCentral connector is now pulling access data into C1.ai. diff --git a/baton/rippling.mdx b/baton/rippling.mdx index e6b06ce8..ca60e54c 100644 --- a/baton/rippling.mdx +++ b/baton/rippling.mdx @@ -1,8 +1,8 @@ --- title: Set up a Rippling connector -og:title: Set up a Rippling connector - C1 docs -og:description: "C1 provides identity governance for Rippling. Integrate your Rippling instance with C1 for unified visibility and governance over user access." -description: "C1 provides identity governance for Rippling. Integrate your Rippling instance with C1 for unified visibility and governance over user access." +og:title: Set up a Rippling connector - C1.ai docs +og:description: "C1.ai provides identity governance for Rippling. Integrate your Rippling instance with C1.ai for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Rippling. Integrate your Rippling instance with C1.ai for unified visibility and governance over user access." sidebarTitle: Rippling --- @@ -27,7 +27,7 @@ A user with the user permissions to view all users and teams in Rippling must pe In Rippling, navigate to **Company Settings** > **API Tokens**. -Give the new token a name, such as "C1", and set the token's unique identifier and API version. +Give the new token a name, such as "C1.ai", and set the token's unique identifier and API version. Configure the scopes for the API token, giving it the permission to view all Rippling users and teams. @@ -43,17 +43,17 @@ Create the token, then carefully copy and save the token value. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Rippling 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Rippling** and click **Add**. @@ -94,12 +94,12 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Rippling connector is now pulling access data into C1. +**Done.** Your Rippling connector is now pulling access data into C1.ai. **Follow these instructions to use the Rippling 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -109,7 +109,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -201,13 +201,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 C1.ai 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 Rippling connector to. Rippling data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Rippling connector to. Rippling data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Rippling connector is now pulling access data into C1. +**Done.** Your Rippling connector is now pulling access data into C1.ai. diff --git a/baton/rocketchat.mdx b/baton/rocketchat.mdx index 291959b6..9d515ad8 100644 --- a/baton/rocketchat.mdx +++ b/baton/rocketchat.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Rocket.Chat connector" og:title: "Set up a Rocket.Chat connector" -description: "C1 provides identity governance for Rocket.Chat. Integrate your Rocket.Chat workspace with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Rocket.Chat. Integrate your Rocket.Chat workspace with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Rocket.Chat. Integrate your Rocket.Chat workspace with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Rocket.Chat. Integrate your Rocket.Chat workspace with C1.ai for unified visibility and governance over user access." sidebarTitle: "Rocket.Chat" --- -C1 provides identity governance for Rocket.Chat. Integrate your Rocket.Chat -workspace with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Rocket.Chat. Integrate your Rocket.Chat +workspace with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -81,11 +81,11 @@ teams it is not a member of and does not work with this connector. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -130,7 +130,7 @@ teams it is not a member of and does not work with this connector. - **Done.** Your Rocket.Chat connector is now pulling access data into C1. + **Done.** Your Rocket.Chat connector is now pulling access data into C1.ai. @@ -157,6 +157,6 @@ teams it is not a member of and does not work with this connector. - **Done.** Your Rocket.Chat connector is now pulling access data into C1. + **Done.** Your Rocket.Chat connector is now pulling access data into C1.ai. diff --git a/baton/rollbar.mdx b/baton/rollbar.mdx index 35394c35..e4c44c90 100644 --- a/baton/rollbar.mdx +++ b/baton/rollbar.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Rollbar connector" og:title: "Set up a Rollbar connector" -description: "C1 provides identity governance for Rollbar. Integrate your Rollbar instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Rollbar. Integrate your Rollbar instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Rollbar. Integrate your Rollbar instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Rollbar. Integrate your Rollbar instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Rollbar" --- -C1 provides identity governance for Rollbar. Integrate your Rollbar -account with C1 for unified visibility and governance over who belongs to +C1.ai provides identity governance for Rollbar. Integrate your Rollbar +account with C1.ai for unified visibility and governance over who belongs to which teams. ## Capabilities @@ -52,11 +52,11 @@ Token with read scope. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -98,7 +98,7 @@ Token with read scope. - **Done.** Your Rollbar connector is now pulling access data into C1. + **Done.** Your Rollbar connector is now pulling access data into C1.ai. @@ -124,7 +124,7 @@ Token with read scope. - **Done.** Your Rollbar connector is now pulling access data into C1. + **Done.** Your Rollbar connector is now pulling access data into C1.ai. diff --git a/baton/rootly.mdx b/baton/rootly.mdx index f7305e6a..728cd962 100644 --- a/baton/rootly.mdx +++ b/baton/rootly.mdx @@ -1,8 +1,8 @@ --- title: Set up a Rootly connector -og:title: Set up a Rootly connector - C1 docs -og:description: "C1 provides identity governance for Rootly. Integrate your Rootly instance with C1 for unified visibility and governance over user access." -description: "C1 provides identity governance for Rootly. Integrate your Rootly instance with C1 for unified visibility and governance over user access." +og:title: Set up a Rootly connector - C1.ai docs +og:description: "C1.ai provides identity governance for Rootly. Integrate your Rootly instance with C1.ai for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Rootly. Integrate your Rootly instance with C1.ai for unified visibility and governance over user access." sidebarTitle: Rootly --- @@ -63,7 +63,7 @@ When prompted to select an API key type, select **Global API Key**. Give the new API key the incident response and on-call roles you created above. -Give the new key a name, such as "C1", and a description, then set an expiration. +Give the new key a name, such as "C1.ai", and a description, then set an expiration. Click **Create**. @@ -79,17 +79,17 @@ Note that if you ever edit a Rootly role used on an API key, the existing key wi ## Configure the Rootly connector To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Rootly 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Rootly** and click **Add**. @@ -122,12 +122,12 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Rootly connector is now pulling access data into C1. +**Done.** Your Rootly connector is now pulling access data into C1.ai. **Follow these instructions to use the Rootly 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -137,7 +137,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -227,13 +227,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 C1.ai 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 Rootly connector to. Rootly data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Rootly connector to. Rootly data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Rootly connector is now pulling access data into C1. +**Done.** Your Rootly connector is now pulling access data into C1.ai. diff --git a/baton/rudderstack.mdx b/baton/rudderstack.mdx index 90f732e7..db3be6be 100644 --- a/baton/rudderstack.mdx +++ b/baton/rudderstack.mdx @@ -1,13 +1,13 @@ --- title: "Set up a RudderStack connector" og:title: "Set up a RudderStack connector" -description: "C1 provides identity governance for RudderStack. Integrate your RudderStack organization with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for RudderStack. Integrate your RudderStack organization with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for RudderStack. Integrate your RudderStack organization with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for RudderStack. Integrate your RudderStack organization with C1.ai for unified visibility and governance over user access." sidebarTitle: "RudderStack" --- -C1 provides identity governance for RudderStack. Integrate your RudderStack -organization with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for RudderStack. Integrate your RudderStack +organization with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -59,11 +59,11 @@ Token. RudderStack SCIM requires the Enterprise plan with SSO enabled. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -108,7 +108,7 @@ Token. RudderStack SCIM requires the Enterprise plan with SSO enabled. - **Done.** Your RudderStack connector is now pulling access data into C1. + **Done.** Your RudderStack connector is now pulling access data into C1.ai. @@ -136,6 +136,6 @@ Token. RudderStack SCIM requires the Enterprise plan with SSO enabled. - **Done.** Your RudderStack connector is now pulling access data into C1. + **Done.** Your RudderStack connector is now pulling access data into C1.ai. diff --git a/baton/runlayer.mdx b/baton/runlayer.mdx index ec8cc0c9..0e66174d 100644 --- a/baton/runlayer.mdx +++ b/baton/runlayer.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Runlayer connector" og:title: "Set up a Runlayer connector" -description: "C1 provides identity governance for Runlayer. Integrate your Runlayer instance with C1 for unified visibility and governance over user access and platform roles." -og:description: "C1 provides identity governance for Runlayer. Integrate your Runlayer instance with C1 for unified visibility and governance over user access and platform roles." +description: "C1.ai provides identity governance for Runlayer. Integrate your Runlayer instance with C1.ai for unified visibility and governance over user access and platform roles." +og:description: "C1.ai provides identity governance for Runlayer. Integrate your Runlayer instance with C1.ai for unified visibility and governance over user access and platform roles." sidebarTitle: "Runlayer" --- -C1 provides identity governance for Runlayer. Integrate your Runlayer instance -with C1 for unified visibility and governance over who can administer your MCP +C1.ai provides identity governance for Runlayer. Integrate your Runlayer instance +with C1.ai for unified visibility and governance over who can administer your MCP platform. ## Capabilities @@ -50,11 +50,11 @@ Runlayer instance, not a shared public endpoint. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -96,7 +96,7 @@ Runlayer instance, not a shared public endpoint. - **Done.** Your Runlayer connector is now pulling access data into C1. + **Done.** Your Runlayer connector is now pulling access data into C1.ai. @@ -118,6 +118,6 @@ Runlayer instance, not a shared public endpoint. - **Done.** Your Runlayer connector is now pulling access data into C1. + **Done.** Your Runlayer connector is now pulling access data into C1.ai. diff --git a/baton/sage-intacct.mdx b/baton/sage-intacct.mdx index 655fd0e0..f2ef2b99 100644 --- a/baton/sage-intacct.mdx +++ b/baton/sage-intacct.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Sage Intacct connector" og:title: "Set up a Sage Intacct connector" -description: "C1 provides identity governance for Sage Intacct. Integrate your Sage Intacct 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 for Sage Intacct. Integrate your Sage Intacct instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance for Sage Intacct. Integrate your Sage Intacct instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance for Sage Intacct. Integrate your Sage Intacct instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "Sage Intacct" --- @@ -23,7 +23,7 @@ sidebarTitle: "Sage Intacct" ### 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 C1.ai 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 | |-------------|-------------------|-------------| diff --git a/baton/sagehr.mdx b/baton/sagehr.mdx index d50f421b..111b8704 100644 --- a/baton/sagehr.mdx +++ b/baton/sagehr.mdx @@ -1,8 +1,8 @@ --- title: Set up Sage HR connector -og:title: Set up Sage HR connector - C1 docs -og:description: "C1 provides identity governance for Sage HR. Integrate your Sage HR instance with C1 for unified visibility and governance over user access." -description: "C1 provides identity governance for Sage HR. Integrate your Sage HR instance with C1 for unified visibility and governance over user access." +og:title: Set up Sage HR connector - C1.ai docs +og:description: "C1.ai provides identity governance for Sage HR. Integrate your Sage HR instance with C1.ai for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Sage HR. Integrate your Sage HR instance with C1.ai for unified visibility and governance over user access." sidebarTitle: Sage HR --- @@ -33,17 +33,17 @@ See the Sage HR docs for information on how to acquire credentials: [View the do To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Sage HR 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Sage HR** and click **Add**. @@ -76,22 +76,22 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Sage HR connector is now pulling access data into C1. +**Done.** Your Sage HR connector is now pulling access data into C1.ai. **Follow these instructions to use the Sage HR 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources -[Contact C1's support team](mailto:support@c1.ai) to download the latest version of the connector. +[Contact C1.ai's support team](mailto:support@c1.ai) to download the latest version of the connector. ### Step 1: Set up a new Sage HR connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -182,13 +182,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 C1.ai 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 sagehr connector to. sagehr data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the sagehr connector to. sagehr data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Sage HR connector is now pulling access data into C1. +**Done.** Your Sage HR connector is now pulling access data into C1.ai. diff --git a/baton/salesforce.mdx b/baton/salesforce.mdx index 5f14051c..900f6636 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 - C1.ai docs +og:description: Integrate your Salesforce instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance for Salesforce. Integrate your Salesforce instance with C1.ai 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 C1.ai 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. +C1.ai 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. @@ -38,13 +38,13 @@ This connector does not support account deprovisioning. You must deprovision acc **Territories require Enterprise Territory Management 2.0 to be enabled in your Salesforce org. If this feature is not enabled, the connector will return an error when attempting to sync territories.** -***Agents (Agentforce agents and Einstein Bots, backed by the `BotDefinition` object) are opt-in and disabled by default. Enable the Agent resource type in C1 to sync them. Agentforce or Einstein Bots must be enabled in your Salesforce org; otherwise the connector skips agents cleanly.** +***Agents (Agentforce agents and Einstein Bots, backed by the `BotDefinition` object) are opt-in and disabled by default. Enable the Agent resource type in C1.ai to sync them. Agentforce or Einstein Bots must be enabled in your Salesforce org; otherwise the connector skips agents cleanly.** ### Optional fields for custom validation rules Some Salesforce orgs have custom validation rules that require additional fields to be set when creating a user (for example, a rule that requires `FederationIdentifier` for SSO). -To add an optional field mapping in C1, use the exact Salesforce field API name as the mapping key (for example, `FederationIdentifier`, `Department`, `CommunityNickname`) allowing you to satisfy any validation rule. +To add an optional field mapping in C1.ai, use the exact Salesforce field API name as the mapping key (for example, `FederationIdentifier`, `Department`, `CommunityNickname`) allowing you to satisfy any validation rule. *You have the option to sync user accounts that use non-standard licenses. @@ -52,7 +52,7 @@ To add an optional field mapping in C1, use the exact Salesforce field API name ### 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 C1.ai 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 | |-------------|-------------------|-------------| @@ -68,7 +68,7 @@ The connector user must have the **API Enabled** and **Manage Users** system per ### Enable API access and permissions for your Salesforce user -Before you begin, make sure that the Salesforce user who will set up the integration with C1 has the required system permissions. The recommended approach is to create a Permission Set and assign it to the connector user. +Before you begin, make sure that the Salesforce user who will set up the integration with C1.ai has the required system permissions. The recommended approach is to create a Permission Set and assign it to the connector user. @@ -78,7 +78,7 @@ Log into Salesforce as an Administrator. Click the gear icon and select **Setup* Search for "permission sets" and select **Permission Sets**. -Click **New** to create a permission set (for example, "C1 Connector Access"). +Click **New** to create a permission set (for example, "C1.ai Connector Access"). In the permission set, click **System Permissions**, then click **Edit**. @@ -102,7 +102,7 @@ Your connector user now has the required permissions to sync Salesforce data. 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: + C1.ai integrates with domains that use one of the following Salesforce URL structures: - `my.salesforce.com` - `sandbox.my.salesforce.com` @@ -209,17 +209,17 @@ Go to the **Settings** tab, expand **OAuth Configuration**, and click **Consumer To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Salesforce v2** and click **Add**. @@ -249,7 +249,7 @@ Select your method of authenticating to Salesforce: **OAuth**, **JWT Bearer**, * 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 C1.ai 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. @@ -257,15 +257,15 @@ Select your method of authenticating to Salesforce: **OAuth**, **JWT Bearer**, * 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. C1.ai 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 C1.ai 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 C1.ai, where you'll see an authorization message. If you chose **JWT Bearer**: @@ -305,7 +305,7 @@ Select your method of authenticating to Salesforce: **OAuth**, **JWT Bearer**, * 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 C1.ai 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. @@ -313,7 +313,7 @@ Select your method of authenticating to Salesforce: **OAuth**, **JWT Bearer**, * 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. C1.ai 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**. @@ -322,12 +322,12 @@ Select your method of authenticating to Salesforce: **OAuth**, **JWT Bearer**, * -**Done.** Your Salesforce connector is now pulling access data into C1. +**Done.** Your Salesforce connector is now pulling access data into C1.ai. **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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -339,7 +339,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -449,14 +449,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 C1.ai 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 C1.ai, 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. -**Done.** Your Salesforce connector is now pulling access data into C1. +**Done.** Your Salesforce connector is now pulling access data into C1.ai. diff --git a/baton/salesloft.mdx b/baton/salesloft.mdx index aba2d6bf..de9cc9d5 100644 --- a/baton/salesloft.mdx +++ b/baton/salesloft.mdx @@ -1,15 +1,15 @@ --- title: "Set up a Salesloft connector" og:title: "Set up a Salesloft connector" -description: "C1 provides identity governance for Salesloft. Integrate your Salesloft account with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Salesloft. Integrate your Salesloft account with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Salesloft. Integrate your Salesloft account with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Salesloft. Integrate your Salesloft account with C1.ai for unified visibility and governance over user access." sidebarTitle: "Salesloft" --- {/* stargate: cf-salesloft-fullimpl-20260605 */} -C1 provides identity governance for Salesloft. Integrate your Salesloft account -with C1 for unified visibility and governance over who can sign in to Salesloft +C1.ai provides identity governance for Salesloft. Integrate your Salesloft account +with C1.ai for unified visibility and governance over who can sign in to Salesloft and which team they belong to. ## Capabilities @@ -52,11 +52,11 @@ visibility policy exposes to its owner. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -97,7 +97,7 @@ visibility policy exposes to its owner. - **Done.** Your Salesloft connector is now pulling access data into C1. + **Done.** Your Salesloft connector is now pulling access data into C1.ai. @@ -120,6 +120,6 @@ visibility policy exposes to its owner. - **Done.** Your Salesloft connector is now pulling access data into C1. + **Done.** Your Salesloft connector is now pulling access data into C1.ai. diff --git a/baton/sap-cloud-identity.mdx b/baton/sap-cloud-identity.mdx index 58e4d52c..8fbd0212 100644 --- a/baton/sap-cloud-identity.mdx +++ b/baton/sap-cloud-identity.mdx @@ -1,8 +1,8 @@ --- title: "Set up a SAP Cloud Identity connector" og:title: "Set up a SAP Cloud Identity connector" -description: "C1 provides identity governance and just-in-time provisioning for SAP Cloud Identity. Integrate your SAP Cloud Identity 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 SAP Cloud Identity. Integrate your SAP Cloud Identity instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for SAP Cloud Identity. Integrate your SAP Cloud Identity instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for SAP Cloud Identity. Integrate your SAP Cloud Identity instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "SAP Cloud Identity" --- @@ -28,7 +28,7 @@ The SAP Cloud Identity connector supports [automatic account provisioning](/prod ### 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 C1.ai 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 | | -------------- | ---------------------------- | ----------------------------------------------------------------- | @@ -63,11 +63,11 @@ Connector actions are custom capabilities that extend C1 automations with app-sp - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -115,20 +115,20 @@ Connector actions are custom capabilities that extend C1 automations with app-sp - **Done.** Your SAP Cloud Identity connector is now pulling access data into C1. + **Done.** Your SAP Cloud Identity connector is now pulling access data into C1.ai. Follow these instructions to use the [SAP Cloud Identity](https://github.com/conductorone/baton-sap-cloud-identity) 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Step 1: Set up a new SAP Cloud Identity connector - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -224,15 +224,15 @@ Connector actions are custom capabilities that extend C1 automations with app-sp - 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 C1.ai 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 SAP Cloud Identity connector to. SAP Cloud Identity data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the SAP Cloud Identity connector to. SAP Cloud Identity data should be found on the **Entitlements** and **Accounts** tabs. - **Done.** Your SAP Cloud Identity connector is now pulling access data into C1. + **Done.** Your SAP Cloud Identity connector is now pulling access data into C1.ai. diff --git a/baton/sap-grc.mdx b/baton/sap-grc.mdx index a28fca4e..821ef073 100644 --- a/baton/sap-grc.mdx +++ b/baton/sap-grc.mdx @@ -1,8 +1,8 @@ --- title: "Set up an SAP GRC connector" og:title: "Set up an SAP GRC connector" -description: "C1 provides identity governance for SAP GRC. Integrate your SAP GRC instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for SAP GRC. Integrate your SAP GRC instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for SAP GRC. Integrate your SAP GRC instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for SAP GRC. Integrate your SAP GRC instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "SAP GRC" --- @@ -128,7 +128,7 @@ You must have SAP Basis administrator access to complete these steps. ## Configure the SAP GRC connector -To complete this task, you need the **Connector Administrator** or **Super Administrator** role in C1. +To complete this task, you need the **Connector Administrator** or **Super Administrator** role in C1.ai. @@ -139,13 +139,13 @@ To complete this task, you need the **Connector Administrator** or **Super Admin Follow these instructions to use the [SAP GRC](https://dist.conductorone.com/ConductorOne/baton-sap-grc) 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Step 1: Set up a new SAP GRC connector - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -248,14 +248,14 @@ To complete this task, you need the **Connector Administrator** or **Super Admin - 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 C1.ai 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 SAP GRC connector to. SAP GRC data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the SAP GRC connector to. SAP GRC data should be found on the **Entitlements** and **Accounts** tabs. - **Done.** Your SAP GRC connector is now pulling access data into C1. + **Done.** Your SAP GRC connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/scalr.mdx b/baton/scalr.mdx index 963d77ec..7c19e759 100644 --- a/baton/scalr.mdx +++ b/baton/scalr.mdx @@ -1,14 +1,14 @@ --- title: "Set up a Scalr connector" og:title: "Set up a Scalr connector" -description: "C1 provides identity governance for Scalr. Integrate your Scalr account with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Scalr. Integrate your Scalr account with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Scalr. Integrate your Scalr account with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Scalr. Integrate your Scalr account with C1.ai for unified visibility and governance over user access." sidebarTitle: "Scalr" --- {/* stargate: cf-scalr-20260605 */} -C1 provides identity governance for Scalr. Integrate your Scalr account with C1 +C1.ai provides identity governance for Scalr. Integrate your Scalr account with C1.ai for unified visibility and governance over who can sign in to Scalr, their email and account status, and when they last signed in. @@ -52,11 +52,11 @@ account's users. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -98,7 +98,7 @@ account's users. - **Done.** Your Scalr connector is now pulling access data into C1. + **Done.** Your Scalr connector is now pulling access data into C1.ai. @@ -122,6 +122,6 @@ account's users. - **Done.** Your Scalr connector is now pulling access data into C1. + **Done.** Your Scalr connector is now pulling access data into C1.ai. diff --git a/baton/segment.mdx b/baton/segment.mdx index e14b4877..82b0ec6d 100644 --- a/baton/segment.mdx +++ b/baton/segment.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Twilio Segment connector" og:title: "Set up a Twilio Segment connector" -description: "C1 provides identity governance and just-in-time provisioning for Twilio Segment. Integrate your Twilio Segment workspace 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 Twilio Segment. Integrate your Twilio Segment workspace with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for Twilio Segment. Integrate your Twilio Segment workspace with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Twilio Segment. Integrate your Twilio Segment workspace with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "Twilio Segment" --- @@ -57,7 +57,7 @@ To configure the Twilio Segment connector, you need **Workspace Owner** or **Wor - Give the new token a name, such as "C1". + Give the new token a name, such as "C1.ai". Assign the token the **Workspace Owner** access level. @@ -79,11 +79,11 @@ For more information, see the [Segment Access Management documentation](https:// - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -127,13 +127,13 @@ For more information, see the [Segment Access Management documentation](https:// - **Done.** Your Twilio Segment connector is now pulling access data into C1. + **Done.** Your Twilio Segment connector is now pulling access data into C1.ai. Follow these instructions to use the [Twilio Segment](https://github.com/conductorone/baton-segment) 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -146,7 +146,7 @@ For more information, see the [Segment Access Management documentation](https:// - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -243,14 +243,14 @@ For more information, see the [Segment Access Management documentation](https:// - 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 C1.ai 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 Twilio Segment connector to. Twilio Segment data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the Twilio Segment connector to. Twilio Segment data should be found on the **Entitlements** and **Accounts** tabs. - **Done.** Your Twilio Segment connector is now pulling access data into C1. + **Done.** Your Twilio Segment connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/seismic.mdx b/baton/seismic.mdx index b31b3c71..9bbb7d43 100644 --- a/baton/seismic.mdx +++ b/baton/seismic.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Seismic connector" og:title: "Set up a Seismic connector" -description: "C1 provides identity governance and just-in-time provisioning for Seismic. Integrate your Seismic 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 Seismic. Integrate your Seismic instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for Seismic. Integrate your Seismic instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Seismic. Integrate your Seismic instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "Seismic" --- @@ -166,11 +166,11 @@ The Seismic connector syncs the following resources: - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -214,14 +214,14 @@ The Seismic connector syncs the following resources: - **Done.** Your Seismic connector is now pulling access data into C1. + **Done.** Your Seismic connector is now pulling access data into C1.ai. Follow these instructions to use the [Seismic](https://github.com/conductorone/baton-seismic) 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. + When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1.ai, automatically syncing and uploading data at regular intervals. ### Resources @@ -234,7 +234,7 @@ The Seismic connector syncs the following resources: - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -332,15 +332,15 @@ The Seismic connector syncs the following resources: - 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 C1.ai 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 Seismic connector to. Seismic data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the Seismic connector to. Seismic data should be found on the **Entitlements** and **Accounts** tabs. - **Done.** Your Seismic connector is now pulling access data into C1. + **Done.** Your Seismic connector is now pulling access data into C1.ai. diff --git a/baton/sendgrid.mdx b/baton/sendgrid.mdx index da7d5fca..e1c13772 100644 --- a/baton/sendgrid.mdx +++ b/baton/sendgrid.mdx @@ -1,8 +1,8 @@ --- title: Set up a Twilio SendGrid connector -og:title: Set up a Twilio SendGrid connector - C1 docs -og:description: Integrate your SendGrid 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 Twilio SendGrid. Integrate your SendGrid instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a Twilio SendGrid connector - C1.ai docs +og:description: Integrate your SendGrid instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance and just-in-time provisioning for Twilio SendGrid. Integrate your SendGrid instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: "Twilio SendGrid" --- @@ -40,7 +40,7 @@ In SendGrid, navigate to **Settings** > **API Keys**. Click **Create API Key**. -Give your API key a name, such as "C1 integration". +Give your API key a name, such as "C1.ai integration". Select **Full Access**. @@ -59,18 +59,18 @@ The new API key is created. Carefully copy and save the API key. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of SendGrid 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **SendGrid** and click **Add**. @@ -109,13 +109,13 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your SendGrid connector is now pulling access data into C1. +**Done.** Your SendGrid connector is now pulling access data into C1.ai. **Follow these instructions to use the SendGrid connector 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -127,7 +127,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -223,12 +223,12 @@ 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 C1.ai 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 SendGrid connector to. SendGrid data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the SendGrid connector to. SendGrid data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your SendGrid connector is now pulling access data into C1. +**Done.** Your SendGrid connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/sendsafely.mdx b/baton/sendsafely.mdx index c908b4c1..3499f782 100644 --- a/baton/sendsafely.mdx +++ b/baton/sendsafely.mdx @@ -1,13 +1,13 @@ --- title: "Set up a SendSafely connector" og:title: "Set up a SendSafely connector" -description: "C1 provides identity governance for SendSafely. Integrate your SendSafely instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for SendSafely. Integrate your SendSafely instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for SendSafely. Integrate your SendSafely instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for SendSafely. Integrate your SendSafely instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "SendSafely" --- -C1 provides identity governance for SendSafely. Integrate your SendSafely -instance with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for SendSafely. Integrate your SendSafely +instance with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -19,7 +19,7 @@ instance with C1 for unified visibility and governance over user access. The connector syncs your SendSafely users along with their contact group and security group memberships. Each contact group and security group exposes a -**Member** entitlement, and C1 records a grant for every member of the group. +**Member** entitlement, and C1.ai records a grant for every member of the group. This connector is read-only. It does not provision or modify access in SendSafely. @@ -52,11 +52,11 @@ API key can read enterprise contact groups and security groups. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -99,7 +99,7 @@ API key can read enterprise contact groups and security groups. - **Done.** Your SendSafely connector is now pulling access data into C1. + **Done.** Your SendSafely connector is now pulling access data into C1.ai. @@ -126,7 +126,7 @@ API key can read enterprise contact groups and security groups. - **Done.** Your SendSafely connector is now pulling access data into C1. + **Done.** Your SendSafely connector is now pulling access data into C1.ai. diff --git a/baton/sentinel-one.mdx b/baton/sentinel-one.mdx index 852ae48e..991617bf 100644 --- a/baton/sentinel-one.mdx +++ b/baton/sentinel-one.mdx @@ -1,8 +1,8 @@ --- title: Set up a SentinelOne connector -og:title: Set up a SentinelOne connector - C1 docs -og:description: "C1 provides identity governance for SentinelOne. Integrate your SentinelOne instance with C1 for unified visibility and governance over user access." -description: "C1 provides identity governance for SentinelOne. Integrate your SentinelOne instance with C1 for unified visibility and governance over user access." +og:title: Set up a SentinelOne connector - C1.ai docs +og:description: "C1.ai provides identity governance for SentinelOne. Integrate your SentinelOne instance with C1.ai for unified visibility and governance over user access." +description: "C1.ai provides identity governance for SentinelOne. Integrate your SentinelOne instance with C1.ai for unified visibility and governance over user access." sidebarTitle: SentinelOne --- @@ -43,18 +43,18 @@ The API token is created. Carefully copy and save the 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 C1.ai - Access to the set of SentinelOne 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **SentinelOne** and click **Add**. @@ -92,13 +92,13 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your SentinelOne connector is now pulling access data into C1. +**Done.** Your SentinelOne connector is now pulling access data into C1.ai. **Follow these instructions to use the SentinelOne 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -108,7 +108,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -198,14 +198,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 C1.ai 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 SentinelOne connector to. SentinelOne data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the SentinelOne connector to. SentinelOne data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your SentinelOne connector is now pulling access data into C1. +**Done.** Your SentinelOne connector is now pulling access data into C1.ai. diff --git a/baton/sentry.mdx b/baton/sentry.mdx index 5c798c59..19ae17f8 100644 --- a/baton/sentry.mdx +++ b/baton/sentry.mdx @@ -1,13 +1,13 @@ --- title: Set up a Sentry connector -og:title: Set up a Sentry connector - C1 docs -og:description: Integrate your Sentry 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 Sentry. Integrate your Sentry instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a Sentry connector - C1.ai docs +og:description: Integrate your Sentry instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance for Sentry. Integrate your Sentry instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: Sentry --- -**This is an updated and improved version of the Sentry connector!** If you're setting up Sentry with C1 for the first time, you're in the right place. +**This is an updated and improved version of the Sentry connector!** If you're setting up Sentry with C1.ai for the first time, you're in the right place. ## Capabilities @@ -39,7 +39,7 @@ In Sentry, navigate to the settings menu and click **Personal Tokens**. Click **Create New Token**. -On the **Create New Personal Token** page, give your the token a name, such as "C1". +On the **Create New Personal Token** page, give your the token a name, such as "C1.ai". In the **PERMISSIONS** section of the page, give the token the relevant set of permissions: @@ -85,18 +85,18 @@ When this list is set, only the specified organizations — and the users, teams To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Sentry 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Sentry v2** and click **Add**. @@ -128,14 +128,14 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Sentry connector is now pulling access data into C1. +**Done.** Your Sentry connector is now pulling access data into C1.ai. **Follow these instructions to use the Sentry 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -145,7 +145,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -240,13 +240,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 C1.ai 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 Sentry connector to. Sentry data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Sentry connector to. Sentry data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Sentry connector is now pulling access data into C1. +**Done.** Your Sentry connector is now pulling access data into C1.ai. diff --git a/baton/servicedesk-plus.mdx b/baton/servicedesk-plus.mdx index 933edee4..bfd0ad15 100644 --- a/baton/servicedesk-plus.mdx +++ b/baton/servicedesk-plus.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Servicedesk Plus connector" og:title: "Set up a Servicedesk Plus connector" -description: "C1 provides identity governance and just-in-time provisioning for Servicedesk Plus. Integrate your Servicedesk Plus 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 Servicedesk Plus. Integrate your Servicedesk Plus instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for Servicedesk Plus. Integrate your Servicedesk Plus instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Servicedesk Plus. Integrate your Servicedesk Plus instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "Servicedesk Plus" --- @@ -22,7 +22,7 @@ The Servicedesk Plus connector syncs the following resources: {/* AUTO-GENERATED:END - capabilities */} -Account provisioning creates new Servicedesk Plus **requesters**. The connector also supports C1 external ticketing, so you can create and read Servicedesk Plus requests from ConductorOne automations. +Account provisioning creates new Servicedesk Plus **requesters**. The connector also supports C1.ai external ticketing, so you can create and read Servicedesk Plus requests from ConductorOne automations. ## Known limitations @@ -49,7 +49,7 @@ email without ever logging in. To configure the Servicedesk Plus connector, you need administrator permissions in Servicedesk Plus and access to the [Zoho API Console](https://api-console.zoho.com) for the same data center as your Servicedesk Plus tenant. -Servicedesk Plus Cloud authenticates through a Zoho OAuth **self-client**, not an API key. C1 needs a client ID, a client secret, and a refresh token. +Servicedesk Plus Cloud authenticates through a Zoho OAuth **self-client**, not an API key. C1.ai needs a client ID, a client secret, and a refresh token. @@ -80,7 +80,7 @@ Servicedesk Plus Cloud authenticates through a Zoho OAuth **self-client**, not a Exchange the grant code for a **refresh token**, substituting your own values and your data center's accounts host. - The console never shows you a refresh token — the value you copied on the **Generate Code** tab is the grant code, and it is not what C1 needs. This one-time exchange is the only thing that mints a refresh token: + The console never shows you a refresh token — the value you copied on the **Generate Code** tab is the grant code, and it is not what C1.ai needs. This one-time exchange is the only thing that mints a refresh token: ```bash curl -X POST https://accounts.zoho.com/oauth/v2/token \ @@ -90,7 +90,7 @@ Servicedesk Plus Cloud authenticates through a Zoho OAuth **self-client**, not a -d code= ``` - The response's `refresh_token` is what C1 needs. It is returned **only on this first exchange** — if you lose it, generate a new grant code and repeat. + The response's `refresh_token` is what C1.ai needs. It is returned **only on this first exchange** — if you lose it, generate a new grant code and repeat. The refresh token does not expire. Store it as securely as a password: a leaked refresh token grants standing API access until it is manually revoked with `POST /oauth/v2/token/revoke`. Note also that Zoho throttles token issuance to **10 requests per 10 minutes**; the connector caches its access token for the full hour, but rapid connector restarts during testing can trip the limit and surface as an authentication failure. @@ -117,11 +117,11 @@ Servicedesk Plus Cloud authenticates through a Zoho OAuth **self-client**, not a - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -173,19 +173,19 @@ Servicedesk Plus Cloud authenticates through a Zoho OAuth **self-client**, not a - **Done.** Your Servicedesk Plus connector is now pulling access data into C1. + **Done.** Your Servicedesk Plus connector is now pulling access data into C1.ai. Follow these instructions to use the [Servicedesk Plus](https://github.com/conductorone/baton-servicedesk-plus) 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. + When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1.ai, automatically syncing and uploading data at regular intervals. ### Step 1: Set up a new Servicedesk Plus connector - In C1, navigate to **Apps** > **Connectors** > **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** > **Add connector**. @@ -292,15 +292,15 @@ Servicedesk Plus Cloud authenticates through a Zoho OAuth **self-client**, not a - 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 C1.ai 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 Servicedesk Plus connector to. Servicedesk Plus data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the Servicedesk Plus connector to. Servicedesk Plus data should be found on the **Entitlements** and **Accounts** tabs. - **Done.** Your Servicedesk Plus connector is now pulling access data into C1. + **Done.** Your Servicedesk Plus connector is now pulling access data into C1.ai. diff --git a/baton/servicenow.mdx b/baton/servicenow.mdx index 53a36bca..d005582f 100644 --- a/baton/servicenow.mdx +++ b/baton/servicenow.mdx @@ -1,8 +1,8 @@ --- title: Set up a ServiceNow connector -og:title: Set up a ServiceNow connector - C1 docs -og:description: Integrate your ServiceNow 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 ServiceNow. Integrate your ServiceNow instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a ServiceNow connector - C1.ai docs +og:description: Integrate your ServiceNow instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance for ServiceNow. Integrate your ServiceNow instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: ServiceNow --- @@ -19,16 +19,16 @@ The ServiceNow connector supports [automatic account provisioning](/product/admi This connector does not support full account deprovisioning. You can disable accounts using a connector action, but you must deprovision accounts directly in ServiceNow. -C1 syncs only roles marked grantable in ServiceNow. Roles without that flag do not appear in C1, and you cannot grant or revoke them through it. +C1.ai syncs only roles marked grantable in ServiceNow. Roles without that flag do not appear in C1.ai, and you cannot grant or revoke them through it. -C1 cannot revoke a role that a user inherits from a group. ServiceNow re-creates inherited role assignments from group membership, so the role returns on the next sync. Revoke the user's group membership instead. +C1.ai cannot revoke a role that a user inherits from a group. ServiceNow re-creates inherited role assignments from group membership, so the role returns on the next sync. Revoke the user's group membership instead. This connector can also be configured to automatically create and update ServiceNow tickets to track manual provisioning assignments. Go to [Configure ServiceNow as an external ticketing provider](/product/admin/external-ticketing#configure-servicenow-as-an-external-ticketing-provider) to learn more. ### 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 C1.ai 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 | |-------------|-------------------|-------------| @@ -71,7 +71,7 @@ In the ServiceNow admin portal, navigate to **All** > **Access Analyzer**. Fill out the form as follows: * **Analyze by**: User - * **Select user**: choose the user you're using for the C1 integration (with the access control list permissions defined above) + * **Select user**: choose the user you're using for the C1.ai integration (with the access control list permissions defined above) * **Rule type**: Table (record) * **Select table**: Choice @@ -92,9 +92,9 @@ Repeat steps 2 through 6 to add the **Tag** and **Label Entry** tables. Each of | Table | Permissions needed | Reason | | :--- | :--- | :--- | -| Choice (`sys_choice`) | Read | Used to configure request state mappings in your external provisioner config. We monitor the ServiceNow request for this state so we can close the task in C1 accordingly. | -| Tag (`label`) | Create, read, write | Used to create a tag with the provided label in your provisioner config to help you filter requests made by C1. | -| Label Entry (`label_entry`) | Create, read, write | Used to tag requests with the provided label in your provisioner config to help you filter requests made by C1. | +| Choice (`sys_choice`) | Read | Used to configure request state mappings in your external provisioner config. We monitor the ServiceNow request for this state so we can close the task in C1.ai accordingly. | +| Tag (`label`) | Create, read, write | Used to create a tag with the provided label in your provisioner config to help you filter requests made by C1.ai. | +| Label Entry (`label_entry`) | Create, read, write | Used to tag requests with the provided label in your provisioner config to help you filter requests made by C1.ai. | **Note:** The `label_entry` table has **write** ACLs for the `table` and `table_key` fields. This configuration can be changed @@ -114,7 +114,7 @@ In the ServiceNow admin portal, navigate to **All** > **Access Analyzer**. Fill out the form as follows: * **Analyze by**: User - * **Select user**: choose the user you're using for the C1 integration (with the access control list permissions defined above) + * **Select user**: choose the user you're using for the C1.ai integration (with the access control list permissions defined above) * **Rule type**: REST endpoints * **REST endpoint**: `/api/sn_sc/servicecatalog/items` * **REST endpoint method**: GET @@ -135,14 +135,14 @@ Repeat steps 2 through 5 to add the three additional endpoints and methods shown | API endpoint | REST method | Reason | | :--- | :--- | :--- | -| `/api/sn_sc/servicecatalog/items` | GET | Used to sync your catalog items to C1. | -| `/api/sn_sc/servicecatalog/items/` | GET | Used to fetch the catalog item configured for your C1 external ticket provisioner. | +| `/api/sn_sc/servicecatalog/items` | GET | Used to sync your catalog items to C1.ai. | +| `/api/sn_sc/servicecatalog/items/` | GET | Used to fetch the catalog item configured for your C1.ai external ticket provisioner. | | `/api/sn_sc/servicecatalog/items//variables` | GET | Used to get the variables required to make a ServiceNow request. | | `/api/sn_sc/servicecatalog/items//order_now` | POST | Used to create the ServiceNow request. | #### Assign user roles -Follow these steps if you need to assign missing user roles to the user you'll use for the C1 integration. +Follow these steps if you need to assign missing user roles to the user you'll use for the C1.ai integration. @@ -219,17 +219,17 @@ Add a role that is already assigned to your user. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of ServiceNow 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **ServiceNow** and click **Add**. @@ -252,20 +252,20 @@ Click **Add**. The connector is created and its configuration page opens. Find the **Settings** area of the page and click **Edit**. -**Optional.** In the **Allowed emails domains** field, enter the email domain or domains (such as `acme.com` and `contractors.acme.com`) associated with the accounts that you want C1 to sync. When set, C1 also filters group and role membership grants to only include users whose email matches an allowed domain. +**Optional.** In the **Allowed emails domains** field, enter the email domain or domains (such as `acme.com` and `contractors.acme.com`) associated with the accounts that you want C1.ai to sync. When set, C1.ai also filters group and role membership grants to only include users whose email matches an allowed domain. To add multiple allowed domains, press **Enter** between each domain. - Accounts with no email address — including many ServiceNow service accounts — match no domain, so C1 excludes them and their membership grants. + Accounts with no email address — including many ServiceNow service accounts — match no domain, so C1.ai excludes them and their membership grants. - If you leave this field blank, C1 will sync all accounts and membership grants in your ServiceNow instance, regardless of the email domain associated with the account. + If you leave this field blank, C1.ai will sync all accounts and membership grants in your ServiceNow instance, regardless of the email domain associated with the account. -**Optional.** In the **Custom user attributes** field, enter the names of any custom user attribute fields you want C1 to sync from ServiceNow. These are fields that start with `u_` in ServiceNow, such as `u_type`. +**Optional.** In the **Custom user attributes** field, enter the names of any custom user attribute fields you want C1.ai to sync from ServiceNow. These are fields that start with `u_` in ServiceNow, such as `u_type`. To add multiple attributes, press **Enter** between each field name. - Synced custom attributes are included in user profiles in C1 and can be used to filter groups by attribute values. + Synced custom attributes are included in user profiles in C1.ai and can be used to filter groups by attribute values. In the **Deployment** field, enter the ServiceNow deployment ID. @@ -285,7 +285,7 @@ In the **Password** and **Username** fields, enter the credentials for your Serv **Optional.** If you want to automatically create ServiceNow tickets to track provisioning tasks, click to **Enable external ticket processing**. [Read more about external ticketing system integrations here.](/product/admin/external-ticketing) - If you enable this option, you can add a **Catalog ID** or **Category ID** in the relevant fields to filter down catalog items. These fields are optional, but C1 only syncs 100 catalog items, so filtering is recommended. + If you enable this option, you can add a **Catalog ID** or **Category ID** in the relevant fields to filter down catalog items. These fields are optional, but C1.ai only syncs 100 catalog items, so filtering is recommended. Click **Save**. @@ -296,14 +296,14 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your ServiceNow connector is now pulling access data into C1. +**Done.** Your ServiceNow connector is now pulling access data into C1.ai. **Follow these instructions to use the ServiceNow 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -315,7 +315,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -419,13 +419,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 C1.ai 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 ServiceNow connector to. ServiceNow data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the ServiceNow connector to. ServiceNow data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your ServiceNow connector is now pulling access data into C1. +**Done.** Your ServiceNow connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/sevenshifts.mdx b/baton/sevenshifts.mdx index d8673936..7858a535 100644 --- a/baton/sevenshifts.mdx +++ b/baton/sevenshifts.mdx @@ -1,8 +1,8 @@ --- title: "Set up 7Shifts connector" -description: "C1 provides identity governance for 7Shifts. Integrate your 7Shifts instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for 7Shifts. Integrate your 7Shifts instance with C1.ai for unified visibility and governance over user access." og:title: "Set up 7Shifts connector" -og:description: "C1 provides identity governance for 7Shifts. Integrate your 7Shifts instance with C1 for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for 7Shifts. Integrate your 7Shifts instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "7Shifts" --- @@ -40,17 +40,17 @@ See the 7shifts docs for information on how to acquire credentials: [View the do **To complete this task, you’ll need:** -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of 7shifts 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **7shifts** and click **Add**. @@ -83,22 +83,22 @@ See the 7shifts docs for information on how to acquire credentials: [View the do -**That’s it!** Your 7shifts connector is now pulling access data into C1. +**That’s it!** Your 7shifts connector is now pulling access data into C1.ai. **Follow these instructions to use the 7shifts 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources -[Contact C1's support team](mailto:support@c1.ai) to download the latest version of the connector. +[Contact C1.ai's support team](mailto:support@c1.ai) to download the latest version of the connector. ### Step 1: Set up a new 7shifts connector - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -187,14 +187,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 C1.ai 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 sevenshifts connector to. sevenshifts data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the sevenshifts connector to. sevenshifts data should be found on the **Entitlements** and **Accounts** tabs. -**That’s it!** Your 7shifts connector is now pulling access data into C1. +**That’s it!** Your 7shifts connector is now pulling access data into C1.ai. diff --git a/baton/sharepoint.mdx b/baton/sharepoint.mdx index 9cbf9442..b50d25ba 100644 --- a/baton/sharepoint.mdx +++ b/baton/sharepoint.mdx @@ -1,8 +1,8 @@ --- title: Set up a Microsoft SharePoint connector -og:title: Set up a Microsoft SharePoint connector - C1 docs -og:description: "C1 provides identity governance for SharePoint. Integrate your SharePoint instance with C1 for unified visibility and governance over user access." -description: "C1 provides identity governance for SharePoint. Integrate your SharePoint instance with C1 for unified visibility and governance over user access." +og:title: Set up a Microsoft SharePoint connector - C1.ai docs +og:description: "C1.ai provides identity governance for SharePoint. Integrate your SharePoint instance with C1.ai for unified visibility and governance over user access." +description: "C1.ai provides identity governance for SharePoint. Integrate your SharePoint instance with C1.ai for unified visibility and governance over user access." sidebarTitle: Microsoft SharePoint --- @@ -36,7 +36,7 @@ In Microsoft Entra admin center, navigate to **App registrations**. Click **New registration**. -Give the application a name, such as "C1", and select the relevant supported account type. You do not need to set a redirect URI. +Give the application a name, such as "C1.ai", and select the relevant supported account type. You do not need to set a redirect URI. Click **Register**. @@ -95,7 +95,7 @@ Some SharePoint groups have *"Who can view the membership of the group"* set to **What the flag does:** when enabled, it skips any SharePoint group whose membership visibility is restricted (regardless of the permission you granted), so those groups and their memberships are excluded from the sync. -**Enabling it on an existing connector:** if the connector previously synced these groups (for example, while using `Sites.FullControl.All`), enabling the flag will remove those groups and their grants from C1 on the next sync, since they're now excluded. +**Enabling it on an existing connector:** if the connector previously synced these groups (for example, while using `Sites.FullControl.All`), enabling the flag will remove those groups and their grants from C1.ai on the next sync, since they're now excluded. ### Create and upload a self-signed certificate @@ -133,10 +133,10 @@ SharePoint defines groups and users **once per site collection**, not once per s Enabling the **deduplicate-site-collection-groups** flag (or setting `BATON_DEDUPLICATE_SITE_COLLECTION_GROUPS=true`) syncs each site collection's groups, users, and administrators a single time, at the collection's root site. Subsites under the `/sites` and `/teams` managed paths, and a first-level web directly under the host root (e.g. `https://host/subweb`), are still synced as **Site** resources, but they're nested under their collection's root site and no longer carry their own group entitlements or grants. A site whose collection root can't be derived from its URL (a custom managed path like `/portals/`, or a web nested more than one level under the host root) is left un-nested and keeps its own groups, users, and administrators — the same as with the flag off — since there's no root to safely consolidate it under. -The flag is **off by default**, so existing connectors keep their current behavior until you turn it on. New connectors created in C1 have the toggle **pre-checked on**, since deduplication is the recommended setting going forward — uncheck it during setup if you'd rather opt in later. +The flag is **off by default**, so existing connectors keep their current behavior until you turn it on. New connectors created in C1.ai have the toggle **pre-checked on**, since deduplication is the recommended setting going forward — uncheck it during setup if you'd rather opt in later. -**Enabling it on an existing connector produces one large diff.** On the first sync after you enable the flag, C1 removes the duplicate SharePoint group resources, re-parents the remaining groups to their site collection root, re-parents subsites under their root site, and removes subsite-level administrator grants. This is expected: the access data itself is unchanged, but the resources representing it are consolidated. Subsequent syncs are stable. +**Enabling it on an existing connector produces one large diff.** On the first sync after you enable the flag, C1.ai removes the duplicate SharePoint group resources, re-parents the remaining groups to their site collection root, re-parents subsites under their root site, and removes subsite-level administrator grants. This is expected: the access data itself is unchanged, but the resources representing it are consolidated. Subsequent syncs are stable. If you have access reviews or policies that reference specific duplicate group resources, review them before enabling the flag. @@ -146,17 +146,17 @@ If you have access reviews or policies that reference specific duplicate group r To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of SharePoint 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **SharePoint** and click **Add**. @@ -205,7 +205,7 @@ Enter your SharePoint subdomain in the **SharePoint domain** field. (For example Click **Save**. -Finally, tell the connector where to find the identities that will be used for this app in C1. +Finally, tell the connector where to find the identities that will be used for this app in C1.ai. 1. In the **Shared identity source** area of the page, click **Edit**. @@ -219,22 +219,22 @@ Finally, tell the connector where to find the identities that will be used for t The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your SharePoint connector is now pulling access data into C1. +**Done.** Your SharePoint connector is now pulling access data into C1.ai. **Follow these instructions to use the SharePoint 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai 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 C1.ai's support team](mailto:support@conductorone.com) to download the latest version of the connector. ### Step 1: Configure the SharePoint connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -334,12 +334,12 @@ 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 C1.ai 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 SharePoint connector to. SharePoint data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the SharePoint connector to. SharePoint data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your SharePoint connector is now pulling access data into C1. +**Done.** Your SharePoint connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/shareworks.mdx b/baton/shareworks.mdx index 7f4afd84..f4efed3e 100644 --- a/baton/shareworks.mdx +++ b/baton/shareworks.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Shareworks connector" og:title: "Set up a Shareworks connector" -description: "C1 provides identity governance for Shareworks. Integrate your Shareworks instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Shareworks. Integrate your Shareworks instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Shareworks. Integrate your Shareworks instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Shareworks. Integrate your Shareworks instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Shareworks" --- -C1 provides identity governance for Shareworks by Morgan Stanley. Integrate your -Shareworks instance with C1 for unified visibility and governance over equity +C1.ai provides identity governance for Shareworks by Morgan Stanley. Integrate your +Shareworks instance with C1.ai for unified visibility and governance over equity plan participant access. ## Capabilities @@ -77,11 +77,11 @@ performs read-only API calls. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -125,7 +125,7 @@ performs read-only API calls. - **Done.** Your Shareworks connector is now pulling access data into C1. + **Done.** Your Shareworks connector is now pulling access data into C1.ai. @@ -147,6 +147,6 @@ performs read-only API calls. - **Done.** Your Shareworks connector is now pulling access data into C1. + **Done.** Your Shareworks connector is now pulling access data into C1.ai. diff --git a/baton/shopify.mdx b/baton/shopify.mdx index c4c69fb7..232af8c4 100644 --- a/baton/shopify.mdx +++ b/baton/shopify.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Shopify connector" og:title: "Set up a Shopify connector" -description: "C1 provides identity governance for Shopify. Integrate your Shopify store with C1 for unified visibility and governance over staff user access." -og:description: "C1 provides identity governance for Shopify. Integrate your Shopify store with C1 for unified visibility and governance over staff user access." +description: "C1.ai provides identity governance for Shopify. Integrate your Shopify store with C1.ai for unified visibility and governance over staff user access." +og:description: "C1.ai provides identity governance for Shopify. Integrate your Shopify store with C1.ai for unified visibility and governance over staff user access." sidebarTitle: "Shopify" --- -C1 provides identity governance for Shopify. Integrate your Shopify store -with C1 for unified visibility and governance over staff user access. +C1.ai provides identity governance for Shopify. Integrate your Shopify store +with C1.ai for unified visibility and governance over staff user access. ## Capabilities @@ -59,11 +59,11 @@ To configure this connector you need: - Follow these instructions to use a built-in connector hosted by C1. + Follow these instructions to use a built-in connector hosted by C1.ai. - In C1, navigate to **Apps > Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps > Connectors** and click **Add connector**. @@ -94,7 +94,7 @@ To configure this connector you need: - **Done.** Your Shopify connector is now pulling access data into C1. + **Done.** Your Shopify connector is now pulling access data into C1.ai. @@ -118,6 +118,6 @@ To configure this connector you need: - **Done.** Your Shopify connector is now pulling access data into C1. + **Done.** Your Shopify connector is now pulling access data into C1.ai. diff --git a/baton/shortcut.mdx b/baton/shortcut.mdx index 6f82a7a6..b7e0179a 100644 --- a/baton/shortcut.mdx +++ b/baton/shortcut.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Shortcut connector" og:title: "Set up a Shortcut connector" -description: "C1 provides identity governance for Shortcut. Integrate your Shortcut instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Shortcut. Integrate your Shortcut instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Shortcut. Integrate your Shortcut instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Shortcut. Integrate your Shortcut instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Shortcut" --- -C1 provides identity governance for Shortcut. Integrate your Shortcut -workspace with C1 for unified visibility and governance over members and +C1.ai provides identity governance for Shortcut. Integrate your Shortcut +workspace with C1.ai for unified visibility and governance over members and group membership. ## Capabilities @@ -53,11 +53,11 @@ connector only reads members and groups — write scope is not required. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -99,7 +99,7 @@ connector only reads members and groups — write scope is not required. - **Done.** Your Shortcut connector is now pulling access data into C1. + **Done.** Your Shortcut connector is now pulling access data into C1.ai. @@ -125,7 +125,7 @@ connector only reads members and groups — write scope is not required. - **Done.** Your Shortcut connector is now pulling access data into C1. + **Done.** Your Shortcut connector is now pulling access data into C1.ai. diff --git a/baton/sigmacomputing.mdx b/baton/sigmacomputing.mdx index 61976353..6479d89f 100644 --- a/baton/sigmacomputing.mdx +++ b/baton/sigmacomputing.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Sigma Computing connector" og:title: "Set up a Sigma Computing connector" -description: "C1 provides identity governance and just-in-time provisioning for Sigma Computing. Integrate Sigma Computing with C1 to review and provision access." -og:description: "C1 provides identity governance and just-in-time provisioning for Sigma Computing. Integrate Sigma Computing with C1 to review and provision access." +description: "C1.ai provides identity governance and just-in-time provisioning for Sigma Computing. Integrate Sigma Computing with C1.ai to review and provision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Sigma Computing. Integrate Sigma Computing with C1.ai to review and provision access." sidebarTitle: "Sigma Computing" --- @@ -26,7 +26,7 @@ The Sigma Computing connector supports [automatic account provisioning and depro **Notes:** -- Team Admin access is sync-only. You can review Team Admin access in C1, but Sigma's API does not support granting or revoking it. +- Team Admin access is sync-only. You can review Team Admin access in C1.ai, but Sigma's API does not support granting or revoking it. - New accounts default to the **View** member type when **Member Type** is empty. The connector does not change an existing account's member type. - The account creation form retains **User Kind** and **Send Invitation** for compatibility, but changing these fields has no effect. Sigma's defaults apply, including sending an invitation email to non-embed users. - Account sync excludes archived and inactive members. Deleting an account archives it, reassigns its documents to the credential owner, and removes it from later syncs. @@ -77,17 +77,17 @@ For more information, see [Generate Sigma API client credentials](https://help.s To complete this task, you need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Your Sigma API base URL, Client ID, and Client Secret -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 C1.ai. -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -136,13 +136,13 @@ The connector's label changes to **Syncing**, followed by **Connected**. View th -**Done.** Your Sigma Computing connector is now pulling access data into C1. +**Done.** Your Sigma Computing connector is now pulling access data into C1.ai. Follow these instructions to host and run the [Sigma Computing connector](https://github.com/conductorone/baton-sigmacomputing) in your environment. -When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1 and uploads data at regular intervals. +When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1.ai and uploads data at regular intervals. ### Resources @@ -153,7 +153,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** > **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** > **Add connector**. @@ -182,7 +182,7 @@ In the **Settings** area, click **Edit**. -Click **Rotate** to generate a new C1 Client ID and Secret. Copy and securely store both values for Step 2. +Click **Rotate** to generate a new C1.ai Client ID and Secret. Copy and securely store both values for Step 2. @@ -252,15 +252,15 @@ spec: -Create a namespace for C1 connectors if desired, and apply the secret and deployment configuration files. +Create a namespace for C1.ai connectors if desired, and apply the secret and deployment configuration files. -In C1, click **Applications**. On the **Managed apps** tab, open the application with the Sigma Computing connector and confirm that Sigma data appears on the **Entitlements** and **Accounts** tabs. +In C1.ai, click **Applications**. On the **Managed apps** tab, open the application with the Sigma Computing connector and confirm that Sigma data appears on the **Entitlements** and **Accounts** tabs. -**Done.** Your Sigma Computing connector is now pulling access data into C1. +**Done.** Your Sigma Computing connector is now pulling access data into C1.ai. diff --git a/baton/sisense.mdx b/baton/sisense.mdx index 54bb4434..d8b2f573 100644 --- a/baton/sisense.mdx +++ b/baton/sisense.mdx @@ -1,8 +1,8 @@ --- title: Set up Sisense connector -og:title: Set up Sisense connector - C1 docs -og:description: Integrate your Sisense 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 Sisense. Integrate your Sisense instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up Sisense connector - C1.ai docs +og:description: Integrate your Sisense instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance and just-in-time provisioning for Sisense. Integrate your Sisense instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: Sisense --- @@ -24,7 +24,7 @@ We recommend closely monitoring workflows that use this connector and contacting Supports [automatic account provisioning and deprovisioning](/product/admin/account-provisioning) - When a new account is created by C1, the account's password will be sent to a [vault](/product/admin/vaults) + When a new account is created by C1.ai, the account's password will be sent to a [vault](/product/admin/vaults) Syncs last login info @@ -43,17 +43,17 @@ Here's the information you'll need: To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1. +- The **Connector Administrator** or **Super Administrator** role in C1.ai. - Access to the set of Sisense 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Sisense** and click **Add**. @@ -85,22 +85,22 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Sisense connector is now pulling access data into C1. +**Done.** Your Sisense connector is now pulling access data into C1.ai. **Follow these instructions to use the Sisense 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources -[Contact C1's support team](mailto:support@c1.ai) to download the latest version of the connector. +[Contact C1.ai's support team](mailto:support@c1.ai) to download the latest version of the connector. ### Step 1: Set up a new Sisense connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -195,13 +195,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 C1.ai 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 sisense connector to. sisense data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the sisense connector to. sisense data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Sisense connector is now pulling access data into C1. +**Done.** Your Sisense connector is now pulling access data into C1.ai. diff --git a/baton/slack-enterprise.mdx b/baton/slack-enterprise.mdx index e20f8ef6..8d081749 100644 --- a/baton/slack-enterprise.mdx +++ b/baton/slack-enterprise.mdx @@ -1,17 +1,17 @@ --- title: Set up a Slack Enterprise Grid connector -og:title: Set up a Slack Enterprise Grid connector - C1 docs -og:description: Integrate your Slack Enterprise Grid 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 Slack Enterprise Grid. Integrate your Slack Enterprise Grid instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a Slack Enterprise Grid connector - C1.ai docs +og:description: Integrate your Slack Enterprise Grid instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance and just-in-time provisioning for Slack Enterprise Grid. Integrate your Slack Enterprise Grid instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: Slack Enterprise Grid --- -**Yes, there are TWO kinds of Slack integration!** The instructions below integrate a Slack Enterprise Grid account with C1 so that you can review access data and grant user access to Slack. This integration supports GovSlack. +**Yes, there are TWO kinds of Slack integration!** The instructions below integrate a Slack Enterprise Grid account with C1.ai so that you can review access data and grant user access to Slack. This integration supports GovSlack. (We also have an integration for [Slack Pro and Business+ accounts](/baton/slack).) -If you want to install the C1 app for Slack, so that you and your colleagues can request access and get notifications about new C1 tasks in your Slack workspace, go to the **Settings** page in C1 and click **Notifications**. +If you want to install the C1.ai app for Slack, so that you and your colleagues can request access and get notifications about new C1.ai tasks in your Slack workspace, go to the **Settings** page in C1.ai and click **Notifications**. ## Capabilities @@ -31,7 +31,7 @@ The Slack Enterprise Grid connector supports [automatic account provisioning](/p ### 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 C1.ai 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 | |-------------|-------------------|-------------| @@ -46,7 +46,7 @@ Configuring the connector requires you to pass in credentials generated in Slack A user with the **Org owner** role in Slack Enterprise Grid must perform this task. -### Create a C1 app in Slack Enterprise Grid +### Create a C1.ai app in Slack Enterprise Grid @@ -56,7 +56,7 @@ Make sure you are signed into your Slack Enterprise Grid account, then navigate Click **Create an App** and select the **From scratch** option. -Give your new app a name, such as "C1 integration", and select a workspace you want to integrate with C1 (later we'll install the app org-wide). +Give your new app a name, such as "C1.ai integration", and select a workspace you want to integrate with C1.ai (later we'll install the app org-wide). Click **Create App**. @@ -78,7 +78,7 @@ Scroll down to the **Scopes** section of the page. In the **Bot Token Scopes** a - groups:read - team:read - usergroups:read - - usergroups:write (include only if you want C1 to provision user group membership) + - usergroups:write (include only if you want C1.ai to provision user group membership) - users.profile:read - users:read - users:read.email @@ -88,18 +88,18 @@ In the **User Token Scopes** area, add the following OAuth Scopes: - admin - admin.roles:read - - admin.roles:write (include only if you want C1 to provision access) + - admin.roles:write (include only if you want C1.ai to provision access) - admin.teams:read - admin.usergroups:read - - admin.usergroups:write (include only if you want C1 to provision user group membership) + - admin.usergroups:write (include only if you want C1.ai to provision user group membership) - admin.users:read - - admin.users:write (include only if you want C1 to provision access) - - usergroups:write (include only if you want C1 to provision user group membership) + - admin.users:write (include only if you want C1.ai to provision access) + - usergroups:write (include only if you want C1.ai to provision user group membership) -### Install the C1 app org-wide +### Install the C1.ai app org-wide -You must now install the new app org-wide so that C1 can sync data from all of your organization's workspaces. +You must now install the new app org-wide so that C1.ai can sync data from all of your organization's workspaces. @@ -110,7 +110,7 @@ Carefully copy and save the token values. -### Add the C1 app to all workspaces +### Add the C1.ai app to all workspaces @@ -139,17 +139,17 @@ Click **Add 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 C1.ai - Access to the set of Slack Enterprise Grid 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Slack Enterprise Grid** and click **Add**. @@ -187,12 +187,12 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Slack Enterprise Grid connector is now pulling access data into C1. +**Done.** Your Slack Enterprise Grid connector is now pulling access data into C1.ai. **Follow these instructions to use the Slack 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -204,7 +204,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -304,13 +304,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 C1.ai 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 Slack Enterprise Grid connector to. Slack Enterprise Grid data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Slack Enterprise Grid connector to. Slack Enterprise Grid data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Slack Enterprise Grid connector is now pulling access data into C1. +**Done.** Your Slack Enterprise Grid connector is now pulling access data into C1.ai. diff --git a/baton/slack.mdx b/baton/slack.mdx index 826dc881..3b76d10b 100644 --- a/baton/slack.mdx +++ b/baton/slack.mdx @@ -1,17 +1,17 @@ --- title: Set up a Slack connector -og:title: Set up a Slack connector - C1 docs -og:description: Integrate your Slack 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 Slack. Integrate your Slack instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a Slack connector - C1.ai docs +og:description: Integrate your Slack instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance and just-in-time provisioning for Slack. Integrate your Slack instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: Slack --- -**Yes, there are TWO kinds of Slack integration!** The instructions below connect a Slack Pro or Business+ workspace with C1 so that you can review access data and grant user access to Slack. +**Yes, there are TWO kinds of Slack integration!** The instructions below connect a Slack Pro or Business+ workspace with C1.ai so that you can review access data and grant user access to Slack. (We also have an connector for [Slack Enterprise Grid accounts](/baton/slack-enterprise).) -If you want to install the C1 app for Slack, so that you and your colleagues can request access and get notifications about new C1 tasks in your Slack workspace, go to the **Settings** page in C1 and click **Notifications**. +If you want to install the C1.ai app for Slack, so that you and your colleagues can request access and get notifications about new C1.ai tasks in your Slack workspace, go to the **Settings** page in C1.ai and click **Notifications**. ## Capabilities @@ -49,7 +49,7 @@ A limitation in the Slack APIs means that [automatic account provisioning](/prod ### 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 C1.ai 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 | |-------------|-------------------|-------------| @@ -74,7 +74,7 @@ Make sure you are signed into Slack, then navigate to [api.slack.com/apps/](http Click **Create an App** and select the **From scratch** option. -Give your new Slack app a name, such as "C1 integration", and select the workspace you want to integrate with C1. +Give your new Slack app a name, such as "C1.ai integration", and select the workspace you want to integrate with C1.ai. Click **Create App**. @@ -122,18 +122,18 @@ Your user OAuth token is created. Copy and save the token value. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Slack 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Slack** and click **Add**. @@ -171,13 +171,13 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Slack connector is now pulling access data into C1. +**Done.** Your Slack connector is now pulling access data into C1.ai. **Follow these instructions to use the Slack 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -189,7 +189,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -287,13 +287,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 C1.ai 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 Slack connector to. Slack data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Slack connector to. Slack data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Slack connector is now pulling access data into C1. +**Done.** Your Slack connector is now pulling access data into C1.ai. diff --git a/baton/smartrecruiters.mdx b/baton/smartrecruiters.mdx index eca70ba9..9db3f303 100644 --- a/baton/smartrecruiters.mdx +++ b/baton/smartrecruiters.mdx @@ -1,13 +1,13 @@ --- title: "Set up a SmartRecruiters connector" og:title: "Set up a SmartRecruiters connector" -description: "C1 provides identity governance for SmartRecruiters. Integrate your SmartRecruiters company with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for SmartRecruiters. Integrate your SmartRecruiters company with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for SmartRecruiters. Integrate your SmartRecruiters company with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for SmartRecruiters. Integrate your SmartRecruiters company with C1.ai for unified visibility and governance over user access." sidebarTitle: "SmartRecruiters" --- -C1 provides identity governance for SmartRecruiters. Integrate your -SmartRecruiters company with C1 for unified visibility and governance over who +C1.ai provides identity governance for SmartRecruiters. Integrate your +SmartRecruiters company with C1.ai for unified visibility and governance over who has access to your hiring data. ## Capabilities @@ -49,11 +49,11 @@ your SmartRecruiters company. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -94,7 +94,7 @@ your SmartRecruiters company. - **Done.** Your SmartRecruiters connector is now pulling access data into C1. + **Done.** Your SmartRecruiters connector is now pulling access data into C1.ai. @@ -117,6 +117,6 @@ your SmartRecruiters company. - **Done.** Your SmartRecruiters connector is now pulling access data into C1. + **Done.** Your SmartRecruiters connector is now pulling access data into C1.ai. diff --git a/baton/smartsheet.mdx b/baton/smartsheet.mdx index 1ce333e3..4327c10c 100644 --- a/baton/smartsheet.mdx +++ b/baton/smartsheet.mdx @@ -1,8 +1,8 @@ --- title: Set up a Smartsheet connector -og:title: Set up a Smartsheet connector - C1 docs -og:description: "C1 provides identity governance for Smartsheet. Integrate your Smartsheet instance with C1 for unified visibility and governance over user access." -description: "C1 provides identity governance for Smartsheet. Integrate your Smartsheet instance with C1 for unified visibility and governance over user access." +og:title: Set up a Smartsheet connector - C1.ai docs +og:description: "C1.ai provides identity governance for Smartsheet. Integrate your Smartsheet instance with C1.ai for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Smartsheet. Integrate your Smartsheet instance with C1.ai for unified visibility and governance over user access." sidebarTitle: Smartsheet --- @@ -33,18 +33,18 @@ See the Smartsheet docs for information on how to acquire credentials: [View the To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Smartsheet 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Smartsheet** and click **Add**. @@ -76,13 +76,13 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Smartsheet connector is now pulling access data into C1. +**Done.** Your Smartsheet connector is now pulling access data into C1.ai. **Follow these instructions to use the Smartsheet 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -92,7 +92,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -184,13 +184,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 C1.ai 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 smartsheet connector to. smartsheet data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the smartsheet connector to. smartsheet data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Smartsheet connector is now pulling access data into C1. +**Done.** Your Smartsheet connector is now pulling access data into C1.ai. diff --git a/baton/snipe-it.mdx b/baton/snipe-it.mdx index 43e66ad5..78debfc2 100644 --- a/baton/snipe-it.mdx +++ b/baton/snipe-it.mdx @@ -1,8 +1,8 @@ --- title: Set up a Snipe-IT connector -og:title: Set up a Snipe-IT connector - C1 docs -og:description: Integrate your Snipe-IT 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 Snipe-IT. Integrate your Snipe-IT instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a Snipe-IT connector - C1.ai docs +og:description: Integrate your Snipe-IT instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance and just-in-time provisioning for Snipe-IT. Integrate your Snipe-IT instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: Snipe-IT --- @@ -39,18 +39,18 @@ Carefully copy and save the new 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 C1.ai - Access to the set of Snipe-IT credentials generated by following the instructions above -**Follow these instructions to use a built-in, no-code connector hosted by C1.** +**Follow these instructions to use a built-in, no-code connector hosted by C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Snipe-IT** and click **Add**. @@ -85,13 +85,13 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Snipe-IT connector is now pulling access data into C1. +**Done.** Your Snipe-IT connector is now pulling access data into C1.ai. **Follow these instructions to use the Snipe-IT connector, hosted and run in your own environment.** -When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1 UI for access reviews and access requests. +When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -101,7 +101,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -194,13 +194,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 C1.ai connectors (if desired), then apply the secret config and deployment config files. -Check that the connector data uploaded correctly. In C1, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Snipe-IT connector to. Snipe-IT data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Snipe-IT connector to. Snipe-IT data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Snipe-IT connector is now pulling access data into C1. +**Done.** Your Snipe-IT connector is now pulling access data into C1.ai. diff --git a/baton/snowflake.mdx b/baton/snowflake.mdx index 663f2a70..e5c21025 100644 --- a/baton/snowflake.mdx +++ b/baton/snowflake.mdx @@ -1,13 +1,13 @@ --- title: Set up a Snowflake connector -og:title: Set up a Snowflake connector - C1 docs -og:description: Integrate your Snowflake 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 Snowflake. Integrate your Snowflake instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a Snowflake connector - C1.ai docs +og:description: Integrate your Snowflake instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance for Snowflake. Integrate your Snowflake instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: Snowflake --- -**This is an updated and improved version of the Snowflake connector!** If you're setting up Snowflake with C1 for the first time, you're in the right place. +**This is an updated and improved version of the Snowflake connector!** If you're setting up Snowflake with C1.ai for the first time, you're in the right place. ## Capabilities @@ -33,7 +33,7 @@ Enable **Issue credentials** to let the connector issue a Snowflake [programmati **Issue credentials** and **Sync secrets** are independent. Enabling **Issue credentials** lets the connector mint and revoke programmatic access tokens, and nothing else; enabling **Sync secrets** inventories Snowflake secrets and RSA public keys without granting the ability to mint tokens. Existing programmatic access tokens are inventoried through the opt-in **Programmatic access token** resource type. -**Inventorying programmatic access tokens requires a privilege on each user.** The **Programmatic access token** resource type is opt-in: enable it in C1 when you want existing tokens in your inventory. While it is enabled, the sync runs `SHOW USER PROGRAMMATIC ACCESS TOKENS FOR USER` for each user in the account, and Snowflake requires ownership of that user or the `MODIFY PROGRAMMATIC AUTHENTICATION METHODS` privilege on it. When the connector's role has neither, the sync fails with an error naming that user instead of silently dropping previously synced tokens — those tokens stay live in Snowflake, and C1 needs its records to keep offering revocation for them. Grant the privilege with `GRANT MODIFY PROGRAMMATIC AUTHENTICATION METHODS ON USER TO ROLE ` (or transfer ownership of the user) before enabling the type. +**Inventorying programmatic access tokens requires a privilege on each user.** The **Programmatic access token** resource type is opt-in: enable it in C1.ai when you want existing tokens in your inventory. While it is enabled, the sync runs `SHOW USER PROGRAMMATIC ACCESS TOKENS FOR USER` for each user in the account, and Snowflake requires ownership of that user or the `MODIFY PROGRAMMATIC AUTHENTICATION METHODS` privilege on it. When the connector's role has neither, the sync fails with an error naming that user instead of silently dropping previously synced tokens — those tokens stay live in Snowflake, and C1.ai needs its records to keep offering revocation for them. Grant the privilege with `GRANT MODIFY PROGRAMMATIC AUTHENTICATION METHODS ON USER TO ROLE ` (or transfer ownership of the user) before enabling the type. Token lifetime is set by the requester. Snowflake accepts whole days only, and the connector rounds down so a token never outlives the requested expiry. The minimum is one day and the maximum is one year; when no expiry is requested the token lasts 15 days. @@ -56,11 +56,11 @@ Token lifetime is set by the requester. Snowflake accepts whole days only, and t ### Connector actions -Connector actions are custom capabilities that extend C1 automations with app-specific operations. +Connector actions are custom capabilities that extend C1.ai automations with app-specific operations. | Automation step | Actions offered | How the target is selected | |-----------------|-----------------|----------------------------| -| Account lifecycle action | `enable_user`, `disable_user` | The step's own target-account selector — either the account in context or a specific account. C1 resolves `user_id` from that account. | +| Account lifecycle action | `enable_user`, `disable_user` | The step's own target-account selector — either the account in context or a specific account. C1.ai resolves `user_id` from that account. | Both actions accept the following fields: @@ -74,7 +74,7 @@ Both actions accept the following fields: This restriction stays hidden when the service account keeps Snowflake's default `DEFAULT_SECONDARY_ROLES = ALL`: a higher secondary role such as `ACCOUNTADMIN` remains active alongside the `USERADMIN` primary role and supplies the privilege. Accounts restricted to `USERADMIN` alone are the ones that hit it. -**`enable_user` does not clear an account lockout.** Snowflake can independently lock a user out after repeated failed logins (tracked via `SNOWFLAKE_LOCK`/`MINS_TO_UNLOCK`), separately from the `DISABLED` property these actions toggle. `enable_user` only clears `DISABLED` - a locked-out user stays locked, and the C1 resource still reports a disabled status (`details: "locked"`) until an administrator clears the lockout directly in Snowflake. +**`enable_user` does not clear an account lockout.** Snowflake can independently lock a user out after repeated failed logins (tracked via `SNOWFLAKE_LOCK`/`MINS_TO_UNLOCK`), separately from the `DISABLED` property these actions toggle. `enable_user` only clears `DISABLED` - a locked-out user stays locked, and the C1.ai resource still reports a disabled status (`details: "locked"`) until an administrator clears the lockout directly in Snowflake. ## Gather Snowflake credentials @@ -82,7 +82,7 @@ This restriction stays hidden when the service account keeps Snowflake's default Configuring the connector requires you to pass in credentials generated in Snowflake. Gather these credentials before you move on. -**For best results, use a dedicated service account.** C1 will use the `DEFAULT_WAREHOUSE`, `DEFAULT_NAMESPACE`, and `DEFAULT_ROLE` properties of the user used for the integration. For this reason, we recommend creating a dedicated service account in Snowflake for integrating with C1 with these default user properties. +**For best results, use a dedicated service account.** C1.ai will use the `DEFAULT_WAREHOUSE`, `DEFAULT_NAMESPACE`, and `DEFAULT_ROLE` properties of the user used for the integration. For this reason, we recommend creating a dedicated service account in Snowflake for integrating with C1.ai with these default user properties. Give the service account the `MONITOR USAGE` and `MANAGE GRANTS` global permissions for the default warehouse and namespace, plus the `MONITOR` privilege on each user secret and database. @@ -134,17 +134,17 @@ Find your account identifier by navigating in the Snowflake console to your acco To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Snowflake 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Snowflake v2** and click **Add**. @@ -195,12 +195,12 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Snowflake connector is now pulling access data into C1. +**Done.** Your Snowflake connector is now pulling access data into C1.ai. **Follow these instructions to use the Snowflake 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -210,7 +210,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -308,13 +308,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 C1.ai 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 Snowflake connector to. Snowflake data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Snowflake connector to. Snowflake data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Snowflake connector is now pulling access data into C1. +**Done.** Your Snowflake connector is now pulling access data into C1.ai. @@ -326,9 +326,9 @@ If you're seeing a `422 unprocessable entity` or `401 unauthorized` error in the ### Connector fails when Snowflake IP allowlisting is enabled -If your Snowflake account has a [network policy](https://docs.snowflake.com/en/user-guide/network-policies) configured that restricts access by IP address, you must add C1's egress IP addresses to the allowlist. Otherwise, Snowflake will reject connections from the connector. +If your Snowflake account has a [network policy](https://docs.snowflake.com/en/user-guide/network-policies) configured that restricts access by IP address, you must add C1.ai's egress IP addresses to the allowlist. Otherwise, Snowflake will reject connections from the connector. -For **cloud-hosted connectors**, C1 manages the connector infrastructure. Add C1's connector egress IPs to your Snowflake network policy. See [C1 egress IP addresses](https://www.c1.ai/docs/product/admin/egress-ips) for the current list. +For **cloud-hosted connectors**, C1.ai manages the connector infrastructure. Add C1.ai's connector egress IPs to your Snowflake network policy. See [C1.ai egress IP addresses](https://www.c1.ai/docs/product/admin/egress-ips) for the current list. For **self-hosted connectors**, the connector runs on your own infrastructure, so you should add the outbound IP addresses of your own environment instead. diff --git a/baton/snyk.mdx b/baton/snyk.mdx index d8dcf6b5..2f78419c 100644 --- a/baton/snyk.mdx +++ b/baton/snyk.mdx @@ -1,14 +1,14 @@ --- title: Set up a Snyk connector -og:title: Set up a Snyk connector - C1 docs -og:description: Integrate your Snyk Enterprise 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 Snyk. Integrate your Snyk Enterprise instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a Snyk connector - C1.ai docs +og:description: Integrate your Snyk Enterprise instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance and just-in-time provisioning for Snyk. Integrate your Snyk Enterprise instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: Snyk --- ## Availability -C1 currently only integrates with Snyk Enterprise. C1 can only integrate with Snyk editions that include API access. You cannot use this connector successfully with the Free or Team editions of Snyk. +C1.ai currently only integrates with Snyk Enterprise. C1.ai can only integrate with Snyk editions that include API access. You cannot use this connector successfully with the Free or Team editions of Snyk. ## Capabilities @@ -21,7 +21,7 @@ C1 currently only integrates with Snyk Enterprise. C1 can only integrate with Sn | Service Accounts | | | -**Revoking an organization entitlement for a service account permanently deletes that service account from the organization.** This is a destructive, irreversible action. C1 will reflect the removal after the next sync. +**Revoking an organization entitlement for a service account permanently deletes that service account from the organization.** This is a destructive, irreversible action. C1.ai will reflect the removal after the next sync. ## Gather Snyk credentials @@ -31,7 +31,7 @@ Configuring the connector requires you to pass in credentials generated in Snyk. A user with access to a service or user account in Snyk with **Group Admin** permissions on the Group you're integrating must perform this task. -If you want to provision invitations using C1, the account used to generate the API token must also have the `org.read`, `org.user.read`, and `org.user.invite` permissions. +If you want to provision invitations using C1.ai, the account used to generate the API token must also have the `org.read`, `org.user.read`, and `org.user.invite` permissions. @@ -69,18 +69,18 @@ In the **Group ID** section of the page, carefully copy and save the group ID. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Snyk 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Snyk** and click **Add**. @@ -109,9 +109,9 @@ Paste the API key into the **API key** field. Paste the Group ID into the **Group ID** field. -**Optional.** If you want C1 to only sync access data from specific Snyk organizations, enter the organization names in the **Org IDs** field. +**Optional.** If you want C1.ai to only sync access data from specific Snyk organizations, enter the organization names in the **Org IDs** field. - If you leave this field blank, C1 will sync data from all organizations. + If you leave this field blank, C1.ai will sync data from all organizations. When Org IDs are specified, org-level service accounts are also scoped to only those organizations. Group-level service accounts are always synced regardless of this setting. @@ -130,12 +130,12 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Snyk connector is now pulling access data into C1. +**Done.** Your Snyk connector is now pulling access data into C1.ai. **Follow these instructions to use the Snyk 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -147,7 +147,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -247,13 +247,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 C1.ai 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 Snyk connector to. Snyk data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Snyk connector to. Snyk data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Snyk connector is now pulling access data into C1. +**Done.** Your Snyk connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/sonarqube.mdx b/baton/sonarqube.mdx index 11579152..6c804dfe 100644 --- a/baton/sonarqube.mdx +++ b/baton/sonarqube.mdx @@ -1,8 +1,8 @@ --- title: "Set up a SonarQube connector" -description: "C1 provides identity governance and just-in-time provisioning for SonarQube. Integrate your SonarQube instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for SonarQube. Integrate your SonarQube instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." og:title: "Set up a SonarQube connector" -og:description: "C1 provides identity governance and just-in-time provisioning for SonarQube. Integrate your SonarQube instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for SonarQube. Integrate your SonarQube instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "SonarQube" --- @@ -80,17 +80,17 @@ Configuring the connector requires a SonarQube API token. Gather this credential **To complete this task, you'll need:** -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Your SonarQube instance URL and the API token generated 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **SonarQube** and click **Add**. @@ -126,12 +126,12 @@ Configuring the connector requires a SonarQube API token. Gather this credential -**Done.** Your SonarQube connector is now pulling access data into C1. +**Done.** Your SonarQube connector is now pulling access data into C1.ai. **Follow these instructions to use the SonarQube 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -141,7 +141,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -234,14 +234,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 C1.ai 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 SonarQube connector to. SonarQube data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the SonarQube connector to. SonarQube data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your SonarQube connector is now pulling access data into C1. +**Done.** Your SonarQube connector is now pulling access data into C1.ai. diff --git a/baton/sonatype-nexus.mdx b/baton/sonatype-nexus.mdx index 0d15c94f..a8d010fa 100644 --- a/baton/sonatype-nexus.mdx +++ b/baton/sonatype-nexus.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Nexus connector" -og:title: Set up an Sonatype Nexus connector - C1 docs -og:description: Integrate your Nexus 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 Sonatype Nexus. Integrate your Nexus instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up an Sonatype Nexus connector - C1.ai docs +og:description: Integrate your Nexus instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance for Sonatype Nexus. Integrate your Nexus instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: "Sonatype Nexus" --- @@ -15,7 +15,7 @@ sidebarTitle: "Sonatype Nexus" The Nexus connector supports [automatic account provisioning and deprovisioning](/product/admin/account-provisioning). All accounts must be assigned at least one role; new accounts will automatically be assigned the `nx-anonymous` role on creation. -When a new account is created by C1, the account's password will be sent to a [vault](/product/admin/vaults). +When a new account is created by C1.ai, the account's password will be sent to a [vault](/product/admin/vaults). ## Gather Nexus credentials @@ -44,18 +44,18 @@ The host URL of your Nexus instance (for example: `https://nexus.company.com`). To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Nexus 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Nexus** and click **Add**. @@ -87,12 +87,12 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Nexus connector is now pulling access data into C1. +**Done.** Your Nexus connector is now pulling access data into C1.ai. **Follow these instructions to use the Nexus 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -102,7 +102,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -196,14 +196,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 C1.ai 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 Nexus connector to. Nexus data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Nexus connector to. Nexus data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Nexus connector is now pulling access data into C1. +**Done.** Your Nexus connector is now pulling access data into C1.ai. diff --git a/baton/spanning.mdx b/baton/spanning.mdx index f99116dd..fabc5e5e 100644 --- a/baton/spanning.mdx +++ b/baton/spanning.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Spanning connector" og:title: "Set up a Spanning connector" -description: "C1 provides identity governance for Kaseya Spanning Backup for Office 365. Integrate your Spanning tenant with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Kaseya Spanning Backup for Office 365. Integrate your Spanning tenant with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Kaseya Spanning Backup for Office 365. Integrate your Spanning tenant with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Kaseya Spanning Backup for Office 365. Integrate your Spanning tenant with C1.ai for unified visibility and governance over user access." sidebarTitle: "Spanning" --- -C1 provides identity governance for Kaseya Spanning Backup for Office 365. -Integrate your Spanning tenant with C1 for unified visibility and governance +C1.ai provides identity governance for Kaseya Spanning Backup for Office 365. +Integrate your Spanning tenant with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -58,7 +58,7 @@ Spanning Backup for Office 365 admin console to generate an API key. ## Synced resource types -- **Users**: Spanning users from the tenant, mapped as C1 users. Each user +- **Users**: Spanning users from the tenant, mapped as C1.ai users. Each user carries its principal name, email, display name, Microsoft object id, license assignment, and admin status. - **Roles**: A fixed set of seven Spanning role tiers — User, Shared Mailbox, @@ -76,17 +76,17 @@ Spanning Backup for Office 365 admin console to generate an API key. endpoint, so all seven roles are always present and role membership is derived from the tags on each user record. - User accounts that are deleted or archived in Spanning are marked disabled in - C1. + C1.ai. ## Configure the Spanning connector - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -129,7 +129,7 @@ Spanning Backup for Office 365 admin console to generate an API key. - **Done.** Your Spanning connector is now pulling access data into C1. + **Done.** Your Spanning connector is now pulling access data into C1.ai. @@ -156,6 +156,6 @@ Spanning Backup for Office 365 admin console to generate an API key. - **Done.** Your Spanning connector is now pulling access data into C1. + **Done.** Your Spanning connector is now pulling access data into C1.ai. diff --git a/baton/split.mdx b/baton/split.mdx index 6bd01a93..4720b1d1 100644 --- a/baton/split.mdx +++ b/baton/split.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Split connector" og:title: "Set up a Split connector" -description: "C1 provides identity governance for Split. Integrate your Split organization with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Split. Integrate your Split organization with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Split. Integrate your Split organization with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Split. Integrate your Split organization with C1.ai for unified visibility and governance over user access." sidebarTitle: "Split" --- -C1 provides identity governance for Split. Integrate your Split organization -with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Split. Integrate your Split organization +with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -47,11 +47,11 @@ requires an Admin key. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -92,7 +92,7 @@ requires an Admin key. - **Done.** Your Split connector is now pulling access data into C1. + **Done.** Your Split connector is now pulling access data into C1.ai. @@ -115,6 +115,6 @@ requires an Admin key. - **Done.** Your Split connector is now pulling access data into C1. + **Done.** Your Split connector is now pulling access data into C1.ai. diff --git a/baton/splunk.mdx b/baton/splunk.mdx index 1b5c29ed..62e1470f 100644 --- a/baton/splunk.mdx +++ b/baton/splunk.mdx @@ -1,13 +1,13 @@ --- title: Set up a Splunk connector -og:title: Set up a Splunk connector - C1 docs -og:description: "C1 provides identity governance for Splunk. Integrate your Splunk instance with C1 for unified visibility and governance over user access." -description: "C1 provides identity governance for Splunk. Integrate your Splunk instance with C1 for unified visibility and governance over user access." +og:title: Set up a Splunk connector - C1.ai docs +og:description: "C1.ai provides identity governance for Splunk. Integrate your Splunk instance with C1.ai for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Splunk. Integrate your Splunk instance with C1.ai for unified visibility and governance over user access." sidebarTitle: Splunk --- -**Are you a Splunk Cloud user?** This page has instructions for integrating C1 with Splunk Enterprise. If you want to integrate C1 with your Splunk Cloud instance, follow the instructions in the [Splunk connector's README file](https://github.com/conductorone/baton-splunk#readme). +**Are you a Splunk Cloud user?** This page has instructions for integrating C1.ai with Splunk Enterprise. If you want to integrate C1.ai with your Splunk Cloud instance, follow the instructions in the [Splunk connector's README file](https://github.com/conductorone/baton-splunk#readme). ## Capabilities @@ -65,13 +65,13 @@ The token is generated. Carefully copy and save the token value. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Splunk 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 C1.ai.** *Cloud-hosted connector not currently available.* @@ -79,7 +79,7 @@ To complete this task, you'll need: **Follow these instructions to use the Splunk 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -89,7 +89,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -187,14 +187,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 C1.ai 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 Splunk connector to. Splunk data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Splunk connector to. Splunk data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Splunk connector is now pulling access data into C1. +**Done.** Your Splunk connector is now pulling access data into C1.ai. diff --git a/baton/statsig.mdx b/baton/statsig.mdx index da496e6c..7004e255 100644 --- a/baton/statsig.mdx +++ b/baton/statsig.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Statsig connector" og:title: "Set up a Statsig connector" -description: "C1 provides identity governance for Statsig. Integrate your Statsig instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Statsig. Integrate your Statsig instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Statsig. Integrate your Statsig instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Statsig. Integrate your Statsig instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Statsig" --- -C1 provides identity governance for Statsig. Integrate your Statsig -organization with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Statsig. Integrate your Statsig +organization with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -48,11 +48,11 @@ users. The key grants access to your Statsig console, so treat it as a secret. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -93,7 +93,7 @@ users. The key grants access to your Statsig console, so treat it as a secret. - **Done.** Your Statsig connector is now pulling access data into C1. + **Done.** Your Statsig connector is now pulling access data into C1.ai. @@ -116,6 +116,6 @@ users. The key grants access to your Statsig console, so treat it as a secret. - **Done.** Your Statsig connector is now pulling access data into C1. + **Done.** Your Statsig connector is now pulling access data into C1.ai. diff --git a/baton/stripe.mdx b/baton/stripe.mdx index ebc984db..78b7e0e5 100644 --- a/baton/stripe.mdx +++ b/baton/stripe.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Stripe connector" og:title: "Set up a Stripe connector" -description: "C1 provides identity governance for Stripe. Integrate your Stripe account with C1 for unified visibility and governance over team member access." -og:description: "C1 provides identity governance for Stripe. Integrate your Stripe account with C1 for unified visibility and governance over team member access." +description: "C1.ai provides identity governance for Stripe. Integrate your Stripe account with C1.ai for unified visibility and governance over team member access." +og:description: "C1.ai provides identity governance for Stripe. Integrate your Stripe account with C1.ai for unified visibility and governance over team member access." sidebarTitle: "Stripe" --- -C1 provides identity governance for Stripe. Integrate your Stripe -account with C1 for unified visibility and governance over team member +C1.ai provides identity governance for Stripe. Integrate your Stripe +account with C1.ai for unified visibility and governance over team member access. ## Capabilities @@ -73,11 +73,11 @@ sign-on** configured. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -123,7 +123,7 @@ sign-on** configured. - **Done.** Your Stripe connector is now pulling access data into C1. + **Done.** Your Stripe connector is now pulling access data into C1.ai. @@ -148,6 +148,6 @@ sign-on** configured. - **Done.** Your Stripe connector is now pulling access data into C1. + **Done.** Your Stripe connector is now pulling access data into C1.ai. diff --git a/baton/stytch.mdx b/baton/stytch.mdx index 663656cd..9c72a9be 100644 --- a/baton/stytch.mdx +++ b/baton/stytch.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Stytch connector" og:title: "Set up a Stytch connector" -description: "C1 provides identity governance for Stytch. Integrate your Stytch instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Stytch. Integrate your Stytch instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Stytch. Integrate your Stytch instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Stytch. Integrate your Stytch instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Stytch" --- -C1 provides identity governance for Stytch. Integrate your Stytch B2B project -with C1 for unified visibility and governance over which Members belong to +C1.ai provides identity governance for Stytch. Integrate your Stytch B2B project +with C1.ai for unified visibility and governance over which Members belong to which Organizations and which RBAC roles they hold. ## Capabilities @@ -52,11 +52,11 @@ project; configure a separate instance for each test or live project. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -100,7 +100,7 @@ project; configure a separate instance for each test or live project. - **Done.** Your Stytch connector is now pulling access data into C1. + **Done.** Your Stytch connector is now pulling access data into C1.ai. @@ -126,6 +126,6 @@ project; configure a separate instance for each test or live project. - **Done.** Your Stytch connector is now pulling access data into C1. + **Done.** Your Stytch connector is now pulling access data into C1.ai. diff --git a/baton/successfactors-odata.mdx b/baton/successfactors-odata.mdx index 8d4bba88..b4105323 100644 --- a/baton/successfactors-odata.mdx +++ b/baton/successfactors-odata.mdx @@ -1,14 +1,14 @@ --- title: "Set up a SAP SuccessFactors connector" og:title: "Set up a SAP SuccessFactors connector" -description: "C1 provides identity governance for SAP SuccessFactors. Integrate your SAP SuccessFactors instance with C1 to run user access reviews (UARs) and gain visibility into your workforce identities, static groups, and dynamic groups." -og:description: "C1 provides identity governance for SAP SuccessFactors. Integrate your SAP SuccessFactors instance with C1 to run user access reviews (UARs) and gain visibility into your workforce identities, static groups, and dynamic groups." +description: "C1.ai provides identity governance for SAP SuccessFactors. Integrate your SAP SuccessFactors instance with C1.ai to run user access reviews (UARs) and gain visibility into your workforce identities, static groups, and dynamic groups." +og:description: "C1.ai provides identity governance for SAP SuccessFactors. Integrate your SAP SuccessFactors instance with C1.ai to run user access reviews (UARs) and gain visibility into your workforce identities, static groups, and dynamic groups." sidebarTitle: "SAP SuccessFactors OData" --- ## Which SAP SuccessFactors connector should I use? -C1 offers two SAP SuccessFactors connectors. Which one you should set up depends on what data you need to bring into C1. +C1.ai offers two SAP SuccessFactors connectors. Which one you should set up depends on what data you need to bring into C1.ai. * **[SAP SuccessFactors connector](/baton/successfactors-odata)**: This connector uses the SAP OData v2 API and is the best choice if you need rich user profile data, including custom fields exposed via OData navigation properties (such as department, cost center, or job title). It is also the right choice if your SAP SuccessFactors instance does not have SCIM enabled. @@ -66,7 +66,7 @@ It is also visible in **Admin Center** > **Company System and Logo Settings**. Fill in the required fields: - **Application Name**: `C1` - **Description**: `C1 identity sync` - - **Application URL**: your C1 tenant URL + - **Application URL**: your C1.ai tenant URL @@ -109,11 +109,11 @@ Provide the SAP SuccessFactors username of the admin account that will be used t - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -162,7 +162,7 @@ Provide the SAP SuccessFactors username of the admin account that will be used t Optionally, configure **User Custom Fields** to sync additional fields into user profiles. - Each entry maps the path to a field in the SAP SuccessFactors user entity, to the name it will appear under in the user's profile in C1. For example, to include the user's department: + Each entry maps the path to a field in the SAP SuccessFactors user entity, to the name it will appear under in the user's profile in C1.ai. For example, to include the user's department: | OData field path | Profile key | | :--- | :--- | @@ -191,19 +191,19 @@ Provide the SAP SuccessFactors username of the admin account that will be used t - **Done.** Your SAP SuccessFactors connector is now pulling user data into C1. + **Done.** Your SAP SuccessFactors connector is now pulling user data into C1.ai. Follow these instructions to use the [SAP SuccessFactors](https://github.com/ConductorOne/baton-successfactors-odata) 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. + When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1.ai, automatically syncing and uploading data at regular intervals. ### Step 1: Set up a new SAP SuccessFactors connector - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -304,15 +304,15 @@ Provide the SAP SuccessFactors username of the admin account that will be used t - 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 C1.ai 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 SAP SuccessFactors connector to. User data should be visible on the **Accounts** tab. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the SAP SuccessFactors connector to. User data should be visible on the **Accounts** tab. - **Done.** Your SAP SuccessFactors connector is now pulling user data into C1. + **Done.** Your SAP SuccessFactors connector is now pulling user data into C1.ai. diff --git a/baton/successfactors-scim.mdx b/baton/successfactors-scim.mdx index 18ace164..336b64bf 100644 --- a/baton/successfactors-scim.mdx +++ b/baton/successfactors-scim.mdx @@ -1,14 +1,14 @@ --- title: Set up a SAP SuccessFactors SCIM connector -og:title: Set up a SAP SuccessFactors SCIM connector - C1 docs -og:description: Integrate your SAP SuccessFactors 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 SAP SuccessFactors. Integrate your SAP SuccessFactors instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a SAP SuccessFactors SCIM connector - C1.ai docs +og:description: Integrate your SAP SuccessFactors instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance for SAP SuccessFactors. Integrate your SAP SuccessFactors instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: SAP SuccessFactors SCIM --- ## Which SAP SuccessFactors connector should I use? -C1 offers two SAP SuccessFactors connectors. Which one you should set up depends on what data you need to bring into C1. +C1.ai offers two SAP SuccessFactors connectors. Which one you should set up depends on what data you need to bring into C1.ai. * **[SAP SuccessFactors connector](/baton/successfactors-odata)**: This connector uses the SAP OData v2 API and is the best choice if you need rich user profile data, including custom fields exposed via OData navigation properties (such as department, cost center, or job title). It is also the right choice if your SAP SuccessFactors instance does not have SCIM enabled. @@ -116,17 +116,17 @@ Carefully copy and save the API server URL (for example, `https://api4.successfa To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of SAP SuccessFactors 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **SAP SuccessFactors** and click **Add**. @@ -165,12 +165,12 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your SAP SuccessFactors SCIM connector is now pulling access data into C1. +**Done.** Your SAP SuccessFactors SCIM connector is now pulling access data into C1.ai. **Follow these instructions to use the SAP SuccessFactors SCIM 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -180,7 +180,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -299,13 +299,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 C1.ai 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 SAP SuccessFactors SCIM connector to. SAP SuccessFactors data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the SAP SuccessFactors SCIM connector to. SAP SuccessFactors data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your SAP SuccessFactors SCIM connector is now pulling access data into C1. +**Done.** Your SAP SuccessFactors SCIM connector is now pulling access data into C1.ai. diff --git a/baton/successfactors.mdx b/baton/successfactors.mdx index 0323782d..bcdb6a48 100644 --- a/baton/successfactors.mdx +++ b/baton/successfactors.mdx @@ -1,13 +1,13 @@ --- title: Set up a SAP SuccessFactors connector -og:title: Set up a SAP SuccessFactors connector - C1 docs -og:description: "C1 provides identity governance for SAP SuccessFactors. Integrate your SAP SuccessFactors instance with C1 for unified visibility and governance over user access." -description: "C1 provides identity governance for SAP SuccessFactors. Integrate your SAP SuccessFactors instance with C1 for unified visibility and governance over user access." +og:title: Set up a SAP SuccessFactors connector - C1.ai docs +og:description: "C1.ai provides identity governance for SAP SuccessFactors. Integrate your SAP SuccessFactors instance with C1.ai for unified visibility and governance over user access." +description: "C1.ai provides identity governance for SAP SuccessFactors. Integrate your SAP SuccessFactors instance with C1.ai for unified visibility and governance over user access." sidebarTitle: SAP SuccessFactors --- -**A newer version of this connector is available.** This version of the connector is no longer available for installation. If you're setting up a SAP SuccessFactors connector with C1 for the first time, use the [SCIM version](/baton/successfactors-scim). +**A newer version of this connector is available.** This version of the connector is no longer available for installation. If you're setting up a SAP SuccessFactors connector with C1.ai for the first time, use the [SCIM version](/baton/successfactors-scim). ## Capabilities @@ -84,7 +84,7 @@ In SuccessFactors, navigate to **Admin Tools** > **Manage OAuth2 Client Applicat Fill out the form, providing: - * Application name, such as "C1 Connector". + * Application name, such as "C1.ai Connector". * Application URL, such as `https://www.conductorone.com/`. Carefully copy and save this URL, it will be used later as the **Issuer URL** when setting up the connector. @@ -108,18 +108,18 @@ Carefully copy and save the API key. When setting up the connector, you'll use t To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of SuccessFactors 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 C1.ai.** -In C1, navigate to **Admin** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Admin** > **Connectors** and click **Add connector**. Search for **SuccessFactors** and click **Add**. @@ -170,18 +170,18 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your SuccessFactors connector is now pulling access data into C1. +**Done.** Your SuccessFactors connector is now pulling access data into C1.ai. **Follow these instructions to use the [SuccessFactors](https://github.com/conductorone/baton-successfactors) 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Step 1: Set up a new SuccessFactors connector -In C1, navigate to **Connectors** > **Add connector**. +In C1.ai, navigate to **Connectors** > **Add connector**. Search for **Baton** and click **Add**. @@ -277,14 +277,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 C1.ai 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 SuccessFactors connector to. SuccessFactors data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the SuccessFactors connector to. SuccessFactors data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your SuccessFactors connector is now pulling access data into C1. +**Done.** Your SuccessFactors connector is now pulling access data into C1.ai. diff --git a/baton/sumo-logic.mdx b/baton/sumo-logic.mdx index 0b92a7ad..09c67d5e 100644 --- a/baton/sumo-logic.mdx +++ b/baton/sumo-logic.mdx @@ -1,8 +1,8 @@ --- title: Set up a Sumo Logic connector -og:title: Set up a Sumo Logic connector - C1 docs -og:description: Integrate your Sumo Logic 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 Sumo Logic. Integrate your Sumo Logic instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a Sumo Logic connector - C1.ai docs +og:description: Integrate your Sumo Logic instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance and just-in-time provisioning for Sumo Logic. Integrate your Sumo Logic instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: Sumo Logic --- @@ -17,7 +17,7 @@ The Sumo Logic connector supports [automatic account provisioning and deprovisio ### 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 C1.ai 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 | |-------------|-------------------|-------------| @@ -62,7 +62,7 @@ Select a service account (or click **+ New** and create a new service account). Click **Add Access Key**. -Give the new key a name, such as "C1". +Give the new key a name, such as "C1.ai". Select the relevant scope: @@ -84,17 +84,17 @@ Carefully copy and save the Access ID and Access Key. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Sumo Logic 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Sumo Logic** and click **Add**. @@ -126,7 +126,7 @@ Enter the API access key value in the **API access key** field. In the **API base URL** field, enter the base URL you use for making API calls to Sumo Logic. The default is `https://api.sumologic.com`. -**Optional.** If you do not want to sync service account info to C1, uncheck the **Include service accounts** checkbox. +**Optional.** If you do not want to sync service account info to C1.ai, uncheck the **Include service accounts** checkbox. **Optional.** In the **Minimal access role name** field, enter the name of a low-privilege role that should be automatically assigned to an account when their last role is revoked during provisioning operations. The default is **Analyst**. @@ -138,12 +138,12 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Sumo Logic connector is now pulling access data into C1. +**Done.** Your Sumo Logic connector is now pulling access data into C1.ai. **Follow these instructions to use the Sumo Logic 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -153,7 +153,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -251,13 +251,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 C1.ai 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 Sumo Logic connector to. Sumo Logic data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Sumo Logic connector to. Sumo Logic data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Sumo Logic connector is now pulling access data into C1. +**Done.** Your Sumo Logic connector is now pulling access data into C1.ai. diff --git a/baton/sumologic.mdx b/baton/sumologic.mdx index 78e5aa32..2a1b88aa 100644 --- a/baton/sumologic.mdx +++ b/baton/sumologic.mdx @@ -1,15 +1,15 @@ --- title: "Set up a Sumo Logic connector" og:title: "Set up a Sumo Logic connector" -description: "C1 provides identity governance for Sumo Logic. Integrate your Sumo Logic account with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Sumo Logic. Integrate your Sumo Logic account with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Sumo Logic. Integrate your Sumo Logic account with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Sumo Logic. Integrate your Sumo Logic account with C1.ai for unified visibility and governance over user access." sidebarTitle: "Sumo Logic" --- {/* stargate: cf-sumologic-20260605 */} -C1 provides identity governance for Sumo Logic. Integrate your Sumo Logic -account with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Sumo Logic. Integrate your Sumo Logic +account with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -57,11 +57,11 @@ grants API access to your account, so treat both halves as secrets. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -108,7 +108,7 @@ grants API access to your account, so treat both halves as secrets. - **Done.** Your Sumo Logic connector is now pulling access data into C1. + **Done.** Your Sumo Logic connector is now pulling access data into C1.ai. @@ -133,6 +133,6 @@ grants API access to your account, so treat both halves as secrets. - **Done.** Your Sumo Logic connector is now pulling access data into C1. + **Done.** Your Sumo Logic connector is now pulling access data into C1.ai. diff --git a/baton/supabase.mdx b/baton/supabase.mdx index 43430655..95959db0 100644 --- a/baton/supabase.mdx +++ b/baton/supabase.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Supabase connector" og:title: "Set up a Supabase connector" -description: "C1 provides identity governance and provisioning for Supabase. Integrate Supabase with C1 to run user access reviews (UARs), enable access requests, and automatically provision and deprovision auth users across all your Supabase projects." -og:description: "C1 provides identity governance and provisioning for Supabase. Integrate Supabase with C1 to run user access reviews (UARs), enable access requests, and automatically provision and deprovision auth users across all your Supabase projects." +description: "C1.ai provides identity governance and provisioning for Supabase. Integrate Supabase with C1.ai to run user access reviews (UARs), enable access requests, and automatically provision and deprovision auth users across all your Supabase projects." +og:description: "C1.ai provides identity governance and provisioning for Supabase. Integrate Supabase with C1.ai to run user access reviews (UARs), enable access requests, and automatically provision and deprovision auth users across all your Supabase projects." sidebarTitle: "Supabase" --- @@ -58,11 +58,11 @@ The Supabase connector syncs the following resources: - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -111,20 +111,20 @@ Generated from config_schema.json. Do not edit manually. */} - **Done.** Your Supabase connector is now pulling access data into C1. + **Done.** Your Supabase connector is now pulling access data into C1.ai. Follow these instructions to use the [Supabase](https://github.com/conductorone/baton-supabase) 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. + When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1.ai, automatically syncing and uploading data at regular intervals. ### Step 1: Set up a new Supabase connector - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -211,14 +211,14 @@ Generated from config_schema.json. Do not edit manually. */} - 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 C1.ai 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 Supabase connector to. Supabase data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the Supabase connector to. Supabase data should be found on the **Entitlements** and **Accounts** tabs. - **Done.** Your Supabase connector is now pulling access data into C1. + **Done.** Your Supabase connector is now pulling access data into C1.ai. diff --git a/baton/sysdig.mdx b/baton/sysdig.mdx index d45eebb4..b94b257b 100644 --- a/baton/sysdig.mdx +++ b/baton/sysdig.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Sysdig connector" og:title: "Set up a Sysdig connector" -description: "C1 provides identity governance for Sysdig. Integrate your Sysdig account with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Sysdig. Integrate your Sysdig account with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Sysdig. Integrate your Sysdig account with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Sysdig. Integrate your Sysdig account with C1.ai for unified visibility and governance over user access." sidebarTitle: "Sysdig" --- -C1 provides identity governance for Sysdig. Integrate your Sysdig account with -C1 for unified visibility and governance over who belongs to which teams and +C1.ai provides identity governance for Sysdig. Integrate your Sysdig account with +C1.ai for unified visibility and governance over who belongs to which teams and who holds team-administrator access. ## Capabilities @@ -23,7 +23,7 @@ The connector reads the users in your Sysdig account, the teams in that account, which users belong to which teams, and whether each member is a team administrator. Each user's organization-wide role (standard user or admin) is recorded on the user, and each user's enabled or disabled status is reflected in -C1. +C1.ai. ## Gather Sysdig credentials @@ -57,11 +57,11 @@ and team lists. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -109,7 +109,7 @@ and team lists. - **Done.** Your Sysdig connector is now pulling access data into C1. + **Done.** Your Sysdig connector is now pulling access data into C1.ai. @@ -134,6 +134,6 @@ and team lists. - **Done.** Your Sysdig connector is now pulling access data into C1. + **Done.** Your Sysdig connector is now pulling access data into C1.ai. diff --git a/baton/tableau.mdx b/baton/tableau.mdx index 3ad5cb8f..de3f1b44 100644 --- a/baton/tableau.mdx +++ b/baton/tableau.mdx @@ -1,8 +1,8 @@ --- title: Set up a Salesforce Tableau connector -og:title: Set up a Salesforce Tableau connector - C1 docs -og:description: Integrate your Salesforce 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 Salesforce Tableau. Integrate your Salesforce Tableau instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a Salesforce Tableau connector - C1.ai docs +og:description: Integrate your Salesforce Tableau instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance for Salesforce Tableau. Integrate your Salesforce Tableau instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: Salesforce Tableau --- @@ -30,7 +30,7 @@ In Tableau, licensing is role-based: each user's **site role** determines their - **Unlicensed** — no access to site features -When your Tableau site has per-tier seat capacities configured, C1 tracks the purchased and consumed seat counts for each license tier, so you can review license utilization alongside who holds each tier. +When your Tableau site has per-tier seat capacities configured, C1.ai tracks the purchased and consumed seat counts for each license tier, so you can review license utilization alongside who holds each tier. ## Permission inheritance @@ -63,7 +63,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 "C1.ai integration") and then click **Create**. Carefully copy and save the newly generated token and its name. @@ -94,17 +94,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 C1.ai - 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Tableau** and click **Add**. @@ -142,12 +142,12 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Tableau connector is now pulling access data into C1. +**Done.** Your Tableau connector is now pulling access data into C1.ai. **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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -159,7 +159,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -258,14 +258,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 C1.ai 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 C1.ai, 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. -**Done.** Your Tableau connector is now pulling access data into C1. +**Done.** Your Tableau connector is now pulling access data into C1.ai. @@ -278,7 +278,7 @@ When provisioning Tableau accounts (Licenses resource type), the connector suppo | **IDP Configuration Name** | Name of an IDP configuration defined on your Tableau site (e.g., a SAML provider). When set, new accounts are created using that IDP. Requires Tableau API version ≥ 3.22. | | **With MFA** | When set to `true`, new accounts are created using Tableau's built-in MFA authentication. Takes precedence over **IDP Configuration Name** if both are set. | -These fields appear in the **provisioning mapping** for the Licenses entitlement in C1 and are not part of the connector's base configuration. +These fields appear in the **provisioning mapping** for the Licenses entitlement in C1.ai and are not part of the connector's base configuration. ### Behavior reference diff --git a/baton/tailscale.mdx b/baton/tailscale.mdx index 477a9c60..864bda44 100644 --- a/baton/tailscale.mdx +++ b/baton/tailscale.mdx @@ -1,13 +1,13 @@ --- title: Set up a Tailscale connector -og:title: Set up a Tailscale connector - C1 docs -og:description: Integrate your Tailscale 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 Tailscale. Integrate your Tailscale instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access. +og:title: Set up a Tailscale connector - C1.ai docs +og:description: Integrate your Tailscale instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance and just-in-time provisioning for Tailscale. Integrate your Tailscale instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access. sidebarTitle: Tailscale --- -**This is an updated and improved version of the Tailscale connector!** If you're setting up Tailscale with C1 for the first time, you're in the right place. +**This is an updated and improved version of the Tailscale connector!** If you're setting up Tailscale with C1.ai for the first time, you're in the right place. ## Capabilities @@ -47,7 +47,7 @@ Click **Trust Credentials**. Click **+ Credentials**. A modal opens to create new OAuth credentials. -Enter a **Description** for these credentials (for example, "C1 connector"). +Enter a **Description** for these credentials (for example, "C1.ai connector"). Configure the scopes: @@ -92,17 +92,17 @@ Copy and save the API key. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Tailscale 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Tailscale v2** and click **Add**. @@ -143,12 +143,12 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Tailscale connector is now pulling access data into C1. +**Done.** Your Tailscale connector is now pulling access data into C1.ai. **Follow these instructions to use the Tailscale 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -158,7 +158,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -277,14 +277,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 C1.ai 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 Tailscale connector to. Tailscale data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Tailscale connector to. Tailscale data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Tailscale connector is now pulling access data into C1. +**Done.** Your Tailscale connector is now pulling access data into C1.ai. diff --git a/baton/talentlms.mdx b/baton/talentlms.mdx index b699c544..df4e4f14 100644 --- a/baton/talentlms.mdx +++ b/baton/talentlms.mdx @@ -1,15 +1,15 @@ --- title: "Set up a TalentLMS connector" og:title: "Set up a TalentLMS connector" -description: "C1 provides identity governance for TalentLMS. Integrate your TalentLMS account with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for TalentLMS. Integrate your TalentLMS account with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for TalentLMS. Integrate your TalentLMS account with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for TalentLMS. Integrate your TalentLMS account with C1.ai for unified visibility and governance over user access." sidebarTitle: "TalentLMS" --- {/* stargate: cf-talentlms-20260605 */} -C1 provides identity governance for TalentLMS. Integrate your TalentLMS account -with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for TalentLMS. Integrate your TalentLMS account +with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -49,11 +49,11 @@ secret. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -98,7 +98,7 @@ secret. - **Done.** Your TalentLMS connector is now pulling access data into C1. + **Done.** Your TalentLMS connector is now pulling access data into C1.ai. @@ -122,6 +122,6 @@ secret. - **Done.** Your TalentLMS connector is now pulling access data into C1. + **Done.** Your TalentLMS connector is now pulling access data into C1.ai. diff --git a/baton/teamcity.mdx b/baton/teamcity.mdx index 607cfbe4..e1fd81c2 100644 --- a/baton/teamcity.mdx +++ b/baton/teamcity.mdx @@ -1,8 +1,8 @@ --- title: Set up a JetBrains TeamCity connector -og:title: Set up a JetBrains TeamCity connector - C1 docs -og:description: Integrate your JetBrains TeamCity 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 JetBrains TeamCity. Integrate your JetBrains TeamCity instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a JetBrains TeamCity connector - C1.ai docs +og:description: Integrate your JetBrains TeamCity instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance and just-in-time provisioning for JetBrains TeamCity. Integrate your JetBrains TeamCity instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: JetBrains TeamCity --- @@ -37,7 +37,7 @@ Log into TeamCity and navigate to **Access Tokens** in your user profile. Click **Create access token**. -Give the token a name, such as "C1". +Give the token a name, such as "C1.ai". Set the **Permission scope** to **Same as current user**. @@ -58,17 +58,17 @@ Carefully copy and save the access 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 C1.ai - Access to the set of TeamCity 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **TeamCity** and click **Add**. @@ -103,22 +103,22 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your TeamCity connector is now pulling access data into C1. +**Done.** Your TeamCity connector is now pulling access data into C1.ai. **Follow these instructions to use the TeamCity 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources -[Contact C1's support team](mailto:support@c1.ai) to download the latest version of the connector. +[Contact C1.ai's support team](mailto:support@c1.ai) to download the latest version of the connector. ### Step 1: Configure the TeamCity connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -212,14 +212,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 C1.ai 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 TeamCity connector to. TeamCity data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the TeamCity connector to. TeamCity data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your TeamCity connector is now pulling access data into C1. +**Done.** Your TeamCity connector is now pulling access data into C1.ai. diff --git a/baton/teamtailor.mdx b/baton/teamtailor.mdx index bb9338a9..5028f7f4 100644 --- a/baton/teamtailor.mdx +++ b/baton/teamtailor.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Teamtailor connector" og:title: "Set up a Teamtailor connector" -description: "C1 provides identity governance for Teamtailor. Integrate your Teamtailor instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Teamtailor. Integrate your Teamtailor instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Teamtailor. Integrate your Teamtailor instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Teamtailor. Integrate your Teamtailor instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Teamtailor" --- -C1 provides identity governance for Teamtailor. Integrate your Teamtailor -account with C1 for unified visibility and governance over the people who can +C1.ai provides identity governance for Teamtailor. Integrate your Teamtailor +account with C1.ai for unified visibility and governance over the people who can access your Teamtailor recruiting account. ## Capabilities @@ -49,11 +49,11 @@ that can read the full list of users. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -97,7 +97,7 @@ that can read the full list of users. - **Done.** Your Teamtailor connector is now pulling access data into C1. + **Done.** Your Teamtailor connector is now pulling access data into C1.ai. @@ -120,6 +120,6 @@ that can read the full list of users. - **Done.** Your Teamtailor connector is now pulling access data into C1. + **Done.** Your Teamtailor connector is now pulling access data into C1.ai. diff --git a/baton/teamviewer.mdx b/baton/teamviewer.mdx index f6dd3dac..aaf4fd52 100644 --- a/baton/teamviewer.mdx +++ b/baton/teamviewer.mdx @@ -1,8 +1,8 @@ --- title: Set up a TeamViewer connector -og:title: Set up a TeamViewer connector - C1 docs -seo_description: Integrate your TeamViewer 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 TeamViewer. Integrate your TeamViewer instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a TeamViewer connector - C1.ai docs +seo_description: Integrate your TeamViewer instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance for TeamViewer. Integrate your TeamViewer instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: TeamViewer --- @@ -24,7 +24,7 @@ Syncing user groups requires a TeamViewer **Tensor** license. On Business and Pr ### 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 C1.ai 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 | |-------------|-------------------|-------------| @@ -50,14 +50,14 @@ In the TeamViewer Management Console, click your profile menu and select **Edit On the **Apps** tab, click **Create Script Token**. -Give the new API token a name, such as "C1". +Give the new API token a name, such as "C1.ai". Set the relevant permissions: - To give C1 sync (READ) access: + To give C1.ai sync (READ) access: * View account data - Required to sync user information * View email address - Required to sync user email addresses @@ -66,7 +66,7 @@ Set the relevant permissions: * View users - Required to sync users * Read user groups - Required to sync user groups (Tensor license only) - To give C1 sync and provision (READ/WRITE) access: + To give C1.ai sync and provision (READ/WRITE) access: * View account data - Required to sync user information * View email address - Required to sync user email addresses @@ -90,17 +90,17 @@ Click **Save**. Carefully copy and save the newly generated API 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 C1.ai - Access to the set of TeamViewer 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **TeamViewer** and click **Add**. @@ -138,22 +138,22 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your TeamViewer connector is now pulling access data into C1. +**Done.** Your TeamViewer connector is now pulling access data into C1.ai. **Follow these instructions to use the TeamViewer 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai 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 C1.ai's support team](mailto:support@conductorone.com) to download the latest version of the connector. ### Step 1: Set up a new TeamViewer connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -251,14 +251,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 C1.ai 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 TeamViewer connector to. TeamViewer data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the TeamViewer connector to. TeamViewer data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your TeamViewer connector is now pulling access data into C1. +**Done.** Your TeamViewer connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/teamwork.mdx b/baton/teamwork.mdx index 17afba4a..7d9e8d55 100644 --- a/baton/teamwork.mdx +++ b/baton/teamwork.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Teamwork connector" og:title: "Set up a Teamwork connector" -description: "C1 provides identity governance for Teamwork. Integrate your Teamwork instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Teamwork. Integrate your Teamwork instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Teamwork. Integrate your Teamwork instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Teamwork. Integrate your Teamwork instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Teamwork" --- -C1 provides identity governance for Teamwork. Integrate your Teamwork -instance with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Teamwork. Integrate your Teamwork +instance with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -73,11 +73,11 @@ API key inherits the access of the account that owns it. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -125,7 +125,7 @@ API key inherits the access of the account that owns it. - **Done.** Your Teamwork connector is now pulling access data into C1. + **Done.** Your Teamwork connector is now pulling access data into C1.ai. @@ -134,7 +134,7 @@ API key inherits the access of the account that owns it. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -152,7 +152,7 @@ API key inherits the access of the account that owns it. - Configure C1 credentials and Teamwork credentials as environment + Configure C1.ai credentials and Teamwork credentials as environment variables: ```bash @@ -175,6 +175,6 @@ API key inherits the access of the account that owns it. - **Done.** Your Teamwork connector is now pulling access data into C1. + **Done.** Your Teamwork connector is now pulling access data into C1.ai. diff --git a/baton/teleport.mdx b/baton/teleport.mdx index 18bf815b..f8dc6b09 100644 --- a/baton/teleport.mdx +++ b/baton/teleport.mdx @@ -1,8 +1,8 @@ --- title: Set up a Teleport connector -og:title: Set up a Teleport connector - C1 docs -og:description: Integrate your Teleport 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 Teleport. Integrate your Teleport instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a Teleport connector - C1.ai docs +og:description: Integrate your Teleport instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance and just-in-time provisioning for Teleport. Integrate your Teleport instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: Teleport --- @@ -18,7 +18,7 @@ sidebarTitle: Teleport The Teleport connector supports [automatic account provisioning](/product/admin/account-provisioning). -Due to Teleport's security rules, it is not possible to auto-generate and assign passwords to newly created accounts. When a new Teleport account is created by C1, a password reset link (associated with a token) will be sent to a [vault](/product/admin/vaults). This allows the user to configure the password for their new account. +Due to Teleport's security rules, it is not possible to auto-generate and assign passwords to newly created accounts. When a new Teleport account is created by C1.ai, a password reset link (associated with a token) will be sent to a [vault](/product/admin/vaults). This allows the user to configure the password for their new account. This connector does not support account deprovisioning. You must deprovision accounts directly in Teleport. @@ -28,7 +28,7 @@ This connector only supports a self-hosted setup. **Follow these instructions to See [the connector's README file](https://github.com/conductorone/baton-teleport/blob/main/README.md) for information on alternative setup methods. -This guide walks you through setting up the Baton Teleport connector in Kubernetes to run continuously and sync with C1. The connector uses certificate-based authentication via `tbot` and connects to C1 using client credentials. +This guide walks you through setting up the Baton Teleport connector in Kubernetes to run continuously and sync with C1.ai. The connector uses certificate-based authentication via `tbot` and connects to C1.ai using client credentials. ### Prerequisites @@ -38,17 +38,17 @@ Before you begin, make sure you have: - A Teleport cluster with admin access - The `tctl` CLI tool configured for your Teleport cluster -### Step 1: C1 setup +### Step 1: C1.ai setup To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -434,19 +434,19 @@ The connector will start automatically and run continuously, performing the foll Install the `baton-teleport` binary (if not available via releases) -Connect to C1 using your client credentials +Connect to C1.ai using your client credentials -Poll for tasks from C1 periodically +Poll for tasks from C1.ai periodically -Execute sync tasks when requested by C1 +Execute sync tasks when requested by C1.ai Handle provisioning requests when access needs to be granted/revoked -Send results back to C1 instead of writing to local files +Send results back to C1.ai instead of writing to local files @@ -488,7 +488,7 @@ kubectl rollout restart deployment/baton-teleport The logs should show: - - Successful connection to C1 + - Successful connection to C1.ai - Periodic polling for tasks - Any sync or provisioning activities diff --git a/baton/temporalcloud.mdx b/baton/temporalcloud.mdx index 01ada7e6..bbc9eab5 100644 --- a/baton/temporalcloud.mdx +++ b/baton/temporalcloud.mdx @@ -1,8 +1,8 @@ --- title: Set up a Temporal Cloud connector -og:title: Set up a Temporal Cloud connector - C1 docs -og:description: Integrate your Temporal Cloud Enterprise 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 Temporal Cloud. Integrate your Temporal Cloud Enterprise instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a Temporal Cloud connector - C1.ai docs +og:description: Integrate your Temporal Cloud Enterprise instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance and just-in-time provisioning for Temporal Cloud. Integrate your Temporal Cloud Enterprise instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: Temporal Cloud --- @@ -53,18 +53,18 @@ Carefully copy and save the API key. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Temporal Cloud 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Temporal Cloud** and click **Add**. @@ -96,13 +96,13 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Temporal Cloud connector is now pulling access data into C1. +**Done.** Your Temporal Cloud connector is now pulling access data into C1.ai. **Follow these instructions to use the Temporal Cloud 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -112,7 +112,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -204,12 +204,12 @@ 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 C1.ai 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 Temporal Cloud connector to. Temporal Cloud data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Temporal Cloud connector to. Temporal Cloud data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Temporal Cloud connector is now pulling access data into C1. +**Done.** Your Temporal Cloud connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/tenable-vm.mdx b/baton/tenable-vm.mdx index 8b720e96..e1099939 100644 --- a/baton/tenable-vm.mdx +++ b/baton/tenable-vm.mdx @@ -1,8 +1,8 @@ --- title: Set up a Tenable Vulnerability Management connector -og:title: Set up a Tenable Vulnerability Management connector - C1 docs -og:description: Integrate your Tenable VM 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 Tenable VM. Integrate your Tenable VM instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a Tenable Vulnerability Management connector - C1.ai docs +og:description: Integrate your Tenable VM instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance and just-in-time provisioning for Tenable VM. Integrate your Tenable VM instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: Tenable Vulnerability Management --- @@ -17,7 +17,7 @@ sidebarTitle: Tenable Vulnerability Management The Tenable VM connector supports [automatic account provisioning and deprovisioning](/product/admin/account-provisioning). -When a new account is created by C1, the account's password will be sent to a [vault](/product/admin/vaults). +When a new account is created by C1.ai, the account's password will be sent to a [vault](/product/admin/vaults). When deprovisioning an account, the Tenable connector **disables** the account, it is not deleted outright. Visit the [Tenable documentation on deleting user accounts](https://docs.tenable.com/vulnerability-management/Content/Settings/Credentials/DeleteAUserAccount.htm) for more information. @@ -25,7 +25,7 @@ The connector also offers the option to opt into enabling existing disabled acco ### 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 C1.ai 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 | | --------------- | ----------------------------- | ------------------------------------------ | @@ -68,18 +68,18 @@ Each setup method requires you to pass in credentials generated in Tenable VM. G To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Tenable VM 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Tenable VM** and click **Add**. @@ -117,13 +117,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 Tenable VM connector is now pulling access data into C1. +**That's it!** Your Tenable VM connector is now pulling access data into C1.ai. **Follow these instructions to use the Tenable VM 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -133,7 +133,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -234,12 +234,12 @@ 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 C1.ai 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 Tenable VM connector to. Tenable VM data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Tenable VM connector to. Tenable VM data should be found on the **Entitlements** and **Accounts** tabs. -**That's it!** Your Tenable VM connector is now pulling access data into C1. +**That's it!** Your Tenable VM connector is now pulling access data into C1.ai. diff --git a/baton/terraform-cloud.mdx b/baton/terraform-cloud.mdx index 8d8c3b0a..c1b22188 100644 --- a/baton/terraform-cloud.mdx +++ b/baton/terraform-cloud.mdx @@ -1,8 +1,8 @@ --- title: "Set up an HCP Terraform connector" og:title: "Set up an HCP Terraform connector" -description: "C1 provides identity governance and just-in-time provisioning for HCP Terraform. Integrate your HCP Terraform 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 HCP Terraform. Integrate your HCP Terraform instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for HCP Terraform. Integrate your HCP Terraform instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for HCP Terraform. Integrate your HCP Terraform instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "HCP Terraform" --- @@ -33,16 +33,16 @@ The HCP Terraform connector supports [automatic account provisioning](/product/a **Notes:** -- Account provisioning creates an organization invitation. HCP Terraform does not accept a password through the API, so C1 does not set one. The invited person receives an email from HCP Terraform and sets their own password when they accept the invitation. +- Account provisioning creates an organization invitation. HCP Terraform does not accept a password through the API, so C1.ai does not set one. The invited person receives an email from HCP Terraform and sets their own password when they accept the invitation. - Account deprovisioning is not supported. HCP Terraform has no user-deletion API, so removing a person from an organization is done by revoking their organization membership grant. - Agent tokens sync as secrets for visibility only. They have no entitlements or grants. -- Projects and workspaces sync for visibility and are read-only. C1 does not provision access to them directly. +- Projects and workspaces sync for visibility and are read-only. C1.ai does not provision access to them directly. - Managing organization members and teams requires an HCP Terraform paid plan. Team management is unavailable on the free tier. ## Gather HCP Terraform credentials -To configure the HCP Terraform connector, you need a **user API token** belonging to an account with the **owners** team membership (organization owner) in each HCP Terraform organization you want C1 to manage. Organization owner permissions are required to read and manage organization members and teams. A token from an account without owner permissions syncs a reduced set of data and cannot provision access. +To configure the HCP Terraform connector, you need a **user API token** belonging to an account with the **owners** team membership (organization owner) in each HCP Terraform organization you want C1.ai to manage. Organization owner permissions are required to read and manage organization members and teams. A token from an account without owner permissions syncs a reduced set of data and cannot provision access. HCP Terraform issues several kinds of API tokens. Create a **user token**, which inherits the permissions of the account that owns it. Team tokens are limited to the workspaces their team can access, and organization tokens cannot cover multiple organizations, so neither is suitable for this connector. @@ -54,7 +54,7 @@ HCP Terraform issues several kinds of API tokens. Create a **user token**, which Sign in to HCP Terraform at [https://app.terraform.io](https://app.terraform.io) as a user who is a member of the **owners** team. -If you run Terraform Enterprise, sign in to your own instance URL instead. You provide that URL to C1 as the **Address** setting. +If you run Terraform Enterprise, sign in to your own instance URL instead. You provide that URL to C1.ai as the **Address** setting. @@ -81,11 +81,11 @@ Configure the token: 2. Choose an **Expiration** for the token. -This token is used by C1 when automatically provisioning and deprovisioning access. **If you do not want C1 to perform these tasks, use an account without owner permissions and do not enable provisioning.** +This token is used by C1.ai when automatically provisioning and deprovisioning access. **If you do not want C1.ai to perform these tasks, use an account without owner permissions and do not enable provisioning.** -If you set an expiration date, record it and rotate the token in C1 before it expires. An expired token causes syncs to fail. +If you set an expiration date, record it and rotate the token in C1.ai before it expires. An expired token causes syncs to fail. @@ -101,17 +101,17 @@ For more information, see the HashiCorp documentation on [API tokens](https://de ## Configure the HCP Terraform connector -To configure a connector in C1, you must have the **Connector Administrator** or **Super Administrator** role. You also need the HCP Terraform API token you created above. +To configure a connector in C1.ai, you must have the **Connector Administrator** or **Super Administrator** role. You also need the HCP Terraform API token you created 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 C1.ai. -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -161,7 +161,7 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your HCP Terraform connector is now pulling access data into C1. +**Done.** Your HCP Terraform connector is now pulling access data into C1.ai. @@ -169,7 +169,7 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can Follow these instructions to use the [baton-terraform-cloud](https://github.com/conductorone/baton-terraform-cloud) 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -180,7 +180,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -284,15 +284,15 @@ 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 C1.ai 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 HCP Terraform connector to. HCP Terraform data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the HCP Terraform connector to. HCP Terraform data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your HCP Terraform connector is now pulling access data into C1. +**Done.** Your HCP Terraform connector is now pulling access data into C1.ai. diff --git a/baton/toggl-track.mdx b/baton/toggl-track.mdx index ff1e5872..3d8878bc 100644 --- a/baton/toggl-track.mdx +++ b/baton/toggl-track.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Toggl Track connector" og:title: "Set up a Toggl Track connector" -description: "C1 provides identity governance for Toggl Track. Integrate your Toggl Track organization with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Toggl Track. Integrate your Toggl Track organization with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Toggl Track. Integrate your Toggl Track organization with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Toggl Track. Integrate your Toggl Track organization with C1.ai for unified visibility and governance over user access." sidebarTitle: "Toggl Track" --- -C1 provides identity governance for Toggl Track. Integrate your Toggl Track -organization with C1 for unified visibility and governance over who belongs +C1.ai provides identity governance for Toggl Track. Integrate your Toggl Track +organization with C1.ai for unified visibility and governance over who belongs to which groups. ## Capabilities @@ -53,11 +53,11 @@ must be an administrator of the organization you want to read. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -105,7 +105,7 @@ must be an administrator of the organization you want to read. - **Done.** Your Toggl Track connector is now pulling access data into C1. + **Done.** Your Toggl Track connector is now pulling access data into C1.ai. @@ -130,6 +130,6 @@ must be an administrator of the organization you want to read. - **Done.** Your Toggl Track connector is now pulling access data into C1. + **Done.** Your Toggl Track connector is now pulling access data into C1.ai. diff --git a/baton/torq.mdx b/baton/torq.mdx index 0d43d473..f6e2a54d 100644 --- a/baton/torq.mdx +++ b/baton/torq.mdx @@ -1,8 +1,8 @@ --- title: Set up a Torq connector -og:title: Set up a Torq connector - C1 docs -og:description: "C1 provides identity governance for Torq. Integrate your Torq instance with C1 for unified visibility and governance over user access." -description: "C1 provides identity governance for Torq. Integrate your Torq instance with C1 for unified visibility and governance over user access." +og:title: Set up a Torq connector - C1.ai docs +og:description: "C1.ai provides identity governance for Torq. Integrate your Torq instance with C1.ai for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Torq. Integrate your Torq instance with C1.ai for unified visibility and governance over user access." sidebarTitle: Torq --- @@ -32,7 +32,7 @@ In Torq, click your username and select **API Keys**. Click **Create API key**. -Give the new API key a name, such as "C1 integration". +Give the new API key a name, such as "C1.ai integration". Click **Create**. @@ -48,18 +48,18 @@ Carefully and copy and save the key's client ID and client secret. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Torq 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Torq** and click **Add**. @@ -94,13 +94,13 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Torq connector is now pulling access data into C1. +**Done.** Your Torq connector is now pulling access data into C1.ai. **Follow these instructions to use the Torq 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -110,7 +110,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -201,14 +201,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 C1.ai 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 Torq connector to. Torq data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Torq connector to. Torq data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Torq connector is now pulling access data into C1. +**Done.** Your Torq connector is now pulling access data into C1.ai. diff --git a/baton/trayai.mdx b/baton/trayai.mdx index 05232319..63a9a86b 100644 --- a/baton/trayai.mdx +++ b/baton/trayai.mdx @@ -1,8 +1,8 @@ --- title: Set up a Tray.ai connector -og:title: Set up a Tray.ai connector - C1 docs -og:description: Integrate your Tray.ai instance with C1 to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. -intro: C1 provides identity governance and just-in-time provisioning for Tray.ai. Integrate your Tray.ai instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a Tray.ai connector - C1.ai docs +og:description: Integrate your Tray.ai instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +intro: C1.ai provides identity governance and just-in-time provisioning for Tray.ai. Integrate your Tray.ai instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: Tray.ai --- @@ -33,16 +33,16 @@ A user with the **Organization Admin** role in in Tray.ai must perform this task In Tray.ai, navigate to **Account Settings** > **Tokens** and click **Create API user**. -Give the new API user a name, such as "C1" and select the relevant workspace. +Give the new API user a name, such as "C1.ai" and select the relevant workspace. -In the **Organization role** and **Workspace role** fields, select **Viewer** to give C1 read-only (sync) permissions, or **Contributor** to give C1 read/write (sync and provision) permissions. +In the **Organization role** and **Workspace role** fields, select **Viewer** to give C1.ai read-only (sync) permissions, or **Contributor** to give C1.ai read/write (sync and provision) permissions. Click **Next**. -Enter a name for the API token, such as "C1 token" and set its expiration. +Enter a name for the API token, such as "C1.ai token" and set its expiration. Carefully copy and save the API token. @@ -55,18 +55,18 @@ Carefully copy and save the API 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 C1.ai - Access to the set of Tray.ai 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Tray.ai** and click **Add**. @@ -98,13 +98,13 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Tray.ai connector is now pulling access data into C1. +**Done.** Your Tray.ai connector is now pulling access data into C1.ai. **Follow these instructions to use the Tray.ai 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -116,7 +116,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -208,13 +208,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 C1.ai 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 Tray.ai connector to. Tray.ai data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Tray.ai connector to. Tray.ai data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Tray.ai connector is now pulling access data into C1. +**Done.** Your Tray.ai connector is now pulling access data into C1.ai. diff --git a/baton/treasure-data.mdx b/baton/treasure-data.mdx index 73cae5c0..77218bcc 100644 --- a/baton/treasure-data.mdx +++ b/baton/treasure-data.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Treasure AI connector" og:title: "Set up a Treasure AI connector" -description: "C1 provides identity governance and just-in-time provisioning for Treasure AI. Integrate your Treasure AI 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 Treasure AI. Integrate your Treasure AI instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for Treasure AI. Integrate your Treasure AI instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Treasure AI. Integrate your Treasure AI instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "Treasure AI" --- @@ -27,7 +27,7 @@ The Treasure AI connector syncs the following resources from **Treasure AI CDP** ### PBAC configuration -Policies and Policy Groups require the PBAC paid add-on. These resources are opt-in and can be enabled from the C1 connector settings. Without opt-in, only Users and Roles are synced. +Policies and Policy Groups require the PBAC paid add-on. These resources are opt-in and can be enabled from the C1.ai connector settings. Without opt-in, only Users and Roles are synced. **Required permissions by resource type:** @@ -82,7 +82,7 @@ Policies and Policy Groups require the PBAC paid add-on. These resources are opt - If your account has IP allowlisting enabled, add C1's egress IP range(s) to the allowlist for the service user. + If your account has IP allowlisting enabled, add C1.ai's egress IP range(s) to the allowlist for the service user. @@ -90,11 +90,11 @@ Policies and Policy Groups require the PBAC paid add-on. These resources are opt - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -144,19 +144,19 @@ Policies and Policy Groups require the PBAC paid add-on. These resources are opt - **Done.** Your Treasure AI connector is now pulling access data into C1. + **Done.** Your Treasure AI connector is now pulling access data into C1.ai. Follow these instructions to use the [Treasure AI](https://github.com/conductorone/baton-treasure-data) 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. + When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1.ai, automatically syncing and uploading data at regular intervals. ### Step 1: Set up a new Treasure AI connector - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -260,15 +260,15 @@ Policies and Policy Groups require the PBAC paid add-on. These resources are opt - 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 C1.ai 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 Treasure AI connector to. Treasure AI data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Treasure AI connector to. Treasure AI data should be found on the **Entitlements** and **Accounts** tabs. - **Done.** Your Treasure AI connector is now pulling access data into C1. + **Done.** Your Treasure AI connector is now pulling access data into C1.ai. diff --git a/baton/trello.mdx b/baton/trello.mdx index 1ad327af..c6f2f39e 100644 --- a/baton/trello.mdx +++ b/baton/trello.mdx @@ -1,8 +1,8 @@ --- title: "Set up an Atlassian Trello connector" -description: "C1 provides identity governance for Trello. Integrate your Trello instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Trello. Integrate your Trello instance with C1.ai for unified visibility and governance over user access." og:title: "Set up an Atlassian Trello connector" -og:description: "C1 provides identity governance for Trello. Integrate your Trello instance with C1 for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Trello. Integrate your Trello instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Atlassian Trello" --- @@ -31,7 +31,7 @@ A user with access to the **Power-Up Admin Portal** in Trello must perform this Navigate to the [Trello Power-Up Admin Portal](https://trello.com/power-ups/admin) and click **New**. - Give the new Power-Up a name, such as "C1", and select your Trello Workspace. + Give the new Power-Up a name, such as "C1.ai", and select your Trello Workspace. Leave the **Iframe connector URL** field blank and fill out the rest of the form. @@ -58,7 +58,7 @@ A user with access to the **Power-Up Admin Portal** in Trello must perform this ### Look up Trello organization slugs -Finally, look up the short name (slug) of each Trello organization you want to sync to C1. +Finally, look up the short name (slug) of each Trello organization you want to sync to C1.ai. @@ -79,17 +79,17 @@ Finally, look up the short name (slug) of each Trello organization you want to s **To complete this task, you'll need:** -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Trello 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Trello** and click **Add**. @@ -126,12 +126,12 @@ Finally, look up the short name (slug) of each Trello organization you want to s -**Done.** Your Trello connector is now pulling access data into C1. +**Done.** Your Trello connector is now pulling access data into C1.ai. **Follow these instructions to use the Trello 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -141,7 +141,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -232,14 +232,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 C1.ai 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 Trello connector to. Trello data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Trello connector to. Trello data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Trello connector is now pulling access data into C1. +**Done.** Your Trello connector is now pulling access data into C1.ai. diff --git a/baton/twilio-segment-v2.mdx b/baton/twilio-segment-v2.mdx index 70f4dddd..3c256d5d 100644 --- a/baton/twilio-segment-v2.mdx +++ b/baton/twilio-segment-v2.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Twilio Segment connector" og:title: "Set up a Twilio Segment connector" -description: "C1 provides identity governance and just-in-time provisioning for Twilio Segment. Integrate your Twilio Segment workspace 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 Twilio Segment. Integrate your Twilio Segment workspace with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for Twilio Segment. Integrate your Twilio Segment workspace with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Twilio Segment. Integrate your Twilio Segment workspace with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "Twilio Segment" --- @@ -52,7 +52,7 @@ To configure the Twilio Segment connector, you need **Workspace Owner** or **Wor - Give the new token a name, such as "C1". + Give the new token a name, such as "C1.ai". Assign the token the **Workspace Owner** access level. @@ -74,11 +74,11 @@ For more information, see the [Segment Access Management documentation](https:// - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -122,13 +122,13 @@ For more information, see the [Segment Access Management documentation](https:// - **That's it!** Your Twilio Segment connector is now pulling access data into C1. + **That's it!** Your Twilio Segment connector is now pulling access data into C1.ai. Follow these instructions to use the [Twilio Segment](https://github.com/conductorone/baton-twilio-segment-v2) 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -141,7 +141,7 @@ For more information, see the [Segment Access Management documentation](https:// - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -241,14 +241,14 @@ For more information, see the [Segment Access Management documentation](https:// - 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 C1.ai 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 Twilio Segment connector to. Twilio Segment data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the Twilio Segment connector to. Twilio Segment data should be found on the **Entitlements** and **Accounts** tabs. - **That's it!** Your Twilio Segment connector is now pulling access data into C1. + **That's it!** Your Twilio Segment connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/twingate.mdx b/baton/twingate.mdx index 57bf4665..82bf4b82 100644 --- a/baton/twingate.mdx +++ b/baton/twingate.mdx @@ -1,13 +1,13 @@ --- title: Set up a Twingate connector -og:title: Set up a Twingate connector - C1 docs -og:description: Integrate your Twingate 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 Twingate. Integrate your Twingate instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access. +og:title: Set up a Twingate connector - C1.ai docs +og:description: Integrate your Twingate instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance and just-in-time provisioning for Twingate. Integrate your Twingate instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access. sidebarTitle: Twingate --- -**This is an updated and improved version of the Twingate connector!** If you're setting up Twingate with C1 for the first time, you're in the right place. +**This is an updated and improved version of the Twingate connector!** If you're setting up Twingate with C1.ai for the first time, you're in the right place. ## Capabilities @@ -42,7 +42,7 @@ Click **Generate Token**. Give the API token a label, such as **C1**. Select the appropriate permission level for the API key: - **Read only** to run access reviews on your Twingate users. - - **Read & Write** to provision group membership via C1 and run access reviews. + - **Read & Write** to provision group membership via C1.ai and run access reviews. Click **Generate**. (Setting the Allowed Range is not required.) @@ -59,18 +59,18 @@ The new API key is generated for you. Click **Copy** and save the key. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Twingate 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Twingate** and click **Add**. @@ -108,13 +108,13 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Twingate connector is now pulling access data into C1. +**Done.** Your Twingate connector is now pulling access data into C1.ai. **Follow these instructions to use the Twingate 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -124,7 +124,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -218,12 +218,12 @@ 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 C1.ai 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 Twingate connector to. Twingate data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Twingate connector to. Twingate data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Twingate connector is now pulling access data into C1. +**Done.** Your Twingate connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/twist.mdx b/baton/twist.mdx index c3cee9af..bcf7c08d 100644 --- a/baton/twist.mdx +++ b/baton/twist.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Twist connector" og:title: "Set up a Twist connector" -description: "C1 provides identity governance for Twist. Integrate your Twist workspace with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Twist. Integrate your Twist workspace with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Twist. Integrate your Twist workspace with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Twist. Integrate your Twist workspace with C1.ai for unified visibility and governance over user access." sidebarTitle: "Twist" --- -C1 provides identity governance for Twist. Integrate your Twist workspace -with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Twist. Integrate your Twist workspace +with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -59,11 +59,11 @@ the token can reach it. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -113,7 +113,7 @@ the token can reach it. - **Done.** Your Twist connector is now pulling access data into C1. + **Done.** Your Twist connector is now pulling access data into C1.ai. @@ -142,6 +142,6 @@ the token can reach it. - **Done.** Your Twist connector is now pulling access data into C1. + **Done.** Your Twist connector is now pulling access data into C1.ai. diff --git a/baton/typeform.mdx b/baton/typeform.mdx index 3baa60b3..8b8616bd 100644 --- a/baton/typeform.mdx +++ b/baton/typeform.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Typeform connector" og:title: "Set up a Typeform connector" -description: "C1 provides identity governance for Typeform. Integrate your Typeform account with C1 for unified visibility and governance over workspace access." -og:description: "C1 provides identity governance for Typeform. Integrate your Typeform account with C1 for unified visibility and governance over workspace access." +description: "C1.ai provides identity governance for Typeform. Integrate your Typeform account with C1.ai for unified visibility and governance over workspace access." +og:description: "C1.ai provides identity governance for Typeform. Integrate your Typeform account with C1.ai for unified visibility and governance over workspace access." sidebarTitle: "Typeform" --- @@ -70,11 +70,11 @@ create it on an account that can see every workspace you want to sync. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -121,7 +121,7 @@ create it on an account that can see every workspace you want to sync. - **Done.** Your Typeform connector is now pulling access data into C1. + **Done.** Your Typeform connector is now pulling access data into C1.ai. @@ -130,7 +130,7 @@ create it on an account that can see every workspace you want to sync. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -148,7 +148,7 @@ create it on an account that can see every workspace you want to sync. - Configure C1 credentials and Typeform credentials as environment + Configure C1.ai credentials and Typeform credentials as environment variables: ```bash @@ -171,6 +171,6 @@ create it on an account that can see every workspace you want to sync. - **Done.** Your Typeform connector is now pulling access data into C1. + **Done.** Your Typeform connector is now pulling access data into C1.ai. diff --git a/baton/uipath.mdx b/baton/uipath.mdx index efc33a58..2ca22218 100644 --- a/baton/uipath.mdx +++ b/baton/uipath.mdx @@ -1,8 +1,8 @@ --- title: "Set up a UiPath Orchestrator connector" og:title: "Set up a UiPath Orchestrator connector" -description: "C1 provides identity governance for UiPath Orchestrator. Integrate your UiPath Orchestrator instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for UiPath Orchestrator. Integrate your UiPath Orchestrator instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for UiPath Orchestrator. Integrate your UiPath Orchestrator instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for UiPath Orchestrator. Integrate your UiPath Orchestrator instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "UiPath Orchestrator" --- @@ -85,11 +85,11 @@ surface used by the connector. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -139,7 +139,7 @@ surface used by the connector. - **Done.** Your UiPath Orchestrator connector is now pulling access data into C1. + **Done.** Your UiPath Orchestrator connector is now pulling access data into C1.ai. @@ -148,7 +148,7 @@ surface used by the connector. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -166,7 +166,7 @@ surface used by the connector. - Configure C1 credentials and UiPath credentials as environment + Configure C1.ai credentials and UiPath credentials as environment variables: ```bash @@ -192,6 +192,6 @@ surface used by the connector. - **Done.** Your UiPath Orchestrator connector is now pulling access data into C1. + **Done.** Your UiPath Orchestrator connector is now pulling access data into C1.ai. diff --git a/baton/ukg.mdx b/baton/ukg.mdx index 4b045c87..a2442919 100644 --- a/baton/ukg.mdx +++ b/baton/ukg.mdx @@ -1,8 +1,8 @@ --- title: Set up a UKG connector -og:title: Set up a UKG connector - C1 docs -og:description: C1 provides identity governance for UKG. Integrate your UKG instance with C1 for unified visibility and governance over user access. -description: C1 provides identity governance for UKG. Integrate your UKG instance with C1 for unified visibility and governance over user access. +og:title: Set up a UKG connector - C1.ai docs +og:description: C1.ai provides identity governance for UKG. Integrate your UKG instance with C1.ai for unified visibility and governance over user access. +description: C1.ai provides identity governance for UKG. Integrate your UKG instance with C1.ai for unified visibility and governance over user access. sidebarTitle: UKG --- @@ -14,7 +14,7 @@ sidebarTitle: UKG | Roles | | | -An employee in UKG Pro can have one employment record per company they've ever been assigned to (for example, a stale record at a former or vendor company alongside a current record at their real employer). C1 considers an account **enabled** if **any** of the employee's employment records is non-terminated, not just their most recent or first-listed one — an employee who is active at one company is synced as enabled even if they also have older, terminated records at other companies. +An employee in UKG Pro can have one employment record per company they've ever been assigned to (for example, a stale record at a former or vendor company alongside a current record at their real employer). C1.ai considers an account **enabled** if **any** of the employee's employment records is non-terminated, not just their most recent or first-listed one — an employee who is active at one company is synced as enabled even if they also have older, terminated records at other companies. ## Gather UKG credentials @@ -43,7 +43,7 @@ Locate the **Customer API Key** at the top of this page. Carefully save this API Still on the **Service Account Administration** page, click **Add** to create a new service account. -Give the new service account a name such as "C1 integration" and enter the email address you want to associate with the account. +Give the new service account a name such as "C1.ai integration" and enter the email address you want to associate with the account. Click to enable the **Generate New Password** checkbox. @@ -84,18 +84,18 @@ Save the service endpoint. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of UKG 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **UKG** and click **Add**. @@ -133,23 +133,23 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your UKG connector is now pulling access data into C1. +**Done.** Your UKG connector is now pulling access data into C1.ai. **Follow these instructions to use the UKG 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai 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 C1.ai's support team](mailto:support@conductorone.com) to download the latest version of the connector. ### Step 1: Set up a new UKG connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -241,14 +241,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 C1.ai 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 UKG connector to. UKG data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the UKG connector to. UKG data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your UKG connector is now pulling access data into C1. +**Done.** Your UKG connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/unifi.mdx b/baton/unifi.mdx index 5cbacb34..e3ad2807 100644 --- a/baton/unifi.mdx +++ b/baton/unifi.mdx @@ -1,13 +1,13 @@ --- title: "Set up a UniFi Access connector" og:title: "Set up a UniFi Access connector" -description: "C1 provides identity governance for UniFi Access. Integrate your UniFi Access console with C1 for unified visibility and governance over door-access credentials." -og:description: "C1 provides identity governance for UniFi Access. Integrate your UniFi Access console with C1 for unified visibility and governance over door-access credentials." +description: "C1.ai provides identity governance for UniFi Access. Integrate your UniFi Access console with C1.ai for unified visibility and governance over door-access credentials." +og:description: "C1.ai provides identity governance for UniFi Access. Integrate your UniFi Access console with C1.ai for unified visibility and governance over door-access credentials." sidebarTitle: "UniFi Access" --- -C1 provides identity governance for UniFi Access. Integrate your UniFi Access -console with C1 for unified visibility and governance over users, visitors, and +C1.ai provides identity governance for UniFi Access. Integrate your UniFi Access +console with C1.ai for unified visibility and governance over users, visitors, and the NFC card and Touch Pass credentials assigned to them. ## Capabilities @@ -60,7 +60,7 @@ and credentials. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -83,4 +83,4 @@ and credentials. -**Done.** Your UniFi Access connector is now pulling access data into C1. +**Done.** Your UniFi Access connector is now pulling access data into C1.ai. diff --git a/baton/unleash.mdx b/baton/unleash.mdx index 964a7820..46a5b1e7 100644 --- a/baton/unleash.mdx +++ b/baton/unleash.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Unleash connector" og:title: "Set up a Unleash connector" -description: "C1 provides identity governance for Unleash. Integrate your Unleash instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Unleash. Integrate your Unleash instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Unleash. Integrate your Unleash instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Unleash. Integrate your Unleash instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Unleash" --- -C1 provides identity governance for Unleash. Integrate your Unleash -instance with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Unleash. Integrate your Unleash +instance with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -53,11 +53,11 @@ user and group endpoints reject any token without it. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -102,7 +102,7 @@ user and group endpoints reject any token without it. - **Done.** Your Unleash connector is now pulling access data into C1. + **Done.** Your Unleash connector is now pulling access data into C1.ai. @@ -126,6 +126,6 @@ user and group endpoints reject any token without it. - **Done.** Your Unleash connector is now pulling access data into C1. + **Done.** Your Unleash connector is now pulling access data into C1.ai. diff --git a/baton/v1/aws.mdx b/baton/v1/aws.mdx index 1d916152..bba731a0 100644 --- a/baton/v1/aws.mdx +++ b/baton/v1/aws.mdx @@ -1,13 +1,13 @@ --- title: "📜 Amazon Web Services (AWS) integration" -og:title: "Set up AWS connector - C1 docs" -og:description: Integrate your AWS instance with C1 to run user access reviews, enable just-in-time (JIT) access requests, and easily provision and deprovision access. -description: C1 provides identity governance for AWS. Integrate your AWS instance with C1 to run user access reviews (UARs) and enable just-in-time (JIT) access requests. +og:title: "Set up AWS connector - C1.ai docs" +og:description: Integrate your AWS instance with C1.ai to run user access reviews, enable just-in-time (JIT) access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance for AWS. Integrate your AWS instance with C1.ai to run user access reviews (UARs) and enable just-in-time (JIT) access requests. sidebarTitle: "AWS" --- -**A newer version of this connector is available.** If you're setting up an AWS connector with C1 for the first time, use the [v2 version](/baton/aws). +**A newer version of this connector is available.** If you're setting up an AWS connector with C1.ai for the first time, use the [v2 version](/baton/aws). ## Availability @@ -16,7 +16,7 @@ sidebarTitle: "AWS" ## Capabilities -- Sync user identities from AWS IAM Users to C1 +- Sync user identities from AWS IAM Users to C1.ai - Federated users authorization mapping - Provisioning supported: @@ -30,12 +30,12 @@ sidebarTitle: "AWS" ## Set up the AWS integration -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 C1.ai. -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. If this is your first AWS integration, the integration form opens automatically. Otherwise, click **Add connector**. @@ -44,19 +44,19 @@ If this is your first AWS integration, the integration form opens automatically. Choose whether to add the new AWS connector as a data source as a data source to an existing application (and select the app of your choice) or to create a new application. - **Do you SSO into AWS using your identity provider (IdP)?** If so, make sure to add the connector to the AWS app that was created automatically when you integrated your IdP with C1, rather than creating a new app. + **Do you SSO into AWS using your identity provider (IdP)?** If so, make sure to add the connector to the AWS app that was created automatically when you integrated your IdP with C1.ai, rather than creating a new 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 C1.ai users. Setting multiple owners is allowed. The AWS connector owner must have the following permissions: - - **Connector Administrator** or **Super Administrator** role in C1 + - **Connector Administrator** or **Super Administrator** role in C1.ai - **Ability to create an IAM Role** in AWS - C1 uses an IAM Trust relationship between your AWS Account and C1's Service AWS Account. - This is the [AWS recommended method of sharing access to AWS Accounts](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_third-party.html). C1 has a specially created and isolated AWS Account dedicated to the AWS integration. + C1.ai uses an IAM Trust relationship between your AWS Account and C1.ai's Service AWS Account. + This is the [AWS recommended method of sharing access to AWS Accounts](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_third-party.html). C1.ai has a specially created and isolated AWS Account dedicated to the AWS integration. For advanced configurations, the only trusted entity should be the following ARN: `arn:aws:iam::765656841499:role/ConductorOneService` @@ -67,17 +67,17 @@ Click **Next**. ### Next steps -- **If you are the integration owner**, proceed to [Integrate your AWS instance](/baton/v1/aws#integrate-your-aws-instance) for instructions on integrating AWS with C1. +- **If you are the integration owner**, proceed to [Integrate your AWS instance](/baton/v1/aws#integrate-your-aws-instance) for instructions on integrating AWS with C1.ai. -- **If someone else is the integration owner**, C1 will notify them by email that their help is needed to complete the setup process. +- **If someone else is the integration owner**, C1.ai will notify them by email that their help is needed to complete the setup process. ## Integrate your AWS instance -A user with the **Connector Administrator** or **Super Administrator** role in C1 and the **ability to create an IAM Role** in AWS must perform this task. +A user with the **Connector Administrator** or **Super Administrator** role in C1.ai and the **ability to create an IAM Role** in AWS must perform this task. -### Step 1: Get C1-provided External ID for AWS IAM Role +### Step 1: Get C1.ai-provided External ID for AWS IAM Role @@ -94,7 +94,7 @@ Copy and save the External ID populated in the **External ID** field. We'll use -### Step 2: Create an AWS IAM Role for C1 to use +### Step 2: Create an AWS IAM Role for C1.ai to use @@ -196,11 +196,11 @@ Copy the **Role ARN** for the Role we created, it should look like: `arn:aws:iam -### Step 3: Integrate C1 to your AWS instance +### Step 3: Integrate C1.ai to your AWS instance -Return to C1 and paste the AWS Role ARN you generated in Step 2 into the **Role ARN** field. +Return to C1.ai and paste the AWS Role ARN you generated in Step 2 into the **Role ARN** field. **Optional.** Click the checkbox to **Enable support for AWS Organizations**. @@ -220,17 +220,17 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your AWS connector is now pulling access data into C1. +**Done.** Your AWS connector is now pulling access data into C1.ai. ## Integrate using Terraform -As an alternative to the instructions above, use the following Terraform script to integrate your AWS instance with C1. +As an alternative to the instructions above, use the following Terraform script to integrate your AWS instance with C1.ai. -### Step 1: Get C1-provided External ID for AWS IAM Role +### Step 1: Get C1.ai-provided External ID for AWS IAM Role -In C1, navigate to **Apps** > **Connectors** > **AWS Connector**. +In C1.ai, navigate to **Apps** > **Connectors** > **AWS Connector**. Copy and save the **External ID** populated in the **External ID** field (we'll use this in Step 2. diff --git a/baton/v1/azure.mdx b/baton/v1/azure.mdx index 1017632c..d53d4b06 100644 --- a/baton/v1/azure.mdx +++ b/baton/v1/azure.mdx @@ -1,8 +1,8 @@ --- title: Set up an Azure Active Directory integration -og:title: Set up Azure connector - C1 docs -og:description: Integrate your Azure 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 Azure Active Directory. Integrate your Azure AD instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access. +og:title: Set up Azure connector - C1.ai docs +og:description: Integrate your Azure instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance and just-in-time provisioning for Azure Active Directory. Integrate your Azure AD instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access. sidebarTitle: Azure Active Directory --- @@ -12,7 +12,7 @@ sidebarTitle: Azure Active Directory ## Capabilities -- Sync user identities from Azure AD to C1 +- Sync user identities from Azure AD to C1.ai - Resources supported: - Groups @@ -27,12 +27,12 @@ sidebarTitle: Azure Active Directory ## Add a new Azure AD 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 C1.ai. -In C1, navigate to **Apps** > **Connectors**. +In C1.ai, navigate to **Apps** > **Connectors**. Search for **Azure AD** and click **Add**. @@ -51,7 +51,7 @@ Click the pencil icon next to **Owners** to choose who can configure and manage A Azure AD connector owner must have the following permissions: - - **Connector Administrator** or **Super Administrator** role in C1 + - **Connector Administrator** or **Super Administrator** role in C1.ai - **Global Administrator** in Azure AD @@ -61,19 +61,19 @@ Click **Add**. The connector is created and its configuration page opens. ### Next steps -Proceed to [Integrate your Azure AD instance](/baton/v1/azure#integrate-your-azure-ad-instance) for instructions on integrating Azure AD with C1. +Proceed to [Integrate your Azure AD instance](/baton/v1/azure#integrate-your-azure-ad-instance) for instructions on integrating Azure AD with C1.ai. ## Integrate your Azure AD instance -A user with the **Connector Administrator** or **Super Administrator** role in C1 and the **Global Administrator** permission in Azure AD must perform this task. +A user with the **Connector Administrator** or **Super Administrator** role in C1.ai and the **Global Administrator** permission in Azure AD must perform this task. ### Step 1: Log in with OAuth -In C1, navigate to the Azure AD connector by either: +In C1.ai, navigate to the Azure AD connector by either: - Clicking the **Set up connector** link in the email you received about configuring the connector. @@ -83,13 +83,13 @@ In C1, navigate to the Azure AD connector by either: Click **Login with OAuth**. -Log in and authorize C1 with your Azure AD instance. +Log in and authorize C1.ai with your Azure AD instance. In order for the integration to work properly, you must consent to all permissions: -### Step 2: Grant permissions to the C1 app +### Step 2: Grant permissions to the C1.ai app @@ -97,10 +97,10 @@ In the Azure AD control panel, go to **Enterprise Applications**. -Click the **C1 Integration** app (not to be confused with the **C1 SSO** app, which is used to log into C1, not to synchronize your data). +Click the **C1 Integration** app (not to be confused with the **C1 SSO** app, which is used to log into C1.ai, not to synchronize your data). -If the C1 Integration app doesn't appear in the list of apps right away, wait a minute and click **Refresh**. +If the C1.ai Integration app doesn't appear in the list of apps right away, wait a minute and click **Refresh**. @@ -118,19 +118,19 @@ Click **Grant admin consent for ...** on the **C1 Integration** app permissions -Return to the Azure AD integration in C1 by clicking the **Azure Active Directory** tile on the **Integrations** page. +Return to the Azure AD integration in C1.ai by clicking the **Azure Active Directory** tile on the **Integrations** page. Click the **Azure Active Directory** connector link that shows today's date in the **Connected on** column. -Click **Login with OAuth** a second time to complete the process and authorize C1 to obtain an access token with the permissions you've just granted. +Click **Login with OAuth** a second time to complete the process and authorize C1.ai to obtain an access token with the permissions you've just granted. -**Done.** Your Azure Active Directory connector is now pulling access data into C1. +**Done.** Your Azure Active Directory connector is now pulling access data into C1.ai. ### What's next? -If Azure Active Directory 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 Azure Active Directory 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.ai 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. diff --git a/baton/v1/bamboohr.mdx b/baton/v1/bamboohr.mdx index 8edcbc10..37bb2f18 100644 --- a/baton/v1/bamboohr.mdx +++ b/baton/v1/bamboohr.mdx @@ -1,13 +1,13 @@ --- title: Set up a BambooHR connector -og:title: Set up a BambooHR connector - C1 docs -og:description: Integrate your BambooHR 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 BambooHR. Integrate your BambooHR instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a BambooHR connector - C1.ai docs +og:description: Integrate your BambooHR instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance for BambooHR. Integrate your BambooHR instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: BambooHR --- -**A newer version of this connector is available.** This version of the connector is no longer available for installation. If you're setting up a BambooHR connector with C1 for the first time, use the [v2 version](/baton/bamboohr). +**A newer version of this connector is available.** This version of the connector is no longer available for installation. If you're setting up a BambooHR connector with C1.ai for the first time, use the [v2 version](/baton/bamboohr). ## Capabilities @@ -56,17 +56,17 @@ Copy the newly generated API key. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of BambooHR 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **BambooHR** and click **Add**. @@ -101,18 +101,18 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your BambooHR connector is now pulling access data into C1. +**Done.** Your BambooHR connector is now pulling access data into C1.ai. **Follow these instructions to use the BambooHR 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Step 1: Set up a new BambooHR connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -199,13 +199,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 C1.ai 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 BambooHR connector to. BambooHR data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the BambooHR connector to. BambooHR data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your BambooHR connector is now pulling access data into C1. +**Done.** Your BambooHR connector is now pulling access data into C1.ai. diff --git a/baton/v1/cloudflare.mdx b/baton/v1/cloudflare.mdx index 6eafabc6..f135a7c3 100644 --- a/baton/v1/cloudflare.mdx +++ b/baton/v1/cloudflare.mdx @@ -1,18 +1,18 @@ --- title: Set up a Cloudflare connector -og:title: Set up a Cloudflare connector - C1 docs -og:description: Integrate your Cloudflare 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 Cloudflare. Integrate your Cloudflare instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access. +og:title: Set up a Cloudflare connector - C1.ai docs +og:description: Integrate your Cloudflare instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance and just-in-time provisioning for Cloudflare. Integrate your Cloudflare instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access. sidebarTitle: Cloudflare --- -**A newer version of this connector is available.** This version of the connector is no longer available for installation. If you're setting up a Cloudflare connector with C1 for the first time, use the [v2 version](/baton/cloudflare). +**A newer version of this connector is available.** This version of the connector is no longer available for installation. If you're setting up a Cloudflare connector with C1.ai for the first time, use the [v2 version](/baton/cloudflare). ## Capabilities -- Sync user identities from Cloudflare to C1 +- Sync user identities from Cloudflare to C1.ai - Resources supported: - Roles @@ -24,12 +24,12 @@ sidebarTitle: Cloudflare ## Add a new Cloudflare 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 C1.ai. -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Cloudflare** and click **Add**. @@ -52,7 +52,7 @@ Click the pencil icon next to **Owners** to choose who can configure and manage A Cloudflare connector owner must have the following permissions: - - **Connector Administrator** or **Super Administrator** role in C1 + - **Connector Administrator** or **Super Administrator** role in C1.ai - **Super Administrator** access in Cloudflare @@ -63,12 +63,12 @@ Click **Add**. The connector is created and its configuration page opens. ### Next steps -Proceed to [Configure your Cloudflare connector](/baton/v1/cloudflare#configure-your-cloudflare-connector) for instructions on integrating Cloudflare with C1. +Proceed to [Configure your Cloudflare connector](/baton/v1/cloudflare#configure-your-cloudflare-connector) for instructions on integrating Cloudflare with C1.ai. ## Configure your Cloudflare connector -A user with the **Connector Administrator** or **Super Administrator** role in C1 and **Super Administrator** access in Cloudflare must perform this task. +A user with the **Connector Administrator** or **Super Administrator** role in C1.ai and **Super Administrator** access in Cloudflare must perform this task. ### Step 1: Locate your Cloudflare Account ID @@ -105,7 +105,7 @@ Fill out the **Create Custom Token** page as follows: 1. Give the API token a name, such as **C1** 2. Set the appropriate permissions for the API token: - - To provision Cloudflare access via C1 and run access reviews on your Cloudflare users: + - To provision Cloudflare access via C1.ai and run access reviews on your Cloudflare users: - Account -> Account Settings -> Edit - Account -> Access: Organizations, Identity Providers, and Groups -> Read - To run access reviews on your Cloudflare users: @@ -120,11 +120,11 @@ Click **Create Token** and copy the token generated for you. We'll use it in Ste -### Step 3: Add your Cloudflare credentials to C1 +### Step 3: Add your Cloudflare credentials to C1.ai -In C1, navigate to the Cloudflare connector by either: +In C1.ai, navigate to the Cloudflare connector by either: - Clicking the **Set up connector** link in the email you received about configuring the connector. @@ -147,7 +147,7 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Cloudflare connector is now pulling access data into C1. +**Done.** Your Cloudflare connector is now pulling access data into C1.ai. diff --git a/baton/v1/confluence.mdx b/baton/v1/confluence.mdx index c83880c1..0aaf6a77 100644 --- a/baton/v1/confluence.mdx +++ b/baton/v1/confluence.mdx @@ -1,18 +1,18 @@ --- title: Set up a Confluence connector -og:title: Set up a Confluence connector - C1 docs -og:description: Integrate your Confluence 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 Confluence. Integrate your Confluence instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a Confluence connector - C1.ai docs +og:description: Integrate your Confluence instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance for Confluence. Integrate your Confluence instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: Confluence --- -**A newer version of this connector is available.** This version of the connector is no longer available for installation. If you're setting up a Confluence connector with C1 for the first time, use the [v2 version](/baton/confluence). +**A newer version of this connector is available.** This version of the connector is no longer available for installation. If you're setting up a Confluence connector with C1.ai for the first time, use the [v2 version](/baton/confluence). ## Capabilities -- Sync user identities from Confluence to C1 +- Sync user identities from Confluence to C1.ai - Resources supported: - Groups @@ -20,12 +20,12 @@ sidebarTitle: Confluence ## Add a new Confluence 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 C1.ai. -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Confluence** and click **Add**. @@ -48,7 +48,7 @@ Click the pencil icon next to **Owners** to choose who can configure and manage A Confluence connector owner must have the following permissions: - - **Connector Administrator** or **Super Administrator** role in C1 + - **Connector Administrator** or **Super Administrator** role in C1.ai - **Administrator** access in Confluence @@ -59,12 +59,12 @@ Click **Add**. The connector is created and its configuration page opens. ### Next steps -Proceed to [Configure your Confluence connector](/baton/v1/confluence#configure-your-confluence-connector) for instructions on integrating Confluence with C1. +Proceed to [Configure your Confluence connector](/baton/v1/confluence#configure-your-confluence-connector) for instructions on integrating Confluence with C1.ai. ## Configure your Confluence connector -A user with the **Connector Administrator** or **Super Administrator** role in C1 and **Administrator** access in Confluence must perform this task. +A user with the **Connector Administrator** or **Super Administrator** role in C1.ai and **Administrator** access in Confluence must perform this task. ### Step 1: Create an API token @@ -87,11 +87,11 @@ Carefully copy the newly generated API token. We'll use it in Step 2. -### Step 2: Add your Confluence credentials to C1 +### Step 2: Add your Confluence credentials to C1.ai -In C1, navigate to the Confluence connector by either: +In C1.ai, navigate to the Confluence connector by either: - Clicking the **Set up connector** link in the email you received about configuring the connector. @@ -117,7 +117,7 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Confluence connector is now pulling access data into C1. +**Done.** Your Confluence connector is now pulling access data into C1.ai. diff --git a/baton/v1/coupa.mdx b/baton/v1/coupa.mdx index e8802f8e..62c64e33 100644 --- a/baton/v1/coupa.mdx +++ b/baton/v1/coupa.mdx @@ -1,13 +1,13 @@ --- title: Set up a Coupa connector -og:title: Set up a Coupa connector - C1 docs -og:description: Integrate your Coupa 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 Coupa. Integrate your Coupa instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a Coupa connector - C1.ai docs +og:description: Integrate your Coupa instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance for Coupa. Integrate your Coupa instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: Coupa --- -**A newer version of this connector is available.** This version of the connector is no longer available for installation. If you're setting up a Coupa connector with C1 for the first time, use the [v2 version](/baton/coupa). +**A newer version of this connector is available.** This version of the connector is no longer available for installation. If you're setting up a Coupa connector with C1.ai for the first time, use the [v2 version](/baton/coupa). ## Capabilities @@ -25,7 +25,7 @@ Choose the hosting method that best suits your needs: | Method | Availability | Notes | | :------------ | :---- | :--------- | -| Cloud-hosted | | A built-in, no-code connector hosted by C1. | +| Cloud-hosted | | A built-in, no-code connector hosted by C1.ai. | | Self-hosted | | A connector hosted and run in your own environment. | ## Gather Coupa credentials @@ -101,13 +101,13 @@ Click **Show/Hide** to view your client secret. Copy and save the client secret. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1. +- The **Connector Administrator** or **Super Administrator** role in C1.ai. - Access to the set of Coupa credentials generated by following the instructions above. -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -154,7 +154,7 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Coupa connector is now pulling access data into C1. +**Done.** Your Coupa connector is now pulling access data into C1.ai. diff --git a/baton/v1/datadog.mdx b/baton/v1/datadog.mdx index d8f7e32e..3e57d96a 100644 --- a/baton/v1/datadog.mdx +++ b/baton/v1/datadog.mdx @@ -1,18 +1,18 @@ --- title: Set up a Datadog connector -og:title: Set up a Datadog connector - C1 docs -og:description: Integrate your Datadog 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 Datadog. Integrate your Datadog instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a Datadog connector - C1.ai docs +og:description: Integrate your Datadog instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance for Datadog. Integrate your Datadog instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: Datadog --- -**A newer version of this connector is available.** This version of the connector is no longer available for installation. If you're setting up a Datadog connector with C1 for the first time, use the [v2 version](/baton/datadog). +**A newer version of this connector is available.** This version of the connector is no longer available for installation. If you're setting up a Datadog connector with C1.ai for the first time, use the [v2 version](/baton/datadog). ## Capabilities -- Sync user identities from Datadog to C1 +- Sync user identities from Datadog to C1.ai - Resources supported: - Roles @@ -20,12 +20,12 @@ sidebarTitle: Datadog ## Add a new Datadog 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 C1.ai. -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Datadog** and click **Add**. @@ -48,7 +48,7 @@ Click the pencil icon next to **Owners** to choose who can configure and manage A Datadog connector owner must have the following permissions: - - **Connector Administrator** or **Super Administrator** role in C1 + - **Connector Administrator** or **Super Administrator** role in C1.ai - **System Admin** access in Datadog @@ -59,12 +59,12 @@ Click **Add**. The connector is created and its configuration page opens. ### Next steps -Proceed to [Configure your Datadog connector](/baton/v1/datadog#configure-your-datadog-connector) for instructions on integrating Datadog with C1. +Proceed to [Configure your Datadog connector](/baton/v1/datadog#configure-your-datadog-connector) for instructions on integrating Datadog with C1.ai. ## Configure your Datadog connector -A user with the **Connector Administrator** or **Super Administrator** role in C1 and **System Admin** access in Datadog must perform this task. +A user with the **Connector Administrator** or **Super Administrator** role in C1.ai and **System Admin** access in Datadog must perform this task. ### Step 1: Locate your Datadog site @@ -89,7 +89,7 @@ Click **API Keys** and then click **+ New Key**. -Enter a name for your new key, such as "C1", and click **Create Key**. +Enter a name for your new key, such as "C1.ai", and click **Create Key**. Copy and save the newly created API key. We'll use this in Step 4. @@ -108,18 +108,18 @@ Click **Application Keys** and then click **+ New Key**. -Enter a name for your new key, such as "C1", and click **Create Key**. +Enter a name for your new key, such as "C1.ai", and click **Create Key**. Copy and save the newly created application key. We'll use this in Step 4. -### Step 4: Add your Datadog credentials to C1 +### Step 4: Add your Datadog credentials to C1.ai -In C1, navigate to the Datadog connector by either: +In C1.ai, navigate to the Datadog connector by either: - Clicking the **Set up connector** link in the email you received about configuring the connector. @@ -145,7 +145,7 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Datadog connector is now pulling access data into C1. +**Done.** Your Datadog connector is now pulling access data into C1.ai. diff --git a/baton/v1/docusign.mdx b/baton/v1/docusign.mdx index 39680453..a83cdafa 100644 --- a/baton/v1/docusign.mdx +++ b/baton/v1/docusign.mdx @@ -1,13 +1,13 @@ --- title: Set up a Docusign connector -og:title: Set up a Docusign connector - C1 docs -og:description: Integrate your Docusign 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 Docusign. Integrate your Docusign instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a Docusign connector - C1.ai docs +og:description: Integrate your Docusign instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance for Docusign. Integrate your Docusign instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: Docusign --- -**A newer version of this connector is available.** This version of the connector is no longer available for installation. If you're setting up a Docusign connector with C1 for the first time, use the [v2 version](/baton/docusign). +**A newer version of this connector is available.** This version of the connector is no longer available for installation. If you're setting up a Docusign connector with C1.ai for the first time, use the [v2 version](/baton/docusign). ## Capabilities @@ -23,16 +23,16 @@ sidebarTitle: Docusign ## Configure the Docusign connector -To complete this task, you'll need the **Connector Administrator** or **Super Administrator** role in C1. +To complete this task, you'll need the **Connector Administrator** or **Super Administrator** role in C1.ai. -**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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Docusign** and click **Add**. @@ -55,11 +55,11 @@ Click **Add**. The connector is created and its configuration page opens. Find the **Settings** area of the page and click **Edit**. -**Optional.** If you have more than one Docusign account, add the Docusign API **Account ID** so that the integration is set up to pull the correct data. If you do not specify an account ID, C1 will use the default account for the user (that's likely you!) who logs into Docusign with Oauth in the next step. To add an account ID: +**Optional.** If you have more than one Docusign account, add the Docusign API **Account ID** so that the integration is set up to pull the correct data. If you do not specify an account ID, C1.ai will use the default account for the user (that's likely you!) who logs into Docusign with Oauth in the next step. To add an account ID: - In Docusign Admin, navigate to the [Apps and Keys](https://admin.docusign.com/authenticate?goTo=apiIntegratorKey) page. - Click to copy the API Account ID for the account you wish to integrate. - - Return to C1. In the **Settings** area of the page, click **Edit**. + - Return to C1.ai. In the **Settings** area of the page, click **Edit**. - Paste the API Account ID into the **Account ID** field. - Click **Save**. @@ -67,10 +67,10 @@ Find the **Settings** area of the page and click **Edit**. Click **Login with OAuth**. -Log in and authorize C1 with your Docusign instance. +Log in and authorize C1.ai with your Docusign instance. -After authorizing, you'll be redirected back to the C1 integrations page, where an "Authorized as" message is now printed. +After authorizing, you'll be redirected back to the C1.ai integrations page, where an "Authorized as" message is now printed. Click **Save**. @@ -79,7 +79,7 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Docusign connector is now pulling access data into C1. +**Done.** Your Docusign connector is now pulling access data into C1.ai. **Follow these instructions to use a connector, hosted and run in your own environment.** diff --git a/baton/v1/github.mdx b/baton/v1/github.mdx index 3cd417e0..c0b60aa2 100644 --- a/baton/v1/github.mdx +++ b/baton/v1/github.mdx @@ -1,12 +1,12 @@ --- title: 📜 GitHub integration -og:title: Set up GitHub connector - C1 docs -og:description: Integrate your GitHub 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 GitHub. Integrate your GitHub instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access. +og:title: Set up GitHub connector - C1.ai docs +og:description: Integrate your GitHub instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance and just-in-time provisioning for GitHub. Integrate your GitHub instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access. --- -**A newer version of this connector is available.** If you're setting up a GitHub connector with C1 for the first time, use the [v2 version](/baton/github). +**A newer version of this connector is available.** If you're setting up a GitHub connector with C1.ai for the first time, use the [v2 version](/baton/github). ## Availability @@ -15,7 +15,7 @@ description: C1 provides identity governance and just-in-time provisioning for G ## Capabilities -- Sync user identities from GitHub to C1 +- Sync user identities from GitHub to C1.ai - Resources supported: - Repositories @@ -29,18 +29,18 @@ description: C1 provides identity governance and just-in-time provisioning for G Connecting to your GitHub environment, you will need: -- **Super Administrator** role in C1 +- **Super Administrator** role in C1.ai - **Org Owner** access in GitHub ## Set up the GitHub integration -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 C1.ai. -In C1, navigate to **Apps** > **Connectors** > **GitHub**. +In C1.ai, navigate to **Apps** > **Connectors** > **GitHub**. If this is your first GitHub integration, the integration form opens automatically. Otherwise, click **Add connector**. @@ -49,16 +49,16 @@ If this is your first GitHub integration, the integration form opens automatical Choose whether to add the new GitHub connector as a data source to an existing application (and select the app of your choice) or to create a new application. - **Do you SSO into GitHub using your identity provider (IdP)?** If so, make sure to add the connector to the GitHub app that was created automatically when you integrated your IdP with C1, rather than creating a new app. + **Do you SSO into GitHub using your identity provider (IdP)?** If so, make sure to add the connector to the GitHub app that was created automatically when you integrated your IdP with C1.ai, rather than creating a new 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 C1.ai users. Setting multiple owners is allowed. A GitHub connector owner must have the following permissions: - - **Connector Administrator** or **Super Administrator** role in C1 + - **Connector Administrator** or **Super Administrator** role in C1.ai - **Org Owner** access in GitHub @@ -69,12 +69,12 @@ Click **Next**. ### Next steps -- **If you are the integration owner**, proceed to **Integrate your GitHub instance [chosen method]** for instructions on integrating GitHub with C1. +- **If you are the integration owner**, proceed to **Integrate your GitHub instance [chosen method]** for instructions on integrating GitHub with C1.ai. -- **If someone else is the integration owner**, C1 will notify them by email that their help is needed to complete the setup process. +- **If someone else is the integration owner**, C1.ai will notify them by email that their help is needed to complete the setup process. -Choose the appropriate set of integration instructions based on the type of GitHub access token you want to use with C1: +Choose the appropriate set of integration instructions based on the type of GitHub access token you want to use with C1.ai: - Option 1: Use a [Personal access token (classic)](/baton/v1/github#option-1-integrate-your-github-instance-using-a-personal-access-token-classic) @@ -86,7 +86,7 @@ Choose the appropriate set of integration instructions based on the type of GitH Follow these instructions to integrate your GitHub instance by using a [GitHub personal access token (classic)](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#types-of-personal-access-tokens). -A user with the **Connector Administrator** or **Super Administrator** role in C1 and **Org Owner** access in GitHub must perform this task. +A user with the **Connector Administrator** or **Super Administrator** role in C1.ai and **Org Owner** access in GitHub must perform this task. @@ -115,11 +115,11 @@ Name your token (for example, **C1 Integration**). Optionally, add a token expir Select the following **Scopes:** - **repo** - select all - - **admin:org** - select all if using C1 for GitHub provisioning (see the note below), or **read::org** otherwise + - **admin:org** - select all if using C1.ai for GitHub provisioning (see the note below), or **read::org** otherwise - **user** - select all - The **write::org** scope is used by C1 when automatically provisioning and deprovisioning GitHub access on your behalf. **If you do not want C1 to perform these tasks for you, do not give your token this scope.** + The **write::org** scope is used by C1.ai when automatically provisioning and deprovisioning GitHub access on your behalf. **If you do not want C1.ai to perform these tasks for you, do not give your token this scope.** @@ -143,11 +143,11 @@ Make a note of your **Organization name**. We'll use it in Step 3. -### Step 3: Add your GitHub credentials to C1 +### Step 3: Add your GitHub credentials to C1.ai -In C1, navigate to **Apps** > **Connectors** > **GitHub**. +In C1.ai, navigate to **Apps** > **Connectors** > **GitHub**. @@ -170,14 +170,14 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your GitHub connector is now pulling access data into C1. +**Done.** Your GitHub connector is now pulling access data into C1.ai. ## Option 2: Integrate your GitHub instance using a fine-grained access token Follow these instructions to integrate your GitHub instance by using a [GitHub fine-grained personal access token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#types-of-personal-access-tokens). -A user with the **Connector Administrator** or **Super Administrator** role in C1 and **Org Owner** access in GitHub must perform this task. +A user with the **Connector Administrator** or **Super Administrator** role in C1.ai and **Org Owner** access in GitHub must perform this task. @@ -203,7 +203,7 @@ Click **Generate new token**. Name your token (for example, **C1 Integration**) and set a token expiration date. Optionally, add a description. -In the **Resource owner** dropdown, select the username associated with the GitHub organization you're integrating with C1. +In the **Resource owner** dropdown, select the username associated with the GitHub organization you're integrating with C1.ai. In the **Repository access** section of the page, select **All repositories**. @@ -221,7 +221,7 @@ In the **Permissions** section of the page, give the token the following permiss - **Metadata**: Read-only access - The repository permissions are used by C1 to sync and display data on repo membership (C1 cannot provision repositories). **If you do not want C1 to sync and display your GitHub organization's repo data, do not give your token these permissions.** + The repository permissions are used by C1.ai to sync and display data on repo membership (C1.ai cannot provision repositories). **If you do not want C1.ai to sync and display your GitHub organization's repo data, do not give your token these permissions.** @@ -242,11 +242,11 @@ Make a note of your **Organization name**. We'll use it in Step 3. -### Step 3: Add your GitHub credentials to C1 +### Step 3: Add your GitHub credentials to C1.ai -In C1, navigate to **Apps** > **Connectors** > **GitHub**. +In C1.ai, navigate to **Apps** > **Connectors** > **GitHub**. In the list of connectors, locate and click on the name of the connector with the **Not connected** label. @@ -267,7 +267,7 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your GitHub connector is now pulling access data into C1. +**Done.** Your GitHub connector is now pulling access data into C1.ai. diff --git a/baton/v1/gitlab.mdx b/baton/v1/gitlab.mdx index 46471ee9..653debdf 100644 --- a/baton/v1/gitlab.mdx +++ b/baton/v1/gitlab.mdx @@ -1,13 +1,13 @@ --- title: Set up a GitLab connector -og:title: Set up a GitLab connector - C1 docs -og:description: Integrate your GitLab 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 GitLab. Integrate your GitLab instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a GitLab connector - C1.ai docs +og:description: Integrate your GitLab instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance for GitLab. Integrate your GitLab instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: GitLab --- -**A newer version of this connector is available.** If you're setting up a GitLab connector with C1 for the first time, use the [v2 version](/baton/gitlab). +**A newer version of this connector is available.** If you're setting up a GitLab connector with C1.ai for the first time, use the [v2 version](/baton/gitlab). @@ -37,7 +37,7 @@ A user with group **Owner** access in GitLab must perform this task. In GitLab, click **Menu** > **Groups** > **Your Groups**. -Click on the group you wish to connect to C1. +Click on the group you wish to connect to C1.ai. Make a note of the Group Name or Group ID. @@ -76,17 +76,17 @@ Carefully copy and save the newly created 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 C1.ai - Access to the set of GitLab 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **GitLab** and click **Add**. @@ -124,7 +124,7 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your GitLab connector is now pulling access data into C1. +**Done.** Your GitLab connector is now pulling access data into C1.ai. diff --git a/baton/v1/google-cloud-platform.mdx b/baton/v1/google-cloud-platform.mdx index d592a3a4..4dd137a0 100644 --- a/baton/v1/google-cloud-platform.mdx +++ b/baton/v1/google-cloud-platform.mdx @@ -1,24 +1,24 @@ --- title: Set up a Google Cloud Platform connector -og:title: Set up a Google Cloud Platform connector - C1 docs -og:description: Integrate your Google Cloud Platform 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 Google Cloud Platform. Integrate your Google Cloud Platform instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access. +og:title: Set up a Google Cloud Platform connector - C1.ai docs +og:description: Integrate your Google Cloud Platform instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance and just-in-time provisioning for Google Cloud Platform. Integrate your Google Cloud Platform instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access. sidebarTitle: Google Cloud Platform --- -**A newer version of this connector is available.** If you're setting up a Google Cloud connector with C1 for the first time, use [Google Cloud Platform with Google Workspace](/baton/google-cloud-platform). +**A newer version of this connector is available.** If you're setting up a Google Cloud connector with C1.ai for the first time, use [Google Cloud Platform with Google Workspace](/baton/google-cloud-platform). **Which Google connector should I use?** -Each of the Google connectors offered by C1 varies in what it can sync and what it can provision. Selecting the right connector for you will depend on which Google services your organization uses, and how you want to manage Google resources within C1. +Each of the Google connectors offered by C1.ai varies in what it can sync and what it can provision. Selecting the right connector for you will depend on which Google services your organization uses, and how you want to manage Google resources within C1.ai. * [Google Cloud Platform](/baton/v1/google-cloud-platform) can sync accounts, projects, roles, and orgs. It can provision projects. * [Google Workspace](/baton/google-workspace) can sync accounts, groups, and roles. It can provision groups and roles. -* [Google Cloud Platform with Google Workspace](/baton/google-cloud-platform) can do all of the above, and it combines all of the resources and entitlements of the two connectors into a single app within C1. +* [Google Cloud Platform with Google Workspace](/baton/google-cloud-platform) can do all of the above, and it combines all of the resources and entitlements of the two connectors into a single app within C1.ai. Running separate connectors can simplify management and make the apps easier to understand and work with, while the combined app unifies resource management and allows Google Cloud to leverage existing Google Workspace groups for authorization. @@ -34,7 +34,7 @@ Running separate connectors can simplify management and make the apps easier to | Secrets | | | -The GCP connector does not sync roles that do not have any grants. As each GCP project contains roughly 1,000 roles by default, removing empty roles from the sync significantly improves the performance of the connector and the usability of the entitlement data it pulls into C1. If you want to include an empty GCP role in your access review, assign a service account to the role before creating the campaign. +The GCP connector does not sync roles that do not have any grants. As each GCP project contains roughly 1,000 roles by default, removing empty roles from the sync significantly improves the performance of the connector and the usability of the entitlement data it pulls into C1.ai. If you want to include an empty GCP role in your access review, assign a service account to the role before creating the campaign. ## Gather Google Cloud Platform credentials @@ -56,7 +56,7 @@ In the Google Cloud console, click the project select dropdown, then click **NEW Create a new project for your organization: - - **Project Name**: Choose a name such as "C1 Integration" + - **Project Name**: Choose a name such as "C1.ai Integration" - **Organization/Location**: Choose any organization and location After the project is created, make sure the correct project is selected in the dropdown at the top. @@ -97,8 +97,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 Cloud Platform Integration" + - **Service account name:** C1.ai Integration + - **Service account description:** for example, "Service account for C1.ai Google Cloud Platform Integration" Click **CREATE AND CONTINUE**. @@ -107,11 +107,11 @@ Click **CREATE AND CONTINUE**. Under **Grant this service account access to a project**, grant the appropriate permission level: - **Viewer** to run access reviews on your Google Cloud Platform users - - **Editor** to provision access via C1 and run access reviews + - **Editor** to provision access via C1.ai and run access reviews Alternatively, you can create and assign a custom role on the org level: - You'll need these permissions to give C1 **READ** access (for syncing access data): + You'll need these permissions to give C1.ai **READ** access (for syncing access data): ```bash cloudasset.assets.analyzeIamPolicy @@ -127,7 +127,7 @@ Under **Grant this service account access to a project**, grant the appropriate resourcemanager.projects.list ``` - You'll need these permissions to give C1 **READ/WRITE** access (for syncing access data and provisioning access): + You'll need these permissions to give C1.ai **READ/WRITE** access (for syncing access data and provisioning access): ```bash cloudasset.assets.analyzeIamPolicy @@ -171,9 +171,9 @@ For the principal, use the service account ID for the service account you create Select the appropriate roles: - - **Organization Viewer** and **Viewer** to give C1 **READ** access + - **Organization Viewer** and **Viewer** to give C1.ai **READ** access - - **Organization Administrator** and **Editor** to give C1 **READ/WRITE** access + - **Organization Administrator** and **Editor** to give C1.ai **READ/WRITE** access Click **Save**. @@ -186,10 +186,10 @@ If you want to sync information about the API tokens and service account keys cr -In the C1 project, search for "API keys" and enable it. +In the C1.ai project, search for "API keys" and enable it. -Next, grant the API Keys Viewer Role to the service account you created for C1. Navigate to **IAM & Admin** > **IAM**. +Next, grant the API Keys Viewer Role to the service account you created for C1.ai. Navigate to **IAM & Admin** > **IAM**. On the IAM page, find your Service Account in the list on the Principals tab. @@ -205,7 +205,7 @@ Click **Save**. -Next, we'll return to the C1 integration project you created earlier to generate the necessary credentials. +Next, we'll return to the C1.ai integration project you created earlier to generate the necessary credentials. ### Get credentials @@ -239,17 +239,17 @@ Keep the downloaded file safe, you'll use it to set up the connector. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Google Cloud Platform 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Google Cloud Platform** and click **Add**. @@ -282,7 +282,7 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Google Cloud Platform connector is now pulling access data into C1. +**Done.** Your Google Cloud Platform connector is now pulling access data into C1.ai. diff --git a/baton/v1/google-workspace.mdx b/baton/v1/google-workspace.mdx index a09f2cd6..2a7c501f 100644 --- a/baton/v1/google-workspace.mdx +++ b/baton/v1/google-workspace.mdx @@ -1,22 +1,22 @@ --- title: 📜 Google Workspace integration -og:title: Set up Google Workspace connector - C1 docs -og:description: Integrate your Google Workspace 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 Google Workspace. Integrate your Google Workspace instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access. +og:title: Set up Google Workspace connector - C1.ai docs +og:description: Integrate your Google Workspace instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance and just-in-time provisioning for Google Workspace. Integrate your Google Workspace instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access. sidebarTitle: Google Workspace --- -**A newer version of this connector is available.** If you're setting up a Google Workspace connector with C1 for the first time, use the [v2 version](/baton/google-workspace). +**A newer version of this connector is available.** If you're setting up a Google Workspace connector with C1.ai for the first time, use the [v2 version](/baton/google-workspace). ## Availability - **General availability.** The Google Workspace connector is available to all C1 users. + **General availability.** The Google Workspace connector is available to all C1.ai users. ## Capabilities -- Sync user identities from Google Workspace to C1 +- Sync user identities from Google Workspace to C1.ai - Resources supported: - Groups @@ -29,12 +29,12 @@ sidebarTitle: Google Workspace ## Set up the Google Workspace integration -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 C1.ai. -In C1, navigate to **Apps** > **Connectors** > **Google Workspace**. +In C1.ai, navigate to **Apps** > **Connectors** > **Google Workspace**. If this is your first Google Workspace integration, the integration form opens automatically. Otherwise, click **Add connector**. @@ -43,12 +43,12 @@ If this is your first Google Workspace integration, the integration form opens a Choose whether to add the new Google Workspace connector as a data source to an existing application (and select the app of your choice) or to create a new application. -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 C1.ai users. Setting multiple owners is allowed. A Google Workspace connector owner must have the following permissions: - - **Connector Administrator** or **Super Administrator** role in C1 + - **Connector Administrator** or **Super Administrator** role in C1.ai - **Super Admin** role in Google Workspace @@ -58,14 +58,14 @@ Click **Next**. ### Next steps -- **If you are the integration owner**, proceed to [Integrate your Google Workspace instance](/baton/v1/google-workspace#integrate-your-google-workspace-instance) for instructions on integrating Google Workspace with C1. +- **If you are the integration owner**, proceed to [Integrate your Google Workspace instance](/baton/v1/google-workspace#integrate-your-google-workspace-instance) for instructions on integrating Google Workspace with C1.ai. -- **If someone else is the integration owner**, C1 will notify them by email that their help is needed to complete the setup process. +- **If someone else is the integration owner**, C1.ai will notify them by email that their help is needed to complete the setup process. ## Integrate your Google Workspace instance -A user with the **Connector Administrator** or **Super Administrator** role in C1 and **Super Admin** role in Google Workspace must perform this task. +A user with the **Connector Administrator** or **Super Administrator** role in C1.ai and **Super Admin** role in Google Workspace must perform this task. ### Step 1: Sign in to the Google Cloud Console and Create a New Project @@ -82,7 +82,7 @@ In the toolbar, click the project select dropdown, and click **NEW PROJECT**. Create a new project for your organization: - - **Project Name**: Choose a names, cush as "C1 Integration" + - **Project Name**: Choose a names, cush as "C1.ai Integration" - **Organization/Location**: Choose the appropriate Organization/Location @@ -122,8 +122,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:** C1.ai Integration + - **Service account description:** for example, "Service account for C1.ai Google Workspace Integration" - Click **CREATE AND CONTINUE** @@ -229,11 +229,11 @@ Click **Manage Domains**. Locate and copy the domain labeled as the **Primary Do -### Step 7: Add your Google Workspace credentials to C1 +### Step 7: Add your Google Workspace credentials to C1.ai -In C1, navigate to **Apps** > **Connectors** > **Google Workspace**. +In C1.ai, navigate to **Apps** > **Connectors** > **Google Workspace**. In the list of connectors, locate and click on the name of the connector with the **Not connected** label. @@ -260,11 +260,11 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Google Workspace connector is now pulling access data into C1. +**Done.** Your Google Workspace connector is now pulling access data into C1.ai. ### 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 C1.ai 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. diff --git a/baton/v1/okta.mdx b/baton/v1/okta.mdx index 8477ce1d..bddfa9c1 100644 --- a/baton/v1/okta.mdx +++ b/baton/v1/okta.mdx @@ -1,19 +1,19 @@ --- title: "Set up an Okta connector" og:title: "Set up an Okta connector" -description: "Integrate your Okta instance with C1 to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access." -og:description: "Integrate your Okta instance with C1 to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access." +description: "Integrate your Okta instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access." +og:description: "Integrate your Okta instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access." sidebarTitle: "Okta (v1)" --- - **A newer version of this connector is available.** This version of the connector is no longer available for installation. If you're setting up an Okta connector with C1 for the first time, use the [v2 version](/baton/okta). + **A newer version of this connector is available.** This version of the connector is no longer available for installation. If you're setting up an Okta connector with C1.ai for the first time, use the [v2 version](/baton/okta). ## Capabilities -- Sync user identities from Okta to C1 -- Promote identities from application users to C1 users +- Sync user identities from Okta to C1.ai +- Promote identities from application users to C1.ai users - Resources supported: - Groups @@ -24,13 +24,13 @@ sidebarTitle: "Okta (v1)" - Group membership - Application assignment -Depending on the permissions of the Okta API Token, C1 has different functionality that it can provide. See the next section for more information. +Depending on the permissions of the Okta API Token, C1.ai has different functionality that it can provide. See the next section for more information. -### API token permissions and C1 capabilities +### API token permissions and C1.ai capabilities -C1's capabilities depend on the permissions of the API token used to set up the connector: +C1.ai's capabilities depend on the permissions of the API token used to set up the connector: -| C1 capability | Read-only admin token | Read-only + app admin + group admin token | Super admin token | +| C1.ai capability | Read-only admin token | Read-only + app admin + group admin token | Super admin token | | :--- | :--- | :--- | :--- | | Review group membership | | | | | Provision group membership | | | | @@ -41,12 +41,12 @@ C1's capabilities depend on the permissions of the API token used to set up the ## Add a new Okta 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 C1.ai. -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -69,7 +69,7 @@ Click the pencil icon next to **Owners** to choose who can configure and manage An Okta connector owner must have the following permissions: -- **Connector Administrator** or **Super Administrator** role in C1 +- **Connector Administrator** or **Super Administrator** role in C1.ai - **Read Only Admin** or **Super Admin** role in Okta @@ -81,12 +81,12 @@ Click **Add**. The connector is created and its configuration page opens. ### Next steps -Proceed to [Configure your Okta connector](/baton/v1/okta#configure-your-okta-connector) for instructions on integrating Okta with C1. +Proceed to [Configure your Okta connector](/baton/v1/okta#configure-your-okta-connector) for instructions on integrating Okta with C1.ai. ## Configure your Okta connector -A user with the **Connector Administrator** or **Super Administrator** role in C1 and **Read Only Admin** or **Super Admin** role in Okta must perform this task. +A user with the **Connector Administrator** or **Super Administrator** role in C1.ai and **Read Only Admin** or **Super Admin** role in Okta must perform this task. @@ -140,7 +140,7 @@ When **creating** an API token, Okta assigns the permissions of the _currently l Log into Okta with the account you'll use to generate the API token. -The account must have **Read Only Administrator,** **Super Administrator,** or a combination of **Read Only/App Admin/Group Admin** privileges. The permissions on the API token affects what features and functionality are available from C1. Before you begin, review the chart in [API permissions and C1 capabilities](/baton/okta#api-token-permissions-and-conductorone-capabilities) to make sure you're creating a token with the right permissions for your needs. +The account must have **Read Only Administrator,** **Super Administrator,** or a combination of **Read Only/App Admin/Group Admin** privileges. The permissions on the API token affects what features and functionality are available from C1.ai. Before you begin, review the chart in [API permissions and C1.ai capabilities](/baton/okta#api-token-permissions-and-conductorone-capabilities) to make sure you're creating a token with the right permissions for your needs. @@ -161,11 +161,11 @@ Copy and save the new API token. -### Step 3: Add your Okta credentials to C1 +### Step 3: Add your Okta credentials to C1.ai -In C1, navigate to the Okta connector by either: +In C1.ai, navigate to the Okta connector by either: - Clicking the **Set up connector** link in the email you received about configuring the connector. - Navigate to **Connectors** > **Okta** (if there is more than one **Okta** listed, click the one with your name listed as owner and the status **Not connected**). @@ -184,7 +184,7 @@ Paste your API token into the **API key** field. -**Optional.** If you want C1 to skip syncing inactive child apps, or to sync deprovisioned users, click the checkboxes accordingly. +**Optional.** If you want C1.ai to skip syncing inactive child apps, or to sync deprovisioned users, click the checkboxes accordingly. @@ -196,10 +196,10 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Okta connector is now pulling access data into C1. +**Done.** Your Okta connector is now pulling access data into C1.ai. ### What's next? -If Okta is your company's identity provider (meaning that it is used to SSO into other software), the connector 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 connectors for the SCIMed apps. +If Okta is your company's identity provider (meaning that it is used to SSO into other software), the connector sync will automatically create applications in C1.ai 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 connectors for the SCIMed apps. diff --git a/baton/v1/onelogin.mdx b/baton/v1/onelogin.mdx index 08e2db2a..6f238f72 100644 --- a/baton/v1/onelogin.mdx +++ b/baton/v1/onelogin.mdx @@ -1,18 +1,18 @@ --- title: "Set up a OneLogin connector" og:title: "Set up a OneLogin connector" -description: "Integrate your OneLogin instance with C1 to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access." -og:description: "Integrate your OneLogin instance with C1 to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access." +description: "Integrate your OneLogin instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access." +og:description: "Integrate your OneLogin instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access." sidebarTitle: "OneLogin (v1)" --- -**A newer version of this connector is available.** This version of the connector is no longer available for installation. If you're setting up a OneLogin connector with C1 for the first time, use the [v2 version](/baton/onelogin). +**A newer version of this connector is available.** This version of the connector is no longer available for installation. If you're setting up a OneLogin connector with C1.ai for the first time, use the [v2 version](/baton/onelogin). ## Capabilities -- Sync user identities from OneLogin to C1 +- Sync user identities from OneLogin to C1.ai - Resources supported: - Roles @@ -24,12 +24,12 @@ sidebarTitle: "OneLogin (v1)" ## Add a new OneLogin 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 C1.ai. -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -52,7 +52,7 @@ Click the pencil icon next to **Owners** to choose who can configure and manage A OneLogin connector owner must have the following permissions: -- **Connector Administrator** or **Super Administrator** role in C1 +- **Connector Administrator** or **Super Administrator** role in C1.ai - **Administrator** or **account owner** access to your OneLogin account @@ -64,12 +64,12 @@ Click **Add**. The connector is created and its configuration page opens. ### Next steps -Proceed to [Configure your OneLogin connector](/baton/v1/onelogin#configure-your-onelogin-connector) for instructions on integrating OneLogin with C1. +Proceed to [Configure your OneLogin connector](/baton/v1/onelogin#configure-your-onelogin-connector) for instructions on integrating OneLogin with C1.ai. ## Configure your OneLogin connector -A user with the **Connector Administrator** or **Super Administrator** role in C1 and **Administrator** or **account owner** access to your OneLogin account must perform this task. +A user with the **Connector Administrator** or **Super Administrator** role in C1.ai and **Administrator** or **account owner** access to your OneLogin account must perform this task. ### Step 1: Locate your OneLogin domain @@ -119,11 +119,11 @@ When the new API credential is created, copy and save the **Client ID** and **Cl -### Step 3: Add your OneLogin credentials to C1 +### Step 3: Add your OneLogin credentials to C1.ai -In C1, navigate to the OneLogin connector by either: +In C1.ai, navigate to the OneLogin connector by either: - Clicking the **Set up connector** link in the email you received about configuring the connector. - Navigate to **Apps** > **Connectors** > **OneLogin** (if there is more than one **OneLogin** listed, click the one with your name listed as owner and the status **Not connected**). @@ -154,10 +154,10 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your OneLogin connector is now pulling access data into C1. +**Done.** Your OneLogin connector is now pulling access data into C1.ai. ### What's next? -If OneLogin is your company's identity provider (meaning that it is used to SSO into other software), the connector 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 connectors for the SCIMed apps. +If OneLogin is your company's identity provider (meaning that it is used to SSO into other software), the connector sync will automatically create applications in C1.ai 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 connectors for the SCIMed apps. diff --git a/baton/v1/ramp.mdx b/baton/v1/ramp.mdx index 6447e5d1..16e85726 100644 --- a/baton/v1/ramp.mdx +++ b/baton/v1/ramp.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Ramp connector" og:title: "Set up a Ramp connector" -description: "Integrate your Ramp instance with C1 to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access." -og:description: "Integrate your Ramp instance with C1 to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access." +description: "Integrate your Ramp instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access." +og:description: "Integrate your Ramp instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access." sidebarTitle: "Ramp (v1)" --- -**A newer version of this connector is available.** This version of the connector is no longer available for installation. If you're setting up a Ramp connector with C1 for the first time, use the [v2 version](/baton/ramp). +**A newer version of this connector is available.** This version of the connector is no longer available for installation. If you're setting up a Ramp connector with C1.ai for the first time, use the [v2 version](/baton/ramp). ## Capabilities @@ -22,17 +22,17 @@ sidebarTitle: "Ramp (v1)" To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - The **Administrator** role in Ramp -**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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -63,11 +63,11 @@ Click **Login with OAuth**. -Log in and authorize C1 with your Ramp instance. +Log in and authorize C1.ai with your Ramp instance. -You will then be redirected back to the Ramp setup page in C1, where you'll see an authorization message. +You will then be redirected back to the Ramp setup page in C1.ai, where you'll see an authorization message. @@ -75,7 +75,7 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Ramp connector is now pulling access data into C1. +**Done.** Your Ramp connector is now pulling access data into C1.ai. diff --git a/baton/v1/salesforce.mdx b/baton/v1/salesforce.mdx index b8acf69b..f43255d5 100644 --- a/baton/v1/salesforce.mdx +++ b/baton/v1/salesforce.mdx @@ -1,18 +1,18 @@ --- title: "Set up a Salesforce connector" og:title: "Set up a Salesforce connector" -description: "Integrate your Salesforce instance with C1 to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access." -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: "Integrate your Salesforce instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access." +og:description: "Integrate your Salesforce instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access." sidebarTitle: "Salesforce (v1)" --- - **A newer version of this connector is available.** This version of the connector is no longer available for installation. If you're setting up a Salesforce connector with C1 for the first time, use the [v2 version](/baton/salesforce). + **A newer version of this connector is available.** This version of the connector is no longer available for installation. If you're setting up a Salesforce connector with C1.ai for the first time, use the [v2 version](/baton/salesforce). ## Availability -C1 only integrates with the Salesforce editions with API access: Salesforce Enterprise, Unlimited, Developer, and Performance editions. +C1.ai 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. @@ -20,7 +20,7 @@ Learn more about which Salesforce editions support API access in the [Salesforce ## Capabilities -- Sync user identities from Salesforce to C1 +- Sync user identities from Salesforce to C1.ai - Resources supported: - Groups @@ -30,12 +30,12 @@ Learn more about which Salesforce editions support API access in the [Salesforce ## Add a new Salesforce 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 C1.ai. -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -62,7 +62,7 @@ Click the pencil icon next to **Owners** to choose who can configure and manage A Salesforce connector owner must have the following permissions: -- **Connector Administrator** or **Super Administrator** role in C1 +- **Connector Administrator** or **Super Administrator** role in C1.ai - A Salesforce user account with a profile that includes the **API Enabled** permission (this permission is included by default in the **Standard User** and **System Administrator** profiles) @@ -74,17 +74,17 @@ Click **Add**. The connector is created and its configuration page opens. ### Next steps -Proceed to [Configure your Salesforce connector](/baton/v1/salesforce#configure-your-salesforce-connector) for instructions on integrating Salesforce with C1. +Proceed to [Configure your Salesforce connector](/baton/v1/salesforce#configure-your-salesforce-connector) for instructions on integrating Salesforce with C1.ai. ## Configure your Salesforce connector -A user with the **Connector Administrator** or **Super Administrator** role in C1 and a Salesforce user account with a profile that includes the **API Enabled** permission must perform this task. +A user with the **Connector Administrator** or **Super Administrator** role in C1.ai and a Salesforce user account with a profile that includes the **API Enabled** permission must perform this task. ### Step 0: 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** permission. This permission is included by default in the **Standard User** and **System Administrator** profiles. +Before you begin, make sure that the Salesforce user who will set up the integration with C1.ai has a profile that includes the **API Enabled** permission. This permission is included by default in the **Standard User** and **System Administrator** profiles. To edit a different profile so that it includes the **API Enabled** permission: @@ -124,7 +124,7 @@ Log into the Salesforce admin panel and copy the URL from your browser. We'll us -C1 integrates with domains that use one of the following Salesforce URL structures: +C1.ai integrates with domains that use one of the following Salesforce URL structures: - `my.salesforce.com` - `sandbox.my.salesforce.com` @@ -140,7 +140,7 @@ C1 integrates with domains that use one of the following Salesforce URL structur -In C1, navigate to the Salesforce connector by either: +In C1.ai, navigate to the Salesforce connector by either: - Clicking the **Set up connector** link in the email you received about configuring the connector. - Navigate to **Connectors** > **Salesforce** (if there is more than one **Salesforce** listed, click the one with your name listed as owner and the status **Not connected**). @@ -155,7 +155,7 @@ In the **Domain** field, enter the Salesforce domain you looked up in Step 1. -**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. +**Optional.** Check the box to tell C1.ai 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. @@ -171,11 +171,11 @@ Click **Login with OAuth**. -Log in and authorize C1 with your Salesforce instance. +Log in and authorize C1.ai with your Salesforce instance. -You will then be redirected back to the Salesforce setup page in C1, where you'll see an authorization message. +You will then be redirected back to the Salesforce setup page in C1.ai, where you'll see an authorization message. @@ -183,7 +183,7 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Salesforce connector is now pulling access data into C1. +**Done.** Your Salesforce connector is now pulling access data into C1.ai. ## Troubleshooting the Salesforce integration diff --git a/baton/v1/sentry.mdx b/baton/v1/sentry.mdx index 50d90736..4a7e46fe 100644 --- a/baton/v1/sentry.mdx +++ b/baton/v1/sentry.mdx @@ -1,8 +1,8 @@ --- title: Set up a Sentry connector -og:title: Set up a Sentry connector - C1 docs -og:description: Integrate your Sentry 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 Sentry. Integrate your Sentry instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a Sentry connector - C1.ai docs +og:description: Integrate your Sentry instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance for Sentry. Integrate your Sentry instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: Sentry --- @@ -60,18 +60,18 @@ Your new integration is created. Scroll to the **TOKENS** section of the page an To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Sentry 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Sentry** and click **Add**. @@ -108,7 +108,7 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Sentry connector is now pulling access data into C1. +**Done.** Your Sentry connector is now pulling access data into C1.ai. diff --git a/baton/v1/snowflake.mdx b/baton/v1/snowflake.mdx index c48ef4a9..ec603bc7 100644 --- a/baton/v1/snowflake.mdx +++ b/baton/v1/snowflake.mdx @@ -1,18 +1,18 @@ --- title: "Set up a Snowflake connector" og:title: "Set up a Snowflake connector" -description: "Integrate your Snowflake instance with C1 to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access." -og:description: "Integrate your Snowflake instance with C1 to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access." +description: "Integrate your Snowflake instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access." +og:description: "Integrate your Snowflake instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access." sidebarTitle: "Snowflake (v1)" --- -**A newer version of this connector is available.** This version of the connector is no longer available for installation. If you're setting up a Snowflake connector with C1 for the first time, use the [v2 version](/baton/snowflake). +**A newer version of this connector is available.** This version of the connector is no longer available for installation. If you're setting up a Snowflake connector with C1.ai for the first time, use the [v2 version](/baton/snowflake). ## Capabilities -- Sync user identities from Snowflake to C1 +- Sync user identities from Snowflake to C1.ai - Resources supported: - Roles @@ -20,12 +20,12 @@ sidebarTitle: "Snowflake (v1)" ## Add a new Snowflake 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 C1.ai. -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -52,7 +52,7 @@ Click the pencil icon next to **Owners** to choose who can configure and manage A Snowflake connector owner must have the following permissions: -- **Connector Administrator** or **Super Administrator** role in C1 +- **Connector Administrator** or **Super Administrator** role in C1.ai - **Manage Grants** global privilege in Snowflake @@ -64,12 +64,12 @@ Click **Add**. The connector is created and its configuration page opens. ### Next steps -Proceed to [Configure your Snowflake connector](/baton/v1/snowflake#configure-your-snowflake-connector) for instructions on integrating Snowflake with C1. +Proceed to [Configure your Snowflake connector](/baton/v1/snowflake#configure-your-snowflake-connector) for instructions on integrating Snowflake with C1.ai. ## Configure your Snowflake connector -A user with the **Connector Administrator** or **Super Administrator** role in C1 and **Manage Grants** global privilege in Snowflake must perform this task. +A user with the **Connector Administrator** or **Super Administrator** role in C1.ai and **Manage Grants** global privilege in Snowflake must perform this task. @@ -84,7 +84,7 @@ In Snowflake, click **Organization**. -Locate the account you wish to connect to C1 in the accounts list. +Locate the account you wish to connect to C1.ai in the accounts list. @@ -93,11 +93,11 @@ Hover over the value in the **LOCATOR** column, and click the copy function. We' -### Step 2: Add your Snowflake credentials to C1 +### Step 2: Add your Snowflake credentials to C1.ai -In C1, navigate to the Snowflake connector by either: +In C1.ai, navigate to the Snowflake connector by either: - Clicking the **Set up connector** link in the email you received about configuring the connector. - Navigate to **Connectors** > **Snowflake** (if there is more than one **Snowflake** listed, click the one with your name listed as owner and the status **Not connected**). @@ -150,10 +150,10 @@ Click **Save**. -Return to C1. After you see the **Connector updated** message, click on **View logs** to verify that the connector syncs successfully. +Return to C1.ai. After you see the **Connector updated** message, click on **View logs** to verify that the connector syncs successfully. -**Done.** Your Snowflake connector is now pulling access data into C1. +**Done.** Your Snowflake connector is now pulling access data into C1.ai. diff --git a/baton/v1/tailscale.mdx b/baton/v1/tailscale.mdx index 470cadba..a6e84c61 100644 --- a/baton/v1/tailscale.mdx +++ b/baton/v1/tailscale.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Tailscale connector" og:title: "Set up a Tailscale connector" -description: "Integrate your Tailscale instance with C1 to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access." -og:description: "Integrate your Tailscale instance with C1 to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access." +description: "Integrate your Tailscale instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access." +og:description: "Integrate your Tailscale instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access." sidebarTitle: "Tailscale (v1)" --- -**A newer version of this connector is available.** This version of the connector is no longer available for installation. If you're setting up a Tailscale connector with C1 for the first time, use the [v2 version](/baton/tailscale). +**A newer version of this connector is available.** This version of the connector is no longer available for installation. If you're setting up a Tailscale connector with C1.ai for the first time, use the [v2 version](/baton/tailscale). ## Capabilities @@ -57,17 +57,17 @@ Copy and save the API key. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Tailscale 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -112,7 +112,7 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Tailscale connector is now pulling access data into C1. +**Done.** Your Tailscale connector is now pulling access data into C1.ai. diff --git a/baton/v1/twingate.mdx b/baton/v1/twingate.mdx index 8ec9dfe4..2f38b446 100644 --- a/baton/v1/twingate.mdx +++ b/baton/v1/twingate.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Twingate connector" og:title: "Set up a Twingate connector" -description: "Integrate your Twingate instance with C1 to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access." -og:description: "Integrate your Twingate instance with C1 to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access." +description: "Integrate your Twingate instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access." +og:description: "Integrate your Twingate instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access." sidebarTitle: "Twingate (v1)" --- -**A newer version of this connector is available.** This version of the connector is no longer available for installation. If you're setting up a Twingate connector with C1 for the first time, use the [v2 version](/baton/twingate). +**A newer version of this connector is available.** This version of the connector is no longer available for installation. If you're setting up a Twingate connector with C1.ai for the first time, use the [v2 version](/baton/twingate). ## Capabilities @@ -45,7 +45,7 @@ Click **Generate Token**. Give the API token a label, such as **C1**. Select the appropriate permission level for the API key: - **Read only** to run access reviews on your Twingate users. - - **Read & Write** to provision group membership via C1 and run access reviews. + - **Read & Write** to provision group membership via C1.ai and run access reviews. @@ -64,17 +64,17 @@ The new API key is generated for you. Click **Copy** and save the key. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Twingate 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -119,7 +119,7 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Twingate connector is now pulling access data into C1. +**Done.** Your Twingate connector is now pulling access data into C1.ai. diff --git a/baton/v1/zendesk.mdx b/baton/v1/zendesk.mdx index 46e3130a..f9923a79 100644 --- a/baton/v1/zendesk.mdx +++ b/baton/v1/zendesk.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Zendesk connector" og:title: "Set up a Zendesk connector" -description: "Integrate your Zendesk instance with C1 to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access." -og:description: "Integrate your Zendesk instance with C1 to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access." +description: "Integrate your Zendesk instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access." +og:description: "Integrate your Zendesk instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access." sidebarTitle: "Zendesk (v1)" --- -**A newer version of this connector is available.** This version of the connector is no longer available for installation. If you're setting up a Zendesk connector with C1 for the first time, use the [v2 version](/baton/zendesk). +**A newer version of this connector is available.** This version of the connector is no longer available for installation. If you're setting up a Zendesk connector with C1.ai for the first time, use the [v2 version](/baton/zendesk). ## Capabilities @@ -76,17 +76,17 @@ Click **Save**. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Zendesk 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -133,19 +133,19 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Zendesk connector is now pulling access data into C1. +**Done.** Your Zendesk connector is now pulling access data into C1.ai. **Follow these instructions to use the Zendesk 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Step 1: Set up a new Zendesk connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -238,15 +238,15 @@ 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 C1.ai 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 Zendesk connector to. Zendesk data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Zendesk connector to. Zendesk data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Zendesk connector is now pulling access data into C1. +**Done.** Your Zendesk connector is now pulling access data into C1.ai. diff --git a/baton/valimail.mdx b/baton/valimail.mdx index 8952bdfa..d41170c4 100644 --- a/baton/valimail.mdx +++ b/baton/valimail.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Valimail connector" -description: "C1 provides identity governance and just-in-time provisioning for Valimail. Integrate your Valimail instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for Valimail. Integrate your Valimail instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." og:title: "Set up a Valimail connector" -og:description: "C1 provides identity governance and just-in-time provisioning for Valimail. Integrate your Valimail instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Valimail. Integrate your Valimail instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "Valimail" --- @@ -23,7 +23,7 @@ This connector does not support full account deprovisioning. You can disable 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 C1.ai 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 | |-------------|-------------------|-------------| @@ -73,17 +73,17 @@ For example, if your ValiMail URL is `https://app.valimail.com/app/conductorone- **To complete this task, you'll need:** -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Valimail 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Valimail** and click **Add**. @@ -116,12 +116,12 @@ For example, if your ValiMail URL is `https://app.valimail.com/app/conductorone- -**Done.** Your Valimail connector is now pulling access data into C1. +**Done.** Your Valimail connector is now pulling access data into C1.ai. **Follow these instructions to use the Valimail 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -131,7 +131,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -225,14 +225,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 C1.ai 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 Valimail connector to. Valimail data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Valimail connector to. Valimail data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Valimail connector is now pulling access data into C1. +**Done.** Your Valimail connector is now pulling access data into C1.ai. diff --git a/baton/veeam.mdx b/baton/veeam.mdx index bd97d317..8514313d 100644 --- a/baton/veeam.mdx +++ b/baton/veeam.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Veeam connector" og:title: "Set up a Veeam connector" -description: "C1 provides identity governance and just-in-time provisioning for Veeam. Integrate your Veeam 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 Veeam. Integrate your Veeam instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for Veeam. Integrate your Veeam instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Veeam. Integrate your Veeam instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "Veeam" --- @@ -35,7 +35,7 @@ To configure the Veeam connector, you need an account with the **Portal Administ - Obtain credentials for C1: + Obtain credentials for C1.ai: 1. **Veeam URL**: The base URL of your Enterprise Manager instance (e.g., `https://veeam-server:9398`). 2. **Username**: A Windows domain or local account that has been added to Enterprise Manager (e.g., `DOMAIN\Administrator` or `hostname\username`). @@ -49,11 +49,11 @@ To configure the Veeam connector, you need an account with the **Portal Administ - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -101,19 +101,19 @@ To configure the Veeam connector, you need an account with the **Portal Administ - **Done.** Your Veeam connector is now pulling access data into C1. + **Done.** Your Veeam connector is now pulling access data into C1.ai. Follow these instructions to use the [Veeam](https://github.com/conductorone/baton-veeam) 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. + When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1.ai, automatically syncing and uploading data at regular intervals. ### Step 1: Set up a new Veeam connector - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -212,15 +212,15 @@ To configure the Veeam connector, you need an account with the **Portal Administ - 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 C1.ai 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 Veeam connector to. Veeam data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Veeam connector to. Veeam data should be found on the **Entitlements** and **Accounts** tabs. - **Done.** Your Veeam connector is now pulling access data into C1. + **Done.** Your Veeam connector is now pulling access data into C1.ai. diff --git a/baton/vercel.mdx b/baton/vercel.mdx index b65cc80a..76fef718 100644 --- a/baton/vercel.mdx +++ b/baton/vercel.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Vercel connector" og:title: "Set up a Vercel connector" -description: "C1 provides identity governance and just-in-time provisioning for Vercel. Integrate your Vercel 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 Vercel. Integrate your Vercel instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for Vercel. Integrate your Vercel instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Vercel. Integrate your Vercel instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "Vercel" --- @@ -23,7 +23,7 @@ The Vercel connector syncs the following resources: {/* AUTO-GENERATED:END - capabilities */} -Projects and Access Groups are Enterprise-only features in Vercel. If you are using a Hobby or Pro plan, disable the **Projects** and **Access Groups** resource types from the C1 UI to avoid 403 authorization errors during sync. +Projects and Access Groups are Enterprise-only features in Vercel. If you are using a Hobby or Pro plan, disable the **Projects** and **Access Groups** resource types from the C1.ai UI to avoid 403 authorization errors during sync. Resource types can also be disabled independently — for example, an Enterprise team that doesn't use Access Groups can disable just **Access Groups** without affecting project-level role grants. @@ -39,7 +39,7 @@ The Vercel connector exposes the following entitlements per resource type: | Projects | `admin`, `project_developer`, `project_viewer`, `project_guest` | -**Grant expansion**: The connector syncs Access Group → Project role mappings as grant expansion, allowing C1 to derive transitive project access for Enterprise accounts. +**Grant expansion**: The connector syncs Access Group → Project role mappings as grant expansion, allowing C1.ai to derive transitive project access for Enterprise accounts. ## Provisioning notes @@ -241,7 +241,7 @@ To configure the Vercel connector, you need administrator permissions in Vercel. - 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 C1.ai connectors (if desired), then apply the secret config and deployment config files. diff --git a/baton/verkada.mdx b/baton/verkada.mdx index 6d5d00d8..6b70c951 100644 --- a/baton/verkada.mdx +++ b/baton/verkada.mdx @@ -1,9 +1,9 @@ --- title: Set up a Verkada connector -og:title: Set up a Verkada connector - C1 docs -og:description: Integrate your Verkada instance with C1 to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. -seo_description: Integrate your Verkada 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 Verkada. Integrate your Verkada instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access. +og:title: Set up a Verkada connector - C1.ai docs +og:description: Integrate your Verkada instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +seo_description: Integrate your Verkada instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance and just-in-time provisioning for Verkada. Integrate your Verkada instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access. sidebarTitle: Verkada --- @@ -32,14 +32,14 @@ In Verkada click **Admin Home**. Click **Verkada API** and select **+ New API Key**. -Give the new API key a name, such as "C1 integration". +Give the new API key a name, such as "C1.ai integration". Select the relevant permission: - - **Read/write** if you want to use C1 to provision Verkada group membership + - **Read/write** if you want to use C1.ai to provision Verkada group membership - - **Read only** if you **do not** want to use C1 to provision Verkada group membership + - **Read only** if you **do not** want to use C1.ai to provision Verkada group membership Select an expiration for the API key, then click **Generate API key**. @@ -55,18 +55,18 @@ Carefully and copy and save the new API key. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Verkada 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Verkada** and click **Add**. @@ -101,13 +101,13 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Verkada connector is now pulling access data into C1. +**Done.** Your Verkada connector is now pulling access data into C1.ai. **Follow these instructions to use the Verkada 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -117,7 +117,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -212,14 +212,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 C1.ai 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 Verkada connector to. Verkada data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Verkada connector to. Verkada data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Verkada connector is now pulling access data into C1. +**Done.** Your Verkada connector is now pulling access data into C1.ai. diff --git a/baton/vgs.mdx b/baton/vgs.mdx index 0781e4f7..faafb0df 100644 --- a/baton/vgs.mdx +++ b/baton/vgs.mdx @@ -1,8 +1,8 @@ --- title: "Set up a VGS connector" -og:title: "Set up a VGS connector - C1 docs" -description: "C1 provides identity governance and just-in-time provisioning for Very Good Security (VGS). Integrate your VGS organization with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision vault access." -og:description: "C1 provides identity governance and just-in-time provisioning for Very Good Security (VGS). Integrate your VGS organization with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision vault access." +og:title: "Set up a VGS connector - C1.ai docs" +description: "C1.ai provides identity governance and just-in-time provisioning for Very Good Security (VGS). Integrate your VGS organization with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision vault access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Very Good Security (VGS). Integrate your VGS organization with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision vault access." sidebarTitle: "VGS" --- @@ -133,7 +133,7 @@ The CLI outputs the service account credentials. Carefully copy and save the **C -Service accounts have an email in the format `clientId@vgs.dev`. These accounts appear in vault member lists but are automatically excluded from synced user resources in C1. +Service accounts have an email in the format `clientId@vgs.dev`. These accounts appear in vault member lists but are automatically excluded from synced user resources in C1.ai. **That's it!** Next, move on to the connector configuration instructions. @@ -143,7 +143,7 @@ Service accounts have an email in the format `clientId@vgs.dev`. These accounts To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - The service account **Client ID** and **Client Secret** from the steps above - Your VGS **Organization ID** @@ -151,11 +151,11 @@ To complete this task, you'll need: -**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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **VGS** and click **Add**. @@ -192,14 +192,14 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**That's it!** Your VGS connector is now pulling access data into C1. +**That's it!** Your VGS connector is now pulling access data into C1.ai. **Follow these instructions to use the VGS 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -211,7 +211,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -307,14 +307,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 C1.ai 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 VGS connector to. VGS data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the VGS connector to. VGS data should be found on the **Entitlements** and **Accounts** tabs. -**That's it!** Your VGS connector is now pulling access data into C1. +**That's it!** Your VGS connector is now pulling access data into C1.ai. diff --git a/baton/victorops.mdx b/baton/victorops.mdx index afcfa571..01cc0747 100644 --- a/baton/victorops.mdx +++ b/baton/victorops.mdx @@ -1,8 +1,8 @@ --- title: Set up a Splunk VictorOps connector -og:title: Set up a Splunk VictorOps connector - C1 docs -og:description: Integrate your Splunk VictorOps 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 Splunk VictorOps. Integrate your VictorOps instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a Splunk VictorOps connector - C1.ai docs +og:description: Integrate your Splunk VictorOps instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance and just-in-time provisioning for Splunk VictorOps. Integrate your VictorOps instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: "Splunk VictorOps" --- @@ -37,9 +37,9 @@ Click **New Key**. Generate a new API key. - Select **Read-only** to give C1 **READ** permission to your VictorOps instance. + Select **Read-only** to give C1.ai **READ** permission to your VictorOps instance. - If you want to provision access to VictorOps teams using C1, this requires **READ/WRITE** access, so do not select this option. + If you want to provision access to VictorOps teams using C1.ai, this requires **READ/WRITE** access, so do not select this option. Carefully copy and save the newly generated **API key**. @@ -52,18 +52,18 @@ Carefully copy and save the newly generated **API key**. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of VictorOps 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **VictorOps** and click **Add**. @@ -99,14 +99,14 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your VictorOps connector is now pulling access data into C1. +**Done.** Your VictorOps connector is now pulling access data into C1.ai. **The [VictorOps](https://github.com/conductorone/baton-victorops) 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -116,7 +116,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -209,13 +209,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 C1.ai 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 VictorOps connector to. VictorOps data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the VictorOps connector to. VictorOps data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your VictorOps connector is now pulling access data into C1. +**Done.** Your VictorOps connector is now pulling access data into C1.ai. diff --git a/baton/vultr.mdx b/baton/vultr.mdx index f4c5d9a8..454665e2 100644 --- a/baton/vultr.mdx +++ b/baton/vultr.mdx @@ -1,8 +1,8 @@ --- title: Set up a Vultr connector -og:title: Set up a Vultr connector - C1 docs -og:description: "C1 provides identity governance for Vultr. Integrate your Vultr instance with C1 for unified visibility and governance over user access." -description: "C1 provides identity governance for Vultr. Integrate your Vultr instance with C1 for unified visibility and governance over user access." +og:title: Set up a Vultr connector - C1.ai docs +og:description: "C1.ai provides identity governance for Vultr. Integrate your Vultr instance with C1.ai for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Vultr. Integrate your Vultr instance with C1.ai for unified visibility and governance over user access." sidebarTitle: Vultr --- @@ -41,18 +41,18 @@ Carefully copy and save the API key. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Vultr 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Vultr** and click **Add**. @@ -84,13 +84,13 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Vultr connector is now pulling access data into C1. +**Done.** Your Vultr connector is now pulling access data into C1.ai. **Follow these instructions to use the Vultr 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -100,7 +100,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -189,13 +189,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 C1.ai 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 Vultr connector to. Vultr data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Vultr connector to. Vultr data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Vultr connector is now pulling access data into C1. +**Done.** Your Vultr connector is now pulling access data into C1.ai. diff --git a/baton/whimsical.mdx b/baton/whimsical.mdx index 0c76c175..187f6544 100644 --- a/baton/whimsical.mdx +++ b/baton/whimsical.mdx @@ -1,8 +1,8 @@ --- title: Set up Whimsical connector -og:title: Set up Whimsical connector - C1 docs -og:description: Integrate your Whimsical 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 Whimsical. Integrate your Whimsical instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up Whimsical connector - C1.ai docs +og:description: Integrate your Whimsical instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance and just-in-time provisioning for Whimsical. Integrate your Whimsical instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: Whimsical --- @@ -51,17 +51,17 @@ See the [Whimsical SCIM documentation](https://help.whimsical.com/security/entra **To complete this task, you'll need:** -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Your Whimsical SCIM OAuth token generated 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Whimsical** and click **Add**. @@ -95,13 +95,13 @@ See the [Whimsical SCIM documentation](https://help.whimsical.com/security/entra -**Done.** Your Whimsical connector is now pulling access data into C1. +**Done.** Your Whimsical connector is now pulling access data into C1.ai. **Follow these instructions to use the Whimsical 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -111,7 +111,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -200,13 +200,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 C1.ai 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 whimsical connector to. whimsical data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the whimsical connector to. whimsical data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Whimsical connector is now pulling access data into C1. +**Done.** Your Whimsical connector is now pulling access data into C1.ai. diff --git a/baton/wiz-insights.mdx b/baton/wiz-insights.mdx index 6983798b..60d5a37e 100644 --- a/baton/wiz-insights.mdx +++ b/baton/wiz-insights.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Wiz Insights connector" og:title: "Set up a Wiz Insights connector" -description: "C1 provides identity governance and security posture visibility for Wiz. Integrate your Wiz instance with C1 to sync security insights related to user and service accounts, enabling identity-aware cloud security posture visibility." -og:description: "C1 provides identity governance and security posture visibility for Wiz. Integrate your Wiz instance with C1 to sync security insights related to user and service accounts, enabling identity-aware cloud security posture visibility." +description: "C1.ai provides identity governance and security posture visibility for Wiz. Integrate your Wiz instance with C1.ai to sync security insights related to user and service accounts, enabling identity-aware cloud security posture visibility." +og:description: "C1.ai provides identity governance and security posture visibility for Wiz. Integrate your Wiz instance with C1.ai to sync security insights related to user and service accounts, enabling identity-aware cloud security posture visibility." sidebarTitle: "Wiz Insights" --- -**There are TWO Wiz connectors.** The instructions below set up the Wiz Insights connector that syncs security issues from Wiz as [external insights](https://www.conductorone.com/docs/product/admin/external-insights), surfacing identity risk scores alongside access decisions in C1. +**There are TWO Wiz connectors.** The instructions below set up the Wiz Insights connector that syncs security issues from Wiz as [external insights](https://www.conductorone.com/docs/product/admin/external-insights), surfacing identity risk scores alongside access decisions in C1.ai. There is also a [Wiz IAM connector](/baton/wiz), which syncs users, roles, and projects from Wiz so that you can review and manage access. @@ -67,11 +67,11 @@ For more information, see [Wiz API documentation](https://docs.wiz.io/). - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -117,19 +117,19 @@ For more information, see [Wiz API documentation](https://docs.wiz.io/). - **Done.** Your Wiz Insights connector is now pulling security insights into C1. + **Done.** Your Wiz Insights connector is now pulling security insights into C1.ai. Follow these instructions to use the [Wiz Insights](https://github.com/conductorone/baton-wiz-insights) 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Step 1: Set up a new Wiz Insights connector - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -226,14 +226,14 @@ For more information, see [Wiz API documentation](https://docs.wiz.io/). - 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 C1.ai 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 Wiz Insights connector to. Wiz security insights should be found on the application page. + Check that the connector data uploaded correctly. In C1.ai, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the Wiz Insights connector to. Wiz security insights should be found on the application page. - **Done.** Your Wiz Insights connector is now pulling security insights into C1. + **Done.** Your Wiz Insights connector is now pulling security insights into C1.ai. diff --git a/baton/wiz-win.mdx b/baton/wiz-win.mdx index f39db7a7..9e5b28d7 100644 --- a/baton/wiz-win.mdx +++ b/baton/wiz-win.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Wiz connector" og:title: "Set up a Wiz connector" -description: "C1 provides identity governance for Wiz. Integrate your Wiz instance with C1 to run user access reviews (UARs) and gain visibility into cloud security access." -og:description: "C1 provides identity governance for Wiz. Integrate your Wiz instance with C1 to run user access reviews (UARs) and gain visibility into cloud security access." +description: "C1.ai provides identity governance for Wiz. Integrate your Wiz instance with C1.ai to run user access reviews (UARs) and gain visibility into cloud security access." +og:description: "C1.ai provides identity governance for Wiz. Integrate your Wiz instance with C1.ai to run user access reviews (UARs) and gain visibility into cloud security access." sidebarTitle: "Wiz" --- @@ -126,7 +126,7 @@ For more information, see [Wiz documentation on service accounts](https://docs.w Follow these instructions to use the [Wiz](https://github.com/ConductorOne/baton-wiz-win) 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 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 C1.ai UI for access reviews and access requests. ### Step 1: Set up a new Wiz connector @@ -229,7 +229,7 @@ For more information, see [Wiz documentation on service accounts](https://docs.w - 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 C1.ai connectors (if desired), then apply the secret config and deployment config files. diff --git a/baton/wiz.mdx b/baton/wiz.mdx index ec6e0625..e202b5d8 100644 --- a/baton/wiz.mdx +++ b/baton/wiz.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Wiz connector" og:title: "Set up a Wiz connector" -description: "C1 provides identity governance for Wiz. Integrate your Wiz instance with C1 to run user access reviews (UARs) and gain visibility into cloud security access." -og:description: "C1 provides identity governance for Wiz. Integrate your Wiz instance with C1 to run user access reviews (UARs) and gain visibility into cloud security access." +description: "C1.ai provides identity governance for Wiz. Integrate your Wiz instance with C1.ai to run user access reviews (UARs) and gain visibility into cloud security access." +og:description: "C1.ai provides identity governance for Wiz. Integrate your Wiz instance with C1.ai to run user access reviews (UARs) and gain visibility into cloud security access." sidebarTitle: "Wiz" --- @@ -15,7 +15,7 @@ We recommend closely monitoring workflows that use this connector and contacting **There are TWO Wiz connectors.** The instructions below set up the Wiz IAM connector, which syncs users, roles, and projects from Wiz so that you can review and manage access. -There is also a [Wiz Insights connector](https://www.conductorone.com/docs/baton/wiz-insights) that syncs security issues from Wiz as [external insights](https://www.conductorone.com/docs/product/admin/external-insights), surfacing identity risk scores alongside access decisions in C1. +There is also a [Wiz Insights connector](https://www.conductorone.com/docs/baton/wiz-insights) that syncs security issues from Wiz as [external insights](https://www.conductorone.com/docs/product/admin/external-insights), surfacing identity risk scores alongside access decisions in C1.ai. ## Capabilities @@ -67,11 +67,11 @@ For more information, see [Wiz documentation on service accounts](https://docs.w - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -120,19 +120,19 @@ For more information, see [Wiz documentation on service accounts](https://docs.w - **Done.** Your Wiz connector is now pulling access data into C1. + **Done.** Your Wiz connector is now pulling access data into C1.ai. Follow these instructions to use the [Wiz](https://github.com/conductorone/baton-wiz-win) 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Step 1: Set up a new Wiz connector - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -229,14 +229,14 @@ For more information, see [Wiz documentation on service accounts](https://docs.w - 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 C1.ai 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 Wiz connector to. Wiz data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the Wiz connector to. Wiz data should be found on the **Entitlements** and **Accounts** tabs. - **Done.** Your Wiz connector is now pulling access data into C1. + **Done.** Your Wiz connector is now pulling access data into C1.ai. diff --git a/baton/workable.mdx b/baton/workable.mdx index f158d65f..8aa9bcbb 100644 --- a/baton/workable.mdx +++ b/baton/workable.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Workable connector" og:title: "Set up a Workable connector" -description: "C1 provides identity governance for Workable. Integrate your Workable account with C1 for unified visibility and governance over member access." -og:description: "C1 provides identity governance for Workable. Integrate your Workable account with C1 for unified visibility and governance over member access." +description: "C1.ai provides identity governance for Workable. Integrate your Workable account with C1.ai for unified visibility and governance over member access." +og:description: "C1.ai provides identity governance for Workable. Integrate your Workable account with C1.ai for unified visibility and governance over member access." sidebarTitle: "Workable" --- -C1 provides identity governance for Workable. Integrate your Workable account -with C1 for unified visibility and governance over the members who can access +C1.ai provides identity governance for Workable. Integrate your Workable account +with C1.ai for unified visibility and governance over the members who can access your recruiting and HR data. ## Capabilities @@ -50,11 +50,11 @@ access token. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -96,7 +96,7 @@ access token. - **Done.** Your Workable connector is now pulling access data into C1. + **Done.** Your Workable connector is now pulling access data into C1.ai. @@ -120,6 +120,6 @@ access token. - **Done.** Your Workable connector is now pulling access data into C1. + **Done.** Your Workable connector is now pulling access data into C1.ai. diff --git a/baton/workato.mdx b/baton/workato.mdx index 8d1e3e4f..f52d8a7a 100644 --- a/baton/workato.mdx +++ b/baton/workato.mdx @@ -1,8 +1,8 @@ --- title: Set up a Workato connector -og:title: Set up a Workato connector - C1 docs -og:description: Integrate your Workato 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 Workato. Integrate your Workato instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a Workato connector - C1.ai docs +og:description: Integrate your Workato instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance and just-in-time provisioning for Workato. Integrate your Workato instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: Workato --- @@ -65,7 +65,7 @@ Each setup method requires you to pass in credentials generated in Workato. Gath In Workato, navigate to **Workspace admin** > **API clients** > **Client roles** > **Add client role**. -Give the new client role a name, such as "C1 integration role". +Give the new client role a name, such as "C1.ai integration role". Select the following endpoints: @@ -84,11 +84,11 @@ Select the following endpoints: | | Collaborator roles | List non-system roles§ | `GET /api/roles` | | | Environment roles | List environment roles† | `GET /api/environment_roles` | | | Environment roles | Get environment role†‡ | `GET /api/environment_roles/:id` | - *If you don’t want to use C1 to provision role assignments, you can skip **Update collaborator’s roles** and **Get environment role**. + *If you don’t want to use C1.ai to provision role assignments, you can skip **Update collaborator’s roles** and **Get environment role**. †**List environment roles** and **Get environment role** are only available after your workspace migrates to RBAC v2 — see [Migrating to RBAC v2](#migrating-to-rbac-v2) for the full cutover sequence. - ‡**Get environment role** is required only if you want C1 to provision environment role assignments. + ‡**Get environment role** is required only if you want C1.ai to provision environment role assignments. §**The Collaborator roles section** (including **List non-system roles**) only appears in the UI if your workspace uses the legacy roles model. If this section is not visible, your workspace has migrated to RBAC v2 — see [Migrating to RBAC v2](#migrating-to-rbac-v2), and use Workato's [Role migration API](https://docs.workato.com/workato-api/role-migration.html) to migrate your legacy custom roles to environment roles. @@ -104,19 +104,19 @@ Save the new role. Navigate to **Workspace admin** and select **API clients** > **Create API client**. -Give the new client a name, such as "C1 integration". +Give the new client a name, such as "C1.ai integration". Select the client role you set up above. -If your workspace has environments enabled, select the environment the API client (and by extension, C1) is allowed to access. +If your workspace has environments enabled, select the environment the API client (and by extension, C1.ai) is allowed to access. Select the projects the API client is allowed to access. -If needed, add allowed IP ranges that API requests using this token can originate from ([view C1's IP addresses](/baton/faq/)). +If needed, add allowed IP ranges that API requests using this token can originate from ([view C1.ai's IP addresses](/baton/faq/)). Click **Create client** @@ -145,18 +145,18 @@ You'll also need to specify the location of your Workato data center. Workato di To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Workato 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Workato** and click **Add**. @@ -198,13 +198,13 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Workato connector is now pulling access data into C1. +**Done.** Your Workato connector is now pulling access data into C1.ai. **Follow these instructions to use the Workato 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -216,7 +216,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -315,14 +315,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 C1.ai 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 Workato connector to. Workato data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Workato connector to. Workato data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Workato connector is now pulling access data into C1. +**Done.** Your Workato connector is now pulling access data into C1.ai. @@ -335,9 +335,9 @@ Workato is retiring legacy roles at the end of August 2026. Every workspace must **After your workspace migrates to RBAC v2**, complete this cutover in order: -1. In Workato, update your C1 API client's role with the permissions that only become available after migration: +1. In Workato, update your C1.ai API client's role with the permissions that only become available after migration: - **List environment roles** — required - - **Get environment role** — required only if C1 provisions environment role assignments + - **Get environment role** — required only if C1.ai provisions environment role assignments 2. In the connector configuration: - Enable **Disable custom roles sync**, since the legacy `/api/roles` endpoint no longer serves custom roles. - Confirm **Environment roles** sync is on (it is on by default — re-enable it now if you excluded it per the note above). diff --git a/baton/workday-wql.mdx b/baton/workday-wql.mdx index ab1103f4..6ae068b1 100644 --- a/baton/workday-wql.mdx +++ b/baton/workday-wql.mdx @@ -1,14 +1,14 @@ --- title: Set up a Workday Accounts connector -og:title: Set up a Workday Accounts 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 Accounts connector - C1.ai docs +og:description: Integrate your Workday instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance and just-in-time provisioning for Workday. Integrate your Workday instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: Workday Account --- ## Which Workday connector should I use? -C1 offers two Workday connectors: Workday and Workday Accounts. How you want to work with Workday in C1 will determine which one you should set up. +C1.ai offers two Workday connectors: Workday and Workday Accounts. How you want to work with Workday in C1.ai 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. @@ -66,7 +66,7 @@ Carefully copy and save the Workday REST API endpoint. 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". -In the modal that appears, give the new API client a name, such as "C1 integration". +In the modal that appears, give the new API client a name, such as "C1.ai integration". In the **Scopes** box, select **Custom Objects** and search for "System". Select **System** and click **OK**. The System scope is required to access the WQL API. @@ -111,7 +111,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 WQL integration security group". +Create a new security group. Give it a name, such as "C1.ai WQL integration security group". On the new group's **Domain Security Policy Permissions** tab, leave the **Select All** box checked. @@ -166,7 +166,7 @@ Select the security group you created and click **OK**. ### Optional: Look up security group types -If you want C1 to sync specific non-user-based security group types (such as `Role-Based Security Group (Constrained)` and `Integration System Security Group`), you'll need to gather the list of these types. +If you want C1.ai to sync specific non-user-based security group types (such as `Role-Based Security Group (Constrained)` and `Integration System Security Group`), you'll need to gather the list of these types. Non-user-based security group types are defined and configured in Workday, and their exact names vary based on how your Workday instance is configured. Remember that security group type names are cases-sensitive. @@ -177,18 +177,18 @@ Non-user-based security group types are defined and configured in Workday, and t To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Workday Accounts 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Workday Accounts** and click **Add**. @@ -238,23 +238,23 @@ To complete this task, you'll need: -**Done.** Your Workday Accounts connector is now pulling access data into C1. +**Done.** Your Workday Accounts connector is now pulling access data into C1.ai. **Follow these instructions to use the Workday Accounts 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources -[Contact C1's support team](mailto:support@c1.ai) to download the latest version of the connector. +[Contact C1.ai's support team](mailto:support@c1.ai) to download the latest version of the connector. ### Step 1: Set up a new Workday Accounts connector - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -368,15 +368,15 @@ 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 C1.ai 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 Accounts connector to. Workday Accounts data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Workday Accounts connector to. Workday Accounts data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Workday Accounts connector is now pulling access data into C1. +**Done.** Your Workday Accounts connector is now pulling access data into C1.ai. diff --git a/baton/workday.mdx b/baton/workday.mdx index 5b627593..b6a7acee 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: "C1 provides identity governance for Workday. Integrate your Workday instance with C1 for unified visibility and governance over user access." -description: "C1 provides identity governance for Workday. Integrate your Workday instance with C1 for unified visibility and governance over user access." +og:title: Set up a Workday connector - C1.ai docs +og:description: "C1.ai provides identity governance for Workday. Integrate your Workday instance with C1.ai for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Workday. Integrate your Workday instance with C1.ai for unified visibility and governance over user access." 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. +C1.ai offers two Workday connectors: Workday and Workday Accounts (WQL). How you want to work with Workday in C1.ai 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. @@ -59,7 +59,7 @@ To authenticate with Workday, you can use a Report-as-a-service (RaaS) **custom **Which authentication method should I use?** -The **Custom Report with Basic Auth** option is the most popular and is often preferred by Workday Admins and HR teams. RaaS allows fine-grained control over what data is sent to C1 and lets you transform attribute formats as needed. +The **Custom Report with Basic Auth** option is the most popular and is often preferred by Workday Admins and HR teams. RaaS allows fine-grained control over what data is sent to C1.ai and lets you transform attribute formats as needed. The **Custom Report with API Client** option is a good choice when your security policies require OAuth-based authentication, while still providing the same fine-grained data control as Basic Auth reports. The refresh token for this option must be generated using the credentials of the Workday user who owns the report. @@ -130,7 +130,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 C1.ai support if you need help figuring out which fields to include. 5. Create the custom report. @@ -175,7 +175,7 @@ A user with the permission to create a new API client in Workday must perform th 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 (report OAuth)". +Give the new API client a name, such as "C1.ai integration (report OAuth)". In the **Scopes** box, select **Tenant Non-Configurable**. Also search for "Staffing" and select **Staffing** and **Organizations and Roles**, then click **OK**. @@ -234,7 +234,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 "C1.ai integration". @@ -263,7 +263,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 "C1.ai integration security group". On the new group's **Domain Security Policy Permissions** tab, leave the **Select All** box checked. @@ -345,7 +345,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 "C1.ai 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. @@ -386,18 +386,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 C1.ai - 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Workday** and click **Add**. @@ -456,14 +456,14 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Workday connector is now pulling access data into C1. +**Done.** Your Workday connector is now pulling access data into C1.ai. **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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -473,7 +473,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -582,13 +582,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 C1.ai 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 C1.ai, 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. -**Done.** Your Workday connector is now pulling access data into C1. +**Done.** Your Workday connector is now pulling access data into C1.ai. ## Troubleshooting the Workday connector diff --git a/baton/wpengine.mdx b/baton/wpengine.mdx index 94035066..8e92b042 100644 --- a/baton/wpengine.mdx +++ b/baton/wpengine.mdx @@ -1,13 +1,13 @@ --- title: "Set up a WP Engine connector" og:title: "Set up a WP Engine connector" -description: "C1 provides identity governance for WP Engine. Integrate your WP Engine instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for WP Engine. Integrate your WP Engine instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for WP Engine. Integrate your WP Engine instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for WP Engine. Integrate your WP Engine instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "WP Engine" --- -C1 provides identity governance for WP Engine. Integrate your WP Engine -portal with C1 for unified visibility and governance over which users have +C1.ai provides identity governance for WP Engine. Integrate your WP Engine +portal with C1.ai for unified visibility and governance over which users have access to which WP Engine accounts. ## Capabilities @@ -51,11 +51,11 @@ connector uses HTTP Basic authentication with an API username and password. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -98,7 +98,7 @@ connector uses HTTP Basic authentication with an API username and password. - **Done.** Your WP Engine connector is now pulling access data into C1. + **Done.** Your WP Engine connector is now pulling access data into C1.ai. @@ -125,7 +125,7 @@ connector uses HTTP Basic authentication with an API username and password. - **Done.** Your WP Engine connector is now pulling access data into C1. + **Done.** Your WP Engine connector is now pulling access data into C1.ai. diff --git a/baton/wrike.mdx b/baton/wrike.mdx index c27ab10a..98635206 100644 --- a/baton/wrike.mdx +++ b/baton/wrike.mdx @@ -1,12 +1,12 @@ --- title: "Set up a Wrike connector" og:title: "Set up a Wrike connector" -description: "C1 provides identity governance for Wrike. Integrate your Wrike instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Wrike. Integrate your Wrike instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Wrike. Integrate your Wrike instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Wrike. Integrate your Wrike instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Wrike" --- -C1 provides identity governance for Wrike. Integrate your Wrike account with C1 +C1.ai provides identity governance for Wrike. Integrate your Wrike account with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -56,11 +56,11 @@ and grants read access to that whole account on behalf of the issuing user. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -102,7 +102,7 @@ and grants read access to that whole account on behalf of the issuing user. - **Done.** Your Wrike connector is now pulling access data into C1. + **Done.** Your Wrike connector is now pulling access data into C1.ai. @@ -126,6 +126,6 @@ and grants read access to that whole account on behalf of the issuing user. - **Done.** Your Wrike connector is now pulling access data into C1. + **Done.** Your Wrike connector is now pulling access data into C1.ai. diff --git a/baton/xero.mdx b/baton/xero.mdx index a171ebcb..842c2c61 100644 --- a/baton/xero.mdx +++ b/baton/xero.mdx @@ -1,8 +1,8 @@ --- title: Set up a Xero connector -og:title: Set up a Xero connector - C1 docs -og:description: "C1 provides identity governance for Xero. Integrate your Xero instance with C1 for unified visibility and governance over user access." -description: "C1 provides identity governance for Xero. Integrate your Xero instance with C1 for unified visibility and governance over user access." +og:title: Set up a Xero connector - C1.ai docs +og:description: "C1.ai provides identity governance for Xero. Integrate your Xero instance with C1.ai for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Xero. Integrate your Xero instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Xero" --- @@ -29,7 +29,7 @@ A user with the ability to create a Xero app for your organization must perform Log into `developer.xero.com` and click **New app**. -In the **Add a new app** form, give the app a name, such as "C1" and select **Web app**. +In the **Add a new app** form, give the app a name, such as "C1.ai" and select **Web app**. Enter `https://developer.xero.com` in the **Company or application URL** field. @@ -60,16 +60,16 @@ Carefully copy and save the **Client secret**. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Xero 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 C1.ai.** -*Due to limitations in Xero's regional availability for custom integration development, C1 cannot provide a cloud-hosted Xero connector.* +*Due to limitations in Xero's regional availability for custom integration development, C1.ai cannot provide a cloud-hosted Xero connector.* @@ -77,7 +77,7 @@ To complete this task, you'll need: **Follow these instructions to host and run the Xero connector 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -87,7 +87,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -177,13 +177,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 C1.ai 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 Xero connector to. Xero data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Xero connector to. Xero data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Xero connector is now pulling access data into C1. +**Done.** Your Xero connector is now pulling access data into C1.ai. diff --git a/baton/xmatters.mdx b/baton/xmatters.mdx index 01e128ff..e79b8087 100644 --- a/baton/xmatters.mdx +++ b/baton/xmatters.mdx @@ -1,13 +1,13 @@ --- title: "Set up an xMatters connector" og:title: "Set up an xMatters connector" -description: "C1 provides identity governance for xMatters. Integrate your xMatters instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for xMatters. Integrate your xMatters instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for xMatters. Integrate your xMatters instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for xMatters. Integrate your xMatters instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "xMatters" --- -C1 provides identity governance for xMatters. Integrate your xMatters -instance with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for xMatters. Integrate your xMatters +instance with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -79,11 +79,11 @@ groups it should read. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -130,7 +130,7 @@ groups it should read. - **Done.** Your xMatters connector is now pulling access data into C1. + **Done.** Your xMatters connector is now pulling access data into C1.ai. @@ -139,7 +139,7 @@ groups it should read. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -157,7 +157,7 @@ groups it should read. - Configure C1 credentials and xMatters credentials as environment + Configure C1.ai credentials and xMatters credentials as environment variables: ```bash @@ -181,6 +181,6 @@ groups it should read. - **Done.** Your xMatters connector is now pulling access data into C1. + **Done.** Your xMatters connector is now pulling access data into C1.ai. diff --git a/baton/xsoar.mdx b/baton/xsoar.mdx index e45000d3..aecfb604 100644 --- a/baton/xsoar.mdx +++ b/baton/xsoar.mdx @@ -1,8 +1,8 @@ --- title: Set up a Palo Alto Networks Cortex XSOAR connector -og:title: Set up a Palo Alto Networks Cortex XSOAR connector - C1 docs -og:description: "C1 provides identity governance for Cortex XSOAR. Integrate your Cortex XSOAR instance with C1 for unified visibility and governance over user access." -description: "C1 provides identity governance for Cortex XSOAR. Integrate your Cortex XSOAR instance with C1 for unified visibility and governance over user access." +og:title: Set up a Palo Alto Networks Cortex XSOAR connector - C1.ai docs +og:description: "C1.ai provides identity governance for Cortex XSOAR. Integrate your Cortex XSOAR instance with C1.ai for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Cortex XSOAR. Integrate your Cortex XSOAR instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Palo Alto Networks Cortex XSOAR" --- @@ -65,18 +65,18 @@ Copy the CURL Example URL. The example contains your FQDN, which forms part of y To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of XSOAR 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **XSOAR** and click **Add**. @@ -114,7 +114,7 @@ Click **Save**. **Follow these instructions to use the XSOAR 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -124,7 +124,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -215,14 +215,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 C1.ai 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 XSOAR connector to. XSOAR data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the XSOAR connector to. XSOAR data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your XSOAR connector is now pulling access data into C1. +**Done.** Your XSOAR connector is now pulling access data into C1.ai. diff --git a/baton/youtrack.mdx b/baton/youtrack.mdx index 814a8e51..61ac71c3 100644 --- a/baton/youtrack.mdx +++ b/baton/youtrack.mdx @@ -1,8 +1,8 @@ --- title: Set up a JetBrains YouTrack connector -og:title: Set up a JetBrains YouTrack connector - C1 docs -og:description: "C1 provides identity governance for JetBrains YouTrack. Integrate your JetBrains YouTrack instance with C1 for unified visibility and governance over user access." -description: "C1 provides identity governance for JetBrains YouTrack. Integrate your JetBrains YouTrack instance with C1 for unified visibility and governance over user access." +og:title: Set up a JetBrains YouTrack connector - C1.ai docs +og:description: "C1.ai provides identity governance for JetBrains YouTrack. Integrate your JetBrains YouTrack instance with C1.ai for unified visibility and governance over user access." +description: "C1.ai provides identity governance for JetBrains YouTrack. Integrate your JetBrains YouTrack instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "JetBrains YouTrack" --- @@ -45,18 +45,18 @@ This connector requires the following scopes: To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of YouTrack 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **YouTrack** and click **Add**. @@ -88,23 +88,23 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your YouTrack connector is now pulling access data into C1. +**Done.** Your YouTrack connector is now pulling access data into C1.ai. **Follow these instructions to use the YouTrack 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources -[Contact C1's support team](mailto:support@c1.ai) to download the latest version of the connector. +[Contact C1.ai's support team](mailto:support@c1.ai) to download the latest version of the connector. ### Step 1: Set up a new YouTrack connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -195,14 +195,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 C1.ai 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 YouTrack connector to. YouTrack data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the YouTrack connector to. YouTrack data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your YouTrack connector is now pulling access data into C1. +**Done.** Your YouTrack connector is now pulling access data into C1.ai. diff --git a/baton/zammad.mdx b/baton/zammad.mdx index 58d26e71..74170cd8 100644 --- a/baton/zammad.mdx +++ b/baton/zammad.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Zammad connector" og:title: "Set up a Zammad connector" -description: "C1 provides identity governance for Zammad. Integrate your Zammad instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Zammad. Integrate your Zammad instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Zammad. Integrate your Zammad instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Zammad. Integrate your Zammad instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "Zammad" --- -C1 provides identity governance for Zammad. Integrate your Zammad instance -with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Zammad. Integrate your Zammad instance +with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -65,11 +65,11 @@ not work with this connector. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -114,7 +114,7 @@ not work with this connector. - **Done.** Your Zammad connector is now pulling access data into C1. + **Done.** Your Zammad connector is now pulling access data into C1.ai. @@ -141,6 +141,6 @@ not work with this connector. - **Done.** Your Zammad connector is now pulling access data into C1. + **Done.** Your Zammad connector is now pulling access data into C1.ai. diff --git a/baton/zendesk.mdx b/baton/zendesk.mdx index 00fc6c79..633f9144 100644 --- a/baton/zendesk.mdx +++ b/baton/zendesk.mdx @@ -1,15 +1,15 @@ --- title: Set up a Zendesk connector -og:title: Set up a Zendesk connector - C1 docs -og:description: C1 provides identity governance for Zendesk. Integrate your Zendesk instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. -description: C1 provides identity governance for Zendesk. Integrate your Zendesk instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a Zendesk connector - C1.ai docs +og:description: C1.ai provides identity governance for Zendesk. Integrate your Zendesk instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. +description: C1.ai provides identity governance for Zendesk. Integrate your Zendesk instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: "Zendesk" --- **This is an updated and improved version of the Zendesk connector!** -If you're setting up Zendesk with C1 for the first time, you're in the right place. +If you're setting up Zendesk with C1.ai for the first time, you're in the right place. ## Capabilities @@ -33,7 +33,7 @@ The Zendesk connector supports [automatic account provisioning and deprovisionin ### 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 C1.ai 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 | |-------------|-------------------|-------------| @@ -42,7 +42,7 @@ Connector actions are custom capabilities that extend C1 automations with app-sp ### External ticketing -C1 can create and track Zendesk tickets as part of access request workflows (external ticket provisioning). To enable this capability, turn on **Enable external ticket provisioning** in the connector's settings, or pass `--ticketing` to a self-hosted connector. +C1.ai can create and track Zendesk tickets as part of access request workflows (external ticket provisioning). To enable this capability, turn on **Enable external ticket provisioning** in the connector's settings, or pass `--ticketing` to a self-hosted connector. - Each active Zendesk ticket form is exposed as a ticket schema containing that form's active custom fields, plus **Priority** and **Type** selectors. - On Zendesk plans without ticket forms support, a single default schema containing all active custom fields is used instead. @@ -107,18 +107,18 @@ Click **Save**. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Zendesk 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Zendesk v2** and click **Add**. @@ -150,7 +150,7 @@ In the **Email** field, enter the email address associated with your System Admi Paste the token into the **API Token** field. -**Optional.** Enter a comma-separated list of the organizations you want to sync in the **Organizations** field. If this field is left blank C1 will sync all available organizations. +**Optional.** Enter a comma-separated list of the organizations you want to sync in the **Organizations** field. If this field is left blank C1.ai will sync all available organizations. Click **Save**. @@ -160,13 +160,13 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Zendesk connector is now pulling access data into C1. +**Done.** Your Zendesk connector is now pulling access data into C1.ai. **Follow these instructions to use the Zendesk 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -176,7 +176,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -269,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 C1.ai 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 Zendesk connector to. Zendesk data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Zendesk connector to. Zendesk data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Zendesk connector is now pulling access data into C1. +**Done.** Your Zendesk connector is now pulling access data into C1.ai. \ No newline at end of file diff --git a/baton/zenduty.mdx b/baton/zenduty.mdx index 2124fbef..e9f74210 100644 --- a/baton/zenduty.mdx +++ b/baton/zenduty.mdx @@ -1,13 +1,13 @@ --- title: "Set up a Xurrent connector" og:title: "Set up a Xurrent connector" -description: "C1 provides identity governance for Xurrent (formerly Zenduty). Integrate your Xurrent account with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for Xurrent (formerly Zenduty). Integrate your Xurrent account with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Xurrent (formerly Zenduty). Integrate your Xurrent account with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for Xurrent (formerly Zenduty). Integrate your Xurrent account with C1.ai for unified visibility and governance over user access." sidebarTitle: "Xurrent" --- -C1 provides identity governance for Xurrent. Integrate your Xurrent -account with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for Xurrent. Integrate your Xurrent +account with C1.ai for unified visibility and governance over user access. Xurrent acquired Zenduty, and this connector is now branded **Xurrent**. If @@ -60,11 +60,11 @@ key. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -105,7 +105,7 @@ key. - **Done.** Your Xurrent connector is now pulling access data into C1. + **Done.** Your Xurrent connector is now pulling access data into C1.ai. @@ -129,6 +129,6 @@ key. - **Done.** Your Xurrent connector is now pulling access data into C1. + **Done.** Your Xurrent connector is now pulling access data into C1.ai. diff --git a/baton/ziphq.mdx b/baton/ziphq.mdx index a0052760..33046107 100644 --- a/baton/ziphq.mdx +++ b/baton/ziphq.mdx @@ -1,8 +1,8 @@ --- title: "Set up ZipHQ connector" -description: "C1 provides identity governance and just-in-time provisioning for ZipHQ. Integrate your ZipHQ instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +description: "C1.ai provides identity governance and just-in-time provisioning for ZipHQ. Integrate your ZipHQ instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." og:title: "Set up ZipHQ connector" -og:description: "C1 provides identity governance and just-in-time provisioning for ZipHQ. Integrate your ZipHQ instance with C1 to run user access reviews (UARs) and enable just-in-time access requests." +og:description: "C1.ai provides identity governance and just-in-time provisioning for ZipHQ. Integrate your ZipHQ instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests." sidebarTitle: "ZipHQ" --- @@ -67,17 +67,17 @@ Click the copy button to the right of the displayed token to copy it to your 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 C1.ai - Access to the set of ZipHQ 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 C1.ai.** - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **ZipHQ** and click **Add**. @@ -110,12 +110,12 @@ Click the copy button to the right of the displayed token to copy it to your cli -**Done.** Your ZipHQ connector is now pulling access data into C1. +**Done.** Your ZipHQ connector is now pulling access data into C1.ai. **Follow these instructions to use the ZipHQ 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -125,7 +125,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -218,14 +218,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 C1.ai 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 ZipHQ connector to. ZipHQ data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the ZipHQ connector to. ZipHQ data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your ZipHQ connector is now pulling access data into C1. +**Done.** Your ZipHQ connector is now pulling access data into C1.ai. diff --git a/baton/zitadel.mdx b/baton/zitadel.mdx index 7f0687f5..0482a774 100644 --- a/baton/zitadel.mdx +++ b/baton/zitadel.mdx @@ -1,13 +1,13 @@ --- title: "Set up a ZITADEL connector" og:title: "Set up a ZITADEL connector" -description: "C1 provides identity governance for ZITADEL. Integrate your ZITADEL instance with C1 for unified visibility and governance over user access." -og:description: "C1 provides identity governance for ZITADEL. Integrate your ZITADEL instance with C1 for unified visibility and governance over user access." +description: "C1.ai provides identity governance for ZITADEL. Integrate your ZITADEL instance with C1.ai for unified visibility and governance over user access." +og:description: "C1.ai provides identity governance for ZITADEL. Integrate your ZITADEL instance with C1.ai for unified visibility and governance over user access." sidebarTitle: "ZITADEL" --- -C1 provides identity governance for ZITADEL. Integrate your ZITADEL instance -with C1 for unified visibility and governance over user access. +C1.ai provides identity governance for ZITADEL. Integrate your ZITADEL instance +with C1.ai for unified visibility and governance over user access. ## Capabilities @@ -91,11 +91,11 @@ IAM read role only if you want the connector to auto-detect the organization. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -139,7 +139,7 @@ IAM read role only if you want the connector to auto-detect the organization. - **Done.** Your ZITADEL connector is now pulling access data into C1. + **Done.** Your ZITADEL connector is now pulling access data into C1.ai. @@ -164,6 +164,6 @@ IAM read role only if you want the connector to auto-detect the organization. - **Done.** Your ZITADEL connector is now pulling access data into C1. + **Done.** Your ZITADEL connector is now pulling access data into C1.ai. diff --git a/baton/zoho-people.mdx b/baton/zoho-people.mdx index 21c28762..951f327e 100644 --- a/baton/zoho-people.mdx +++ b/baton/zoho-people.mdx @@ -1,8 +1,8 @@ --- title: Set up a Zoho People connector -og:title: Set up a Zoho People connector - C1 docs -og:description: "C1 provides identity governance for Zoho People. Integrate your Zoho People instance with C1 for unified visibility and governance over user access." -description: "C1 provides identity governance for Zoho People. Integrate your Zoho People instance with C1 for unified visibility and governance over user access." +og:title: Set up a Zoho People connector - C1.ai docs +og:description: "C1.ai provides identity governance for Zoho People. Integrate your Zoho People instance with C1.ai for unified visibility and governance over user access." +description: "C1.ai provides identity governance for Zoho People. Integrate your Zoho People instance with C1.ai for unified visibility and governance over user access." sidebarTitle: Zoho People --- @@ -46,7 +46,7 @@ In the [Zoho API Console](https://api-console.zoho.com), click **Get Started**. On the **Self client** tile, click **Create Now**. -Give the client a name, such as "C1". +Give the client a name, such as "C1.ai". Click **Create** then click **OK**. A client ID and client secret are generated and shown on the **Client Secret** tab. @@ -94,18 +94,18 @@ Carefully copy and save the 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 C1.ai - Access to the set of Zoho People 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Zoho People** and click **Add**. @@ -143,13 +143,13 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Zoho People connector is now pulling access data into C1. +**Done.** Your Zoho People connector is now pulling access data into C1.ai. **Follow these instructions to use the Zoho People 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -159,7 +159,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -252,13 +252,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 C1.ai 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 Zoho People connector to. Zoho People data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Zoho People connector to. Zoho People data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Zoho People connector is now pulling access data into C1. +**Done.** Your Zoho People connector is now pulling access data into C1.ai. diff --git a/baton/zoom.mdx b/baton/zoom.mdx index 4ebaa3a1..e2613ffc 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 - C1.ai docs +og:description: Integrate your Zoom instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance for Zoom. Integrate your Zoom instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: Zoom --- @@ -28,7 +28,7 @@ This connector works with Zoom on the Pro, Business, Business Plus, or Enterpris Licenses are a derived resource type — Zoom exposes no `/licenses` endpoint, so license grants are emitted from the account sync using each user's Zoom license tier. If licenses are excluded from the connector's sync, accounts skip their grants pass entirely, since license grants are the only grants accounts emit. -Invites represent pending Zoom user invitations and are transient — they disappear once the invitee accepts. C1 syncs invites for visibility but skips sync anomaly detection on them, since their counts naturally fluctuate. +Invites represent pending Zoom user invitations and are transient — they disappear once the invitee accepts. C1.ai syncs invites for visibility but skips sync anomaly detection on them, since their counts naturally fluctuate. The Zoom connector supports [automatic account provisioning](/product/admin/account-provisioning). @@ -36,13 +36,13 @@ The Zoom connector supports account deprovisioning (user deletion). ### 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 C1.ai 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 | |-------------|-------------------|-------------| | `transfer_and_delete_user` | `user_id` (resource, required), `action` (string, required: `disassociate` or `delete`), `transfer_email` (string; requires at least one transfer option, and is required when one is set), `transfer_meeting` (bool), `transfer_webinar` (bool), `transfer_recording` (bool) | Reassigns a user's meetings, webinars, and cloud recordings to another Zoom user, then removes the user from the account | -To run this action, give the Zoom app the `user:delete:user:admin` scope. When you set `transfer_email`, C1 confirms that the recipient exists before removing the user, which requires `user:read:user:admin` — a scope the connector already needs to sync accounts. The transfer options do not require any additional scopes. +To run this action, give the Zoom app the `user:delete:user:admin` scope. When you set `transfer_email`, C1.ai confirms that the recipient exists before removing the user, which requires `user:read:user:admin` — a scope the connector already needs to sync accounts. The transfer options do not require any additional scopes. ## Gather Zoom credentials @@ -62,7 +62,7 @@ Configuring the connector requires you to pass in credentials generated in Zoom. 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 "C1.ai" 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. @@ -93,9 +93,9 @@ On the **Scopes** page, click **+ Add Scopes**. Give the app the following set o - role:read:list_members:admin - user:read:user:admin - user:read:list_users:admin -- `billing:read:plan_usage:admin` (optional — required only if you want C1 to surface purchased vs. consumed Licensed seat counts) +- `billing:read:plan_usage:admin` (optional — required only if you want C1.ai to surface purchased vs. consumed Licensed seat counts) -If you want to use C1 to provision and deprovision Zoom permissions, or to run the `transfer_and_delete_user` connector action, add these scopes as well: +If you want to use C1.ai to provision and deprovision Zoom permissions, or to run the `transfer_and_delete_user` connector action, add these scopes as well: - role:write:member:admin - role:delete:member:admin @@ -122,7 +122,7 @@ 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 C1.ai - Access to the set of Zoom credentials generated by following the instructions above @@ -130,11 +130,11 @@ To complete this task, you'll need: -**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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Zoom** and click **Add**. @@ -163,7 +163,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 C1. 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.ai. This is disabled by default. Click **Save**. @@ -172,13 +172,13 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Zoom connector is now pulling access data into C1. +**Done.** Your Zoom connector is now pulling access data into C1.ai. **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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -188,7 +188,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -286,17 +286,17 @@ spec: - Create a namespace in which to run C1 connectors (if desired), then apply + Create a namespace in which to run C1.ai connectors (if desired), then apply the secret config and deployment config files. - Check that the connector data uploaded correctly. In C1, click **Apps**. On + Check that the connector data uploaded correctly. In C1.ai, 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. -**Done.** Your Zoom connector is now pulling access data into C1. +**Done.** Your Zoom connector is now pulling access data into C1.ai. diff --git a/baton/zscaler-zidentity.mdx b/baton/zscaler-zidentity.mdx index a90f4a45..f282f8f3 100644 --- a/baton/zscaler-zidentity.mdx +++ b/baton/zscaler-zidentity.mdx @@ -1,8 +1,8 @@ --- title: "Set up Zscaler ZIdentity connector" -og:title: Set up Zscaler ZIdentity connector - C1 docs -og:description: Integrate your Zscaler ZIdentity 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 Zscaler ZIdentity. Integrate your Zscaler ZIdentity instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up Zscaler ZIdentity connector - C1.ai docs +og:description: Integrate your Zscaler ZIdentity instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance and just-in-time provisioning for Zscaler ZIdentity. Integrate your Zscaler ZIdentity instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: Zscaler ZIdentity --- @@ -11,7 +11,7 @@ sidebarTitle: Zscaler ZIdentity This means it's undergoing ongoing testing and development while we gather feedback, validate functionality, and improve stability. Beta connectors are generally stable, but they may have limited feature support, incomplete error handling, or occasional issues. -We recommend closely monitoring workflows that use this connector and contacting the C1 Support team with any issues or feedback. +We recommend closely monitoring workflows that use this connector and contacting the C1.ai Support team with any issues or feedback. ## Capabilities @@ -27,7 +27,7 @@ We recommend closely monitoring workflows that use this connector and contacting This connector does not support account deprovisioning. You must deprovision accounts directly in Zscaler ZIdentity. - When a new account is created by C1, the account's password will be sent to a [vault](/product/admin/vaults). + When a new account is created by C1.ai, the account's password will be sent to a [vault](/product/admin/vaults). ## Gather Zscaler ZIdentity configuration information @@ -46,18 +46,18 @@ See the Zscaler ZIdentity docs for information on how to acquire credentials: [V To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Zscaler ZIdentity 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Zscaler ZIdentity** and click **Add**. @@ -89,23 +89,23 @@ Click **Save**. The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing. -**Done.** Your Zscaler ZIdentity connector is now pulling access data into C1. +**Done.** Your Zscaler ZIdentity connector is now pulling access data into C1.ai. **Follow these instructions to use the Zscaler ZIdentity 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources -[Contact C1's support team](mailto:support@c1.ai) to download the latest version of the connector. +[Contact C1.ai's support team](mailto:support@c1.ai) to download the latest version of the connector. ### Step 1: Set up a new Zscaler ZIdentity connector -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -200,13 +200,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 C1.ai 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 zscaler-zidentity connector to. zscaler-zidentity data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the zscaler-zidentity connector to. zscaler-zidentity data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Zscaler ZIdentity connector is now pulling access data into C1. +**Done.** Your Zscaler ZIdentity connector is now pulling access data into C1.ai. diff --git a/baton/zulip.mdx b/baton/zulip.mdx index 44103714..7ca3ff36 100644 --- a/baton/zulip.mdx +++ b/baton/zulip.mdx @@ -1,15 +1,15 @@ --- title: "Set up a Zulip connector" og:title: "Set up a Zulip connector" -description: "C1 provides identity governance for Zulip. Integrate your Zulip organization with C1 for unified visibility and governance over who has access and what role they hold." -og:description: "C1 provides identity governance for Zulip. Integrate your Zulip organization with C1 for unified visibility and governance over who has access and what role they hold." +description: "C1.ai provides identity governance for Zulip. Integrate your Zulip organization with C1.ai for unified visibility and governance over who has access and what role they hold." +og:description: "C1.ai provides identity governance for Zulip. Integrate your Zulip organization with C1.ai for unified visibility and governance over who has access and what role they hold." sidebarTitle: "Zulip" --- {/* stargate: cf-zulip-fullimpl-20260605 */} -C1 provides identity governance for Zulip. Integrate your Zulip organization -with C1 for unified visibility and governance over who can sign in and what +C1.ai provides identity governance for Zulip. Integrate your Zulip organization +with C1.ai for unified visibility and governance over who can sign in and what organization role they hold. ## Capabilities @@ -64,11 +64,11 @@ key as a secret. - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -111,7 +111,7 @@ key as a secret. - **Done.** Your Zulip connector is now pulling access data into C1. + **Done.** Your Zulip connector is now pulling access data into C1.ai. @@ -136,6 +136,6 @@ key as a secret. - **Done.** Your Zulip connector is now pulling access data into C1. + **Done.** Your Zulip connector is now pulling access data into C1.ai. diff --git a/baton/zuora.mdx b/baton/zuora.mdx index c3f0fb8a..35cf9d2a 100644 --- a/baton/zuora.mdx +++ b/baton/zuora.mdx @@ -1,8 +1,8 @@ --- title: "Set up a Zuora connector" og:title: "Set up a Zuora connector" -description: "C1 provides identity governance and just-in-time provisioning for Zuora. Integrate your Zuora 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 Zuora. Integrate your Zuora instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +description: "C1.ai provides identity governance and just-in-time provisioning for Zuora. Integrate your Zuora instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." +og:description: "C1.ai provides identity governance and just-in-time provisioning for Zuora. Integrate your Zuora instance with C1.ai to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." sidebarTitle: "Zuora" --- @@ -30,13 +30,13 @@ The Zuora connector supports [automatic account provisioning](/product/admin/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 C1.ai 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 | | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------- | | `enable_user` | `user_id` (string, required) | Reactivates a Zuora OneID user by setting `active` to `true` | | `disable_user` | `user_id` (string, required) | Deactivates a Zuora OneID user by setting `active` to `false` | -| `update_user` | `user_id` (string, required); `user_profile` (JSON string, required) | Updates profile attributes from a JSON object (used by C1 push rules / automated profile sync) | +| `update_user` | `user_id` (string, required); `user_profile` (JSON string, required) | Updates profile attributes from a JSON object (used by C1.ai push rules / automated profile sync) | | `update_profile`| `user_id` (resource, required); `displayName`, `givenName`, `familyName`, `externalId`, `custom_attributes` (optional) | Updates a user's name, display name, federated ID, or non-reserved profile attributes | ## Understanding roles in Zuora @@ -70,7 +70,7 @@ Zuora OneID stores role membership on the SCIM user resource (`roles[]`), not as 4. Grant the client the **admin** scope. - The **admin** scope is used by C1 when automatically provisioning and deprovisioning access. **If you do not want C1 to perform these tasks, do not grant this scope.** + The **admin** scope is used by C1.ai when automatically provisioning and deprovisioning access. **If you do not want C1.ai to perform these tasks, do not grant this scope.** 5. Click **Create**. @@ -84,11 +84,11 @@ For more information, see [Zuora authentication](https://developer.zuora.com/res - 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 C1.ai. - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -135,14 +135,14 @@ For more information, see [Zuora authentication](https://developer.zuora.com/res - **Done.** Your Zuora connector is now pulling access data into C1. + **Done.** Your Zuora connector is now pulling access data into C1.ai. Follow these instructions to use the [Zuora](https://github.com/conductorone/baton-zuora) 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -154,7 +154,7 @@ For more information, see [Zuora authentication](https://developer.zuora.com/res - In C1, navigate to **Apps** > **Connectors** and click **Add connector**. + In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. @@ -253,15 +253,15 @@ For more information, see [Zuora authentication](https://developer.zuora.com/res - 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 C1.ai 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 Zuora connector to. Zuora data should be found on the **Entitlements** and **Accounts** tabs. + Check that the connector data uploaded correctly. In C1.ai, click **Applications**. On the **Managed apps** tab, locate and click the name of the application you added the Zuora connector to. Zuora data should be found on the **Entitlements** and **Accounts** tabs. - **Done.** Your Zuora connector is now pulling access data into C1. + **Done.** Your Zuora connector is now pulling access data into C1.ai. diff --git a/baton/zuper.mdx b/baton/zuper.mdx index 4c26878f..f59f0cfe 100644 --- a/baton/zuper.mdx +++ b/baton/zuper.mdx @@ -1,8 +1,8 @@ --- title: Set up a Zuper connector -og:title: Set up a Zuper connector - C1 docs -og:description: Integrate your Zuper 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 Zuper. Integrate your Zuper instance with C1 to run user access reviews (UARs) and enable just-in-time access requests. +og:title: Set up a Zuper connector - C1.ai docs +og:description: Integrate your Zuper instance with C1.ai to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access. +description: C1.ai provides identity governance and just-in-time provisioning for Zuper. Integrate your Zuper instance with C1.ai to run user access reviews (UARs) and enable just-in-time access requests. sidebarTitle: Zuper --- @@ -17,7 +17,7 @@ sidebarTitle: Zuper The Zuper connector supports [automatic account provisioning](/product/admin/account-provisioning). -When a new account is created by C1, the account's password will be sent to a [vault](/product/admin/vaults). +When a new account is created by C1.ai, the account's password will be sent to a [vault](/product/admin/vaults). This connector does not support account deprovisioning. You must deprovision accounts directly in Zuper. @@ -38,7 +38,7 @@ Each setup method requires you to pass in credentials generated in Zuper. Gather Click **New API Key**. - Enter a name for your key, such as "C1", and click **Generate**. + Enter a name for your key, such as "C1.ai", and click **Generate**. Carefully copy and save the API key. @@ -80,18 +80,18 @@ The `dc_api_url` in the response is your Zuper account's BASE API URL. To complete this task, you'll need: -- The **Connector Administrator** or **Super Administrator** role in C1 +- The **Connector Administrator** or **Super Administrator** role in C1.ai - Access to the set of Zuper 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 C1.ai.** -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Zuper** and click **Add**. @@ -127,12 +127,12 @@ The connector's label changes to **Syncing**, followed by **Connected**. You can -**Done.** Your Zuper connector is now pulling access data into C1. +**Done.** Your Zuper connector is now pulling access data into C1.ai. **Follow these instructions to use the Zuper 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 C1.ai, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1.ai UI for access reviews and access requests. ### Resources @@ -142,7 +142,7 @@ When running in service mode on Kubernetes, a self-hosted connector maintains an -In C1, navigate to **Apps** > **Connectors** and click **Add connector**. +In C1.ai, navigate to **Apps** > **Connectors** and click **Add connector**. Search for **Baton** and click **Add**. @@ -236,15 +236,15 @@ 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 C1.ai 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 Zuper connector to. Zuper data should be found on the **Entitlements** and **Accounts** tabs. +Check that the connector data uploaded correctly. In C1.ai, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Zuper connector to. Zuper data should be found on the **Entitlements** and **Accounts** tabs. -**Done.** Your Zuper connector is now pulling access data into C1. +**Done.** Your Zuper connector is now pulling access data into C1.ai.