Revocation-Aware Identity: Real-Time Portal Generation Gated by Heddle Feed
A new identity gate now synchronizes portal account creation with the live Heddle revocation feed, ensuring that revoked or at-risk identities can no longer slip through at onboarding time. This bridges the gap between identity lifecycle events and portal user provisioning, hardening the boundary where trust is established and enforced.

At a glance
113
merged changes
18
code projects involved
Underlined terms are explained: just hover or tap.
Imagine an operator onboarding a new partner or customer principal into the Helpifyr portal, only to discover-too late-that the account was provisioned for an identity that should have been blocked due to a recent revocation event. Until now, the portal’s generation pipeline could not guarantee that every new user reflected the latest revocation state: a revoked or suspicious principal could be onboarded between the time of revocation and the next periodic sync. This window, small as it might be, was a real risk-especially when onboarding is automated or integrated with external ERP or identity systems. The tension here is between automation speed and the need for real-time enforcement: operators and auditors need to know that every new portal user is vetted against the current, authoritative revocation feed, not just a stale snapshot.
01Why it matters
Why This Day Mattered
This change matters because it closes a critical timing gap at the boundary between identity management and portal user provisioning. By gating portal generation on the Heddle revocation feed, the system now offers a real-time guarantee: any identity that has been revoked, or is pending revocation, is immediately ineligible for portal onboarding. This is not just a technical improvement; it fundamentally shifts the trust model for operators and auditors. Now, access control and compliance teams can rely on onboarding events being tightly coupled to the true, canonical state of identity validity-no lag, no manual reconciliation, and no risk of onboarding a user whose identity is already compromised or withdrawn. For developers, this unlocks new patterns: ERP integrations and automated onboarding flows can be built with confidence that the portal will never provision access to a revoked principal, even in high-throughput or multi-tenant scenarios. For users, it means that their access rights reflect the true organizational intent, as of the very instant of onboarding.
The closed UTC day 2026-10-17 resolved into 113 merged PRs across 18 repos.
02What changed
What Actually Changed
The core shift is architectural: portal generation is now actively gated by a live pull from the Heddle revocation feed. Specifically, Helpifyr Fabric’s identity logic integrates directly with the Heddle feed, blocking portal account creation for any principal found in the revocation list. This is not a periodic reconciliation or a passive audit; it is an enforced, synchronous check at the moment of account generation. The mechanism is a feed-driven gate: when a portal creation event is triggered, the system queries the latest revocation state from Heddle, and only proceeds if the identity is clear. This closes the race window between revocation and onboarding, making the revocation feed a true source-of-truth for portal access. The integration is deep: the portal’s onboarding logic is now contractually bound to the feed, and the identity lifecycle is enforced at the boundary where it matters most-before any access is granted or credentials are issued.
03Why it holds better now
Why It Holds Better Now
This new state is technically superior because it removes the possibility of onboarding drift: there is no longer a lag between revocation and enforcement in the portal. The enforcement is atomic and synchronous with the revocation feed, eliminating windows where a revoked identity could be (even briefly) onboarded and granted access. The feed-driven gate is contract-based and testable: onboarding logic can be validated against simulated or real-time revocation events, ensuring that the system’s guarantees are both auditable and reliable. This also simplifies operator workflows: there is no need for periodic manual cleanups or downstream audits to catch revoked identities that slipped through. By making the revocation feed the canonical source for onboarding eligibility, the system ensures that every portal account reflects the current organizational intent and compliance posture, with no hidden state or reconciliation debt.
04Food for thought
Want to Know More?
How might this revocation-aware onboarding pattern be extended to other automated provisioning flows-such as API key issuance, delegated access, or cross-tenant grants-where real-time identity state is critical for security and compliance?
Terms in this post
- Fabric
- Module for rules, contracts and governance across the whole system.
- Heddle
- Module for identity, sign-in and SSO.
- source of truth
- The single authoritative source all other places align with.
- drift
- Target and actual state silently moving apart.
- PR
- Pull request: a reviewed code change that gets merged into the project.
- repo
- Repository: a code project under version control.
- operator
- The person or team running the system.
What would this look like in your company?
A pilot shows it with a real process.
More on Identity and access
See all
Identity and access3 min
Model-Resolution Leases: Precision Control for Identity, Custody, and Signing Paths in Fabric API Compose
Today, the Helpifyr/JaddaHelpifyr stack gains a new level of explicitness and operational separation in how model resolution is managed during API composition. With the introduction of model-resolution leases for consumer, identity, custody, and signing, the platform now orchestrates resource access and lifecycle boundaries with a clarity that was previously implicit or left to convention. This change is not just internal housekeeping; it redefines how API consumers, backend operators, and even downstream integrators can reason about, audit, and extend identity and custody flows in critical business processes.
Read
Identity and access4 min
Session-Bound Claims: Precise Invocation Control for cc_read Operations
The Helpifyr/JaddaHelpifyr stack now enforces session-bound claim tokens for cc_read operations, eliminating ambiguous worker claim reuse and providing a concrete, auditable chain from session authority to every resource access. This breakthrough ties each data read to a specific Heddle-issued session, raising both operational safety and forensic traceability for operators and downstream applications.
Read
Identity and access4 min
Projection as a Portal Service: Real-Time ERP Views, Rights, and Onboarding for Every Customer
Today's work transforms the Partner and Customer Portal from a static data sink into a living, rights-aware projection of each customer's ERP reality. By wiring Spindle's portal_projection into the portal's backend, onboarding, and UI, we unlock real-time, role-based access to ERP-linked data, events, and boost inventories, setting the stage for secure self-service and granular entitlement across tenants.
Read