Skip to content

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.

Jadda Helpifyr4 min read
Projection as a Portal Service: Real-Time ERP Views, Rights, and Onboarding for Every Customer

At a glance

76

merged changes

14

code projects involved

Underlined terms are explained: just hover or tap.

Picture a customer portal that feels like a lagging shadow of the ERP: data copied over in batches, rights modeled in brittle code, and onboarding that depends on manual intervention. Now imagine a portal where every user’s view is a live projection of their ERP state, their entitlements shaped by real contract assemblies, and onboarding flows that assign MFA and roles at the moment of registration, not weeks later. This is the tension Helpifyr’s portal stack has lived with: the need to move from brittle, duplicated logic and stale data to a model where the ERP’s truth is available, filtered, and actionable for every customer and partner, in real time.

Why This Day Mattered

This day marks the point where the Partner and Customer Portal becomes more than a static front-end to legacy data. By integrating Spindle’s portal_projection as a read-only service, every customer and partner can now see a real-time, rights-filtered view of their ERP-linked data. This isn’t just a technical cleanup: it means that onboarding new customers, assigning roles, and exposing boosts or entitlements can be done with confidence, knowing that the portal’s view is always in sync with the ERP’s actual state. Operators gain a single source of truth for user rights and inventory, eliminating the risk of stale or mismatched data. Developers can now build new features-like self-service onboarding, entitlement management, or granular event notifications-using projection as their contract, not as a guess. For end users, the portal feels alive: registration flows can assign Heddle accounts and MFA in one go, rights reflect contract assemblies, and boosts are visible per subscription. This unlocks a future where the portal is not just a view, but a self-service platform grounded in ERP reality.

The closed UTC day 2026-10-16 resolved into 76 merged PRs across 14 repos.

What Actually Changed

The portal’s backend now consumes Spindle’s portal_projection as a first-class service, with a feature-gate that enables it for target tenants. Registration flows have been overhauled to assign Heddle accounts and sign principal attestations immediately, making onboarding a single, atomic operation. Rights within the portal are now derived from activated Contract Assembly Manifests, ensuring that every user’s capabilities are determined by the same contracts that govern the ERP. Boost inventories are exposed per customer and subscription, and new event hooks (like portal_identity_registered) fire on key onboarding moments. The UI and mock adapters have been aligned to the real projection interface, eliminating the gap between test and production. This is not just about plumbing: the projection acts as a live, queryable contract, and the portal’s state is now a filtered, rights-aware materialization of ERP data.

Why It Holds Better Now

Previously, the portal relied on ad-hoc replication and brittle logic to approximate ERP state and user rights. This led to friction in onboarding, risk of rights drift, and a slow path for new features. With projection as a service, the portal’s state is always up to date and consistent with the ERP. Rights are enforced by contract manifests, not scattered code, making them auditable and safe to extend. Onboarding is now atomic: assigning a Heddle account, attesting the principal, and setting up MFA and roles all happen in one transaction, reducing operator burden and race conditions. Boost inventories and entitlements are exposed directly from the ERP’s truth, enabling granular, per-subscription features without manual sync. For developers, the projection contract provides a stable, testable interface to build on, and the feature-gate allows for controlled rollout. This model is safer, more expressive, and ready for future growth, including self-service, granular notifications, and cross-tenant features.

Want to Know More?

How could projection-based rights and inventory unlock self-service upgrades, entitlement workflows, or even automated provisioning for new tenants? What does it take to extend the projection to writable flows-like contract negotiation or real-time ERP actions-without losing the guarantees of atomicity and source-of-truth alignment?

Terms in this post

Spindle
Module for business rules and operational logic.
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.

Request a pilot

More on Identity and access

See all
Model-Resolution Leases: Precision Control for Identity, Custody, and Signing Paths in Fabric API ComposeIdentity and access

3 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
Session-Bound Claims: Precise Invocation Control for cc_read OperationsIdentity and access

4 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
Revocation-Aware Identity: Real-Time Portal Generation Gated by Heddle FeedIdentity and access

4 min

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.

Read