[To the blog](https://88lab.eu/en/blog/) [Websites](https://88lab.eu/en/category/ueb-sajtove/) # Website maintenance: access, backups and responsibilities Evgeny Dimitrov 3 October 2026 6 min read  In this article + [Let's discuss your project](https://88lab.eu/en/contact/) ## In short Site maintenance is reliable when you know who has access, how data is restored, and who handles each important task. Updates are only one part. You also need checks for forms and orders, working backups, hosting management, and a clear way to respond to problems. ## Who holds the keys to the site Imagine the domain needs to be renewed, but the notice goes to the email of someone you no longer work with. The site may be well built and still stop working. Such dependencies build up quietly: hosting registration, theme license, email account, or admin access. Make a list of the main systems: domain, hosting, administration, business email, analytics tools, external integrations, and licensed components. For each one, note the owner, recovery method, and renewal date. Do not put passwords in this shared document; store them in a suitable secure tool. The business must be able to regain control of the main accounts. The contractor gets the necessary rights for their work. A shared admin account for everyone seems convenient, but it makes tracking and removing access harder when someone leaves. ## Give the needed permissions, not all permissions The person who publishes articles rarely needs to change a payment integration or delete users. Separate content editing, technical work, and account management. Use individual profiles and extra login confirmation when the system supports it. In WordPress, this can start with [the standard roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/). They should be tailored to the specific plugins, because additional features can introduce their own permissions. Check with the real account what the employee can view and change. When you change partners, remove unnecessary accounts, update shared secrets, and confirm recovery contacts. Handover should also include information about integrations, backup schedules, and known issues. Sending over a password alone is not a full support transfer. ## A backup is useful if it can be restored A file with a date in the name provides reassurance, but it proves nothing yet. The backup may be incomplete, corrupted, or stored in the same place that will be affected in a problem. You need a plan for what is backed up, where it is stored, how many versions are kept, and how restoration is tested. For WordPress [the official backup guide](https://developer.wordpress.org/advanced-administration/security/backup/) covers the database and files. If you only have the images and theme but no current database, pages, settings, or orders may be missing. For other platforms and external systems, identify the relevant data separately. Choose a frequency based on how much loss you can tolerate. A showcase site with rare changes and a store with orders all day long have different needs. If you restore the store from yesterday, the orders after the backup will not automatically appear. You need to know where they can be reconciled and how payments and notifications will be handled. A test restore is best done in a separate environment. Note which version was used, what was restored, and which key functions were checked. The time it takes to get the site back depends on this process, the amount of data, and the issue. “We have a backup” and “we can restore service” are different claims. ## Updating with rollback options Before an important change, create a current backup and define how you will roll back to the previous working version. For a store or a site with integrations, test first in a separate environment when possible. Real payments and notifications should be restricted there so you do not create orders or emails by mistake. After an update, checking the homepage is not enough. Run a test inquiry, check search, login, and key integrations. For a store, go through variant selection, shipping, payment, and confirmation. External services may follow different rules, so include their settings too. Leave a brief report: what changed, how it was checked, and whether any questions remain. That way the next person will not have to guess why a component was turned off or why a setting is different. This is especially useful when more than one person works on the site. ## Assign work by name Often everyone assumes someone else is tracking the renewal, form, or product data. To avoid that, make a simple list of responsibilities. The roles shown are examples; replace them with real people or teams. Task Executes Approves or receives information Domain renewal Assigned employee Business owner Hosting and technical settings Technical partner Site owner Backups and restore test Technical partner The owner receives the report Updates and checks Technical partner The owner approves risky changes Content and product data Business editor The person who verifies the facts Receiving inquiries Sales team Sales owner Tracking check Analytics or marketing team Marketing Manager Incident Response Agreed Technical Team Designated Business Contact Add a request channel and a way to approve paid extra work to the list. Not every small text change needs to go through a complex process. But a design change, feature, or integration should have a clear decision on scope, price, and review. ## Monitoring should also catch work that has silently stopped The site may open, but the form may stop delivering inquiries. It may accept an order but calculate shipping incorrectly. That is why uptime monitoring should be complemented with checks of key actions. The list depends on the business, not on the number of installed tools. For a small business site, the main checks may be loading, forms, and contact links. For a store, add stock levels, variations, payments, and notifications. Use an appropriate test mode and clearly marked tests so you do not confuse the team with fake customers. It also makes sense to monitor speed after changes. A new image, external script, or extension can change behavior. [Google describes Core Web Vitals](https://developers.google.com/search/docs/appearance/core-web-vitals) as experience metrics, but a single lab result does not replace monitoring of real visitors and key pages. ## What to include in a maintenance agreement Separate first response from problem resolution. A “response within a certain time” may mean the request has been received and diagnosis has begun. Some causes require an external vendor or access that is still missing. The terms should describe how these cases are communicated. Separate an issue from a new request. A broken form is a problem to fix. A new field, new design, or new integration is a change that should be evaluated. For broader [Website maintenance](https://88lab.eu/en/website-maintenance/) scope, content, speed, and sales improvements can be included, but the specific work still needs to be clear. Finally, ask for a regular short report that you can actually read: completed tasks, check results, upcoming renewals, and decisions waiting on you. You do not need a list of technical terms. You need to know whether the site is working, where the risks are, and what comes next. ## frequently asked questions ### Is the hosting backup enough? It depends on what it includes, how many versions it keeps, where they are, and how they are restored. Check whether it covers all critical data and whether there is an independent copy based on the risk. Do a test restore before relying on it. ### How often should a site be backed up? Based on how often it changes and the acceptable data loss. A store with many orders may need more frequent copies than a brochure site. Also agree on how to compare data created after the last backup. ### Can support include content upload? Yes, if that is part of the agreed scope. Specify who provides the materials, who checks them, and how publishing is approved. Technical support alone does not automatically mean editing and entering all texts. ### What should we prepare when changing the support team? A list of systems and access, information about licenses, backups, integrations, and known issues. Confirm business control of the main accounts and remove unnecessary old profiles after handover.  About the author ## Evgeny Dimitrov the founder and manager of 88Lab He has worked in web technologies, digital marketing, and information security for more than two decades. His path began back in **2001 with LinuxExpress** - his first web project, dedicated to Linux. Later, under the pseudonym **KByte** , he published technical materials and articles on Linux-BG.org, and in **2002 he founded Security-BG** - a project for learning and sharing knowledge in the field of computer security. Today, he is **the founder and manager of 88Lab** , where he works on web platforms, SEO, Google Ads, AI solutions, and online business optimization. The agency’s projects include **Banker, Pulse Fitness & Spa, CoolFit, and the Bulgarian Construction Chamber** . His expert opinions on **web technologies, digital marketing, and online business** have been published in the newspaper **Banker and Actualno.com** . [More about 88Lab](https://88lab.eu/en/za-nas/) ## Share the post [Facebook](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2F88lab.eu%2Fen%2Fwebsite-maintenance-access-backups%2F)[LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2F88lab.eu%2Fen%2Fwebsite-maintenance-access-backups%2F) CONTINUE READING ## More on this topic [](https://88lab.eu/en/how-to-choose-a-website-agency/) Websites / 6 MIN ### [How to choose a website agency and compare proposals](https://88lab.eu/en/how-to-choose-a-website-agency/) Two website quotes can look the same while covering very different work. How to compare tasks, ownership, and handover before choosing an agency. [Read the article](https://88lab.eu/en/how-to-choose-a-website-agency/) [](https://88lab.eu/en/business-website-brief-template/) Websites / 7 MIN ### [Business website brief: a template and worked example](https://88lab.eu/en/business-website-brief-template/) You do not need to know how to code a website to prepare a good brief. Use the template and completed example to describe the real tasks. [Read the article](https://88lab.eu/en/business-website-brief-template/) [](https://88lab.eu/en/classifieds-website-features/) Websites / 6 MIN ### [Classifieds website: features, moderation and launch](https://88lab.eu/en/classifieds-website-features/) A classifieds website should help the seller, buyer, and administrator. An example with furniture shows how to organize fields, search, and moderation. [Read the article](https://88lab.eu/en/classifieds-website-features/)