> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to Okta

The Okta connector lets your AI agent act in each user's Okta account. Each user connects their own Okta API key once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 23 tools.

**Authentication:** API Key
**Categories:** Developer Tools, Productivity
**Tools:** 23: 13 read, 8 write, 2 destructive
**Users sign in with:** API key
**Built by:** Scalekit connector
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=OKTA)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the Okta connection

   In **AgentKit > Connections**, create an Okta connection. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

4. ### Authorize a user and make your first call

   **Node.js** (`quickstart.mts`)

   ```typescript
   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   import { createInterface } from 'node:readline/promises'

   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENVIRONMENT_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions

   const connector = 'okta'
   const identifier = 'user_123'

   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize Okta:', link)
   const rl = createInterface({ input: process.stdin, output: process.stdout })
   await rl.question('Press Enter after authorizing...')
   rl.close()

   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'okta_apps_list',
     toolInput: {},
   })
   console.log(result)
   ```

   ```bash
   npx tsx quickstart.mts
   ```

   **Python** (`quickstart.py`)

   ```python
   import os
   from scalekit import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()

   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions

   connection_name = "okta"
   identifier = "user_123"

   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize Okta:", link_response.link)
   input("Press Enter after authorizing...")

   # Make your first call
   result = actions.execute_tool(
       tool_input={},
       tool_name="okta_apps_list",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)
   ```

   ```bash
   python quickstart.py
   ```

   Each user opens the link once and enters their Okta credentials there. See [Authorize a user](/agentkit/tools/authorize/) for the full flow and statuses.

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'okta_app_get',
  toolInput: {
    app_id: '<app_id>',
  },
  connector: 'okta',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="okta_app_get",
    tool_input={
        "app_id": "<app_id>",
    },
    connection_name="okta",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `okta_app_get`

Get App · Read-only

Get one Okta application by ID.
Returns id, name, label, status, signOnMode, features, settings and credentials settings.
Use okta_app_get when you know the app ID. Use okta_apps_list to find it.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `app_id` (`string`, required): Okta application ID (starts with 0oa). Get it from okta_apps_list. Example: 0oa1a2b3c4d5e6f7g8h9

Example input: `{"app_id":"<app_id>"}`

### `okta_app_groups_list`

List App Group Assignments · Read-only

List the groups assigned to an Okta application.
Returns assignments with id (the group ID), priority and profile.
Use okta_app_groups_list for one app's groups. Use okta_app_users_list for its users.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `app_id` (`string`, required): Okta application ID (starts with 0oa). Get it from okta_apps_list. Example: 0oa1a2b3c4d5e6f7g8h9
- `after` (`string`, optional): Pagination cursor for the next page. Okta puts it in the after parameter of the rel="next" Link response header; for app group assignments Okta uses the id of the last item on the previous page. Leave empty for the first page. Example: 00g1a2b3c4d5e6f7g8h9
- `limit` (`integer`, optional): Maximum number of results to return in this page. Okta default is 20. Maximum is 200. Example: 20
- `q` (`string`, optional): Finds assigned groups whose name starts with this text. Example: Eng

Example input: `{"app_id":"<app_id>"}`

### `okta_app_users_list`

List App Users · Read-only

List the users assigned to an Okta application.
Returns app user objects with id (the Okta user ID), scope (USER or GROUP), status, credentials.userName and the app-specific profile.
Use okta_app_users_list for one app's users. Use okta_app_groups_list for its group assignments.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `app_id` (`string`, required): Okta application ID (starts with 0oa). Get it from okta_apps_list. Example: 0oa1a2b3c4d5e6f7g8h9
- `after` (`string`, optional): Pagination cursor for the next page. Okta puts it in the after parameter of the rel="next" Link response header; for app users Okta uses the id of the last item on the previous page. Leave empty for the first page. Example: 00u1a2b3c4d5e6f7g8h9
- `limit` (`integer`, optional): Maximum number of results to return in this page. Okta default is 50. Maximum is 500. Example: 50
- `q` (`string`, optional): Finds assigned users whose userName, firstName, lastName or email starts with this text. Example: jane

Example input: `{"app_id":"<app_id>"}`

### `okta_apps_list`

List Apps · Read-only

