> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ravenna.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Connect Okta to Ravenna to provision users, sync groups and applications, and automate access request workflows through identity-driven automation.

Connect Okta to automate application access requests and user provisioning through Okta groups.

Sync Okta users, groups, and applications, then enable workflow actions to manage group memberships and provision application access.

## What you can do

<CardGroup cols={3}>
  <Card title="Group management" icon="layers">
    Add/remove users from Okta groups and check group memberships
  </Card>

  <Card title="Application access" icon="app-window">
    Provision and deprovision application access automatically
  </Card>

  <Card title="Workflow interpolation" icon="code">
    Use Okta user metadata in workflow conditions and actions
  </Card>
</CardGroup>

## User profile data

Ravenna syncs Okta user profiles for org hierarchy, approval workflows, and workflow interpolation.

### Available fields

| Field          | Description                                                                                     |
| -------------- | ----------------------------------------------------------------------------------------------- |
| `title`        | Job title                                                                                       |
| `department`   | Department name                                                                                 |
| `organization` | Organization name                                                                               |
| `userType`     | User type classification                                                                        |
| `primaryPhone` | Primary phone number                                                                            |
| `mobilePhone`  | Mobile phone number                                                                             |
| `city`         | City                                                                                            |
| `state`        | State or region                                                                                 |
| `countryCode`  | Country code                                                                                    |
| `managerEmail` | Custom Okta profile field for manager's email address (checked first for manager relationships) |
| `managerId`    | Manager's email address or Okta user ID (checked second for manager relationships)              |
| `manager`      | Manager's email address (checked last for manager relationships)                                |

<Note>
  Ravenna checks `managerEmail` first, then `managerId`, then `manager` when establishing manager-employee relationships. Using email addresses ensures accurate matching across systems.
</Note>

### Auto-provisioning during sync

When Ravenna syncs users from Okta, any Okta user who doesn't already have a matching Ravenna account is automatically created as an Organization Guest. This ensures your Ravenna directory stays in sync with your identity provider without requiring manual user creation.

<Callout icon="info-circle" color="#6B7280">
  The `managerEmail` field is optional and requires a custom Okta profile field configuration. If your Okta organization uses a custom profile field for manager email addresses, configure it in your Okta admin console and ensure it's named `managerEmail`.
</Callout>

### Using profile data in workflows

Access these fields through the user's Okta metadata when building workflow conditions or actions:

* Route approval requests based on department or organization
* Apply different access policies by user type
* Include contact information in notifications
* Build location-based access rules using city, state, or country