Demo: How Okta and Workday Can Work Together

Speaker 1: You already use Workday to manage your HR data and it works. But what if it could work better? What if you could eliminate the manual and risky ways HR and IT onboard and offboard users, exchanging info via email, file drops and tickets? What if changes in sensitive HR data or user statuses could seamlessly and securely trigger changes in your IT systems? What if the tools and information your employees have access to could automatically be updated whenever it needed to be? What if you could instantly enable and disable that access? What if you could do all of this without ever having to do anything more than what you've always done?

Speaker 1: Here's how Okta can make life cycle management easier, faster and safer for you and your company. As new employees are added in your HR system, Okta imports them on their start date or a few days before. Next, Okta provisions access to specific cloud apps such as Box, ServiceNow and Concur, based on the new hire's role. Additionally, Okta creates an account in Active Directory for the new user and if any downstream apps like AD, Office 365 or RingCentral make updates to the new hire's business email address or phone number, the changes can be synchronized in the reverse direction.

Speaker 1: Next, as your employees get promoted or other job details change, Okta automatically detects the updates, grants the user additional permissions to applications as needed and even provides access to new applications for the new role. Lastly, as employees are offboarded, Okta automatically revokes access and licenses from applications and even deactivates the user's account in Active Directory. Let's see these three scenarios in action.

Speaker 1: In the first scenario, your company just hired Barry Brown, a new sales leader. Your HR team adds this new employee in Workday as they typically do. Next, as soon as Okta synchronizes with Workday, Barry and other new users get detected and imported into Okta. Because Okta also imports groups and job specific fields, such as department and title, Barry gets automatically placed into the sales group, which gives him access to sales applications. If we take a closer look at Active Directory, we see that Barry has a new account and has been properly added to the right organizational unit. Okta also wrote specific attributes to the user's AD profile, including the sales title. Not only is this a win for IT, but also for Barry, who gets seamless access to the apps he needs on day one.

Speaker 1: In the second scenario, Barry decided to switch from sales to marketing. Your HR team process