Send access details through a safer intake path.
Use this XMLA intake page when support, migration, repair, launch, email, hosting, or managed service work requires temporary access details, account context, and authorization.
Before You Submit
Context matters as much as the credentials.
Clear authorization and account details help XMLA use the right login path without guessing across hosts, registrars, applications, and support requests.
Access scope
Only send credentials or access details that XMLA needs for the active request.
Account context
Include the site, host, registrar, mailbox, platform, or service tied to the access.
Authorization
Identify the account holder or approved contact authorizing XMLA to use the access.
Expiration plan
Rotate, revoke, or update temporary access after the work is complete.
Access Types
Use one intake path for the systems behind your website.
Website work often touches more than a WordPress login. Include the platform, host, domain, DNS, email, or connected app details that apply to the request.
Website Admin
WordPress, WooCommerce, page builder, plugin, and content management access.
Hosting / SFTP
cPanel, SFTP, file manager, database, backup, or server-level access paths.
Domain / DNS
Registrar, DNS zone, nameservers, SSL validation, MX, SPF, DKIM, and DMARC records.
Email / Apps
Mailbox, SMTP, IMAP, API, CRM, analytics, automation, or connected-service access.
Secure Form
Submit the requested access details.
Please reference the project, ticket, request, site, or service this access is related to. Use temporary or role-based access whenever available.
Do not submit unrelated third-party accounts, banking credentials, payment method passwords, or personal accounts that are not required for the approved XMLA request.
How XMLA Handles It
A defined path keeps access limited and accountable.
The goal is to collect only what is needed, use it for the active work, verify the result, and close the loop cleanly.
Submit
Send details through the secure form with context and authorization.
Review
XMLA checks the access path against the support, migration, repair, or project need.
Use
Access is used only for the active approved work and related verification.
Close
Rotate passwords, remove temporary users, or confirm ongoing managed access.
Related Paths
Use the right request when credentials are not the next step.
If you need support, onboarding, password recovery, or a guided remote session, these pages route the request more directly.
Support Center
Use support for active requests, account questions, or service coordination.
LiveRemote Support
Start a guided session when access needs to be entered or tested with a technician.
StartQuick Start
Start onboarding when XMLA needs accounts, hosting, domains, email, and launch details.
ResetPassword Reset
Request an XMLA-managed password reset instead of submitting a reusable password.
Security Reminder
Temporary access is usually the best access.
Create limited users where possible, avoid sharing unrelated credentials, and rotate or revoke access after XMLA confirms the work is complete.