Manage user roles

We have a freelance writer leaving this Friday. Remove her Editor role, keep her account for reference, and add the new contractor, Luis Rivera, as Author with publishing rights only after I’ve approved two test posts. Make the change today and email both Luis and the departing writer a confirmation of the role change and next steps.

Before I change user roles for the departing writer and new contractor, make the request easy for the site owner to approve. Put the current access level and the exact risk of leaving it in place at the top, show a one-line remediation for each risk, and highlight any plugin or workflow that relies on the departing writer’s Editor privileges. Flag whether Luis needs additional plugin access to submit his posts.

I was asked to give Contractor Luis Editor rights so he can fix taxonomy pages before launch. I’m worried Editor access might let him change other content or settings we don’t want altered. I don’t know if the fixes actually require Editor rights or if a temporary Author plus a quick admin review could work. What’s the likely least-risky path that still meets the Friday deadline?

We repeatedly hand out Editor-level access for short tasks and then spend hours auditing changes and reversing mistakes. Which habit should I change to stop this loss of time and control? Recommend a single distribution of responsibilities, a temporary-elevation policy, and how to enforce it with minimal friction for contractors over the next quarter.