Ask for a separate user
Ask the client to create a named admin user for your agency or freelancer account. That is cleaner than sharing the client owner password and easier to revoke after the project.
Use a message like: “Please invite [agency email] as an administrator so we can review the site setup. If admin access is not appropriate yet, editor access is enough for content review.”
Collect site context
WordPress access alone is not enough. Ask for the login URL, hosting provider, staging environment, backup process, theme or page builder, important plugins, and any areas that should not be changed.
Confirm permissions
Clarify whether you are allowed to make changes directly or only inspect the setup. This prevents awkward surprises when technical work begins.
Use a portal
A portal keeps the WordPress access request next to hosting, domain, content, and approval requests, so your team does not hunt through old emails for the one missing login detail.
Plain-language access request
Use this as the human version of the ask before you turn it into a structured portal.
WordPress access is safest when it is requested as a named user invitation with a clear role, purpose, and end date.
Fields worth separating
Separate fields help the client understand what you need and help your team see exactly what is still missing.
Login URL
Required url
Use the exact admin URL, especially if wp-admin is hidden or protected.
User invite
Required access
Ask for a named user invitation instead of the client owner password.
Role level
Required text
Clarify whether administrator, editor, shop manager, or temporary access is appropriate.
Backup process
Required text
Collect where backups live and who can restore the site if something breaks.
Do-not-touch areas
Optional approval
Ask about checkout, forms, custom code, plugins, or live campaign pages that should not change.
Safe access checklist
Use these checks before asking a client to grant access or share sensitive account details.
Account
Invite [agency email] as a named WordPress user.
Named accounts are easier to revoke and audit.
Permissions
Confirm the role and whether direct changes are allowed.
Some teams only want inspection until the scope is approved.
Environment
Share staging, production, and backup details.
This prevents edits from happening in the wrong place.
Plugins
List important plugins, builders, and custom code.
Access without context can create avoidable site risk.
Approval
Name the person who approves changes to content, layout, plugins, and launch settings.
Technical access still needs business ownership.
Access request wording
The right wording protects the client relationship and reduces back-and-forth.
Do
- Request a separate user account with the minimum role needed.
- Ask for staging and backup details before making changes.
- Clarify whether you can edit directly or only inspect.
- Keep WordPress, hosting, and domain access as separate asks.
Avoid
- Ask the client to send their personal admin password.
- Assume admin access includes hosting, DNS, or database access.
- Change plugins before you know how backups are handled.
- Leave temporary agency accounts active after the project ends.
Why move access requests into a portal?
The same request becomes more reliable when every field has an owner, a status, and a place to submit it.
WordPress access sits beside hosting, domain, content, and approval requests.
The client can see whether admin, staging, and backup details are still missing.
Your team has one source of truth when production work begins.
Practical questions
What WordPress role should I request?
Request the lowest role that fits the work. Editor can be enough for content. Administrator is usually needed for themes, plugins, users, and site settings.
Is it okay to use the client owner account?
A named agency user is cleaner because it can be revoked later and avoids sharing the client's personal password.
Should I ask for hosting too?
Yes, if your work touches files, backups, staging, performance, redirects, DNS, or launch. WordPress admin alone is not always enough.