Permissions and safety switches

Atlas — permissions and safety switches

Atlas decides what a person or system is allowed to do, including an emergency stop on a sensitive change. It does not hold account balances.

For your technology team. Atlas is the central service for permissions and controls: which institutions (tenants) and modules are licensed, feature switches, emergency stops (kill switches), and capability checks. That includes the checks that must pass before a change on account-opening and money-movement platforms. Atlas holds controls, not core banking data.

What it does

  • Decides what a person or a system is allowed to do.
  • Turns product features on or off for an institution.
  • Limits an entitlement to a period of time.
  • Stops a sensitive change when the emergency switch is on.
  • Stops a sensitive change when permission cannot be confirmed.
  • Checks that the institution is entitled to the module it is using, including an on-premises license check.
  • Writes an audit when an entitlement or a safety switch changes.
  • Does not hold account balances, and it does not replace sign-in. Aegis does that.

Who uses it

Risk, operations, and platform administrators who control access and safety switches.

Detail for your technology team

  • The list of institutions (tenants) and their modules, with time-limited licenses
  • Live permission checks, and checks of signed license files
  • A check other platforms call before they allow a change
  • A log of every change to permissions and emergency stops

How it connects

Atlas CONNECTS TO Aegis Staff sign in through Aegis; Atlas does not replace sign-in and identity Nova / TeKYC / Titan Account-opening, money, and identity changes ask Atlas first; where a path is set to stop on failure, a failed check stops the change Pulse, Ceres, and other money platforms Ask whether an action is allowed before a sensitive operation Regulated platforms Use the same permission interface across every Trudi platform
Connections named on this page, with the platform marks. The diagram does not show balances or a live screen.
  • AegisStaff sign in through Aegis; Atlas does not replace sign-in and identity
  • Nova / TeKYC / TitanAccount-opening, money, and identity changes ask Atlas first; where a path is set to stop on failure, a failed check stops the change
  • Pulse, Ceres, and other money platformsAsk whether an action is allowed before a sensitive operation
  • Regulated platformsUse the same permission interface across every Trudi platform

What it is not

The customer master file (CIF); the general ledger; payment rails; the system of record for user sign-in (Aegis).