I’m looking for the same solution.
At the moment I have to give anyone entering a job from the WordPress Admin area Administrator access, which is risky.
WP Job Manager is designed so that jobs can, and *should*, be submitted from the frontend job submission form. 🙂 You should not have to make anyone an admin that way.
You can see how to set up the frontend submission form here:
https://wpjobmanager.com/document/installation/
Thanks!
You can’t expect a client once they have paid for a website, not to be able to access the backend of their own site. But they do understand when they haven’t got Administrator access, as they don’t want to potentially damage areas where they shouldn’t really need to access. Consequently, it would make much more sense to provide them access to the backend and the jobs listings using a lesser role that won’t cause the rest of the site any issues.
Adam
I think the point here is to have non-Admins able to edit job listings on the backend versus only those with Admin role.
They can still enter the backend of the site if you want them to, I’m not saying you should lock them out. 🙂
All I’m saying is that WP Job Manager is designed to have jobs submitted and edited from the front-end only, even if the user submitting a job is an admin on the site.
To edit jobs, use dashboard shortcode:
https://wpjobmanager.com/document/the-job-dashboard/
I think you’re missing the point Adam. Both myself and jacob00 are requesting non-Admin roles to be able to edit jobs listings from the backend.
I’ve read through other support requests asking for the same thing. I don’t see what the big deal is about changing the plugin to have this ability?
If you really want to give non-admins backend access, you can do so via a custom user role made with a plugin like this one:
https://wordpress.org/plugins/user-role-editor/
You’d have to grant that custom role all the capabilities needed to manage jobs, etc.
From Mike’s past comments on issues like this one:
https://github.com/Automattic/WP-Job-Manager/issues/177
… I doubt we will be adding an “official” way to do this within WP Job Manager itself.
Thank you Adam for your suggestion [although untested], this resolves this issue perfectly.
