The Scope Model
v1.0
·
Updated 5 days ago
The Scope Model
Each server profile carries its own scopes — checkboxes that define which operations are allowed. Six scopes are provided:
| Scope | Meaning |
|---|---|
system_monitoring | logs and fleet-wide health checks |
file_operations | file operations on the server |
package_management | package management |
service_management | service management |
docker_compose | Docker and Compose commands |
file_transfer | file transfer (/copy, /sync) |
Hard-enforced vs. advisory
For the most important commands, scopes are enforced in code — if the checkbox is unticked, the command refuses to run:
docker_compose→ all/compose-*commands and/docker-listsystem_monitoring→/logs(refuses without the scope) and/health-summary(skips the server)file_transfer→/copyand/sync
For free-form ad-hoc SSH actions, the remaining scopes are advisory: they signal what should be allowed on a server before anything destructive happens.