Appearance
Permissions
Server Diagnosis reuses Pterodactyl's own access model — there is no separate permission to assign.
Who can generate
Any user who can access a server (owner, subuser, or root admin) can generate a bundle for it. Anyone else gets a 404 — the same response Pterodactyl gives for servers you cannot see.
What each user sees
Sections follow the same permissions as the panel pages that show the same data:
| Section | Required permission | Same as |
|---|---|---|
| Server information | server access | Server console |
| Resource limits | server access | Server console |
| Runtime | startup.read | Startup page |
| Startup configuration | startup.read | Startup page |
| Allocations | allocation.read | Network page |
Additional rules:
- Only egg variables marked user viewable are included — exactly the set the Startup page shows
- Sections the user (or admin config) does not allow are skipped and reported as skipped, never silently included
- A bundle can only be downloaded/deleted by the user who generated it, through the server it belongs to — knowing the bundle ID is never enough
So a subuser with limited permissions gets a bundle containing only what they could already see in the panel — Server Diagnosis is never a privilege-escalation path.