Suspension
2026 extension — suspension rules move into a versioned policy engine with Continuous Access Evaluation for near-real-time revocation, plus Defender/Sentinel-driven automation. See Security Extensions →
Suspension lets you revoke access without deleting anything, enforced inside the pipeline. B5 Secure supports two kinds for advanced business applications.
User suspension
Suspend an individual identity — for example, a user under investigation or one whose payment has lapsed. Suspended identities are blocked from protected actions until reinstated. Exempt specific endpoints (such as a billing page) with [AllowSuspendedUser].
Entity suspension
Suspend an entire entity (such as a tenant or organization), cutting off all access that depends on it — useful when a whole account must be frozen rather than a single user.
Suspension runs before authorization, so a suspended identity never reaches your business logic even if its permits are otherwise intact.
Implementing suspension
Provide an ISuspensionService implementation that tells B5 Secure whether a given identity or entity id is suspended; the pipeline does the rest. Use NullSuspensionService when you don’t need the feature.
Talk to a human.
Get architecture guidance, Test Mode access, integration review, or help choosing the right B5 identity and authorization pattern.