Approvals and submissions
Review every submission, approve or reject with a reason, and see pending counts per form. Members and admins get real-time notifications, with a banner waiting for anyone who was offline.
Powered by Klarica
Build dashboards, forms, letters and approvals without writing code. Brand each plan in one guided run. Let AI draft the heavy lifting, with guardrails and sign-offs you control.
The platform
From a member’s first login to an administrator’s final approval, Protea covers both sides of the journey: the toolkit for the people who build, and the portal for the people who belong.
Drag, drop and resize charts, tables and summaries. Bind them to live SQL or external APIs.
Multi-page forms with repeaters, signatures, validation and fields pre-filled from member data.
Describe what you need in plain English. Get SQL, dashboards, forms and templates drafted for review.
Point Protea at a provider’s website and get a theme, curated dashboards and matched forms.
A review queue for form submissions and AI runs. Approve, reject and track in real time.
Word-document letters and HTML emails with smart placeholders that know where their data lives.
Colours, typography, layout, logo and login screen, tailored to each plan.
SQL Server datasources, reusable global queries and external API libraries, ready to bind.
Auth0-backed sign-in, invite-only registration, and access scoped by role and by plan.
Dashboard Builder
Constructors compose a member’s home screen on a drag-and-drop canvas. Members get a clean, read-only view that looks like it was made for their scheme, because it was.
{{placeholders}} that scope every value to the member viewing itForm Builder
Pension paperwork is repetitive. Protea forms know who is signed in, pre-fill what’s already known, and route the rest to the right person for approval.
White-label theming
Members never see “a vendor’s portal”. They see their scheme. Themes are configured per plan and applied across every dashboard and form, with a live preview as you tweak.
AI Studio
Protea uses Anthropic’s Claude for the tedious first draft, then keeps a human in the loop for anything that matters. Generated SQL is a suggestion you review, never something that runs on its own.
SELECT s.SchemeName, SUM(c.AmountDue - c.AmountPaid) AS Arrears FROM dbo.Contributions c JOIN dbo.Schemes s ON s.SchemeId = c.SchemeId WHERE c.DueDate >= DATEADD(QUARTER, DATEDIFF(QUARTER, 0, GETDATE()), 0) GROUP BY s.SchemeName ORDER BY Arrears DESC;
Four widgets drafted and bound to your saved queries. Open the Dashboard Builder to refine.
Drafted in seconds. It opens in the Form Builder, so you tune every field before it goes live.
Illustrative example. Real output depends on your datasource schema and prompt.
SQL generation is built from a datasource’s table and column names and types, not row data. Nothing is executed for you.
Upload an existing paper form and review the rebuilt version step by step before it’s created.
Generate email templates and their tokens, and let AI classify each letter placeholder as form, SQL or calculation.
Register agents with their own model, prompt and tools. Set guardrails: approval, PII redaction, rate limits and blocked actions.
Turn approval on and every agent run waits for a human. Each run is logged with its tokens, duration and status.
AI usage is metered per call, with monthly token and spend totals, so there are no surprises on the invoice.
Plan onboarding
Give Protea a provider’s website. It works through three stages, streaming progress as it goes, and a person signs off before anything new is created.
Colours, logos, background images and fonts are extracted from the provider’s site and turned into a matching theme.
A curated set of template dashboards is cloned for the plan and styled with its new theme.
Existing forms that already fit are linked. Where none do, new drafts are written and held for approval.
Generated forms always land in the approval queue first, whatever an agent’s own settings say.
Day to day
The unglamorous work that keeps a pension administration team moving, handled.
Review every submission, approve or reject with a reason, and see pending counts per form. Members and admins get real-time notifications, with a banner waiting for anyone who was offline.
Upload a Word document and define its placeholders as form fields, SQL results or calculations. AI suggests which is which, with a confidence rating and reason for each.
Named HTML templates with their own tokens, optionally scoped to a single plan. Describe the email you want and let AI write the first version.
Create and edit users, assign roles, and link people to the plans they belong to, including bulk assignment by CSV import.
Search for a member and open their dashboard read-only in a new tab. The fastest way to answer “why does mine look different?”.
Platform-wide branding for the login screen and feature toggles, in one place, cached for speed.
Data and integrations
Protea doesn’t ask you to move your records. It connects to them, and keeps every query scoped to the member who’s looking.
{{externalUserId}} keep each query member-specific, resolved on the serverSecurity and architecture
Access is checked twice, once at the edge and again inside every service, and every service reports what it’s doing.
Under the hood
Questions
Pension administrators, trustees and scheme providers. Constructors (your own team) build the dashboards, forms and templates. Members and delegates use the finished portal. Administrators and HR review what comes in.
No. Every builder is visual and the AI assistants can draft the first version for you. Connecting a new SQL Server datasource is a one-off setup step.
Yes. Themes are configured per plan and apply across that plan’s dashboards and forms. The onboarding wizard can even build a theme from the provider’s own website.
Only what you allow. Generated SQL is shown for review and never executed by the AI service. Agents can be set to require approval, and generated forms in plan onboarding always wait in the approval queue.
For SQL generation, it sees the table names, column names and types of the datasource you pick, not the rows inside. Other features send only what they need: your prompt, an uploaded document, or a public web page you point it at.
Protea ships as container images with Helm charts for Kubernetes, connecting to your own MongoDB, SQL Server and Redis. Talk to us about the deployment model that suits you.
Tell us about a scheme and we’ll show you its portal, branded and populated, in a live demo.
Request a demo