Pause at the route markers.
This guide is educational and must be adapted to your organization’s policies. It does not replace authorization, vendor documentation, or security review.
Home / Remote access field guide
Name the destination
Use the canonical host, role, environment, and service owner.
Confirm identity
Use the approved account and key source; keep secrets out of notes.
Verify trust
Know where the expected host fingerprint comes from.
Trace the gateway
State each boundary and the reason it exists.
Bound the task
Describe commands, transfers, display use, and expected result.
Close the route
End tunnels, capture evidence, and report exceptions.
Decision notes
Host identification changed. Continue?
Stop and use the approved verification and escalation channel. Do not normalize an unexplained change.
The SFTP browser opened. Is transfer approved?
Availability is not authorization. Confirm source, destination, permission, and task scope.
The GUI feels slow. Increase complexity?
Measure the route and try the documented fallback before layering on unreviewed changes.
Official product facts
Mobatek’s current documentation is authoritative for MobaXterm behavior, supported protocols, editions, and license terms. Route Atelier interprets workflows independently and does not provide product support.
Read the rollout decision guide