List applications in the Okta org, optionally by name or label prefix or a filter expression.
Returns app objects with id, name, label, status, signOnMode and created.
Use okta_apps_list to find apps or their IDs. Use okta_app_get for one app by ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `after` (`string`, optional): Pagination cursor for the next page. Okta puts it in the after parameter of the rel="next" Link response header; for apps Okta uses the id of the last item on the previous page. Leave empty for the first page. Example: 0oa1a2b3c4d5e6f7g8h9
- `filter` (`string`, optional): Okta filter expression on status, name, user.id or group.id. Example: status eq "ACTIVE"
- `limit` (`integer`, optional): Maximum number of results to return in this page. Okta returns all apps by default. Example: 50
- `q` (`string`, optional): Finds apps whose name or label starts with this text. Example: Salesforce

Example input: `{}`

### `okta_group_get`

Get Group · Read-only

Get one Okta group by ID.
Returns id, type, created, lastUpdated, lastMembershipUpdated and profile (name, description).
Use okta_group_get when you know the group ID. Use okta_groups_list to find it.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `group_id` (`string`, required): Okta group ID (starts with 00g). Get it from okta_groups_list. Example: 00g1a2b3c4d5e6f7g8h9

Example input: `{"group_id":"<group_id>"}`

### `okta_group_members_list`

List Group Members · Read-only

List the users who are members of an Okta group.
Returns user objects with id, status and profile (login, email, firstName, lastName).
Use okta_group_members_list for one group's users. Use okta_user_groups_list for one user's groups.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `group_id` (`string`, required): Okta group ID (starts with 00g). Get it from okta_groups_list. Example: 00g1a2b3c4d5e6f7g8h9
- `after` (`string`, optional): Pagination cursor for the next page. Okta puts it in the after parameter of the rel="next" Link response header; for group members Okta uses the id of the last item on the previous page. Leave empty for the first page. Example: 00u1a2b3c4d5e6f7g8h9
- `limit` (`integer`, optional): Maximum number of results to return in this page. Okta default is 1000. Example: 200

Example input: `{"group_id":"<group_id>"}`

### `okta_groups_list`

List Groups · Read-only

List or search groups in the Okta org by name prefix, filter expression or search expression.
Returns group objects with id, type (OKTA_GROUP, APP_GROUP, BUILT_IN), created and profile (name, description).
Use okta_groups_list to find groups or their IDs. Use okta_group_get for one group by ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `after` (`string`, optional): Pagination cursor for the next page. Okta puts it in the after parameter of the rel="next" Link response header; for groups Okta uses the id of the last item on the previous page. Leave empty for the first page. Example: 00g1a2b3c4d5e6f7g8h9
- `filter` (`string`, optional): Okta filter expression on id, type, lastUpdated or lastMembershipUpdated. Example: type eq "APP_GROUP"
- `limit` (`integer`, optional): Maximum number of results to return in this page. Okta's default depends on the org. Okta recommends a value of 10000 or less. Example: 100
- `q` (`string`, optional): Finds groups whose name starts with this text. Returns at most 300 results and does not page. Do not combine with search. Example: Engineering
- `search` (`string`, optional): Okta search expression over group properties, including profile attributes and type. Example: type eq "OKTA_GROUP" and profile.name sw "Eng"

Example input: `{}`

### `okta_system_log_events_list`

List System Log Events · Read-only

List Okta System Log events, such as sign-ins, MFA challenges, admin changes and app access, within a time range.
Returns events with uuid, published, eventType, displayMessage, severity, actor, client, outcome and target.
Use okta_system_log_events_list to audit activity. Narrow it with since, until, filter or q.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `after` (`string`, optional): Opaque pagination cursor from the after parameter of the rel="next" Link response header. To read further, prefer narrowing since and until. Example: 1731628800000_1
- `filter` (`string`, optional): Okta filter expression on event properties. Example: eventType eq "user.session.start" and outcome.result eq "FAILURE"
- `limit` (`integer`, optional): Maximum number of results to return in this page. Okta default is 100. Maximum is 1000. Example: 100
- `q` (`string`, optional): Case-insensitive keywords to match anywhere in the event, separated by spaces. Example: jane.doe@example.com
- `since` (`string`, optional): Start of the time range, as an ISO 8601 timestamp. Okta defaults to 7 days before until and keeps logs for 90 days. Example: 2026-11-01T00:00:00Z
- `sort_order` (`string`, optional): Order of events by published time. Okta default is ASCENDING. Example: DESCENDING. One of: `ASCENDING`, `DESCENDING`.
- `until` (`string`, optional): End of the time range, as an ISO 8601 timestamp. Defaults to now. Example: 2026-11-15T00:00:00Z

