> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/nightfall_settings/directory_sync/okta.md).
# Add Okta to Nightfall
Learn how to sync your Okta data to Nightfall.
This document explains the process of adding your Okta tenant to Nightfall to enable Directory Sync. Once you add Okta to Nightfall, you can sync users and user groups data from your Okta account to Nightfall. To get an overview of the Directory Sync feature in Nightfall, you can read [this article](/nightfall_settings/directory_sync.md) and then proceed with this document.
In this document you are basically authorizing the Nightfall application in Okta. The authorization process involves two steps. In the first step, you authorize the Nightfall app in the Okta console. This process generates an Okta domain, client ID and client secret. You must copy these values. In the second step, you must paste these values in the Nightfall console to complete the process.
## Prerequisites
* You must have Super Administrator access to your Okta account. Okta requires this role to add API service integrations.
Nightfall's Okta access is read only. For the scopes it requests and why, see [SaaS App Permissions Reference](/nightfall_integrations/saas-app-permissions-reference.md).
## Integrating Nightfall in Okta
1. Log in to your Okta account with admin credentials and navigate to the admin console.
2. In the left pane, expand **Applications** and select **API Service Integrations**.
3. Click **Add Integration**.
4. Select the **Nightfall AI** integration.
5. Click **Install & Authorize**.
6. The client secret is generated. Click **Copy to clipboard** and store this secret securely. You cannot view this secret again.
7. Click **Done**.
7. Copy the values in the **Okta Domain** and **Client ID** fields.
## Configuring Okta in Nightfall
1. Log in to your Nightfall console.
2. In the left pane, click the **Settings** menu.
3. Click the **Directory Sync** tab.
4. Click **Add directory**.
{% hint style="info" %}
If you have already created IdP with Google Workspace or Microsoft Entra, you can view the list of IdP(s). In this case, you must click the **+ Add Directory** button.
{% endhint %}
5. Click **Set up** on the Okta widget.
6. Paste the **Okta Domain**, **Client ID,** and **Client Secret** values, obtained in the previous section.
7. Click **Connect** (This button is activated only after you enter the values as mentioned in the previous step).
6. A dialogue box with successful connection message is displayed. Click **Finish** to complete the process.
You can view the connection details as shown in the following image. Click **+ Add directory** to authorize the Nightfall app on additional Okta domains.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.nightfall.ai/nightfall_settings/directory_sync/okta.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
