Manage team access without taking over accounts
See whether each server user is invited, active or disabled. Reset a user’s access, disable and enable them again, rename them or change their role, and remove host access or a shared resource. An Effective access view shows what each user can reach.
Released in 0.1.66 with a fix for a security issue: earlier versions let any administrator issue an invitation for an existing user and sign in as them. Every controller route now has a checked access policy; a route without one fails the tests. Administrators still manage users only; hosts, resources, compute and settings remain operator actions. The existing walkthrough does not show these actions.
How it works
Invite only new users
An invitation activates only a user who has no password and no live sign-in, so it can never sign in as someone who already uses the account. Choose its lifetime up to 7 days; the console preselects 24 hours.
Reset access in one step
Reset access removes the password, revokes every session and remembered device and issues one new invitation. Only the server owner can reset, disable, rename or change the role of another administrator, or create administrators.
Disable and enable safely
Disable revokes sign-ins and workspace grants and suspends published-resource grants instead of deleting them. Enable restores those grants; host assignments, budgets and account shares are kept.
Remove access deliberately
Remove host access once the user’s workspaces on that host are stopped. Unsharing a resource also revokes the user’s workspace grants of it.
Check effective access
Administrators and each user can list assigned hosts with active workspace counts, published resources, shared accounts, project shares and session shares.
Try the interface
Explore the sample projects, accounts, files and access requests. Live sessions and file transfers are available in your own console.
Release videos
- devctrl 0.4.0: Sign in to Core with GitHub, GitLab, Google or OpenID Connect chapter at 1:08 on YouTube
Put your server to work.
Give your agents persistent remote workspaces. Start with one repository and server, then add projects, developers and resources from the same console.