Example input: `{}`

### `okta_user_app_links_list`

List User App Links · Read-only

List the apps assigned to an Okta user, as shown on their Okta dashboard.
Returns app links with appInstanceId, appName, label, linkUrl and hidden.
Use okta_user_app_links_list for one user's apps. Use okta_app_users_list for the users of one app.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `user_id` (`string`, required): Okta user ID, login (username) or unambiguous login short name of the user. Get the ID from okta_users_list. Example: 00u1a2b3c4d5e6f7g8h9 or jane.doe@example.com

Example input: `{"user_id":"<user_id>"}`

### `okta_user_factors_list`

List User Factors · Read-only

List the MFA factors an Okta user has enrolled, such as Okta Verify, SMS, email or WebAuthn.
Returns factor objects with id, factorType, provider, vendorName, status and profile.
Use okta_user_factors_list to check a user's MFA enrollment.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `user_id` (`string`, required): Okta user ID (starts with 00u). Get it from okta_users_list or okta_user_get. Example: 00u1a2b3c4d5e6f7g8h9

Example input: `{"user_id":"<user_id>"}`

### `okta_user_get`

Get User · Read-only

Get one Okta user by ID or login.
Returns id, status, created, activated, lastLogin, passwordChanged, profile and credentials.provider.
Use okta_user_get when you know the user's ID or login. Use okta_users_list to search.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `user_id` (`string`, required): Okta user ID, login (username) or unambiguous login short name of the user. Get the ID from okta_users_list. Example: 00u1a2b3c4d5e6f7g8h9 or jane.doe@example.com

Example input: `{"user_id":"<user_id>"}`

### `okta_user_groups_list`

List User Groups · Read-only

List the groups an Okta user belongs to.
Returns group objects with id, type and profile (name, description).
Use okta_user_groups_list for one user's groups. Use okta_group_members_list for the users in one group.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `user_id` (`string`, required): Okta user ID, login (username) or unambiguous login short name of the user. Get the ID from okta_users_list. Example: 00u1a2b3c4d5e6f7g8h9 or jane.doe@example.com

Example input: `{"user_id":"<user_id>"}`

### `okta_users_list`

List Users · Read-only

List or search users in the Okta org, with a simple name/email query, a filter expression or a search expression.
Returns user objects with id, status, created, lastLogin and profile (login, email, firstName, lastName).
Use okta_users_list to find users or their IDs. Use okta_user_get for one user by ID or login. Use okta_group_members_list for users in one group.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `after` (`string`, optional): Pagination cursor for the next page. Okta puts it in the after parameter of the rel="next" Link response header; for users Okta uses the id of the last item on the previous page. Leave empty for the first page. Example: 00u1a2b3c4d5e6f7g8h9
- `filter` (`string`, optional): Okta filter expression on a limited set of properties: status, lastUpdated, id, profile.login, profile.email, profile.firstName, profile.lastName. Only the eq operator (and gt/lt for lastUpdated). Use search for anything else. Example: status eq "SUSPENDED"
- `limit` (`integer`, optional): Maximum number of results to return in this page. Okta default is 200 (10 when q is used). Maximum is 200. Example: 50
- `q` (`string`, optional): Simple text lookup that matches the beginning of firstName, lastName or email. Best for a quick name or email lookup; returns at most 10 results unless limit is set and does not page. Do not combine with search. Example: jane
- `search` (`string`, optional): Okta search expression over most user properties, including custom profile attributes; Okta recommends it over filter. Uses SCIM-style operators (eq, sw, co, gt, lt, pr, and, or). Example: profile.department eq "Engineering" and status eq "ACTIVE"
- `sort_by` (`string`, optional): Property to sort by. Works only together with search. Example: profile.lastName
- `sort_order` (`string`, optional): Sort direction, asc or desc. Ignored unless sort_by is set. Example: asc. One of: `asc`, `desc`.

