Get the Asset Panda Pro App
Get

Integrations

Okta + Asset Panda Pro

Sync employee information from Okta into Asset Panda Pro, support asset assignments, and manage login access with group-based role mapping and configured synchronization.

Key benefits

  1. Spend less time maintaining employee records

    Import selected Okta users into Asset Panda Pro People records, helping teams prepare employee records for equipment assignment and checkout.

  2. Assign access using Okta groups

    Map Okta user groups to Asset Panda Pro user roles when creating login users, instead of granting every imported People record a platform login.

  3. Apply directory changes through synchronization

    Start with a full import, then use delta syncs for supported updates. Login accounts deactivated in Okta are deactivated in Asset Panda Pro when the next sync runs.

What Okta data and workflows are supported?

Okta sends selected user information into Asset Panda Pro. People-record imports and login-user mappings are separate workflows.

Information / workflow Direction Supported behavior
Employee People records Okta → Asset Panda Pro Import users into a selected People collection for employee and asset-assignment records; a People record alone does not create a login.
User attributes Okta → Asset Panda Pro Map identifiers and fields such as Okta user ID, name, email, and department to the corresponding Asset Panda fields.
Collection filters Okta → Asset Panda Pro Limit imported People records by department, group, or status. Login-user imports use Okta group filters.
Login users and roles Okta → Asset Panda Pro Create login users through a separate mapping and associate selected Okta groups with Asset Panda Pro user roles.
Sync and login status Okta → Asset Panda Pro Run an initial full import, followed by delta syncs for changes. Deactivating a user in Okta deactivates their Asset Panda Pro login on the next sync. The corresponding People record status updates only when the Status field is mapped.

The Okta integration imports information into Asset Panda Pro; it does not provide two-way directory synchronization.

How the Okta integration works

  1. Create an Okta API token

    In the Okta Admin Console, go to Security > API > Tokens and create a token with the necessary access. Copy the token when it is generated.

  2. Connect Okta to Asset Panda Pro

    Go to Settings > Account Management > Integrations, open the Integrations Store, and add Okta. Enter your Okta URL and API token, then select Test and Save Connection.

  3. Map the users you need

    Choose whether to import People records or create login users. Match Okta attributes to Asset Panda fields and select a unique identifier. For login users, map an Okta group to the appropriate Asset Panda Pro user role.

  4. Create and run your sync

    From the mapping card, use Create sync to set a schedule or Run to synchronize on demand. The initial import loads selected records; later delta syncs apply supported changes.

Requirements

  • An Asset Panda Pro account with access to the Integrations Store and the relevant module.
  • An Okta organization and permission to create an Okta API token in its Admin Console.
  • Your Okta organization URL and API token to authenticate the connection.
  • An Asset Panda Pro collection and fields for People-record imports, or Okta user groups and corresponding Asset Panda Pro roles for login-user mappings.
  • A unique identifier, such as Okta user ID or an email address that is unique in your directory, to match records across syncs.

Frequently asked questions

Can I import Okta users without giving them Asset Panda Pro login access?

Yes. Import employees as People records to support asset assignments and checkouts. Creating Asset Panda Pro login users is a separate mapping option.

Can Okta groups control which users receive Asset Panda Pro access?

Yes. For login-user mappings, select Okta groups and map them to Asset Panda Pro user roles. The integration uses those mappings when creating login accounts.

Does the Okta integration sync data both ways?

No. Supported data flows from Okta into Asset Panda Pro. Changes made in Asset Panda Pro are not written back to the Okta directory through this integration.

How often does the Okta integration update user information?

You can create a synchronization schedule from the Okta mapping card or run a sync on demand. After the initial full import, delta syncs process supported changes.

What happens when an employee is deactivated in Okta?

When the next synchronization runs, Asset Panda Pro deactivates the corresponding login account. The employee's People record status is updated only if the Okta Status field has been mapped to the corresponding field in Asset Panda Pro.

How does Asset Panda Pro avoid duplicate employee records?

During field mapping, choose a unique identifier such as Okta user ID or a reliably unique email address. This helps subsequent syncs match updates to existing records.

Does connecting Okta to Asset Panda Pro automatically enable SSO?

No. Connecting Okta through the API and mapping user groups to Asset Panda Pro roles supports user synchronization and login provisioning. Single sign-on (SSO) requires a separate configuration and is not automatically enabled by the integration.

About Okta

Okta is an identity and access management platform that organizations use to manage employees, groups, and access to business applications. Connecting Okta with Asset Panda Pro brings selected directory information into asset records and provides a way to map login access by group.

Keep employee data connected to asset management

See how Asset Panda Pro can use your Okta directory to reduce repeated data entry, support equipment assignments, and manage platform login access through mapped user roles.