Dashboard
Gateway
Evidence
Recent requests
Everything an approver needs is on the card. If a decision needs information that is not here, that is a bug in the card, not a reason to guess.
Sessions happening right now. A jump box holds ONE login however many people are watching it — asking to join attaches you to the screen that is already open, which is why it needs the person in the chair to say yes as well as an approval of your own.
Each machine's credential situation, in the words the database uses. A shared secret that cannot be rotated is always recorded, and cannot be configured otherwise. A jump host shows what it reaches, because that is what approving it grants.
What this product knows about itself. Every sign-in attempt is recorded, refused ones especially — an attempt against an address that matches nobody is the likeliest sign of somebody probing, so it is shown to every vessel rather than to none.
People on this vessel
Signed in now
Sign-in attempts
Every session that ran, in order, hash-chained. The chain detects a record altered or removed, and — once anchored — one removed from the end. It cannot prove a recording is truthful, and does not claim to.