Ask for the admin login before launch day, not after

What admin access actually consists of

The invoice for the final payment sits in your inbox, and you haven't logged into your own website yet. Not once. Admin access is the plainest, most concrete form of ownership there is: a URL, a username, and a password that gets you into the backend of the site you paid for.

That's really it. Three pieces of information, none of them complicated, and none of them requiring anything technical from you beyond typing them into a browser.

A business owner who has never logged in isn't unusual, and it isn't a sign of anything wrong with the site. It just means one specific step got skipped, and it's an easy one to fix once you notice.

Make it the first thing you do after launch, not something you get to eventually. Eventually has a way of never quite arriving, especially once the daily work of running a business takes over again. Ten minutes on launch day is worth more than a month of good intentions that never quite turn into action.

It isn't a metaphor and it isn't implied. It's a login screen, and either you have working credentials for it or you don't. There's no partial version of this. A site you can't log into is a site you don't control, no matter how nicely it was built or how proud you are of the result.

The login itself costs nothing to hand over. There's no technical reason it should ever be delayed. Setting up a second administrator account takes minutes on almost any platform in use today.

If a designer resists sharing it, ask why, directly, and listen closely to the answer. A good reason exists sometimes. A vague one is worth pressing on further.

The difference between admin access and full ownership

A password gets you into the dashboard. It doesn't transfer the domain, the hosting account, or the underlying code — those are separate control points with their own accounts and their own logins. Who owns your website breaks down the full set.

Admin access is the piece you'll actually use every week: editing a page, checking a form submission, publishing a post. It sits on top of the other four, not in place of them. Having it doesn't mean the rest is settled, and treating it as proof of full ownership is a common, understandable mistake.

Think of admin access as the front door key. It's essential. It's also not the deed to the house. You can hold one without the other for years and never notice, until you try to sell the house.

Ask for both, in the same conversation, so neither one gets treated as covering the other by default.

Why this gets requested after launch instead of before

Most buyers don't think to ask for login credentials until the project is basically finished, because until then there's nothing to log into. By the time the site is live, the final invoice is already the thing on everyone's mind, and access gets treated as an afterthought.

That gap between launch and actually receiving a working login is exactly where problems start. It's a short window, but it's the window where a request can quietly slip through the cracks on both sides.

Ask for it as a deliverable, not a favor, and put a date on it: access transfers on or before the final payment, not sometime after. Write the date down. Refer back to it if the date passes.

A designer who plans to hand over access anyway loses nothing by agreeing to a date. Resistance to naming one is information on its own.

Confirming access actually works, not just receiving a password

Receiving credentials in an email is not the same as confirming they work. Log in the same day you get them. Do it before you reply to say thank you.

Check that the account has full administrator rights, not a limited editor role that can change text but not settings, users, or plugins. That distinction matters more than it sounds like it should.

If two-factor authentication is set up, confirm you control the phone number or app it's tied to, not the designer's. Can you edit your own website once it's built depends entirely on whether that login actually does what it's supposed to.

Test one real action while you're logged in, not just the login screen itself. Edit a line of text, save it, and confirm the change appears on the live page.

Do this once, right away, and you'll never have to wonder later whether the access you were given actually works when it counts.

What to do if access is withheld

If access is delayed past the date agreed in writing, put the request in writing again. Reference the agreement. Set a clear deadline, and say plainly what happens if it passes.

Stay factual. A dated, specific request is harder to ignore than a frustrated one, and it builds a record you may need later.

Keep every message. A short paper trail, sent in plain email rather than a chat app that disappears, is worth more than it feels like in the moment.

Most of these situations resolve once a clear, written deadline is on the table. Very few designers want an unpleasant paper trail sitting in their inbox for long.

What to get in writing before you pay for a website is worth reading before you ever reach this point, because a documented request is a very different conversation than a verbal one. If a designer has already gone quiet, what happens if your web designer disappears covers the recovery options that still exist even without their cooperation.

More from the blog

All posts