# Sign-in codes for CircleCI and SailPoint

[Read this guide on KeySigner](https://keysigner.io/integrations/guides/set-up-circleci-and-sailpoint-sign-in-codes/)

Save a test account’s sign-in code in KeySigner, confirm it in CircleCI or SailPoint, and try the same account in a fresh browser.

## Before you start

**KeySigner on iPhone or Mac with Sign-in codes**

- Use a direct CircleCI email and password test account. Save CircleCI’s one-time recovery code separately.
- Use a test account on a SailPoint tenant configured for authenticator codes. Confirm how you can recover access before enrolling.

## Data and access

- **Shared or checked**. CircleCI or SailPoint checks the code you enter for the selected account in a fresh browser.
- **Check separately**. CircleCI jobs and API tokens, or SailPoint provisioning and app assignments, follow their own controls.

## 1. Open the setup QR code

Use a test account you control and confirm you have an independent recovery route. Keep the original browser session open while you enroll.

**Check.** The provider shows a setup QR code for the intended account.

### Find your provider’s setup screen

- **[CircleCI](https://circleci.com/docs/guides/permissions-authentication/mfa/)**. Use a direct CircleCI email and password account. In User Settings, open Password & authentication and choose Add authenticator app. Confirm your password to view the QR code. A GitHub or Bitbucket sign-in uses that provider’s security settings.
- **[SailPoint](https://documentation.sailpoint.com/saas/user-help/accounts/mfa.html)**. Use a test account on a SailPoint tenant configured for authenticator codes. At the enrollment prompt, display the setup QR code. If the prompt routes through another provider, follow that provider’s setup instructions.

## 2. Add the account in KeySigner

Open Accounts and choose Add (+), then Sign-in codes and backup. Unlock Sign-in codes and choose Add account. Scan the QR code and check the account label before saving. Keep the QR code and setup key private.

![The KeySigner for Mac setup screen with options to scan a QR code, pick an image, or enter a setup link.](https://keysigner.io/integrations/guides/set-up-a-time-based-sign-in-code/keysigner-add-account.png)

The KeySigner setup screen on Mac. Scan the code from your test account.

**Check.** The KeySigner entry identifies the intended provider and account.

## 3. Confirm your first code

Choose Show code in KeySigner and complete the required approvals. Enter the current code in the provider’s setup form. CircleCI displays a one-time recovery code when you finish. Save it somewhere you can reach separately from KeySigner. For SailPoint, confirm who can restore access to the test account if you lose your authenticator.

**Check.** CircleCI shows that the authenticator app is enabled, or SailPoint accepts the code when you choose Verify.

## 4. Try signing in again

In a private browser window, sign in as the same test user and enter a fresh KeySigner code when prompted. Keep the original session open until the test passes.

**Check.** The provider prompts for and accepts a new code for the same account in your private browser.

## Check your result

Record which provider asked for the code, which test account signed in, and where you can recover access. Test CircleCI pipeline permissions and SailPoint application assignments separately.

### What we tested

**Tested on November 18, 2026.** KeySigner imported separately generated test QR codes and produced codes that matched an independent verifier. The CircleCI and SailPoint enrollment steps follow their published instructions. Verify each hosted account with a fresh browser sign-in.

[How to verify your setup](https://keysigner.io/integrations/verify-a-setup/)

## If you get stuck

### There is no code prompt, or the provider rejects the code

Check that you opened a private browser and selected the same account. If sign-in opens another provider, check the settings there. For a rejected code, check your device clock and wait for a new code if the current one is about to expire. For a SailPoint reset, confirm that you can recover access before following the provider’s reset instructions, which sign you out.

## Tools in this guide

- [CircleCI](https://keysigner.io/integrations/circleci/)
  - [Restrict access to contexts with deployment credentials](https://circleci.com/docs/guides/security/contexts/)
  - [Setup requirements](https://keysigner.io/integrations/setup-requirements/#circleci)
- [SailPoint](https://keysigner.io/integrations/sailpoint/)
  - [Configure access request approvals](https://documentation.sailpoint.com/saas/help/requests/config_ap_roles.html)
  - [Setup requirements](https://keysigner.io/integrations/setup-requirements/#sailpoint)

## Setup instructions

- [Check a CircleCI release approval](https://keysigner.io/integrations/guides/test-a-release-approval-gate/)
- [Verify SailPoint application assignments](https://keysigner.io/integrations/guides/verify-application-assignments/)
- [Set up a time-based sign-in code in KeySigner](https://keysigner.io/integrations/guides/set-up-a-time-based-sign-in-code/)

[More guides for this task](https://keysigner.io/integrations/tasks/set-up-sign-in-codes/)
