# Pilot an Okta access policy without locking out admins

[Read this guide on KeySigner](https://keysigner.io/integrations/guides/pilot-an-okta-access-policy/)

Run the same test with a pilot user and a backup administrator so you know what your policy covers and how you can roll it back.

## Before you start

- Use a disposable app in Okta Identity Engine, a pilot user and a second administrator who can restore the prior policy.
- Set up the authenticators the pilot will use and check the global session policy before assigning an app policy.

## Data and access

- **Shared or checked**. Okta checks the test identity and evaluates whether the rule applies before it grants access to the selected app.
- **Check separately**. Backup administrators, other groups, and other apps may match different rules. Check each path you depend on.

## Who does what

- **Setup administrator**. Selects the test app, assigns the test group and chooses the app policy and authenticators.
- **Pilot user**. Opens the test app from a fresh session and records which check Okta requires.
- **Backup administrator**. Keeps independent admin access and restores the prior policy if the pilot user loses access.

## 1. Choose a test group

Check which verification methods your edition allows for this app. Record the policy and the exact action you will test.

**Check.** The test account is in the pilot group, and the target app shows the policy and rule you expect it to use.

## 2. Test the expected paths

Exercise an allowed action and check what happens when a required approval or credential is missing. Use a disposable app and keep independent administrator access.

**Check.** The allowed action reaches the test app. The attempt that omits a required step stops at the provider prompt or denial.

## 3. Practice a rollback

Have the backup administrator restore the previous policy. Confirm that the pilot user can regain access and that the administrator's access is unaffected.

**Check.** The app shows the previous policy again, and a fresh session reproduces the pilot account’s original behavior.

## Check your result

A test proves coverage for the exact pilot account and policy you exercised. Repeat it for the administrator or application paths you intend to rely on.

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

## If you get stuck

### The pilot user never sees the expected check

Inspect the policy’s app assignment and rule order. Check the pilot user’s groups and review the sign-in event in the System Log before repeating the test in a fresh session.

## Tools in this guide

- [Okta](https://keysigner.io/integrations/okta/)
  - [Review passkey access controls](https://help.okta.com/oie/en-us/content/Topics/identity-engine/authenticators/passkeys-access-controls.htm)
  - [Review verification rules for the Okta Admin Console](https://help.okta.com/oie/en-us/Content/topics/security/mfa/mfa-enable-admins.htm)
  - [Check Google Authenticator enrollment](https://help.okta.com/oie/en-us/content/Topics/identity-engine/authenticators/google-authenticator.htm)

## Setup instructions

- [Create an Okta app policy](https://help.okta.com/oie/en-us/content/topics/identity-engine/policies/create-auth-policy.htm)
- [Check which authenticator methods a provider allows](https://keysigner.io/integrations/guides/check-authenticator-app-policies/)
- [Use the integration rollout checklist](https://keysigner.io/integrations/rollout-checklist/)

[More guides for this task](https://keysigner.io/integrations/tasks/test-account-access/)
