How to add another contact to your account

Sharing your own login with a developer, a business partner or an accountant is the easiest way to give someone access, and also the easiest way to lose track of what they actually did on your account. Adding them as a separate contact gives them their own login and, usually, their own limited set of permissions — which is a better arrangement for both of you.

Why a separate contact beats a shared login

A shared password means shared responsibility for keeping it secure, no way to tell who made a particular change, and a password reset that affects both of you every time either of you needs one. A dedicated contact solves all three: their own credentials, their own activity, and access you can remove without touching your own login at all.

How to add a contact

1. Sign in to your client area

   Use your own login as the account owner.

2. Find the contacts or sub-accounts section

   This is usually under account management or account settings, separate from your own profile details.

3. Add their name and email address

   Use an email address that belongs to them, not a shared inbox — the point is that their access is genuinely theirs.

4. Choose what they can see and do

   Depending on what your account offers, permissions typically cover things like viewing invoices, opening support tickets, or managing specific services. Give them only what the situation actually requires.

5. Send the invitation

   They will typically receive an email to set up their own password and sign in separately from you.

What a contact can typically do

Exactly what is available differs by account type, but additional contacts are generally there to let someone act on the account without being the account owner — viewing invoices, raising support tickets, or handling day-to-day service management, according to whatever permissions you have set for them. What a contact cannot normally do is take over the account entirely or lock out the actual owner, which remains you.

Removing a contact

When a developer's contract ends or an accountant changes, remove their contact from the account rather than leaving old access sitting unused. This is the same principle as revoking a password you no longer want active — unused access is a risk with no upside, and removing it takes moments from the same section you added them in.

If you are handing the whole account over, not just adding a helper

Adding a contact gives someone a role alongside you as the owner; it does not change who owns the account. If you actually want to transfer ownership entirely — selling a business, handing a project to a client — that is a different and more permanent step. See how to transfer your account to someone else for that process instead.

Common reasons people add a contact

• An accountant or bookkeeper who needs to see invoices and payment history without touching services or support tickets.
• A developer or agency who needs to raise support tickets on your behalf while a project is underway, without needing billing visibility.
• A business partner who shares responsibility for the account day to day and should not depend on one person's password to act.
• A second point of contact in case the account owner is unreachable, so an urgent billing or renewal notice does not go unseen.

Each of these calls for a different level of access, which is exactly why setting permissions per contact — rather than an all-or-nothing invite — matters. A bookkeeper does not need to manage your hosting plan, and a developer chasing a support ticket does not need to see your payment history.

Communicating the change

Once a contact is added, tell them plainly what they can and cannot do on the account, and let them know you may adjust or remove that access later without it being anything personal — it is account hygiene, not a judgement on them. A quick conversation up front avoids any confusion later about who is expected to do what.