[ Employee offboarding ]

Offboard anyone in one action

Removing a person in ROIkeep bans them from every connected app, ends their active sessions, and writes an audit entry. It is one action, performed by an owner, from one console.

[ What happens ]

One action, every module

Every module signs in through the hub, so there is one account to remove, not one per tool.

  • Banned everywhere at once

    The person is banned from every connected app in the same action.

  • Sessions ended

    Their active sessions end immediately.

  • On the record

    An audit entry records the removal.

  • Signed and timed

    The revocation message to each app is signed with HMAC and carries a five minute timestamp window.

the hub console showing a person's roles and the remove action

[ What they hold ]

Know what to collect before they go

Company property has a named holder, so an exit comes with a list rather than a guess.

See device management
  • Devices and keys

    Computers, phones, and office keys are recorded against the person who holds them.

  • Shared credentials

    Vaults are shared with named people, so you can see what was shared with whom.

  • GitHub collaborators

    Linked GitHub repositories show their collaborators. ROIkeep reads GitHub and never changes it.

[ Onboarding ]

Joining is one invite

A new person gets one account by invite, with a role in each module. There is no open sign-up, and access is granted in the same place it is removed.

See team management

[ The limit ]

What it does not reach

One action removes access to every ROIkeep module. Accounts in tools outside ROIkeep still need removing in those tools.

See it running

Book a call and we walk you through it. Check whatever you need to check.