Requirements and responsibilities
Have named ownership of the domain, selected xCloud team and site, and WordPress administrator access. For this scenario, agree who supplies the data and signs off: A paid community wants restricted articles and a clear way to cancel access.
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: A full restore may discard new subscriptions and payments.
Before a source copy or backup restore starts, the authorized operator must restrict the target and quarantine outbound mail, payment, fulfillment and other provider effects at the receiving environment. Restored WordPress settings can overwrite plugin suppression; reapply sandbox credentials and verify isolation before tests.
Create a staging environment in xCloud · Site backups in xCloud
Illustrative situation
Illustrative scenario, not a customer case study: A paid community wants restricted articles and a clear way to cancel access. An active test member sees protected content; an expired member cannot.
Choose the approach
Select a membership plugin only after reviewing its roles, billing integration and export path. Verify the selected provider or plugin documentation and license against this requirement; xCloud hosting does not supply its business configuration. Paid Memberships Pro is one documented example; confirm its current level, gateway and license choices before selecting it.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · WordPress roles and capabilities · Paid Memberships Pro initial setup and payment gateway planning
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
Define member access states
- Where
- WordPress administrator or the selected plugin/application
- Permissions
- Named WordPress or selected app administrator; business owner approves results.
- Inputs
- Owner, hostname, approved requirements, sample record and decision date. Define member access states.
- Action
- Write an access matrix for anonymous visitor, active member, expired member and staff administrator. Include each protected page, renewal interval, cancellation rule and where billing records live.
- Expected result
- Membership rules and data ownership are explicit.
- Verify
- The owner signs the matrix and names one sample URL for each state.
- If it fails
- If billing or access policy is unresolved, do not promise paid access on the public page.
Sources: WordPress roles and capabilities · WordPress plugin administration
Step 2 of 5
Select a documented membership plugin
- Where
- WordPress administrator or the selected plugin/application
- Permissions
- Named WordPress or selected app administrator; business owner approves results.
- Inputs
- Target team/site, server or plugin version, license and documented prerequisites. Select a documented membership plugin.
- Action
- Choose a membership plugin from its current vendor documentation. Check compatibility with the site's WordPress/PHP versions, required payment gateway, license and member export path before installation.
- Expected result
- One candidate can implement the required states.
- Verify
- Match every access rule to a documented setting or integration and record any gap.
- If it fails
- If a required state lacks a supported rule, compare a different plugin before collecting payments.
Sources: WordPress roles and capabilities · WordPress plugin administration · Paid Memberships Pro initial setup and payment gateway planning
Step 3 of 5
Configure levels and sandbox billing
- Where
- WordPress administrator or the selected plugin/application
- Permissions
- Named WordPress or selected app administrator; business owner approves results.
- Inputs
- Approved change scope, backup state, selected version and maintenance window. Configure levels and sandbox billing.
- Action
- Configure the selected plugin's levels and protected content in WordPress, and connect payment in the provider's test mode. Keep gateway keys and billing configuration with authorized administrators.
- Expected result
- A test user can enroll without affecting live billing.
- Verify
- Create a sandbox member and inspect both plugin access state and payment provider event.
- If it fails
- If one system advances while the other does not, stop launch and repair the integration mapping.
Sources: WordPress roles and capabilities · WordPress plugin administration · Paid Memberships Pro initial setup and payment gateway planning
Step 4 of 5
Test access and cancellation
- Where
- WordPress public pages, administrator and relevant external provider
- Permissions
- Named WordPress or selected app administrator; business owner approves results.
- Inputs
- Test accounts, sample content or transaction, expected result and provider access. Test access and cancellation.
- Action
- Use separate accounts to test active, expired and anonymous access; test renewal and cancellation with the plugin and gateway in test mode. Check personalized pages with cache bypass rules.
- Expected result
- Only the intended account reaches member material.
- Verify
- Compare three session results and confirm the same member state in the application record.
- If it fails
- If a protected page leaks or an active member is blocked, remove the public sales path until rules and caching pass.
Sources: WordPress roles and capabilities
Step 5 of 5
Protect member data and assign operators
- Where
- xCloud Site Backup dashboard
- Permissions
- Named xCloud team/site administrator; confirm the exact production or staging target.
- Inputs
- Observed results, unresolved failures, backup point and owner contacts. Protect member data and assign operators.
- Action
- Confirm that backups include membership data and rehearse a safe-target restore. Assign a staff member to review failed payments, access requests and plugin updates.
- Expected result
- Membership service has a named operator and recovery path.
- Verify
- Inspect a restored test member and compare the backup time with new payments or registrations.
- If it fails
- Never overwrite newer member or payment data without an explicit reconciliation plan.
Sources: Site backups in xCloud · xCloud agent capability boundaries
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: An active test member sees protected content; an expired member cannot. 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
Before restoring, compare the chosen recovery point with newer business records. A full restore may discard new subscriptions and payments. Use the xCloud dashboard for native restore only after the owner approves target and scope; reconcile or preserve newer data first.
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
- 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
- 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.
- 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: Configure the selected plugin's levels and protected content in WordPress, and connect payment in the provider's test mode. Keep gateway keys and billing configuration with authorized administrators.
- The business owner compares the controlled sample with this observable result: Only the intended account reaches member material.
- 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): An active test member sees protected content; an expired member cannot. Test access and cancellation
- recovery (covered): A full restore may discard new subscriptions and payments. Protect member data and assign operators
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
- Paid Memberships Pro initial setup and payment gateway planning
- Manage WordPress updates with Updates Manager
- Vulnerability Checker in xCloud