Temp Access for Blueprint v1.0.0

Access you forget about is a breach waiting to happen.

You add a plugin developer as a subuser to debug something. Three months later they still have console and file access - you just forgot. Every Pterodactyl server accumulates these ghost accounts.

Temp Access adds one thing Pterodactyl always missed: an expiry date on subuser access.

How it works

• A Temporary Access panel appears above the subuser list on the Users tab
• Pick a subuser, pick a duration (1 hour, 1 day, 3 days, 1 week, 30 days), done
• When the timer runs out, a scheduled task removes the subuser exactly like a manual removal - on newer panels this includes revoking live SFTP sessions
• Extend or clear an expiry at any time; "Make permanent" restores normal behavior

Fully integrated

• Uses Pterodactyl's own permission system: user.read to see expiries, user.update to manage them
• Every set, extension, clear and automatic removal lands in the server activity log
• Admin overview: all upcoming expirations across the panel, plus a log of recent automatic removals
• Expiries clean themselves up when a subuser or server is deleted
• Sweeps run every minute, so "1 hour" means 1 hour

Use cases

• Plugin/mod developers who need access "just for today"
• Freelance builders and config specialists on a fixed gig
• Support staff investigating a specific ticket
• Event moderators who only need access this weekend

What it needs
The standard Pterodactyl cron (schedule:run) that every install already has. No extra services.

Installation
Running the panel in Docker? Restart the panel container after installing so the database migrations apply (standard Blueprint-in-Docker behavior).
Requires the free Blueprint extension framework (blueprintframe.work). Game-agnostic - works with any egg.