New App: Terminals — open a real SSH terminal inside your workspace, in the browser, with no SSH client and no key handed to anyone.
Terminals: an administrator saves a connection once (host, user, key) and grants it to a role, a team or a person. The credential stays encrypted on the server and is never shown again, so removing someone's access is one change instead of a key rotation across every server.
Terminals: every session is recorded and can be replayed in the browser exactly as it happened. Refused attempts are recorded too, so the log answers who tried to reach what and was turned away.
Terminals: closing the tab no longer kills your work. The shell keeps running on the server and you can re-attach later with the screen you left restored.
Terminals: several terminals open at once as tabs on one page, each with its own session, and any tab can be popped out into its own window.
Terminals: connections can be attached to Projects, so a project page answers "which servers does this project touch?".
Terminals: each connection can carry its own colour, shown on its tabs, so a production server is not mistaken for a staging one.
Terminals: personal display settings per user — font, size, colour theme, cursor and scrollback — applied to every terminal you open, on any device.
Terminals: server host keys are pinned after an administrator confirms the fingerprint, so a server that has been swapped or impersonated is refused rather than silently trusted.
Terminals: session limits an administrator controls — idle timeout, maximum session length, and how many terminals one person may keep open. Withdrawing someone's access closes their open shells immediately rather than at the next timeout.
Updates
Recordings can be filtered by user and by status, and an administrator can delete a recording. The session itself stays in the audit log and the deletion is recorded against the person who made it.
