Requirements and responsibilities
Have the online educators owner approve public copy, required staff roles and the exact sample journey. An online educator sells courses and tracks learner completion.
xCloud agent capability boundaries · WordPress roles and capabilities
Use a compatible Nginx or OpenLiteSpeed stack for native WordPress. Verify current server resources, plan eligibility and each selected plugin or service license and requirements before installing; a Docker server does not host a new native WordPress site.
xCloud agent capability boundaries · WordPress plugin administration
Prepare a safe test identity and a completed, accessible backup before consequential changes. The important failure to plan around is: Database rollback can erase recent progress or access changes.
Before any database copy or restore starts, the authorized operator restricts the target and quarantines outbound mail, payment, fulfillment and other provider effects. Restored settings may overwrite plugin suppression; reapply sandbox credentials and verify isolation before testing.
Create a staging environment in xCloud · Site backups in xCloud
Illustrative situation
Illustrative scenario, not a customer case study: An online educator sells courses and tracks learner completion. A paid test learner gains the right lesson access and progress persists.
Choose the approach
Choose LMS and commerce integrations based on enrolment and progress evidence. Verify the selected provider or plugin documentation and license against this requirement; xCloud hosting does not supply its business configuration.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · WordPress roles and capabilities · Tutor LMS official documentation and course administration
Keep application setup, domain/DNS ownership, mail delivery and external integrations with their named administrators. Use a plain documented path when a proposed integration cannot be demonstrated end to end.
xCloud agent capability boundaries · WordPress plugin administration
Dashboard and application procedure
Follow these steps yourself, or use the scoped AI handoff below for supported hosting operations.
Step 1 of 5
Map courses, cohorts, instructor roles and lesson states
- Where
- WordPress or selected application administrator and public test browser
- Permissions
- Named WordPress or selected application administrator; business owner accepts result.
- Inputs
- Map courses, cohorts, instructor roles and lesson states; named administrator and a harmless representative sample.
- Action
- Define course, cohort, payment, instructor and learner-progress requirements with a sample completion event.
- Expected result
- The educator can evaluate an LMS against a real learner path.
- Verify
- The educator can evaluate an LMS against a real learner path. Have the responsible business staff member record the sample identity and observed result.
- If it fails
- If grading or certificates are mandatory, mark them as plugin-specific before purchase.
Sources: WordPress roles and capabilities · WordPress plugin administration · Tutor LMS official documentation and course administration
Step 2 of 5
Deploy WordPress and verify selected lms requirements
- Where
- xCloud Add Site dashboard
- Permissions
- Named xCloud team and site administrator; confirm server, domain and WordPress stack.
- Inputs
- Deploy wordpress and verify selected lms requirements; named administrator and a harmless representative sample.
- Action
- Deploy native WordPress on a compatible stack, then review the selected LMS vendor's WordPress/PHP version and license requirements.
- Expected result
- Hosting and application requirements agree.
- Verify
- Check site identity and match each requirement to current vendor docs. Have the responsible business staff member record the sample identity and observed result.
- If it fails
- If an extension or license is missing, do not sell the course yet.
Sources: WordPress roles and capabilities · WordPress plugin administration · Tutor LMS official documentation and course administration · xCloud agent capability boundaries
Step 3 of 5
Configure enrolment, lesson and completion workflow
- Where
- WordPress or selected application administrator and public test browser
- Permissions
- Named WordPress or selected application administrator; business owner accepts result.
- Inputs
- Configure enrolment, lesson and completion workflow; named administrator and a harmless representative sample.
- Action
- In the LMS build a short sample module, assign an instructor and enroll a test learner using the chosen payment or manual path.
- Expected result
- The learner enters only their authorized lesson.
- Verify
- Compare enrollment in LMS and payment system where used. Have the responsible business staff member record the sample identity and observed result.
- If it fails
- If payment and access disagree, pause enrollment and repair mapping.
Sources: WordPress roles and capabilities · WordPress plugin administration · Tutor LMS official documentation and course administration
Step 4 of 5
Test paid, expired and resumed learner sessions
- Where
- WordPress or selected application administrator and public test browser
- Permissions
- Named WordPress or selected application administrator; business owner accepts result.
- Inputs
- Test paid, expired and resumed learner sessions; named administrator and a harmless representative sample.
- Action
- Complete a lesson, sign out and return; compare learner progress with instructor view and test an expired account.
- Expected result
- Progress persists and unauthorized accounts remain blocked.
- Verify
- Record test account, lesson and completion timestamp. Have the responsible business staff member record the sample identity and observed result.
- If it fails
- If progress disappears after login, investigate session or database state before release.
Sources: WordPress roles and capabilities · WordPress plugin administration · Tutor LMS official documentation and course administration
Step 5 of 5
Schedule backups and reconcile enrolments before restores
- Where
- xCloud Site Backup dashboard
- Permissions
- Named xCloud site administrator; compare newer learner records before any restore.
- Inputs
- Schedule backups and reconcile enrolments before restores; named administrator and a harmless representative sample.
- Action
- Back up course content, users and progress; rehearse a safe restore and plan reconciliation of new enrollments.
- Expected result
- A recovered site can reconstruct current learner state.
- Verify
- Compare restore point with the latest completion and identify replay owner. Have the responsible business staff member record the sample identity and observed result.
- If it fails
- Do not overwrite newer progress or purchases with an older database.
Sources: Site backups in xCloud · xCloud agent capability boundaries · Tutor LMS official documentation and course administration
Maintenance
Assign a cadence for selected WordPress core, theme and plugin updates, review version-based findings and retest the path in this guide. In particular, repeat: A paid test learner gains the right lesson access and progress persists. A chat prompt is not a scheduled task.
Manage WordPress updates with Updates Manager · Vulnerability Checker in xCloud
Record actual backup completion, storage access and responsible staff. Recheck connected application and provider behavior after changes rather than relying on a site health status alone.
Recovery decisions
Compare backup time with new enrollments, payments and learner/member progress. Reconcile newer application records before an in-place restore and retest access states after recovery.
Site backups in xCloud · Tutor LMS official documentation and course administration
Validate the restored copy with representative content, authentication, HTTPS and this guide’s business acceptance test before moving traffic or closing the incident.
AI handoff
Connect xCloud MCP through the current documented profile and grant only the scopes needed for the selected team. Discover tool schemas first. Read resources to plan; require approval for any supported write. Use returned dashboard URLs for manual work. The packaged REST wrapper accepts GET requests only.
Supported scope
- Confirm requirements and inspect resources mcp · read
Discover the connected profile and operation schema first; only teams granted to the connection are visible.
Checkpoint: Confirm exact team, server and site identity. Use dashboard_url returned by the resource; do not invent a dashboard link.
Operation identifiers and scopes to discover
teams.index, servers.show, sites.show
Scopes: read:servers, read:sites
xCloud MCP documentation and connection profiles · xCloud agent capability boundaries
- Review a WordPress business journey app · manual
Application data and observed transactions cannot be inferred from xCloud resource reads. Use authorized test accounts and the application or provider evidence.
Checkpoint: Record the test identity, timestamp, expected outcome, observed result and owner decision.
- Create a WordPress site mcp · write
Requires a compatible Nginx or OpenLiteSpeed server; Docker and single-site agentic servers cannot host a new WordPress site.
Checkpoint: Approve the exact server, domain, capacity, cost and creation inputs before provisioning. Verify completion and HTTPS.
Operation identifiers and scopes to discover
servers.sites.wordpress.create
Scopes: write:sites
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles
- Configure WordPress content, users and selected plugins app · manual
Requires a named WordPress administrator or suitable editor. Plugin behavior, commercial license, payment, email and external integration are verified in the chosen vendor documentation and application; xCloud hosting or MCP reads do not configure them.
Checkpoint: Open the actual WordPress or selected plugin interface, record the version and role, and have the business owner accept a real user journey.
WordPress roles and capabilities · WordPress plugin administration
- Configure native WordPress backup and restore dashboard · manual
Native schedule, retention and destination changes and all restores are dashboard-only.
Checkpoint: Use Site → Site Backup. Before restoring, confirm backup, target, scope and treatment of newer records.
Copyable agent brief
Manual checkpoints
- The named WordPress, app, dashboard or provider administrator performs the guide’s actual configuration step: In the LMS build a short sample module, assign an instructor and enroll a test learner using the chosen payment or manual path.
- The business owner compares the controlled sample with this observable result: Progress persists and unauthorized accounts remain blocked.
- Staging push/pull, native backup schedules, restores and cache-setting edits require the authorized xCloud dashboard operator; the packaged REST wrapper is GET-only.
Feature coverage
- business-acceptance (covered): A paid test learner gains the right lesson access and progress persists. Test paid, expired and resumed learner sessions
- recovery (covered): Database rollback can erase recent progress or access changes. Schedule backups and reconcile enrolments before restores
Sources
- xCloud agent capability boundaries
- WordPress roles and capabilities
- WordPress plugin administration
- Site backups in xCloud
- WordPress hardening handbook
- Create a staging environment in xCloud
- xCloud MCP documentation and connection profiles
- Tutor LMS official documentation and course administration
- Manage WordPress updates with Updates Manager
- Vulnerability Checker in xCloud