Title
Instance-wide admin access to view and manage all users SSH hosts and credentials
Platform
Web-app
Is it related to an issue?
Hosts and credentials in Termix are scoped per-user. RBAC lets users opt in to sharing, but there's no top-down view for an admin to audit, recover, or manage hosts/credentials owned by other users.
This breaks down in real multi-user deployments:
- Offboarding, when a user leaves, their hosts/credentials are orphaned, no clean way to re-assign or delete.
- Incident response, can't inspect or rotate a suspected-compromised credential without the owner's cooperation.
- Audit, no way to enumerate what exists across the instance, who owns what, and which auth method is used. Blocker for regulated environments.
- Recovery, if a user is locked out at the moment its very manual and difficult to fix, you have to go in the database and make manual user changes to recover user successfully.
The Solution
A new tab in Admin Settings (e.g. Host & Credential Management) showing every host and credential on the instance with owner, auth type, last-used, and shared-with. Admins can:
- View host configs and credential metadata for any user.
- Re-assign ownership, edit, or delete.
- Env-variable kill-switch (
ADMIN_CAN_VIEW_SECRETS=false by default)
- Re-auth / TOTP at point of access
- Mandatory audit log entry (actor, target, action, timestamp, IP)
Additional Context
No response
Title
Instance-wide admin access to view and manage all users SSH hosts and credentials
Platform
Web-app
Is it related to an issue?
Hosts and credentials in Termix are scoped per-user. RBAC lets users opt in to sharing, but there's no top-down view for an admin to audit, recover, or manage hosts/credentials owned by other users.
This breaks down in real multi-user deployments:
The Solution
A new tab in Admin Settings (e.g. Host & Credential Management) showing every host and credential on the instance with owner, auth type, last-used, and shared-with. Admins can:
ADMIN_CAN_VIEW_SECRETS=falseby default)Additional Context
No response