Okta

Okta is where an organization keeps its users, signs them in to their apps with single sign-on, and asks for MFA. Each of your clients that uses Okta has its own Okta org, and so may your own company. Connect Okta for those clients, and Neo agents can work in it while they handle a ticket or run a scheduled task.

​

What Neo can do with Okta

• Create and activate a new hire, add them to their groups and assign their apps, from the same onboarding ticket as their Microsoft 365 account
• Offboard a leaver: sign them out everywhere, revoke their app tokens and deactivate them, which removes their app access
• Unlock an account, send a password reset or give a temporary password, and reset a lost phone’s MFA
• Send an Okta Verify push to check that a caller is who they say before a reset
• Assign an app to a user or a group, and set the licences an app such as Microsoft 365 provisions with it
• Read the System Log to explain a failed sign-in or a lockout, and read sign-on policies, admin roles and devices

See Okta API for the permission groups and profiles.

​

One connection per client

An Okta API token belongs to one Okta org, so you connect Okta once for each client, with that client’s org address and token, and the connection belongs to that client’s company in Neo. On a ticket that belongs to a company, the agent reaches only that company’s connection. Otherwise (a chat, a scheduled agent, or a ticket with no company) it names the client it works for, and Neo accepts only a company on your Companies tab. To connect your own company’s Okta, pick your own company in the PSA as the customer.

​

Next steps