We love to hear your feedback. Your suggestions and ideas are important to us. Our feedback forum is a great place to post your ideas and vote on others. Please share your detailed use case and how the proposed enhancements can increase value to your business. We do read all of your posts, but may not be able to respond to all comments.
More information on the status of submitted ideas can be found here
We would like to request the ability to have sourcing channels available on a campus by campus basis or possibly on a teams basis. That way a recruiter from a single campus will only see the career sites and sourcing channels applicable to them. We cannot do this with the current permission set up, it doesn't allow enough granularity.
|
What business value are you trying to achieve?
When our recruiters are selecting sourcing channels, the list is becoming very long. this is because (1) we have shared permissions with all our campuses, so the single shared permission has to have all our campuses career sites showing to the recruiters and (2) each campus (x23) can have an internal and external career site (up to x64 if everyone has both). Finally (3) we are looking at adding additional career sites and improving our quality of life in the system, adding things like indeed, linkedin, etc to our sourcing channels. Because this list is already so long because we are such a large client, when we are discussing adding new sourcing channels to improve our quality of life, our conversations instead turn into conversations about saving space and we have too many channels listed already. We would like to request the ability to have sourcing channels available on a campus by campus basis or possibly on a teams basis. That way a recruiter from a single campus will only see the career sites and sourcing channels applicable to them. We cannot do this with the current permission set up, it doesn't allow enough granularity. |
