Skip to main content

​
Highlights

​
Phone agent authentication

You can now require end users to pass an authentication challenge before the phone agent can reach any knowledge or automations. Until the caller is verified, the agent is restricted to just two workflows you define: a challenge workflow and a verification workflow. The challenge workflow might send a one-time code or trigger an Okta push, and the verification workflow confirms the code or checks the Okta API for completion. After three failed attempts, the agent hangs up and escalates the call as a ticket. For example, an employee calls the help desk to reset MFA. The agent first sends a one-time code to their Slack, confirms the code, and only then looks up their account and runs the reset.

​
Unified catalog for tags

You can now apply tags to apps, skills, workflows, resources, and roles. Additionally, you can manage all tags from a single catalog in Team settings. For example, you can tag every finance-related app, resource, and role as “finance” and pull them all up together when you are reviewing access.

​
Team, resource, and role owners

In addition to apps, you can now set owners for teams, resources, and roles. Owners can now also be designated approvers in access policies, so the people who own something are the ones who approve access to it. For example, you can make the finance systems team the owner of your finance resources and designate them as the approvers for associated access requests.