Identity lifecycle
Identity configuration affects existing customer access. A provider connection names an identity namespace, not just a login button. Before disconnecting or replacing it, inspect the customers and payments that depend on it.
Disconnecting a provider
Disconnection revokes the connection’s identity namespace, removes its linked identities from active use and suspends affected customers. Modem refuses the transition while linked purchases are unfinished or nonterminal Stripe subscriptions still require attention. Resolve those purchases or cancel the subscriptions, then retry the transition.
Changing settings uses the revision last read by the editor. If another session changed the connection first, reload its current state and review your edit before saving again.
Reconnecting a historical provider does not silently restore identities that may have missed lifecycle events while disconnected. Likewise, unsuspending a customer does not reverse a provider identity that has already been revoked. Restore access through the supported identity/customer workflow after resolving the cause.
Provider deletion events
For Clerk, configure the signed lifecycle webhook. For Firebase, configure the server deletion integration. The connection offers two deprovisioning policies:
| Policy | Effect |
|---|---|
| Keep active product grants | Delete the provider-linked customer while keeping active grants; Stripe subscriptions continue billing. This is the editor’s default. |
| Complete active product grants | Cancel paid subscriptions first; after cancellation succeeds, delete the customer and end active grants. |
Choose the policy intentionally for your billing model. The selected policy determines the handling of linked subscriptions. Identity revocation and customer suspension can occur before billing cancellation finishes.
A webhook acknowledgement means Modem received the event. Inspect the resulting customer and subscription state before assuming cleanup completed. Refunds and cancellation explains why billing actions are independent of access removal.
Existing sessions and streams
A Modem session is not a permanent entitlement. Customer suspension, deletion, provider revocation and session replacement can end access while a request is running. The SDK reports access invalidation and clears affected session state; update the UI rather than retrying forever with the same identity token.
The gateway checks access during an active stream. If those authoritative checks themselves become unavailable, it can stop with stream_authorization_unavailable. That error is an availability failure, not proof that the user was deleted or revoked. Preserve the request ID and distinguish it from an explicit access refusal.
See session handling and gateway errors for client recovery.