yodai Academy Domain and email

Academy › Publishing › Domain and email

The account you log in with can't be your everyday one

Create a new account, just for the business, and put the domain, the email, and the other services under it before giving anyone else access.

By Yodai · Published on September 6, 2026 · Updated on October 12, 2026

7 min read

You registered your business domain three years ago, on a Sunday night, with the Google account you use for everything: your phone photos, your bank, the family group chat. It worked. Nobody asked any questions.

Now the business has grown. You need someone else to be able to get into the domain settings, set up a new email address, renew the payment if you're ever unavailable. And that's when you realize giving that access means handing over your personal password. The one for your photos, your bank, and your family.

That's the sign it's time to separate things. Not after something happens: before it happens.

What's hanging off a single account

The domain, the business email, the website, and sometimes even the account you use to get paid if you log into it with the business email, all of that depends on the account where the domain is registered. That account holds the domain's contact email, which is where renewal notices go. For a .es domain, if your registrar hasn't requested the renewal five days before it expires, Dominios.es notifies the administrative contact. For a .com or any other generic domain, the notices go to the registrant's email, and if the domain expires without being renewed, the registrar cuts off its service and the website and email that depend on it stop working, as explained in the ICANN guide on expired domains. If that account is your personal Gmail, every one of those services depends on nothing happening to you: not losing your phone, not someone trying to get into your account by pretending to be you, not deciding one day to disconnect for a few days without telling anyone.

If the business has partners, the problem runs the other way. If the account is yours, control of the domain doesn't belong to both of you, even if the contract says the business does. To the registrar, what counts is who's listed as the registrant, not who has signing authority: according to the ICANN Transfer Policy, the registrant is the only party who can approve or deny moving the domain to another registrar, and changing the registrant requires their confirmation. A partner who joins six months in inherits a business whose domain and email hang off an account they can't open. ICANN says so in its FAQ for registrants: anyone who isn't the registrant or the administrative contact may not have access to the domain.

What matters is who owns the account that holds the business's domain and email. Not the business in the abstract: one specific account, with one specific password, that only you know today.

Personal account or business account

The question isn't whether you trust the person you're about to give access to. It's what happens the day that person is gone, or you're gone, or the business changes hands. A personal account handles the first question fine and the other three poorly. That's why it's worth deciding this by picturing the business two or three years out, not where things stand today.

What happens depending on whose account it is
Personal account (your regular one)
  • One access problem on your end locks up the whole business
  • Giving someone access means giving them the password to everything else too
  • With partners, the domain is registered to whoever signed up for it, not to the company
  • Changing the registrant on the day you sell or close depends on you confirming the change
New account, just for the business
  • Shared without touching anything of your own
  • You can grant and revoke access without changing your own password
  • If the business is incorporated, the domain can be registered to the company, not to a person
  • Transferring or selling means changing the registrant, not negotiating with your personal account

Which one to pick: Choose the business account as soon as the domain needs to outlast a single person: a partner, an employee, a successor. The personal account only works if the business is just you, with no plans to grow or sell, and even then, the day you hire your first employee, you migrate.

How it's done, in an afternoon

Four steps to separate the account from the business
  1. 1Open a new email account, just for this
    An account that doesn't depend on your personal phone number or your usual recovery account. Don't use it for anything else: not for online shopping, not for signing up for a newsletter. It exists for one thing: running the business.
  2. 2Register the domain under it, or transfer it if it already existed
    If the domain is already in your personal name, you can change the registrant's details without losing the domain or having to buy it again: the email becomes the one on the new account, and if the business is incorporated, the registrant can become the company itself. For a .com or any other generic domain, changing just the registrant's email already counts as a change of registrant: the registrar asks both of you to confirm, and once you do, it has one day to make the change. For a .es domain, the change of registrant is called a transmission, confirmed by the new administrative contact from the Dominios.es panel. It's done once and you never have to touch it again. The change affects the registrant's details, not the servers the domain points to, so the website keeps working: the only thing that changes is who's listed as the domain's owner.
  3. 3Put the business email and other services under that account
    The email you use to talk to customers and the services you use for your website need to live under the business account, not your everyday one. For new ones, sign up with it. For the ones you already use, change the login email or the recovery email if the service allows it; if it doesn't, don't share your password: give each person their own access wherever possible. None of them move over automatically with the domain: each one gets changed separately.
  4. 4Store the password somewhere someone else can inherit it
    A password manager shared with the right person, not a note in your head or on your personal phone. If you're the only one who knows it, you haven't separated anything: you've just moved the same problem somewhere else.
