How to get website access from clients without asking for passwords
By The Onbo team · Updated
Short answer
Ask for delegated access instead of passwords. Most hosting companies, domain registrars and website platforms let the owner invite you as a user with a specific role. List what you need (hosting, domain DNS, the website admin, analytics), send the client short instructions for each invite, and remove access when the work ends.
At some point every website project needs access: to the hosting, the domain, the old site, the analytics. The quick route is asking the client to email their password. It’s also the route that creates the most risk for both of you. A short access plan gets you what you need without anyone sharing a login.
Why shouldn’t you ask clients for passwords?
- The password is often used elsewhere. Clients reuse logins, so one shared password can expose other accounts.
- You inherit responsibility. If the account is misused later, you were one of the people holding the key.
- Two-factor codes get in the way. The client’s phone receives the code, so you end up waiting on them anyway.
- Access never ends. A shared password keeps working long after the project, unless someone remembers to change it.
- It looks careless. Clients notice when a professional asks for a password in a form or an email.
Delegated access solves all of these: you get your own login, with your own two-factor setup, and the client can remove it with one click.
What access does a website project need?
Ask only for what the work requires, and say when you need it:
| Access | What it lets you do | When you need it | How it’s usually granted |
|---|---|---|---|
| Website admin or CMS | Build and edit pages | From the start of the build | Invite you as an admin or editor user |
| Hosting | Upload files, set up the site, manage backups | During the build | Team or developer access, or a separate limited login |
| Domain and DNS | Point the domain to the new site | At launch | Delegate DNS access, or the client changes records you provide |
| Analytics and search tools | Set up tracking and verify the site | Near launch | Add you as a user with an appropriate role |
| Email or forms services | Connect contact forms | During the build | Add you as a user, or the client connects it |
If the platform offers no way to invite a user, the client can create a separate account for you with limited permissions, rather than sharing their own.
How do you ask for access?
Send one message that lists every item, why you need it and how to grant it. Keep it out of your onboarding questionnaire: access should be arranged directly with the client, not typed into a form.
To build your site, I’ll need access to three things. For each one you can invite me as a user, so you never need to share a password:
- Website admin: please invite [email] as an administrator.
- Hosting: please add [email] as a team member or developer.
- Domain: at launch, I’ll send you the DNS records to add, or you can delegate DNS access to [email].
You can remove my access at any time. I’ll remind you to do so when the project ends.
For example, a freelance web developer might send this message the day the deposit is paid. The client adds them to the hosting and the website platform in ten minutes, and the domain change waits until launch week, when the developer sends the exact records to add.
What if the client doesn’t know where things are?
This is common, especially for older sites. Help them find out:
- Ask who set the site up. The original designer or an IT contact may hold the accounts.
- Look up the domain registrar using a public lookup tool, so the client knows where to log in.
- Check billing emails. Hosting and domain renewals usually arrive by email, naming the provider.
- Plan a recovery route if nobody has the login: the provider’s account recovery process, done by the client as the owner.
Agree in your contract or kickoff notes that the client owns their accounts and is responsible for granting and removing access.
An access checklist
- List every system the project touches
- Note the access level and timing for each
- Ask for invites, never passwords
- Keep access requests out of questionnaires and forms
- Use your own login with two-factor authentication
- Record who granted what, and when
- Confirm domain changes at launch with the client
- Hand over any accounts you created on the client’s behalf
- Ask the client to remove your access when the project ends
- Confirm removal in writing
Access is one step of a website project kickoff; see the website client onboarding checklist for the full sequence, and client onboarding for web design agencies for the agency view.
If the domain itself sits in a previous designer’s account, see when the domain is registered by the previous web designer.
Where Onbo fits
Onbo handles the parts of website onboarding that belong in a client flow: the client accepts your agreement, pays the deposit, answers your website questionnaire and uploads brand files into your own Google Drive, all from one link. Onbo never collects passwords or logins, so access stays a direct conversation between you and your client. Try it free for 30 days; see pricing.
Questions
How do I get access to a client's hosting without their password?
Ask the client to invite you as a user from their hosting account, if the host supports it, or to create a separate login with only the permissions you need. Many hosts offer developer or team access for this.
What access do I need for a website project?
Usually the website admin or CMS, hosting or file access for the build, DNS access at launch, and analytics or search tools. Ask only for what the project needs.
Should I keep access after the project ends?
Only if you're contracted for ongoing work. Otherwise ask the client to remove your access and confirm it in writing.