Demo: How Okta and SuccessFactors Can Work Together
Speaker 1: You already use SuccessFactors 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 off-board 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? And what if you could do all of this without ever having to do anything more than what you've always done? Here's how Okta can make lifecycle management easier, faster, and safer for you and your company.
Speaker 1: 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 hires 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 hires 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.
Speaker 1: Lastly, as employees are off-boarded, Okta automatically revokes access and licenses from applications, and even deactivates the user's account in Active Directory.
Speaker 1: 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 SuccessFactors as they typically do.
Speaker 1: Next, as soon as Okta synchronizes with SuccessFactors, 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 application.
Speaker 1: 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 processes this change and job titles as they normally do. Okta imports these changes, sees is now in marketing and modifies his access. Barry now as a bunch of marketing applications, but no longer has access to sales applications. If we look in Active Directory, we can see that Okta changed Barry's title to reflect his new position.
Speaker 1: In the third and final scenario, Barry chose to leave the organization. Your HR team terminates him in SuccessFactors. As in the previous scenarios, Okta detects the change in the HR system and deactivates Barry's IT accounts. Looking in Active Directory, we can also see that Barry's account has been automatically disabled, preventing any possibility of logging into corporate resources after his end date.
Speaker 1: By integrating SuccessFactors with Okta, you can transform the way your business manages the employee lifecycle, save time and money for IT, secure your corporate environment, and empower your employees to be productive.
Together, Okta and SuccessFactors securely manages HR data by making lifecycle management more efficient for your organization.