---
title: "Okta"
slug: "okta"
updated: 2025-07-13T14:56:24Z
published: 2025-07-13T14:56:24Z
canonical: "help.unleash.so/okta"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.unleash.so/llms.txt
> Use this file to discover all available pages before exploring further.

# Okta

## Connection

The integration with Okta utilizes an API Key for connection.

To set up credentials, you need to create a dedicated application for API Services within your Okta tenant.

## Step 1 - Creating an App

- In the `Applications` section of your Okta admin console, click `Create App Integration` and select `API Services` app from the pop up that follows.
- Give your app a name.

![](https://cdn.document360.io/9c439416-8f37-43ae-8ba7-d5c31de26a65/Images/Documentation/01 (3).png)

![](https://cdn.document360.io/9c439416-8f37-43ae-8ba7-d5c31de26a65/Images/Documentation/02 (5).png)

![](https://cdn.document360.io/9c439416-8f37-43ae-8ba7-d5c31de26a65/Images/Documentation/Untitled (17).png)

## Step 2 - Config Scopes

Now that the integration is created, go to the `OKTA API Scopes` tab and grant access to the following scopes:

- `okta.users.read`
- `okta.groups.read`
- `okta.userTypes.read`

![](https://cdn.document360.io/9c439416-8f37-43ae-8ba7-d5c31de26a65/Images/Documentation/04 (3).png)

## Step 3 - Config Credentials

- Go to the `General` tab and edit the `Client Credentials` section.

![](https://cdn.document360.io/9c439416-8f37-43ae-8ba7-d5c31de26a65/Images/Documentation/05 (3).png)

- Change the Client authentication type to Public key/Private key .

![](https://cdn.document360.io/9c439416-8f37-43ae-8ba7-d5c31de26a65/Images/Documentation/06 (3).png)

- Click Add key to generate a new key.

![](https://cdn.document360.io/9c439416-8f37-43ae-8ba7-d5c31de26a65/Images/Documentation/07 (3).png)

- Copy the private key and save the new key pair.

![](https://cdn.document360.io/9c439416-8f37-43ae-8ba7-d5c31de26a65/Images/Documentation/08 (2).png)

- Disable DPoP (Demonstrating Proof of Possession) by unchecking the box in the General Settings section

![](https://cdn.document360.io/9c439416-8f37-43ae-8ba7-d5c31de26a65/Images/Documentation/image(3).png)

Finally, paste the new Private Key and Client ID values in the connection screen in your Unleash workspace.

![](https://cdn.document360.io/9c439416-8f37-43ae-8ba7-d5c31de26a65/Images/Documentation/09 (1).png)

## Step 4 - Assign Admin Role

So that the granted scopes will be effective you will need to assign your app a read-only admin role.

You can do that by navigating the *Admin roles* tab and assigning a `Read-only Administrator` role like the following screenshot:

![](https://cdn.document360.io/9c439416-8f37-43ae-8ba7-d5c31de26a65/Images/Documentation/Untitled (18).png)

### Scopes

The integration necessitates the following scopes:

```plaintext
okta.groups.read
okta.userTypes.read
okta.users.read
```

## Supported Resources

The integration currently supports the following resource:

- Users

## Sync

The integration does not support incremental updates and hence sync is scheduled for every 6 hours.

## API Calls

The table below details the primary endpoints utilized by the integration:

| Endpoint | Docs | Purpose |
| --- | --- | --- |
| /api/v1/users | [https://developer.okta.com/docs/reference/api/users/#list-users](https://developer.okta.com/docs/reference/api/users/#list-users) | List users in the tenant |

## HRIS

The Okta integration can be configured as an HRIS (Human Resources Information System) to activate the People view feature.

For more information:

- [HRIS](https://help.unleash.so/docs/search-settings#hris)
- [People](/v1/docs/people)

****Example Questions****

- Who is the R&D lead of the ABC project?
- Who is the finance approver for internal audit?
- Who manages the sales enablement team in the company?
- What is expected from a senior software engineer according to the career framework?
- Who can provision access to Google Analytics?