One Front Door. Every Audience Sees Only Their Own.
Customers, members, employers, brokers, providers and internal staff — authenticated against your identity provider, scoped by role and by record, and reading and writing to your system of record in real time.
What Makes a Multi-Audience Portal Work
One platform, many audiences
Comcover Launchpad gives 168 Commonwealth entities a single sign-on dashboard, with role-based access scoping each entity to its own applications and data. One platform — not one instance per audience.
Scoped to whose data, not just what data
Row-level security is enforced at the platform level, not in custom code per user type. A broker sees only the employers they manage; a provider sees only the participants they are actively treating; a sub-entity administrator sees only their own subsidiary.
One user, several roles
The native User Group model lets a single person belong to multiple groups at once — a broker who is also an internal delegate for a specific employer. Group permissions govern both what the UI shows and what the back end will actually do.
Identity-provider agnostic
AWS Cognito fronts the portal, with your enterprise IdP — Entra ID, Okta, or another — sitting behind it. Adding or changing an identity provider becomes a Cognito configuration change rather than custom integration work in the portal. Stack9 implements no MFA of its own by design; your IdP’s policy is inherited automatically.
In front of your system of record, not instead of it
The portal reads from and writes back to the system of record in real time — FINEOS, Dynamics, a policy admin system — rather than maintaining a separate copy of the data or the status logic. Comcover’s claim forms integrate directly with MS Dynamics CRM.
Reporting your members can see
Customer-facing reporting — policy status, payment history, claims summaries — is delivered through embeddable tools such as Power BI, configured against the same entity data used across the rest of the portal.
The Recurring Pattern
Authenticate a diverse mix of external users
Claimants, employers, members, brokers and providers against one or more identity providers, with permission and visibility levels defined in consultation with you — because record types and data sensitivity vary widely by organisation.
Guide them through structured self-service
Multi-step, validated intake and self-service journeys — screening questions, attachments, save-and-return, submission tracking — built on a schema-driven form engine.
Integrate with the system of record in real time
Connectors register each external system behind one consistent interface, so the portal integrates against a stable contract rather than point-to-point against every underlying system.
Adjust after launch without a release
Feature flags and portal-wide configuration let capability be enabled, disabled or tuned post-launch — and form structure changes in the back office with no code change and no redeployment.
Portals in Production
Federal government, member organisations and regulated fundraising — the same platform underneath.
The Platform Accelerates It. We Still Build It Around You.
Web App Templates, the headless CMS, Connectors and Stack9 Core significantly accelerate delivery — but a self-service portal remains a solution tailored to your workflows and your data. We would rather say that up front than discover it in delivery.