Knowledge base

Giving someone access to my account

Invite them properly instead of sharing your password — and choose the role that fits what they actually do.

Never share your sign-in. An invited user has their own password, their own two-factor, and their own line in the audit log — so you can see who did what, and remove one person without changing anything for everybody else.

Inviting

Organisation → Team → Invite, enter their email, choose a role, send. They set their own password; you never see it.

Choosing a role

Owner — everything, including billing and closing the account. Keep this to yourself and perhaps one other person.

Admin — everything operational: sites, domains, DNS, backups. No billing.

Developer — sites and deployments, no billing and no user management. The right role for an agency or a contractor.

Billing — invoices and payment methods, and nothing that touches a site.

Read-only — can see, cannot change. Good for a stakeholder who wants the dashboard without the risk.

A freelancer, an agency or a client who should reach only some of your sites does not belong on Team at all: share those sites from Organisation → Delegated access instead. See Sharing some of your sites with a freelancer, agency or client.

Removing someone

Organisation → Team → remove. Their access ends immediately, in every session they have open. Do this the day somebody leaves, not the week after.

What they cannot do

An invited user cannot change your billing details unless you gave them Billing or Owner, and cannot invite an Owner unless they are one.

Latest from the blog

What we have been writing about hosting, SEO and running sites at scale.

SEO and Link Building from the Hosting Layer: A 2026 Operator's View

How hosting shapes indexing and link equity in 2026: keeping pages indexed, vetting aged domains before you build on them, link building without a footprint, and an honest line on what infrastructure can and cannot do for SEO.

Read the post →

Making WordPress Fast and Secure: A Performance and Plugin Checklist

A practical checklist for fast, secure WordPress: server-level caching, a per-site object cache, the handful of plugins worth running, keeping the stack current, and the WooCommerce pages you must never cache.

Read the post →

How to Choose Managed Web Hosting in 2026: A Buyer's Guide

What actually separates good managed hosting from a cheap box with a control panel — migrations, backups, isolation, real caching and honest scaling — and how to judge it before you commit.

Read the post →

Read the blog →

Still stuck?

Support is included on every plan, the desk is open 24 hours a day, and you can write to us in any of our 58 languages — we answer you in yours.

Contact support → All articles →