The Jet Admin Okta integration lets your app authenticate users against your organization's Okta directory, driven by the same roles and permissions you already manage in Jet. Whether an employee opens the app for the first time, a group membership changes, or an account needs to be cut off, the whole sign-in flow runs through Okta, and access stays in sync with your directory.

That covers what teams build with Okta first: internal tools that inherit single sign-on rather than a separate password, and access reviews that stay accurate because they run off the same directory IT already maintains. Because Jet maps Okta groups to app roles, a person's permissions update automatically as their group membership changes, and removing them from Okta removes their access everywhere at once.

Key benefits

• One login for everything. Employees use the same Okta account for your Jet app as for every other company tool.
• Automatic role sync. Permissions update the moment someone's Okta group changes, with no manual account edits.
• Centralized offboarding. Removing someone from Okta removes their access to the app immediately.
• Fewer passwords, less risk. No separate password to phish, forget or reuse.
• Audit-ready access. Who has access is always exactly who your directory says should.

How to connect Jet Admin with Okta

1. In Okta, create a new application integration and choose OIDC or SAML.
2. In Jet Admin, open your app's authentication settings and choose Okta as the sign-in method.
3. Enter the client ID, client secret and Okta domain from your Okta application.
4. Map the Okta groups you want to use to roles inside your Jet app.
5. Test sign-in with a user in each group to confirm roles apply correctly.
6. Roll out the login link to your team, and turn off the built-in password login if you want Okta as the only path in.