Requirements and responsibilities
Have the law firms owner approve public copy, required staff roles and the exact sample journey. A law firm wants practice-area pages and conflict-safe intake.
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 website submission must not imply an attorney-client relationship.
Approve form fields and readership with the organization; keep sensitive client, patient, student or account records in its authorized system. Hosting availability does not establish sector compliance.
WordPress roles and capabilities · WordPress hardening handbook
Illustrative situation
Illustrative scenario, not a customer case study: A law firm wants practice-area pages and conflict-safe intake. A sample inquiry reaches intake staff; an unrelated editor cannot read it.
Choose the approach
Use a general inquiry form only for the fields legal staff approve. 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
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
Approve practice descriptions, jurisdiction and intake wording
- Where
- WordPress or selected application administrator and public test browser
- Permissions
- Named WordPress or selected application administrator; business owner accepts result.
- Inputs
- Approve practice descriptions, jurisdiction and intake wording; named administrator and a harmless representative sample.
- Action
- Ask the firm's intake partner to approve practice areas, jurisdiction, form wording and the statement about when a professional relationship begins.
- Expected result
- The approved intake boundary is documented.
- Verify
- The approved intake boundary is documented. Have the responsible business staff member record the sample identity and observed result.
- If it fails
- If the wording could be read as advice for a specific case, get firm review before publication.
Sources: WordPress roles and capabilities · WordPress plugin administration
Step 2 of 5
Create pages and staff profiles under editorial review
- Where
- WordPress or selected application administrator and public test browser
- Permissions
- Named WordPress or selected application administrator; business owner accepts result.
- Inputs
- Create pages and staff profiles under editorial review; named administrator and a harmless representative sample.
- Action
- Create practice pages and staff biographies in WordPress with editor approval, and keep only approved claims visible.
- Expected result
- Visitors can find the right service and contact path.
- Verify
- Visitors can find the right service and contact path. Have the responsible business staff member record the sample identity and observed result.
- If it fails
- If a profile or jurisdiction is stale, hold that page until counsel corrects it.
Sources: WordPress roles and capabilities · WordPress plugin administration
Step 3 of 5
Configure approved inquiry fields and recipient access
- Where
- WordPress or selected application administrator and public test browser
- Permissions
- Named WordPress or selected application administrator; business owner accepts result.
- Inputs
- Configure approved inquiry fields and recipient access; named administrator and a harmless representative sample.
- Action
- Configure an inquiry form with only approved fields and a restricted recipient list; keep document exchange in the firm's chosen secure process.
- Expected result
- Intake staff own the submitted information.
- Verify
- Intake staff own the submitted information. Have the responsible business staff member record the sample identity and observed result.
- If it fails
- If the form asks for confidential case documents without an approved channel, remove uploads.
Sources: WordPress roles and capabilities · WordPress plugin administration · Contact Form 7 getting started guide
Step 4 of 5
Test routing, response expectation and accidental disclosure
- Where
- WordPress or selected application administrator and public test browser
- Permissions
- Named WordPress or selected application administrator; business owner accepts result.
- Inputs
- Test routing, response expectation and accidental disclosure; named administrator and a harmless representative sample.
- Action
- Submit a synthetic inquiry for two practice areas and compare routing, delivery and automatic reply; inspect stored entries only where the selected system documents and enables persistence.
- Expected result
- Each sample reaches the intended intake queue and no other editor.
- Verify
- Each sample reaches the intended intake queue and no other editor. Have the responsible business staff member record the sample identity and observed result.
- If it fails
- If routing is ambiguous, send all new inquiries to a staffed central intake until fixed.
Sources: WordPress roles and capabilities · WordPress plugin administration · Contact Form 7 getting started guide
Step 5 of 5
Schedule content review and preserve intake records before recovery
- 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
- Schedule content review and preserve intake records before recovery; named administrator and a harmless representative sample.
- Action
- Review the site after staff moves or practice changes; preserve intake records and response timestamps before any restore.
- Expected result
- The firm can continue handling open inquiries during site repair.
- Verify
- The firm can continue handling open inquiries during site repair. Have the responsible business staff member record the sample identity and observed result.
- If it fails
- If a restore point omits a new inquiry, reconcile it from the intake system first.
Sources: Site backups in xCloud · xCloud agent capability boundaries · 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 sample inquiry reaches intake staff; an unrelated editor cannot read 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
Before restoring, compare the chosen recovery point with newer business records. A website submission must not imply an attorney-client relationship. 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
- 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: Configure an inquiry form with only approved fields and a restricted recipient list; keep document exchange in the firm's chosen secure process.
- The business owner compares the controlled sample with this observable result: Each sample reaches the intended intake queue and no other editor.
- 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 sample inquiry reaches intake staff; an unrelated editor cannot read it. Test routing, response expectation and accidental disclosure
- recovery (covered): A website submission must not imply an attorney-client relationship. Schedule content review and preserve intake records before recovery
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
- Manage WordPress updates with Updates Manager
- Vulnerability Checker in xCloud
- Contact Form 7 getting started guide