Workflow Guides

Workflow Guides connect individual pages into complete jobs, because customers usually ask for an outcome rather than the name of a menu item.

Where to find it: Documentation > Hosting Manager > Workflow Guides.

Available to: Anyone reading the public documentation. The related SHM action still follows the role stated on its page.

What this page does

Use these sequences for onboarding, domain launch, application deployment, incident handling, migration, and recovery. Each workflow moves from identity and scope to change, then to independent verification.

Before you start

Record the customer request, authorized target, current state, and recovery option before starting. When a workflow crosses root, reseller, and account contexts, complete each step using the narrowest role that owns it.

Provision and hand over a new account

1. Confirm package and feature profile.
2. Create the account.
3. Verify DNS and issue SSL.
4. Create or migrate web, mail, and database resources.
5. Run a backup.
6. Sign in as the customer and verify enabled tools.

Launch a website

1. Choose or create the domain and document root.
2. Upload, deploy, or install the application.
3. Select PHP, Node.js, or container routing in Web Manager.
4. Set DNS and wait for authoritative resolution.
5. Issue SSL, enable HTTPS redirect, and test the public site.
6. Enable cache or security policy only after a working baseline exists.

Investigate a customer incident

1. Capture the domain, symptom, time, and last known change.
2. Check Health Center and Diagnostics Center.
3. Correlate access/error logs, usage, and the relevant runtime.
4. Build the smallest safe fix.
5. Apply it in the owning module.
6. Verify from the customer-facing service and record the outcome.

Restore data

1. Confirm customer approval and the exact missing or damaged scope.
2. Choose the correct restore point.
3. Understand whether current data will be replaced.
4. Start the restore and wait for a final result.
5. Verify files, databases, mail, ownership, and the application.

How to use it

1. Identify whether the task is server-wide, reseller-scoped, or limited to one account.
2. Open the page that owns the resource instead of using a nearby page with a similar name.
3. Read the page-specific prerequisites and impact before changing anything.
4. Verify the result in SHM and from the customer-facing service.

Result and next check

A workflow is complete when the requested customer outcome works and the related SHM state agrees. A green button alone is useful evidence, but it is not the whole proof.