Your teammate needs to correct a service description. You send the website login, and suddenly they have controls for far more than the sentence they came to change.
Set up access around the work someone needs to do. A person who writes news, a person who approves it and a person who maintains the site may need different controls.
For a Tempe business using WordPress, the useful question is not simply “Can they sign in?” It is whether their own account supports the agreed job, including where they should stop and ask for help.
Start with tasks instead of role names
List the updates each person handles. Include the content they touch, whether it belongs to somebody else and whether they can publish without review.
Imagine a Tempe workshop business with a receptionist correcting class descriptions and a freelance writer preparing news posts. The receptionist needs access to existing pages. The writer may only need to prepare articles for someone else to approve.
Those are different jobs even if both people call themselves editors. Write the tasks down before choosing a WordPress role.
- Content
- Own articles, shared pages or both?
- Action
- Write, upload, revise or schedule?
- Decision
- Publish directly or send for review?
Include the awkward parts of ordinary work. Does the person need to add an image, change a link, update a published page or schedule an announcement? A successful sign-in does not answer any of those questions.
Our editable-website guide covers the wider content-editing experience. Here, the goal is to decide who can perform each part of that work.
Check what the default roles actually allow
WordPress roles bundle permissions. In the default setup, an Editor can publish and manage other people's posts. An Author can publish their own posts. A Contributor can prepare their own posts but cannot publish them. Read the official role definitions (new tab).
That makes “Editor” a poor shorthand for “someone whose changes must be approved.” If approval is required, explain that requirement to your maintainer and test the resulting process.
Do not assume a role suitable for writing posts also covers editing existing business pages. Compare the required task with the permission list. WordPress separates page capabilities from post capabilities, and its default roles can be customized. Review the capability table (new tab).
Ask about your actual site, including its page builder and plugins. A role name alone does not establish what a customized installation permits. If one necessary control is missing, identify that control before granting broad administrator access.
Keep website maintenance with the people responsible for it. Installing software or changing site settings should be an intentional responsibility, not a workaround for a missing editing button.
Set up a named account and a clear handoff
Have the authorized administrator create an account for the person doing the work. WordPress's Add New User screen includes the account email and role selection. Choose the role deliberately. See the user-creation documentation (new tab).
Give each person their own sign-in rather than circulating one staff login. Record who the account belongs to, what work it supports and who approves changes to its access.
Use your established account setup and recovery process. The handoff notes should identify the sign-in page and support contact without containing passwords or recovery codes.
Also check the public identity attached to the account. WordPress has a “Display name publicly as” profile setting, while the theme determines how author information appears. Read the profile settings guide (new tab).
Open an appropriate public article and review its byline and author destination. Confirm they show the intended identity. Do not treat a friendly display name as a promise that every other account identifier is hidden.
For domain, hosting and recovery ownership beyond the editing account, use our website handover checklist.
Test from the account the person will use
Arrange an unpublished test item or a separate test copy of the site with your maintainer. Keep the test away from real customer-facing changes until you know what the controls do.
Sign in as the intended staff account in a separate browser profile. A demonstration from an administrator account can conceal exactly the limitation you need to find.
Work through the task list. Find the content, edit a paragraph, add the intended image, preview it and save it through the expected route. If the job includes changing someone else's page, test that case too.
- Work they should complete
- Use the real account to finish a representative editing task.
- Work that needs another person
- Verify the review route and who handles restricted actions.
Test the review boundary as carefully as the editing task. If the writer must submit work for approval, confirm who receives it and whether the writer can publish directly. If the person is allowed to publish, have them demonstrate the public check afterward.
When a task fails, record the content type, attempted action and result. Ask the maintainer to resolve that specific gap. Avoid making every account an administrator just to get through the demonstration.
Plan content ownership when access ends
Include account review in staff and contractor handoffs. First identify any unfinished drafts, scheduled posts and published content associated with the person leaving.
WordPress's Users screen supports role changes and deletion. Its deletion process includes a choice between removing the person's content and attributing it to another account. Read that choice carefully before confirming. Review the user-management guidance (new tab).
Have the maintainer preserve the content your business intends to keep. Check public bylines and author links afterward, along with any site-specific content or integrations that need separate treatment.
Reducing a role is also different from ending access entirely. Decide which outcome the business needs and ask the maintainer to verify it. Review connected tools separately rather than assuming a WordPress account change covers them.
For work waiting to go live, our scheduled-announcement guide helps check the release date, reviewer and public result. Reassign that responsibility before the original editor leaves.
Keep the access plan small and current
Maintain a short list of active editors, their responsibilities and the person who can approve access changes. Review it when responsibilities change, not only when someone leaves.
Repeat the account test after a major change to your editing setup. A new page builder or publishing process may change what your team needs to do, even when the role labels stay the same.
Keep a fallback for an urgent correction when the usual editor is away. Name the person to contact and what information they need. Do not make shared credentials the emergency plan.
Agree on how to recover a mistaken content edit too. Our page-revision guide explains how to recover earlier text while preserving newer corrections. Access planning and recovery are separate parts of a workable editing process.
Your Tempe business website should be manageable by the people who keep its information current. Our content management service can help make those responsibilities clear. Talk to Brandon about your team's website editing access.
