Give a contributor their own account and a clear submission workflow instead of sharing an administrator login. This preserves accountability and keeps site settings, plugins and other users outside ordinary writing access.
IN THIS ARTICLE
01 Define the editorial process
Decide who drafts, who reviews, who supplies images and who publishes. A standard Contributor role can prepare posts for review but has limitations, including media-upload restrictions in a normal installation. Plan those limitations rather than discovering them during a deadline.
If the work requires a custom role, use a maintained permission-management approach and document the capabilities granted. Do not add broad administration rights merely to expose one content feature.
02 Invite and orient the contributor
- Create a separate user with the correct email address and the intended role.
- Send the supported account setup notification so the contributor can establish their own password.
- Explain the site login URL, naming conventions, category choices and review expectations.
- Ask them to create a short test draft and submit it through the available review action.
- Have the responsible editor review, revise and publish the test only if it is suitable for the public site.
How can a Contributor supply images without administrator access?
Use an agreed process for image delivery when the contributor cannot upload directly. The editor should check rights, file size and alternative text before insertion. Avoid giving access to the whole hosting account for a task limited to writing one article.
Keep editorial feedback inside the approved workflow or project channel. Do not place private reviewer notes in the public body and assume they will remain hidden.
03 Review access when the work ends
Confirm which drafts and published posts belong to the project. Remove or reduce access when it is no longer needed, preserving content attribution deliberately.
If the contributor cannot see the expected control, check their role, the content type and any workflow plugin. A missing Pages menu may be an intentional role boundary rather than an error. Troubleshoot that specific requirement instead of lending another user's credentials, which obscures who made later changes and makes clean revocation more difficult.