Your business should have clearly documented control of its domain, hosting and website accounts, with named people responsible for administration, renewals and recovery. A developer can manage the technical work, but the business needs a workable route to continue operating when a staff member or supplier changes.
Account ownership, day-to-day access and payment responsibility are separate questions. Resolve all three before launch. This is an operational planning guide, not advice about contractual ownership or a guarantee of account security.
Distinguish the services behind the website
A domain registration is not the same service as website hosting. The content management system, business email, analytics and third-party integrations may also have separate accounts. One invoice or login screen can make them appear connected even when different providers control important parts.
Ask the delivery team to identify the actual services in use. Record the provider name and business purpose in ordinary language. “Hosting account that runs the website” is more useful to an administrator than an unexplained vendor name.
Create a responsibility matrix without credentials
The following fictional example concerns a small consultancy. Each service record answers four questions: who controls it, who administers it, who pays for it and who acts if the primary contact is unavailable. Names would be added privately in the business's own records.
Domain registration
- Business control: a designated business representative verifies registration and account details with the provider
- Technical administrator: the nominated website administrator handles authorised technical changes
- Renewals: finance tracks the renewal date and payment arrangements
- Continuity: a second authorised business contact knows the provider's recovery process
Check the rules for the actual domain and registrar. ICANN's renewal guidance explains that renewal arrangements vary and should be checked with the registrar. Do not assume a particular grace period or process applies to every domain extension, including country-code domains.
Hosting and backups
The business records the provider and billing contact. The technical maintainer documents what is hosted, where backups are managed and who can request a restore. Finance knows whether hosting renews separately from other services. A backup person knows how to contact support if the main maintainer is away.
Website editing system
Give named editors the access needed for their tasks through the platform's supported account system. Record who can add users and who approves that change. An employee who updates service text may not need the same access as the person maintaining the software.
Email, analytics and integrations
Document each service separately. For an enquiry-email service, identify the destination, operational contact and person who can investigate delivery problems. For reporting tools, confirm the business can reach its own reporting information through an authorised account.
Check recovery while everyone is available
Ask each account owner to verify that recovery contact details are current and reachable. Follow the provider's supported recovery and authentication process. Keep passwords, authentication codes and recovery codes out of general project documents, shared spreadsheets and email threads.
Do not test continuity by locking someone out or changing live settings unnecessarily. A useful handover can record the supported process, authorised contacts and evidence that the business representative can access the account. Any sensitive changes should be handled deliberately by the authorised account holder.
Make renewals an assigned task
For each paid service, record the renewal date, person responsible, notification destination and how payment failures are escalated. Avoid recording full payment-card information. Check that reminders are reaching a monitored business contact rather than an inbox belonging to someone who has left.
Automatic renewal still needs an owner. Payment details can expire and contact information can become outdated. Schedule an appropriate administrative review based on the actual provider's arrangements and the importance of the service.
Plan supplier and staff changes
Before removing access, confirm who will take over the affected responsibilities. Review pending renewals, recent changes and support requests. Ensure essential documentation and agreed deliverables are available to the business. Then have an authorised administrator review and remove access that is no longer needed using the provider's process.
The objective is continuity with a clear record. Avoid making several unrelated account changes at once if nobody can explain their impact on the live website or email.
Walk through an absence scenario
Imagine the fictional consultancy's usual website contact is away when a renewal notice arrives. Finance recognises the supplier's name but does not know which service is affected. The notice was forwarded without its account reference, and the only person who understands it is unavailable.
A useful responsibility record would let finance identify the service, contact the authorised administrator through a known route and confirm the actual renewal status with the provider. Nobody should need to guess from a screenshot or send payment information to an unfamiliar address.
Run this discussion before there is a problem. Ask the backup contact to locate the non-secret service record and explain the next step. If the answer depends on a private message stored only on one person's phone, improve the documented route. This exercise checks organisational readiness without changing a live account.
Distinguish business control from unlimited access
Business control does not mean every employee needs administrator privileges. The owner needs an authorised route to the service and a clear ability to assign responsibility. Individual team members need access appropriate to the work they perform.
For example, a content editor may update page text, while a technical maintainer manages the implementation and a finance contact receives invoices. Record these as separate roles even if one person currently fills several of them. When staffing changes, the business can transfer responsibilities intentionally.
For a public site, raise these questions in the website development scope. A private system can introduce additional role distinctions; discuss the intended users and account lifecycle when considering web portals and dashboards. Neither arrangement should rely on an undocumented assumption that the supplier will handle everything indefinitely.
What belongs in the handover record?
Include the provider, service purpose, non-secret account reference, authorised business owner, operational contact and support route. Add renewal responsibility, relevant documentation location and known dependencies. Record that recovery arrangements have been checked, without copying authentication material into the handover.
Keep contractual questions separate. If the business and supplier disagree about ownership or transfer obligations, administrative notes cannot settle that dispute. Identify the unresolved issue and use appropriate professional advice rather than treating possession of a login as a complete answer.
A careful offboarding sequence
- List the departing person's responsibilities and current work
- Assign replacements and confirm their authorised access routes
- Review renewals, pending support requests and unresolved problems
- Transfer relevant documentation and agreed business records
- Have the authorised administrator review access that should end
- Check that the website's essential operation continues as expected
Common mistakes include removing the only functioning administrator before appointing a replacement, overlooking a separate email service and assuming cancelled supplier support also cancels hosting. Ask what each proposed change affects. Where the impact is unclear, resolve it with the actual provider or responsible administrator before acting.
Frequently asked questions
Can my developer manage the accounts?
Yes, if that arrangement is agreed. Document the business's access, renewal responsibilities, recovery route and handover expectations rather than relying on informal assumptions.
Does paying an invoice prove I control the domain?
An invoice alone does not establish the full administrative arrangement. Verify account and registration details with the provider and seek appropriate professional advice for contractual questions.
Should we share one administrator login?
Prefer the provider's supported named-user or delegated-access approach where available. Ask the administrator to document roles without distributing credentials.
What if the original supplier is unavailable?
Start with the provider's official support and recovery process. Gather non-secret account references and records the authorised business representative can supply.
Plan your next project with Tralionex
When discussing website development with Tralionex, include account administration and handover in the scope conversation. Confirm who manages each service after delivery and which ongoing responsibilities are separately agreed.
No comments:
Post a Comment