Copyable client message
Hi [client name], to work on the WordPress site safely, please create a separate admin user for our team instead of sending your personal login.
We also need the website URL, hosting provider, staging environment if one exists, backup process, important plugins, theme notes, and any areas we should not change without approval.
Request checklist
| Section | Ask for |
|---|---|
| WordPress login | Admin user email, login URL, role, temporary password or invite |
| Hosting | Provider name, control panel access, staging access, backup location |
| Site context | Theme, page builder, critical plugins, custom post types |
| Safety | Latest backup, change freeze dates, approval owner |
| Integrations | Forms, ecommerce, CRM, analytics, caching, CDN |
Permission notes
Ask for a named user account whenever possible. Shared passwords are harder to revoke, harder to audit, and more awkward when a project ends.
Portal upgrade
Kicklayer lets you request WordPress access as part of the same onboarding flow as content, brand files, and approvals, so the client sees one checklist instead of several separate emails.
Client-ready request
A version you can paste into an email, Slack thread, or Kicklayer portal.
Hi [client name], please create a separate WordPress user for [agency email] and send the login URL, role, staging details, hosting provider, backup process, theme or builder notes, and plugin constraints. If admin access is not appropriate yet, editor access is enough for content review.
How to structure the request
Break the ask into fields a client can answer cleanly, rather than a single vague upload request.
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.
Client request breakdown
These are the asks that make the request specific enough for the client to complete without a follow-up loop.
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.
Make the request easier to complete
Small wording choices change whether a client sends useful material or another incomplete reply.
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.
When the checklist becomes 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.