Feature reference

EPAdmin menu reference: Terminal & SSH

Every terminal & ssh menu item, its destination, permissions and explicit unavailable behavior.

Platform
Go
Technology
Go

Open Terminal & SSH

In the EPAdmin administrator workspace, open Terminal & SSH or search the exact tool label. A general web terminal is unavailable; typed security controls do not expose root commands. Read the detailed operational guide before making changes. The table lists every requested leaf in this group. A connected destination remains subject to current local permissions, resource ownership, installed capability, licence and fresh verification. It is not a production acceptance claim.

Complete tool reference

Tool Destination and behavior Permission or limitation
Web Terminal Unavailable in this checkpoint Browser-accessible Root shell is not exposed. A narrowly confined terminal transport has not been implemented.
SSH Key Management Unavailable in this checkpoint Root SSH key enrollment/revocation is not implemented. Customer SFTP authorized keys are separate.
SSH Access Settings Server → Security Any listed local Admin grant: security:read, security:manage
Root Access Security Server → Security Any listed local Admin grant: security:read, security:manage
Command History Unavailable in this checkpoint Shell command-history collection is not implemented.
SSH Login Logs ServerLogs → Security Any listed local Admin grant: security:read, security:manage

Make and verify a change

Select the intended owned resource and load its current detail. Read impact, current revision, applicable preview and confirmation before an explicit submission. If the server requires fresh authentication, complete its password/MFA flow and submit the reviewed request again; no write is automatically replayed. Keep the durable operation ID and inspect the final resource/service state.

When a tool is missing or denied

Check the current role/grants, installed version and actual capability. A menu label marked unavailable has no supported action to force. Source updates can be newer than your installed kit; they do not automatically add hosting acceptance. Preserve the safe operation/correlation reference and inspect original state before retrying an interrupted change. Do not disable confinement, modify private journals or substitute another account to bypass denial.

← All EmailaPanel guidesGet help →

Need help with EmailaPanel?

Tell us the product version and what you are trying to do. Keep passwords and private keys out of your message.

Contact Emaila