Giving a Web Agency Access to WordPress, Hosting and Your Domain Safely
Short answer: Give the agency its own named user in every system that supports it, and keep ownership of the accounts that would be hard to recover. In practice that means a separate WordPress administrator account for the agency, a sub-user or delegated access in your hosting panel, and DNS-only help at the registrar rather than your registrar password. Add the agency to Google tools as a user, not as an owner. Share anything that has no user system through a password manager, and write a removal checklist on day one so access ends cleanly when the project does.
The principle: their own login, your ownership
When an agency starts, it is tempting to email a document full of passwords. That causes three problems: you cannot see who changed what, you cannot remove one person without changing the password for everyone, and if the relationship ends badly the agency may hold the keys to your domain.
Two rules avoid most of this:
- Every person or company gets its own login wherever the service allows it.
- The business owns the top-level accounts: domain registrar, hosting, Google and payment accounts are registered to a business email you control.
Account-by-account table
| System | Recommended access for the agency | Keep with you |
|---|---|---|
| WordPress | Own Administrator user for the agency, or Editor if they only add content | Your own Administrator account, never shared |
| Hosting | Sub-user, collaborator or delegate access, if the host offers it; SFTP user scoped to the site folder | Billing and the main account login |
| Domain registrar | No login. You change DNS records yourself on request, or use the registrar's delegate or DNS-manager role if one exists | Account, transfer lock, auth code |
| DNS provider (e.g. Cloudflare) | Member with DNS-only permissions on the one domain | Account ownership, billing |
| Google Search Console | Full user, not owner | Verified owner |
| Google Analytics | Editor or marketer role on the property | Administrator |
| Google Business Profile | Manager | Primary owner |
| Email marketing, CRM | Separate team user with limited role | Owner and billing |
| Anything without users | Shared item in a password manager vault | The vault itself |
WordPress: create a named administrator
- Go to Users > Add New in WordPress.
- Use the agency's own email address (preferably a shared support address at the agency) and a name like "Agency name, support".
- Choose the role. Administrator is needed for installing plugins and themes. Editor is enough for content work. WordPress describes what each role can do in its roles and capabilities guide.
- Ask them to enable two-factor authentication through whichever security plugin your site uses.
- If several people at the agency work on the site, ask for separate users rather than one shared account.
Before handing over, take a full backup of files and database, as described in WordPress's backup documentation, so you have a known starting point.
Hosting: delegate rather than share
Many hosts have a way to add a collaborator, sub-user or technical contact who can manage sites without seeing billing. Look in the account or team settings of your hosting panel.
- If the host supports it, invite the agency with access to the specific site only.
- If not, create an SFTP or SSH user limited to the website's folder and a separate database user if needed.
- Keep the main hosting login, which can cancel the account or change billing, for yourself.
- Ask the agency to work on a staging copy for big changes.
If the agency proposes moving the site to hosting on their account, decide this deliberately. It can be convenient, but make sure the contract says you can move the site and its backups away at any time.
Domain registrar: the account to guard most carefully
Your registrar account controls the domain itself. Whoever logs in can change nameservers, unlock the domain and request a transfer code. Losing it can mean losing your website and email.
- Do not share the registrar password.
- When the agency needs DNS changes, ask them to send the exact records (type, name, value, TTL) and add them yourself, or screen-share while you do it.
- If your registrar offers a delegated or DNS-only role, use that instead.
- Keep the domain's registrant contact as your business, with an email you check.
- Leave the transfer lock on.
Google tools: users, not owners
In Search Console, Analytics, Tag Manager and Business Profile, add the agency's Google account with a role below owner. Owners can remove other owners, including you. Check the user lists regularly for accounts nobody recognizes.
Password manager for everything else
Some services have no user system, such as an old FTP account or a plugin license portal. For those:
- Create a shared folder or vault for the agency in your business password manager.
- Share only the items needed.
- When the project ends, remove the share and change those passwords.
Avoid sending passwords by email or chat, where they stay in message history.
Removal checklist when the work ends
Write this list now and keep it with the contract.
- WordPress: delete the agency's user and reassign their content to your account when prompted.
- Hosting: remove the sub-user, SFTP and database users created for them.
- DNS provider: remove their membership.
- Google tools: remove their users from Search Console, Analytics, Tag Manager and Business Profile.
- Password manager: revoke shared items and rotate the passwords.
- API keys and app passwords created during the project: revoke them.
- Confirm you hold current backups and a copy of any custom code.
- Update any contact details at the registrar or host that point to the agency.
FAQ
Is it rude to refuse sharing the registrar login?
No. Experienced agencies are used to sending DNS records for the owner to add.
Should the agency be an administrator in WordPress?
If they install plugins or edit themes, yes. Their own administrator account can be removed cleanly later.
What about a site the agency already built on its own hosting?
Ask for the site files, database export and a list of licenses, and agree on how a move would work if you part ways.
How often should we review user lists?
Every few months and whenever someone leaves the project.
Before your next website project starts, we can help you set up access so the agency gets what it needs and the business keeps the keys.