Blog / WordPress /

Reviewing WordPress roles before adding a new editor

A new editor starts on Monday. You’re busy, the login screen is open, and the dropdown says Administrator. One click and it’s done.

Don’t. Administrator hands over settings, plugins and user data the editor has no need to touch. Review the roles first and give the least access the work needs.

Define the tasks

List what the person must do: draft, edit, upload media, publish or manage specific content. Compare those tasks with existing roles and custom capabilities. Don’t trust a role name alone, since plugins can add permissions. Ask the site administrator to confirm the real access boundary. When I’m handed a client site, the user list is one of the first things I check.

Protect the account

Use an individual account, strong authentication and the organisation’s approved account process. Avoid shared logins. Confirm how access is removed when the editor leaves or changes responsibilities. If the person needs temporary elevated access, define the duration and who approves it.

Verify safely

Test permissions with a suitable account in staging or a controlled way. Confirm the editor can complete assigned work without accessing unrelated settings or private information.

Review plugins that change permissions

Plugins can add capabilities or change what a role can do. Before granting access, review the role-management and editorial plugins with the administrator. A role’s default label may not describe its custom permissions. Decide whether the editor should upload files, publish, edit others’ content or manage taxonomies, and grant only that.

Media uploads can introduce risk if file types or metadata are not controlled. Explain the approved image and document workflow. If an editor manages a specific section, consider whether the site supports scoped access rather than granting sitewide permissions.

Maintain access over time

Review accounts when responsibilities change and remove access promptly when it is no longer needed. Keep an owner for periodic access reviews. Avoid sharing passwords to solve an urgent publishing problem; use the approved account recovery or invitation process.

Test the account’s actual workflow and confirm it cannot reach unrelated settings or user data.

Separate editorial tasks from administration

A new editor may need to publish articles but not install plugins, manage users or change settings. Map responsibilities to capabilities instead of picking the most powerful role for convenience. Check whether they edit only their own posts or others’ too, and review access to media, comments and private content.

If custom post types or page builders are involved, check their permissions specifically. A role may publish blog posts but not edit landing pages, or it may allow access to a broader area than intended. Ask the site administrator to test the actual account before the editor begins work.

Provide a safe onboarding path

Share guidance on drafts, previews, media handling, revisions and how to request help. Make sure the person knows how to avoid publishing confidential material. Use an individual account with the organisation’s approved authentication process, and do not send passwords in shared documents.

Review access when responsibilities change. If someone needs temporary elevated capability, define approval and expiry.

Plan for a safe access transition

If the editor is replacing another person, decide whether the previous account should be disabled and whether any content ownership needs to move. Do not transfer a personal login. Confirm who retains responsibility for drafts and scheduled posts. If the new editor needs access to confidential material, verify that the role and onboarding process are approved.

Test the account by completing its actual tasks, then check that restricted pages and settings remain unavailable. Document who approved access and how to request changes. Avoid recording passwords in the onboarding notes.

Separate publishing access from user management

A new editor usually doesn’t need to create users, change settings or install extensions. Keep those with designated administrators. If a workflow really needs broader access, explain why and approve it explicitly. I don’t trust “temporary” admin access. It tends to become permanent.

Review revision and publishing settings too. If the editor can publish directly, ensure the editorial process supports that responsibility. If all content must be approved, use roles and workflow tools that enforce the intended review. Do not assume an informal reminder will prevent accidental publication.

Document how to request permission changes and who reviews them.

Review the editor’s workflow after permission changes

Once an account is active, have the editor complete a draft, preview it, upload an approved image and submit it for review. Confirm that each step works within the intended permission boundary. If an editor cannot do assigned work, adjust only the needed capability and record the reason. Avoid escalating the account broadly because one workflow setting is misconfigured.

Check that the account does not inherit access through a group or plugin role.

If the editor changes roles later, review access again rather than layering new permissions onto the old account. Remove capabilities that are no longer needed and confirm content ownership remains clear.

Keep the review simple enough to repeat whenever someone joins or changes duties. A short capability list, test account and named approver can prevent permissions from expanding by habit. Open your Users screen right now. Who in that list has more access than their job needs?