Give WordPress clients the access they need, without sharing admin
A client asks to change a sentence. Someone sends the agency’s administrator login because it is the quickest way to help. The edit gets done, but the account now has two users and no clear owner for the next change.
Start with the task instead of the familiar role name. The right access lets a person do their work and makes their actions attributable to their own account.
Write down the required actions
Does the person need to draft articles, publish them, edit landing pages, manage orders or configure plugins? These are different responsibilities. Ask for a concrete example before deciding that administrator access is necessary.
WordPress’s roles and capabilities reference describes the core role system. Installed extensions can add capabilities and custom roles, so test the actual workflow on the site rather than relying only on the default role description.
A shop employee’s access, for example, should be evaluated against the order tasks they perform and the customer information they need. A developer’s temporary troubleshooting access has a different purpose and should not quietly become a permanent client account.
Use named accounts and a trial task
Create access through the site’s authorized process and use a separate account for each person. Ask them to complete a representative task. Check that they can reach the required screen and cannot perform unrelated high-impact actions.
If the role is too restrictive, identify the missing capability before increasing the whole account to administrator. A custom role may be appropriate, but it becomes configuration your team must maintain and test when extensions change.
- Content contributor: test drafting, media access and the approval path.
- Publisher: test the intended publishing scope and access to other authors’ work.
- Store operator: test the specific order and customer tasks in scope.
- Technical support: define the issue, necessary access and removal date.
Do not use a real customer’s order as a convenient permissions experiment. Use a controlled test case and keep the data exposure proportional to the work.
Temporary access needs an owner
When a vendor needs to investigate an issue, agree who can authorize access, what environment they should use and when it ends. Prefer staging when the issue can be reproduced there safely. Record any production access and review it when the ticket closes.
A calendar reminder is better than relying on memory. If a tool can enforce expiry, verify how it behaves before depending on it. An “expires soon” note in a ticket does not revoke a credential.
Review more than the Users screen
Interactive accounts are only part of the access picture. Application passwords, deployment keys, hosting collaborators and management-platform connections may remain active after a person’s WordPress user is removed.
Keep an inventory of those access paths with their purpose and owner. During offboarding, check dependencies before revoking them so a necessary production integration is not accidentally broken. Rotate shared secrets where the departing person should no longer know the value.
Revisit access when responsibilities change, not only when somebody leaves. A former developer who now handles content may no longer need the same capabilities.
Use the handover checklist when taking over a site and include access reviews in the maintenance routine. Close the access request with the tested task and the role granted. If access is temporary, include its removal date in the same record; do not leave that detail in somebody’s inbox.
Have a correction or a workflow we should cover? Tell the IrmaWP team.