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
Hide a single job from a recruiter not the entire team. The recruiter may still need to be the recruiter for the job on the particular team. Since we integrated with our PeopleSoft solution, it doesn't make sense in PeopleSoft to create a "dummy" team just for hiding jobs. Attached are examples of this functionality that we lost transitioning to pageup from neogov. Thanks
|
What business value are you trying to achieve?
hide a job from a recruiter, not the entire team. |
The idea is in line with a potential future direction of the product. While not on the current roadmap, this idea will be taken into account as we look to develop similar areas of the system.
We definitely need this function! It would be very useful for our campus.
More flexibility with access vs. no access to jobs without touching security/permission group settings just makes sense. It will alleviate the hoops that we need to jump through for everyone to still be able to perform their jobs as part of the recruitment team.
Definetly need this! I'm having to lower a user's permission just so they are unable to see a specific job they are applying to.
Definately, we've had to disable a lot of functionality because it's too difficult to manage who can access which records
a setting that strips a job from reporting and hides it from any User not actively involved would be very useful instead of using Hidden teams - controlled by SuperUser