You do not have to ask us any more. Add a developer, a colleague or a client to any website you hold, add as many people as you need, and take them off again the moment the work is finished. It happens the second you press the button.
There is no cap and no counter. This is not a favour you use up.
One website can have as many people on it as the job needs: a developer, the designer they brought in, your marketing person, and your own second login. Add them one at a time, whenever you want, and remove any of them on their own without disturbing the others.
The same goes across your sites. If you hold ten websites you can share all ten, or three of them, or a different person on each. Nothing is deducted from anything.
It works in both directions too. If somebody else adds you to one of their websites, it appears in your own list under “shared with you”, so an agency and a client can each hold their own sites and still work on each other’s.
The one rule worth knowing: everyone you add needs their own free 365i account, and only whoever holds the plan can change who is on it.
Three jobs, one mechanism. Nobody has to send a password over email.
They need the control panel for the site they are fixing, and nothing else. Give them that one site for the length of the job, then remove it. No shared password to rotate afterwards, and no wondering months later whether they still have the keys.
Staff and contractors get their own named logins to the sites they actually work on. When somebody leaves, you remove that person rather than changing one password and telling everyone the new one.
Because a grant covers one package, an agency can give a client access to that client's website without revealing a single other site on the plan. The client sees their own site. They do not see your portfolio, and they cannot see what anyone else pays.
"Everything they need and nothing else" is a slogan. Here is the actual boundary.
| They get | They never get |
|---|---|
| The control panel for that one website | Your billing, invoices or payment details |
| Its files, database and mailboxes | Any other website on your plan |
| Backups and restore points for that site | Your plan, contract or renewal |
| Its staging site, if the plan includes one | Your domain names |
| Their own named login, with their own password | Your VPS, cloud servers or SSL certificates |
Four steps, no support ticket, and nothing that expires while you wait for someone to accept.
The person you are adding needs their own 365i login first. It is free and takes a minute at my.365i.co.uk/register. This is the part people miss: use the address they sign in with, not the address on their email signature.
Open Manage website access and enter your own address. We email you a one-time link that expires in thirty minutes. There is no password to type on the page, which means there is no password to intercept.
Choose the one site you want to share, type their address, and add it. Access is live immediately: there is no invitation sitting in a queue waiting to be accepted, and nothing for you to chase.
You, the person you added, and our support desk are all emailed on every change. Nobody gains or loses access to your website quietly, and the same applies when you remove it.
Plenty of hosts let you do this. We are not going to pretend otherwise. What differs is how long it takes to happen.
| Platform | Scope of access | How it takes effect |
|---|---|---|
| 365i | One website package | Immediately, adding and removing |
| SiteGround, Kinsta, WP Engine, Cloudways | Per site or per application, much like ours | They have to accept an invitation or activation email first |
| Hostinger | Everything on the plan, unless you are on their Agency product | They have to accept an email invitation first |
| GoDaddy | Delegated at account level rather than per site | They have to accept a delegate invitation first |
| Traditional cPanel hosts | Sub-accounts get email and FTP, but cannot sign in to cPanel at all | Immediate, but there is no control panel login to give |
The part most pages skip, and the part that matters once the work is finished.
Open the same screen, find the person, remove them. It takes effect straight away and everyone is emailed.
Then the part that is not ours to do for you. Removing someone’s hosting access does not touch anything they created inside the website:
No hosting control panel can reach inside your website and tidy those up, ours included. Work down the list yourself before you call the job closed.
Most do: contact form submissions, customer records, orders. Letting somebody into the website lets them into that data, and the ICO expects it to be reachable only by authorised people acting within their permitted scope. Per-site access supports that. It does not complete it.
A developer processing personal data on your instructions usually needs a written contract under Article 28.
Letting somebody outside the UK reach that data can count as a restricted international transfer, even though the site stays on UK servers.
If personal data is exposed you assess and record it, and a reportable breach carries a 72-hour deadline.
Every point above links to the ICO’s own guidance. This is practical guidance from running a hosting company, not legal advice: if the data is sensitive, take proper advice.
Ask them to create a free 365i account, then open Manage website access, sign in with the one-time link we email you, pick the website and enter their address. They get their own control panel login to that one site. The whole thing takes about a minute and needs no support ticket.
Yes, and you should. Sharing your own password gives someone your billing, your contract, your domains and every other site on your plan, and it cannot be undone without changing that password and telling everyone else the new one. Shared access gives them a separate named login of their own, limited to one website, that you can remove on its own.
That is exactly how it works. Access is granted per website package, so the person you add sees the single site you chose. Every other site on the plan stays invisible to them, which is what makes it safe for an agency to give one client access to that client’s own site.
No. Shared access covers the hosting package for one website and nothing else. Billing, invoices, payment details, the plan itself, the contract, your domain names, your VPS or cloud servers and your SSL certificates are all outside what is shared.
They need a free 365i account, not a hosting plan. There is nothing to pay and no contract created. If the address you enter is not already a 365i login, the change is refused rather than half-applied, and we tell you so you can check you have the right address.
Open the same screen, find them on the list and remove them. It takes effect immediately and everyone involved is emailed. Do remember that this removes their hosting access only: if they created a WordPress administrator user, an SFTP login, a database user or a plugin API key inside the site itself, you need to remove those separately.
No. The contract, the plan and the billing stay entirely with whoever holds them. Only the contract holder can share or remove access, a contract holder cannot be removed by anybody, and nothing about sharing a site transfers ownership of it.
Yes. You can add more than one person to the same website, each with their own named login, and remove any of them individually. That is the point of named access rather than a shared password: when somebody leaves, you remove that person instead of changing one password for everyone.
Safer than the alternative, which is usually emailing them a password. Two things are worth doing first. Take a restore point before anyone starts, because somebody who can edit a website can break a website. And if the site holds personal data, remember that letting a contractor reach it may need a written processor contract, and may count as an international transfer if they are outside the UK.
Yes, and this is one of the better reasons to use it. Because a grant covers one package, a client added to their own site cannot see any other site on the agency’s plan, cannot see the agency’s billing, and cannot see what anybody else is paying.
We built this because our own team was doing it by hand. Customers would ask us to give their developer access to a site, and somebody here would go and make the change for them, then again when the job finished and it needed taking off. It was quick work, but it sat between the customer and something they should never have had to ask permission for. Now they do it themselves, and we still get the email when it happens.
By Mark McNeece, Founder of 365i. Last reviewed 30 July 2026.
Editorial integrity: read our editorial standards.
Sharing website access is included on every 365i hosting plan, from £5.99 a month. There is nothing to switch on and nothing extra to pay.
