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

# Okta

1. Create a new Okta admin (e.g. "Material Admin") and assign the required roles based on selected capabilities.
2. **Groups** - Group, Help Desk, App, or Read Only Admin
3. **MFA Status** - App or Read Only Admin
4. **End-User Verification** - Help Desk Admin
5. Log in to your Okta organization as the new admin.
6. Select **API** from the **Security** menu, and then select **Tokens**.
7. Click **Create Token**.
8. Name your token (e.g. "Material") and click **Create Token**. Make note of your API token, as you only see it one time.
9. In Material, enter your full Okta Org URL (e.g. <https://acme.okta.com>) and the token you created.
10. Next, in Okta go to **Security** > **Networks** and click **Add Zone** to create a new **IP Zone**.
11. Name the zone and copy the **Outbound IPs** from Material into the **Trusted Proxy IPs** field. This lets Okta display the correct geographic location during identity verification.
12. Press **Save** in Okta to save the IP Zone.
13. Enable the **Integration Enabled** switch above.
14. Click **Save**.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.material.security/integrations/integration-fundamentals/identity-integrations/okta.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.