## Inspect without editing
Beem uses a separate inspection mode to identify the CMS, view the admin panel or explain the available permissions. No hosting-backup confirmation is needed for this. Saving changes, arbitrary commands, SQL and JavaScript are unavailable in this mode. If sign-in needs your help, Beem can request the site browser.
## Three choices before changes
When a change requires a hosting backup, choose one option:
- I have a backup — confirm a full website backup is available for recovery, including its files and database if used. You do not need to enter a date, location or technical details.
- I do not have a backup — add hosting-panel access through the protected form. Beem will inspect available copies and whether a new one can be created.
- I do not know — help me check — follow the same inspection path without assuming a backup exists.
Your confirmation is recorded separately from technical verification; it does not mean that restoration was tested. The original website changes remain deferred while Beem checks backups.
## If you do not have a copy
Select Add hosting access. This is your hosting-provider account, not your website admin password. Enter credentials only in the protected form. After saving, select Check hosting backups.
Beem can inspect the panel and use a supported backup operation. The current automatic adapter supports cPanel through an authenticated private browser: it checks the website domain and available copies and can request a full backup to the hosting home directory for a single-site account. A multi-site account, another panel, unsupported sign-in or insufficient permissions requires checking/creating the copy in the hosting panel or contacting hosting support. Backup mode cannot restore/delete hosting copies or edit the website.
Creation can take time. Requested is not completed: Beem must check the provider status. An uncertain creation request is not repeated automatically, avoiding duplicate archives. Once the copy is ready, choose I have a backup and Confirm and continue.
You may also create a copy yourself in your hosting panel’s Backups section. If you cannot find it, ask hosting support: “Is there a current full backup of my website, and how can I create one for recovery?” Then return to this form.
## Beemlix copies and hosting copies
Beemlix preserves initial data before supported file changes and creates controlled project checkpoints. These cover a specific scope; they are not automatically a full backup of every external website or database. External SSH/SQL and admin changes require hosting-backup confirmation. A changed connection or expired confirmation may show the form again.
Copies of individual files changed over a file connection are available for recovery for 30 days. After this period, the copies are deleted; cleanup may be postponed while the environment is in use. Hosting copies are stored separately and are not removed by Beemlix cleanup. This rule does not delete chat history or delivered documents. The activity log retains the relevant actions and verification details.
### Builders and managed platforms
For Shopify, Webflow and Horoshop, check backups and data export in the platform account or ask its support team. Beemlix does not request FTP or a separate hosting account for this connection or start cPanel backup jobs. Version history may not cover all data; check the scope before confirming a copy.
## New site: work without a backup
If the site is new and you explicitly authorize changes without a backup, select “New site — continue without a backup”. While the task awaits a backup, you can also write “Backup is not needed, this is a new site”. This permission is recorded separately and does not confirm a recovery copy exists. It applies to this task for up to 24 hours and is invalidated by changed credentials. Automatic file checkpoints for supported file operations continue as before.
When you confirm a full backup, Beem continues without separately inspecting it on the hosting account unless you request that inspection. Your confirmation does not mean recovery was tested.
Beemlix keeps original versions of changed local files for 30 days. It does not create new full workspace, container or local database snapshots. Keep a full website and database backup at your hosting provider. A file checkpoint becomes available after writers stop and changes are committed; enabled protection does not yet mean a saved copy exists. Recovery checks for conflicts with later edits and saves an undo file checkpoint. It does not restore databases or external servers.