Checked against the product’s code on 7 November 2026.
Amadalis has a separate operations console for staff. Your site’s Admin role does not give access to that console. Ask support to explain the scope and result of an operation affecting your site.
What the operations areas cover
Section titled “What the operations areas cover”| Area | What it supports |
|---|---|
| Customers and sites | Account records, hosted site status and the assigned customer. |
| Site creation | Creating a hosted site through the platform workflow. |
| Account status | Suspension, reactivation and the separate termination process. |
| Billing and usage | Subscription and invoice records, billing accounts, site groups and capability grants. |
| Domains | Domain ownership, routing and certificate states. |
| Incidents and support | Recorded incidents, response work and governed support entry. |
| AI configuration | Model choices, configured restrictions and recorded usage. |
| Staff copilot | Permitted staff requests with customer scope and approval for consequential changes. |
These are staff workflows, not additional self service controls in your account. Site preferences cannot grant a capability outside the platform’s entitlement.
Health, backups and restore
Section titled “Health, backups and restore”Health checks and backups have scheduled jobs. A schedule is not proof that a particular run succeeded.
Before planning recovery:
- Ask support for the current health result.
- Ask support for the available backup.
A hosted restore replaces a whole site database with the chosen backup and can replace newer work. Its workflow takes a fresh backup and suspends the site while it runs. If the restore does not finish, your site stays suspended until Amadalis has checked it. Amadalis performs the operation; EmDash’s downloadable content backup is a separate feature.
When a termination finishes, Amadalis can give you a deletion certificate that lists what was destroyed, when and by whom. Ask support for it.
Access and records
Section titled “Access and records”Staff access has separate scopes and two factor checks. Customer grants, incident entry and full Admin override have the boundaries described in Account Security, including how revocation ends an open support session on its next request after the grant check refreshes, within 30 seconds, and how expiry ends it at the next request.
Action log entries are linked by checksums, digital fingerprints linking each entry to the previous entry in the platform’s audit log. Amadalis staff run tamper-evident checks: editing or deleting an earlier entry breaks the chain, and the platform checks the whole chain every night. The result identifies four recorded gaps from 19 August 2026. Account erasure is designed to remove personal details without breaking the check. Read verification and its limits.
Your account reports the recorded database region where available. That is not a promise that caches, network services and AI requests all stay in that region. The current list of service providers that process customer data is published on the account site’s Subprocessors page. Ask Amadalis for any other facts your review needs.