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

# Connect Okta

Install the Siit API Service from the Okta marketplace and add its client ID and secret in Siit to run Okta actions like suspend user, reset MFA or update groups from requests

**Shortcuts capability:** Siit empowers your IT team with shortcuts, enabling them to trigger Okta actions such as adding users to groups, clearing sessions, or resetting multifactor authentication directly from the request conversation.

### Perform tasks such as:

* Activate user
* Suspend user
* Reset user password
* Expire password
* Reset user MFA
* Update user groups

### Install Siit API Service from your Okta Admin Console:

1. **Open the integration page on Okta Marketplace:** Visit <https://www.okta.com/integrations/siit-api-service/>
2. Click **Add Integration**.
3. **Log in to Okta Admin (if prompted):** Enter your admin credentials to continue.
4. Click **Install and Authorize** to complete the setup.
5. **Save your credentials:** After installation, **copy and securely store** the generated
6. **Client ID**
7. **Client Secret**
8. **Okta Domain**\*\*\
   \*\*

### Setting Up Okta Actions Integration with Siit:

1. **Navigate to the Settings Page:** In Siit, navigate to Settings → Workspace → Integration Library.
2. **Select Okta Actions:** Click "Okta Actions" to initiate the setup.

<figure><img src="https://2274035325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlWFhpq2ia6gdHet0opKx%2Fuploads%2Fgit-blob-15c3005af3ee2e952a73be66aac77e437dc80a33%2FCleanShot-2026-04-10-at-08-50-41-png.png?alt=media" alt=""><figcaption></figcaption></figure>

### The “Connect Okta” Window

The setup window allows you to securely link your Okta environment to Siit.\
You’ll need to provide the following information:

* **Domain:**\
  Your Okta domain (e.g. `testing.okta.com`).\
  If your Okta URL is `https://testing.okta.com`, simply enter `testing.okta.com`.
* **Client ID:**\
  The Client ID generated from your Siit API Service application in Okta.
* **Client Secret:**\
  The Client Secret generated from your Siit API Service application in Okta.
* **Roles for which Okta actions are enabled:**\
  You can restrict access to Okta actions by selecting which teams or roles in Siit are allowed to trigger them.

<figure><img src="https://2274035325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlWFhpq2ia6gdHet0opKx%2Fuploads%2Fgit-blob-ddd0203ced8df82172dea0b3cc876706bfc6f026%2FCleanShot-2025-10-09-at-13-52-14-2x-png.png?alt=media" alt=""><figcaption></figcaption></figure>

### Selecting Scopes for Okta Actions

Siit now allows you to **select which Okta scopes (permissions)** are enabled when connecting your Okta account. This gives you more control and flexibility over which actions Siit can perform on behalf of your IT team.

When configuring your Okta connection, you’ll see a section called **“Scopes for which Okta actions are enabled.”**\
From there, you can choose which permissions to include based on your organization’s security policies and needs.

**Available Scopes:**

* `okta.users.manage` – Manage Okta users (create, update, activate, deactivate).
* `okta.users.read` – Read user information.

  > ⚠️ **Mandatory:** This scope is required if you want Siit to display and trigger actions for individual users.
* `okta.groups.manage` – Manage group memberships and group details.
* `okta.apps.manage` – Manage Okta applications.
* `okta.sessions.manage` – Manage user sessions (clear or terminate sessions).
* `okta.eventHooks.manage` – Manage event hooks for Okta integrations.

These scopes define which Okta actions are available directly from Siit when handling IT requests.


---

# 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://docs.siit.io/guides/integrations/integrations-iam/okta-actions-integration.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.