World ID for Zoom Okta administrator setup guide

Use this guide to connect World ID for Zoom to Okta, authorize an approved application to request verification and test the employee experience.

Before you begin

  • Ask World ID support to confirm that Cross App Access (XAA) and Enterprise Portal onboarding are enabled for your organization.
  • You need Okta administrator permissions to manage applications and XAA connections, plus an application that supports XAA. Zoom's requesting integration must be available before you can use it as the requester.
  • Your test employee needs a corporate Zoom account matched in Enterprise Portal, a supported version of the World ID app, Proof of Human claimed through Orb verification and phone notifications enabled.

Supported features

Employees can sign in from the World ID for Zoom page or the Okta dashboard tile. An approved application can request verification notifications. Eligible employees connect during supported Enterprise Portal enrollment. The tile itself does not enroll or verify employees. This integration does not provide MFA or SCIM provisioning.

Set up the integration

1 Add World ID for Zoom

In the Okta Admin Console, open Applications and Resources > Applications > Browse App Catalog. Search for World ID for Zoom, select Add Integration and assign a test employee under Assignments.

2 Connect your organization

Give World ID support your Okta organization URL and the application's OpenID Connect (OIDC) client ID. Transfer the client secret through the secure channel agreed with support; do not email it. Use your organization URL, such as https://your-company.okta.com, without /oauth2/default.

The sign-in URIs are preset by the catalog listing; no changes are needed. Wait for support to confirm the connection.

3 Check XAA access

Open World ID for Zoom > Machine Assignments. Under Access method, confirm that Cross App Access (XAA) shows Enabled. If it is disabled, enable it there. The issuer, resource identifier and scope are supplied by the catalog listing; no manual entry is needed.

4 Authorize the requesting application

Follow the requesting application's own XAA setup instructions. The steps depend on the provider. For applications registered as AI agents in Okta, use Directory > AI Agents to register or select the agent. Add an Application resource connection to World ID for Zoom, enter the connection client ID supplied by World ID, allow notify and activate it. Assign the test employee to both applications.

For Zoom, use Zoom's setup instructions when its requesting integration is available. Only create additional application or agent registrations if those instructions require them.

World ID support coordinates the requester's credentials with your application provider. These differ from the OIDC credentials in step 2.

5 Check the connection

Open World ID for Zoom, sign in through Okta and confirm the employee can access the page. Check that their Okta tile opens the same page.

Have the employee complete supported Enterprise Portal enrollment. Once support confirms their XAA connection, request verification from the requesting application. Check that the employee receives the notification and completes the requested verification. Acceptance of a notification request does not confirm successful verification or change a Zoom meeting badge.

Troubleshooting and support

  • Missing tile or failed sign-in: Check application assignments, visibility and the Okta organization registered with World ID.
  • No notification: Check phone permissions and ask support to confirm the employee's enrollment connection. A manual Zoom link alone does not establish XAA access.
  • XAA settings missing: Ask Okta support to confirm feature availability.

Contact [email protected] with the failed step, error and time with time zone. Do not include passwords, secrets or tokens.

To stop new grants, disable the resource connection in Okta. Contact World ID support for immediate service-side disablement or employee offboarding. Existing tokens may remain valid until expiry; removing an assignment does not delete the World ID connection.