Skip to main content

Introduction

Bastion sends these notifications when identities and accounts in your organization gain or lose the ability to transact for compliance reasons. There is a single type of event trigger for compliance notifications:
  • identity_status_update events: Sent whenever an identity (and its associated accounts) undergoes a change in status. These can happen for various reasons:
    • During onboarding, Bastion initiates compliance checks for an identity when it receives a Submit Compliance Data request. The event returns updates to the status, or indicates if an RFI is required.
    • Throughout the customer lifecycle post-onboarding, a change in identity status can occur. For example, an identity could move from ACTIVE to SUSPENDED.

Identity status update events

An example identity_status_update event payload of an identity that has completed onboarding is as follows:
An example identity_status_update event payload of an approved identity that has been suspended is as follows: