nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle Communities

Oracle Analytics and AI

Child Item

Any best practices for Security / User group setup?

Tonya Henderson, Cummins Inc

Summary

best practice recommendations on security/user groups

Content

We are looking at different options for security using User Groups to limit the requisitions that recruiters have access to. Our concern is that we would still need several dispatchers to be able to assign the requisitions. Do you have any best practice recommendations on security/user groups?

We currently load draft requisitions from another system that is used by HR. Requisitions aren't typically created in Taleo.

Find more posts tagged with

Taleo Enterprise

Comments

Prudence K

Hi Tonya - we use user groups to limit access to locations. For example, if you are a store recruiter, than your user group would be Store#### ... distribution recruiter would have a user group of DC#####, etc. The User Type says that you can create/edit a req if you are part of the user group, so many of our users will have multiple groups - some as large as 500 or so, others only have 1. Feel free to reach out to me directly and we can discuss further!