How long it takes to move the domain from your account to the business's
  • FirstYou request the ownership change with the domain registrar, using the new business account's details.
  • ThenThe registrar asks for confirmation both from you, as the outgoing registrant, and from the incoming account, for example with an email that includes a code. Each registrar sets its own deadline to confirm, which can't be more than 60 days: if you don't confirm in time, the request doesn't go through.
  • One dayOnce both confirmations are in, the registrar makes the change within a day at most and notifies both of you. From there, the domain can't be moved to another registrar for 60 days, unless yours let you waive that lock before the change. If you also want to switch registrars, the Transfer Policy recommends doing that before the change of registrant.
  • When it's doneThe domain now shows the new registrant's details. The business email and other services don't move over with it: each one gets changed separately, as in step 3.
What to call this account
admin.yourbusiness@gmail.com or a similar address on another provider, but never one on the domain it's going to support, like accounts@yourbusiness.com: ICANN recommends registering the domain with an email that isn't tied to it. Not anasbakery@gmail.com or a person's name: the business name followed by what that account is for, admin, accounts, domain.
The mistake that gets expensive two years from now
Almost no one makes this separation early on, because it already works fine without it. The cost doesn't show up until the day you actually need it: a partner who leaves angry, a personal account someone gets into without your permission, a succession because you're retiring or because something worse happens. On that day there's no quick fix. If the domain is registered under someone else's name, ICANN points you back to them to get the login credentials or have the registrant changed, and to your registrar if you can't track them down. For a .es domain that changes hands through a succession, Dominios.es requires proof with supporting documents. And if the domain expires in the meantime and no one renews it, the registrar cuts it off: the website stops loading, the business email stops working, and any customer who writes in gets no response. You make the separation before you need it, not after, because afterward it's no longer up to you; it's up to a verification process you don't control. And the customer who wrote that week and got no response might not wait around for the paperwork to get sorted out; they may just go somewhere else.

With the account separated, the next question is whose name is on the email you use to invite each person in. That's the next lesson.

What you'll walk away with
  • New email created, just for the business, not tied to your personal phone
  • Domain registered or transferred under that account's name, not your regular Gmail
  • Business email and other services tied to the new account, not your everyday one
  • Password stored in a shared manager, not just in your head

Three cases to decide

Answer before opening each one. If one gives you trouble, go back to the section that explains it.

1. You run the business by yourself, no partners or employees, and you're not planning to sell it. Do you need to separate the account now?

You can wait. A personal account works fine as long as the business depends on just one person: you. The day you hire someone or bring on a partner, migrate the domain and email to the new account that same month, don't put it off.

2. You have a 50/50 partner, and the domain has been registered under your personal Gmail from the start. What changes with a separate account?

Access no longer depends on your personal password, and if you also list the company as the registrant, the domain belongs to the business, not to whoever registered it. Without that, even if the contract says the business belongs to both of you, real control over the domain and the email stays in your personal account, and a partner can't rely on an arrangement that depends on your password.

3. You're setting up the business account and can't decide between anasbakery@gmail.com and admin.anasbakery@gmail.com. Which one do you use?

admin.anasbakery@gmail.com. Even if you already have an email address on your own domain, like accounts@anasbakery.com, the account that holds the domain shouldn't be on that same domain: if the domain stops working, that email address goes down with it. The name carries the business and the account's role, never a person's name: the account has to outlast whoever created it.

That same rule, the role and not the person, is exactly what's going to be missing from every inbox you hand out across your team.

Sources

  1. Transfer Policy. ICANN, version updated February 21, 2024, mandatory as of August 21, 2025, and in effect as of October 2026 (accessed October 2026).
  2. FAQs: Domain Name Registrant Contact Information and ICANN's Whois Data Reminder Policy (WDRP). ICANN (accessed October 2026).
  3. 5 Things Every Domain Name Registrant Should Know About ICANN's Expired Registration Recovery Policy (ERRP). ICANN, 2018 (accessed October 2026).
  4. Do You Have a Domain Name? Here's What You Need to Know, part IV: "How to Protect Your Domain Name Against Domain Hijacking or Unauthorized Transfers." ICANN, 2018 (accessed October 2026).
  5. Changing the Domain's Registrant. Dominios.es, Red.es (accessed October 2026).
  6. Renew Your Domain. Dominios.es, Red.es (accessed October 2026).

In Yodai you connect the domain you already have to your site, and it stays registered where it is, in your name. See how your own domain for your website works.

NextAn email address for the role, not the name