Requirements and responsibilities
Have the coworking spaces owner approve public copy, required staff roles and the exact sample journey. A coworking space markets desks, meeting rooms and memberships.
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 calendar embed alone cannot enforce room inventory.
Illustrative situation
Illustrative scenario: a coworking space receives overlapping room requests. Staff compare them with the room ledger and confirm at most one reservation.
Choose the approach
Choose whether booking and billing sit in a specialized space tool. 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 · Easy!Appointments official application settings
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 rooms, occupancy, opening hours and membership terms
- Where
- WordPress or selected application administrator and public test browser
- Permissions
- Named WordPress or selected application administrator; business owner accepts result.
- Inputs
- Map rooms, occupancy, opening hours and membership terms; named administrator and a harmless representative sample.
- Action
- List rooms, desk capacity, opening hours, member terms and who owns availability across walk-ins and online requests.
- Expected result
- The space has one room-inventory owner.
- Verify
- The space has one room-inventory owner. Have the responsible business staff member record the sample identity and observed result.
- If it fails
- If two calendars can confirm the same room, resolve that before booking online.
Sources: WordPress roles and capabilities · WordPress plugin administration · Easy!Appointments official application settings
Step 2 of 5
Publish WordPress space and pricing pages
- Where
- WordPress or selected application administrator and public test browser
- Permissions
- Named WordPress or selected application administrator; business owner accepts result.
- Inputs
- Publish wordpress space and pricing pages; named administrator and a harmless representative sample.
- Action
- Publish WordPress room descriptions, capacities, directions and pricing notes with a visible inquiry path.
- Expected result
- A visitor can distinguish a desk from a meeting room.
- Verify
- A visitor can distinguish a desk from a meeting room. Have the responsible business staff member record the sample identity and observed result.
- If it fails
- If pricing depends on membership, explain the qualification rather than promise a fixed total.
Sources: WordPress roles and capabilities · WordPress plugin administration · Easy!Appointments official application settings
Step 3 of 5
Publish staffed room requests
- Where
- WordPress or selected application administrator and public test browser
- Permissions
- Named WordPress or selected application administrator; business owner accepts result.
- Inputs
- Configure chosen room booking service separately; named administrator and a harmless representative sample.
- Action
- Publish a staffed room-request form and keep membership qualification, billing and final room allocation with the space manager. Choose a documented room-booking product separately if instant confirmation is needed.
- Expected result
- A room request reaches staff, while availability is decided from the authoritative room ledger.
- Verify
- A room request reaches staff, while availability is decided from the authoritative room ledger. Record the exact account or record tested, result, and time with the responsible owner.
- If it fails
- If the app cannot model equipment or setup time, include buffer manually.
Sources: WordPress roles and capabilities · WordPress plugin administration · Easy!Appointments official application settings · Contact Form 7 getting started guide
Step 4 of 5
Test overlapping request decisions
- Where
- WordPress or selected application administrator and public test browser
- Permissions
- Named WordPress or selected application administrator; business owner accepts result.
- Inputs
- Test overlapping rooms, cancellations and inquiries; named administrator and a harmless representative sample.
- Action
- Request the last free room slot and an overlapping one with synthetic details. Ask staff to accept one and decline or waitlist the other; test how cancellation returns a slot to the ledger.
- Expected result
- No second guest receives an unverified automatic confirmation for the occupied room.
- Verify
- No second guest receives an unverified automatic confirmation for the occupied room. Record the exact account or record tested, result, and time with the responsible owner.
- If it fails
- If overlap is allowed, stop instant confirmation and use staffed approval.
Sources: WordPress roles and capabilities · WordPress plugin administration · Easy!Appointments official application settings · Contact Form 7 getting started guide
Step 5 of 5
Maintain availability owner and reconcile bookings before restore
- Where
- WordPress or selected application administrator and owner handoff
- Permissions
- Named WordPress/application administrator and business owner; inspect backup separately if recovery is in scope.
- Inputs
- Maintain availability owner and reconcile bookings before restore; named administrator and a harmless representative sample.
- Action
- Assign availability review and preserve future room bookings before WordPress or booking-app restores.
- Expected result
- Staff can handle an outage with a current reservation list.
- Verify
- Staff can handle an outage with a current reservation list. Have the responsible business staff member record the sample identity and observed result.
- If it fails
- If the restore point predates new bookings, reconcile them first.
Sources: Site backups in xCloud · xCloud agent capability boundaries · Easy!Appointments official application settings · WordPress roles and capabilities
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 visitor requests a room for the correct capacity and staff see it. 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
The staff room ledger and membership billing system require their own preservation and recovery path. A WordPress site restore cannot recreate decisions recorded only in those systems.
Site backups in xCloud · Contact Form 7 getting started guide
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.
- 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
Copyable agent brief
Manual checkpoints
- The named WordPress, app, dashboard or provider administrator performs the guide’s actual configuration step: Publish a staffed room-request form and keep membership qualification, billing and final room allocation with the space manager. Choose a documented room-booking product separately if instant confirmation is needed.
- The business owner compares the controlled sample with this observable result: No second guest receives an unverified automatic confirmation for the occupied room.
- 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 visitor requests a room for the correct capacity and staff see it. Test overlapping request decisions
- recovery (covered): A calendar embed alone cannot enforce room inventory. Maintain availability owner and reconcile bookings before restore
Sources
- xCloud agent capability boundaries
- WordPress roles and capabilities
- WordPress plugin administration
- Site backups in xCloud
- WordPress hardening handbook
- xCloud MCP documentation and connection profiles
- Easy!Appointments official application settings
- Manage WordPress updates with Updates Manager
- Vulnerability Checker in xCloud
- Contact Form 7 getting started guide