Before you start
The administration terminal requires its specific capability and authority for the intended machine-level work. Check the target and recovery needs before entering any command.
What to do
- For a website-level operation, first use that website's Commands view when it provides the scope you need. Check its directory and runtime limit.
- When an authorised machine-level interactive session is required, open Terminal and select the exact server target.
- Check the displayed connection state and prompt target before entering the intended command. The administration shell has broad privileges; changing the selected machine changes the operation's scope.
- Read the actual command result and verify any affected resource separately. Use Reconnect for a failed terminal connection, then inspect whether earlier work is still running before submitting it again.
- Keep credentials and sensitive output private. Leaving or reconnecting the browser view is not evidence that a command's underlying work has stopped.
What happens next
You can distinguish a connected administration shell from a resource command and keep the intended target and operation scope explicit.
If something goes wrong
A missing Terminal entry can reflect a capability restriction; it is not a reason to substitute another person's session. If the terminal fails to load or disconnects, reconcile current work and target state before retrying. Contact the infrastructure administrator with the target type, time and redacted error, without copying private terminal output into public reports.