Example input: `{}`

### `okta_group_create`

Create Group · Write

Create an Okta group (type OKTA_GROUP) with a name and optional description.
Returns the new group with id, type and profile.
Use okta_group_create for a new group, then okta_group_member_add to add users.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): Group name, unique in the org. Example: Engineering - Backend
- `description` (`string`, optional): Group description. Example: Backend engineers with access to production tools

Example input: `{"name":"<name>"}`

### `okta_group_member_add`

Add Group Member · Write

Add an Okta user to an OKTA_GROUP group.
Returns an empty response on success; adding an existing member has no effect.
Use okta_group_member_add to grant group membership. Use okta_group_member_remove to revoke it.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `group_id` (`string`, required): Okta group ID (starts with 00g). Get it from okta_groups_list. Example: 00g1a2b3c4d5e6f7g8h9
- `user_id` (`string`, required): Okta user ID (starts with 00u). Get it from okta_users_list or okta_user_get. Example: 00u1a2b3c4d5e6f7g8h9

Example input: `{"group_id":"<group_id>","user_id":"<user_id>"}`

### `okta_group_update`

Update Group · Write

Replace the name and description of an OKTA_GROUP group. App-imported groups (APP_GROUP) cannot be changed.
Returns the updated group.
Use okta_group_update to rename a group. A description you leave empty is cleared.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `group_id` (`string`, required): Okta group ID (starts with 00g). Get it from okta_groups_list. Example: 00g1a2b3c4d5e6f7g8h9
- `name` (`string`, required): New group name. Example: Engineering - Platform
- `description` (`string`, optional): New group description. Leaving it empty clears the current description, because this replaces the whole profile. Example: Platform engineering team

Example input: `{"group_id":"<group_id>","name":"<name>"}`

### `okta_user_activate`

Activate User · Write

Activate a STAGED or DEPROVISIONED Okta user, optionally emailing them an activation link.
Returns activationUrl and activationToken when send_email is false, otherwise an empty object.
Use okta_user_activate for new or deactivated users. Use okta_user_unsuspend for a SUSPENDED user.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `user_id` (`string`, required): Okta user ID, login (username) or unambiguous login short name of the user. Get the ID from okta_users_list. Example: 00u1a2b3c4d5e6f7g8h9 or jane.doe@example.com
- `send_email` (`boolean`, optional): Whether Okta emails the user an activation link. Okta default is true. Set false to get the activation URL back instead. Example: false

Example input: `{"user_id":"<user_id>"}`

### `okta_user_create`

Create User · Write

Create a user in the Okta org, optionally with a password and group memberships, and optionally activate them.
Returns the new user with id, status (STAGED, PROVISIONED or ACTIVE) and profile.
Use okta_user_create for a new person. Use okta_user_update to change an existing user.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `email` (`string`, required): User's primary email address. Example: jane.doe@example.com
- `first_name` (`string`, required): User's given name. Example: Jane
- `last_name` (`string`, required): User's family name. Example: Doe
- `activate` (`boolean`, optional): Whether to activate the user now. true (Okta default) activates and sends an activation email when no password is set; false creates the user in STAGED status. Example: false
- `department` (`string`, optional): User's department. Example: Engineering
- `group_ids` (`array`, optional): IDs of Okta groups to add the user to at creation, up to 20. Get IDs from okta_groups_list. Example: ["00g1a2b3c4d5e6f7g8h9"]
- `login` (`string`, optional): Unique username, in email format by default. Defaults to the email when left empty. Example: jane.doe@example.com
- `mobile_phone` (`string`, optional): User's mobile phone number. Example: +1-555-415-1337
- `password` (`string`, optional): Initial password. Must meet the org's password policy. Leave empty to create a user who sets a password through the activation email. Example: Tlpe$2026xQ!
- `profile` (`object`, optional): Other Okta profile attributes to set, as a JSON object of attribute name to value. Standard attributes include city, countryCode, displayName, employeeNumber, manager, managerId, organization and secondEmail; custom attributes from your org's user schema also work. These are merged into the profile and override the fields above. Example: {"employeeNumber": "1042", "city": "San Francisco"}
- `title` (`string`, optional): User's job title. Example: Software Engineer

Example input: `{"email":"<email>","first_name":"<first_name>","last_name":"<last_name>"}`

