When changing website developers, a question soon comes up: who can provide hosting panel access, renew the domain and hand over editing access? If one person outside your business handles all of these, start by documenting the current arrangements. A decision about a new website can come later.
Do not put passwords on this list. You need service names, responsible people and information on obtaining authorised access.
Separate the website address from its technical setup
The domain is the address, hosting provides the website’s environment and the CMS is the content management system. Email may be with another provider. Even if one company issues all the invoices, check your ability to manage each element separately.
For a .pl domain, the registrant’s details and the registrar through which the registrant manages the domain matter. NASK lists actions including changing delegation, renewal and transfer of service. The registrar sets the details of these procedures. NASK’s explanation.
Having a panel password alone does not establish who the registrant is. Check the account details, domain documents and information from the registrar. Public WHOIS does not show identifying details for a registrant who is a natural person. Data publication rules for the .pl registry.
Prepare a short list
For each element, record:
- the provider’s name and panel address;
- the business account and people with permissions;
- the address receiving notifications and recovery information;
- the renewal date and person responsible for payment;
- missing access or documents.
Add who can change domain settings and who is responsible for email. For the website, also note where the backup is and who arranges restoration.
Keep this list somewhere authorised people in the business can access. A note in a developer’s private notebook will not help you handle a renewal independently.
Agree the developer’s access
The person maintaining the website needs permissions to do the work. Agree which accounts they cover, their scope and what happens when the relationship ends. Where the service allows it, use separate accounts or invitations instead of a shared login.
Your business should know how to revoke unnecessary access and who handles account recovery. Check before changing developers, rather than waiting for an urgent offer update.
Organise access before deciding on changes
Before moving hosting or changing domain settings, establish what depends on them. The plan must also include email and other services in use. Missing access is no reason to guess settings or copy DNS records yourself.
With CyberKlucz, you can agree on taking over and organising an existing website. The starting point is the current access and responsibility arrangements. Describe which panels you can access and which are managed by the current developer. Do not send passwords in your first message.
