Permissions and sudo
The dashboard connects as the Ubuntu account you register. That account's existing access controls which reads and management actions succeed.
Begin with inspection
Check service status, metrics and logs before trying a management operation. Missing metrics and denied journal access do not imply that a service has failed. They may describe what the account is permitted to read.
The local dashboard does not grant additional Ubuntu privileges during first-run setup. Ask the server owner which services your account may manage.
Review a service before approving control
Use the canonical unit name and confirm that it belongs to the expected application. A display name is a convenient label; the unit identifies the actual systemd target.
The server owner should understand the unit's dependencies and who can modify its executable, configuration and launch inputs. Permission to restart an app can have a wider effect when its dependencies or files are shared.
When sudo is required
The SSH adapter uses the account's existing sudo policy. If sudo requests authentication, the app supplies the session password through standard input. It records a failed operation when the command is denied.
The optional direct-hosting mode has separate installation and privilege rules in the application repository. Those instructions are not required to run the normal local SSH dashboard.
If permissions need changing, the server owner should review the exact commands in the shipping application and test a narrowly scoped policy in an authorized environment. Avoid copying broad examples from unrelated installations.
Detailed application security model · Application management.