### `okta_user_suspend`

Suspend User · Write

Suspend an ACTIVE Okta user so they cannot sign in, keeping their app assignments.
Returns an empty response on success; status becomes SUSPENDED.
Use okta_user_suspend for a temporary block. Use okta_user_unsuspend to restore. Use okta_user_deactivate to offboard.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `user_id` (`string`, required): Okta user ID, login (username) or unambiguous login short name of the user. Get the ID from okta_users_list. Example: 00u1a2b3c4d5e6f7g8h9 or jane.doe@example.com

Example input: `{"user_id":"<user_id>"}`

### `okta_user_unsuspend`

Unsuspend User · Write

Return a SUSPENDED Okta user to ACTIVE so they can sign in again.
Returns an empty response on success.
Use okta_user_unsuspend after okta_user_suspend. Use okta_user_activate for STAGED or DEPROVISIONED users.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `user_id` (`string`, required): Okta user ID, login (username) or unambiguous login short name of the user. Get the ID from okta_users_list. Example: 00u1a2b3c4d5e6f7g8h9 or jane.doe@example.com

Example input: `{"user_id":"<user_id>"}`

### `okta_user_update`

Update User · Write

Update an Okta user's profile, changing only the attributes you pass.
Returns the updated user with id, status and full profile.
Use okta_user_update to edit profile fields. Use okta_user_activate, okta_user_deactivate or okta_user_suspend to change status.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `user_id` (`string`, required): Okta user ID, login (username) or unambiguous login short name of the user. Get the ID from okta_users_list. Example: 00u1a2b3c4d5e6f7g8h9 or jane.doe@example.com
- `department` (`string`, optional): New department. Example: Engineering
- `email` (`string`, optional): New primary email address. Example: jane.smith@example.com
- `first_name` (`string`, optional): New given name. Example: Jane
- `last_name` (`string`, optional): New family name. Example: Smith
- `login` (`string`, optional): New unique username. Example: jane.smith@example.com
- `mobile_phone` (`string`, optional): New mobile phone number. Example: +1-555-415-1337
- `profile` (`object`, optional): Other profile attributes to change, as a JSON object of attribute name to value; standard or custom attributes. Attributes you leave out keep their current value. Example: {"city": "Austin", "managerId": "00u9z8y7x6w5v4u3t2s1"}
- `title` (`string`, optional): New job title. Example: Engineering Manager

Example input: `{"user_id":"<user_id>"}`

### `okta_group_member_remove`

Remove Group Member · Destructive

Remove an Okta user from an OKTA_GROUP group.
Returns an empty response on success. The user may lose apps assigned through this group.
Use okta_group_member_remove to revoke membership. Use okta_group_member_add to grant it.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `group_id` (`string`, required): Okta group ID (starts with 00g). Get it from okta_groups_list. Example: 00g1a2b3c4d5e6f7g8h9
- `user_id` (`string`, required): Okta user ID (starts with 00u). Get it from okta_users_list or okta_user_get. Example: 00u1a2b3c4d5e6f7g8h9

Example input: `{"group_id":"<group_id>","user_id":"<user_id>"}`

### `okta_user_deactivate`

Deactivate User · Destructive

Deactivate an Okta user, which sets status to DEPROVISIONED and removes them from all assigned apps.
Returns an empty response on success. This cannot be undone without reactivating the user, and app data may be lost.
Use okta_user_deactivate to offboard. Use okta_user_suspend to block sign-in temporarily.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `user_id` (`string`, required): Okta user ID, login (username) or unambiguous login short name of the user. Get the ID from okta_users_list. Example: 00u1a2b3c4d5e6f7g8h9 or jane.doe@example.com
- `send_email` (`boolean`, optional): Whether Okta emails the org admins about the deactivation. Okta default is false. Example: false

Example input: `{"user_id":"<user_id>"}`

## Related

Other Developer Tools connectors ([all 200](/agentkit/connectors/?category=developer-tools)):

- [GitHub](/agentkit/connectors/github/): Scalekit connector, OAuth, 217 tools
- [Datadog](/agentkit/connectors/datadog/): Scalekit connector, API key, 105 tools
- [Linear](/agentkit/connectors/linear/): Scalekit connector, OAuth, 64 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
