Your organisation should have appropriate control of its domain registration, hosting, website administration and recovery contacts. A developer can manage those services for you, but the arrangement should leave you able to renew, recover and hand over the website.
Start by separating the accounts. Paying for a website, holding its administrator password and being the domain registrant are different things. A useful handover makes each responsibility clear.
Map the accounts behind the website
List the domain registrar, DNS provider, hosting service, content management system, business email and any payment or external services. One supplier may manage several of these, but that does not make them one account.
| Account or asset | What to establish | Evidence to retain |
|---|---|---|
| Domain | Registrant details, renewal owner and account access | Registration and billing records |
| DNS | Where records are managed and who can change them | Provider and authorised administrators |
| Hosting | Service arrangement and recovery route | Plan, renewal and support details |
| Website | Administrator access and appropriate staff roles | Named users and handover record |
| External services | Business control of integrations and billing | Service owners and renewal responsibilities |
Understand what domain registration means
ICANN describes the registrant as the person or entity registering a domain under an agreement with a registrar. The registrant manages settings through that registrar and has renewal and management responsibilities. Reference: https://www.icann.org/registrants.
For a business website, ask whose details are recorded and how the organisation can manage the registration. A supplier’s technical contact role should not be confused with the organisation’s agreed control of its name.
Domain extensions and provider arrangements can have different rules. If registration details need changing, check the relevant registrar’s process first. A hosting move does not necessarily require a domain transfer.
Use recovery details the organisation can maintain
A website can become difficult to recover if every account depends on a former employee’s personal email address or phone. Choose recovery contacts deliberately and keep them current.
Avoid making the only recovery route depend on a mailbox that fails when the website’s hosting expires. Discuss an appropriate alternative with the provider. Protect administrator accounts with strong, unique credentials and supported additional authentication.
Keep credentials in a suitable password manager. A general project spreadsheet can record who controls an account without containing the passwords themselves.
Give suppliers the access needed for their work
Use named users and supported delegated access where practical. Someone editing news does not necessarily need hosting control. Someone maintaining the server may need access that a content editor does not.
Record why access was granted and review it when an engagement ends. Removing a supplier’s access should follow a working handover, with replacement support and recovery arrangements ready. Do not lock out the only person who knows how the system is operated before collecting the necessary information.
A hypothetical handover problem
Imagine a company that can edit WordPress pages but cannot access the domain registrar. Its developer is unavailable when the registration needs renewal. The WordPress password does not resolve that separate account problem.
The first task is to identify the registration account, existing records and provider recovery process. Rebuilding the website would not restore control of the domain. This is an illustrative scenario, not a report about a named client.
My website care and technical support can include reviewing the current arrangement and identifying handover gaps.
Separate access from rights to the work
Administrator access does not, by itself, answer every question about source code, photographs, content or licensed software. The project agreement should explain what is delivered, what you may use and which third-party licences continue separately.
Ask about premium themes, plugins, fonts and stock assets. A licence managed through an agency account may need a different arrangement when support ends. Where a dispute concerns contractual rights, obtain advice suited to that agreement.
My website development service can be scoped with those delivery and support responsibilities made explicit.
Maintain an account register after launch
- Name the business owner responsible for each renewal.
- Record the provider and appropriate recovery route.
- Review staff and supplier access when roles change.
- Check that backup access does not depend on one unavailable person.
- Keep billing and contact details current.
- Include account handover when changing suppliers.
Review the register periodically and before a redesign or migration. Its purpose is to make the website manageable throughout its life.
Frequently asked questions
Can my developer pay for hosting on my behalf?
Yes, under a clear arrangement. Confirm the service, renewal terms, access, backup responsibilities and exit process.
Must every staff member be an administrator?
No. Assign roles around actual tasks and keep high-level control with appropriate authorised people.
What should I request first if access is unclear?
Ask for an account and asset register, renewal information and an agreed handover plan. Start with the records rather than changing systems blindly.
Discuss your next step
For help applying this to your organisation, share a short description of your situation and the decision you need to make.





