![]() ![]() ![]() Barry now has a bunch of marketing applications, but no longer has access to sales applications. Okta imports these changes, sees Barry is now in marketing, and modifies his access. Your HR team processes this change in job titles as they normally do. Speaker 1: In the second scenario, Barry decided to switch from sales to marketing. Not only is this a win for IT, but also for Barry, who gets seamless access to the apps he needs on day one. Okta also wrote specific attributes to the user's AD profile, including the sales title. 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. Because Okta also imports groups and job-specific fields, such as department and title, Barry gets automatically placed in to the sales group, which gives him access to sales applications. Next, as soon as Okta synchronizes with Namely, Barry and other new users get detected and imported in to Okta. Your HR team adds this new employee in Namely as they typically do. In the first scenario, your company just hired Barry Brown, a new sales leader. Speaker 1: Let's see these three scenarios in action. Lastly, as employees are offboarded, Okta automatically revokes access and licenses from applications, and even deactivates the user's account and active directory. 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. Additionally, Okta creates an account and 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. Next, Okta provisions access to specific cloud apps, such as Box, ServiceNow, and Concur based on the new hire's role. As new employees are added in your HR system, Okta imports them on their start date or a few days before. Speaker 1: Here's how Okta can make lifecycle management easier, faster, and safer for you and your company. Speaker 1: You already use Namely 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? And what if you could do all of this without ever having to do anything more than what you've always done? ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |