Workflow
Follow a predictable path from setup to response: local plugin ownership first, cloud authority where durable state and team coordination matter.
Main Steps
Each step is written for a public website visitor deciding what WPLURA does and where the next action belongs.
01
Start from a site-owned WordPress plugin flow, then hand off to hosted cloud authentication only when cloud workflows are needed.
02
Enable product-specific local controls and understand which features stay local versus which require cloud entitlement.
03
Use public checks, product reports, and customer account views to identify risk without exposing internal operations.
04
Use guided response, backup/restore, and disaster-recovery workflows with realistic confirmations and durable job state.
Incident Timeline
01
Set roles, product scope, backup posture, retention expectations, and escalation paths before an incident.
02
Review warnings, scan results, public risk, customer reports, and recent changes before taking action.
03
Contain and remediate through approved plugin, customer-panel, support, or cloud workflow paths.
04
Confirm the site is stable, reports are updated, follow-up actions are assigned, and recovery guidance is documented.
