> For the complete documentation index, see [llms.txt](https://www.cakewalk.security/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.cakewalk.security/docs/platform-overview/connections-and-integrations/identity-sources/okta.md).

# Okta

Connect Okta to Cakewalk as an identity source: the admin role you need, your Okta domain and where to create the API token.

Okta connects to Cakewalk with your Okta domain and an API token you create in Okta. The shared flow in [Connecting an HRIS](/docs/platform-overview/connections-and-integrations/connecting-an-hris.md) covers what syncs and what happens after you save; this page covers the Okta side.

### ✅ Before You Start

* You need a user who is an Administrator in your organization's Okta account to complete the setup.
* To check: log in to Okta. If you cannot see the **Admin** menu in the top right, you are not an Administrator.

### 🛠 Connect

1. In Cakewalk, go to **Settings → Data Sources → Users** and select Okta.
2. In the top right corner of your company's Okta home page, click **Admin**.
3. Click the dropdown arrow in the top right where your email appears, hover over `your-company.okta.com` to copy the value and paste it into the connection flow.
4. In the left menu, navigate to **Security > API**.
5. Under **Tokens**, press **Create token** and enter a name for your token.
6. Copy the **Token Value** and paste it into the connection flow.

The first sync starts immediately. Sync details and cadence: [Connecting an HRIS](/docs/platform-overview/connections-and-integrations/connecting-an-hris.md).

### 📚 Related

* [HRIS and IdP](/docs/platform-overview/connections-and-integrations/hris-and-idp.md)
* [Connecting an HRIS](/docs/platform-overview/connections-and-integrations/connecting-an-hris.md)


---

# 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://www.cakewalk.security/docs/platform-overview/connections-and-integrations/identity-sources/okta.md?ask=<question>&goal=<user_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.