Platform · Experience
Staff portals and public portals, from the same application.
Pages generated from your data to start, portals designed around each audience, and one set of data, rules, and permissions behind all of them. In your brand, in your users’ languages, on every screen.
Arrive
Working pages from the first day.
Define the data, and the application already has somewhere to live: a page for every entity, a menu that finds it, and an address people can read. From there, every page is yours to reshape, rearrange, or replace.
Generated to start.
Every entity arrives with a list page and a detail page, with a tab for each kind of related record.
Designed where it counts.
Portals for the public are laid out for their audience, from the same listings, forms, and dashboards, or started from a page template.
Navigation that keeps up.
Menus, breadcrumbs, and site search follow the page tree, and every page gets a friendly URL.
Tailor
Each person sees their own application.
Staff, applicants, and the public share one application, and each sees only their part of it. The pages they can open, the menus they see, and the buttons they can press all follow their role.
PageVisible to
- HomeEveryone
- ApplyEveryone
- My requestsApplicants
- RequestsReviewersProgram managers
- Request detailNot in menuReviewersProgram managers
- ProgramsProgram managers
- DashboardProgram managers
Pages open by role.
Each page opens only for the roles allowed to see it, and menus never show what someone can’t open.
Public where it belongs.
Information, eligibility checks, and applications open to anyone. Everything else waits behind sign-in.
One screen, adjusted.
Buttons, columns, tabs, and fields appear, hide, or lock by role or by any condition.
Only their own records.
Applicants see their requests, reviewers see the queue, from the same list, under the same rules.
Different experiences.Same application logic.
Staff portal
Reviewers and program managers
Partner portal
Program partners
Applicant portal
Applicants
Public site
Everyone
One application
- Data
- Workflows
- Rules
- Permissions
You don’t build a separate application for every audience. Staff, partners, applicants, and the public each get a portal of their own, and every one of them runs on the same data, workflows, rules, and permissions.
How people sign in, and how their roles are set: Identity & Access →
Work
Lists people can work from, not just read.
Most of the working day happens in a list: find the record, act on it, move to the next. Listings are built for that rhythm, and every entity comes with one, ready to shape.
Review queue
TableCardsCalendar
SearchStatus: In reviewOldest first
- R-2041Housing repair2 days
- R-2038Energy upgrade3 days
- R-2035Small business5 days
- R-2029Housing repair6 days
- R-2027Energy upgrade8 days
Request
R-2041
- Applicant
- A. Okafor
- Program
- Housing repair
- Amount
- $12,400
- Submitted
- 12 Sep
Request infoApprove
Find it.
Search, filters, and sorting are kept in the address, so a filtered view can be bookmarked or shared.
Act in place.
Edit a row inline, act on many rows at once, or open a record in a side panel without losing your place.
See it your way.
A table, cards, or a calendar, with columns chosen for each device, and a different default view on phones.
Take it with you.
Any list exports to Excel, CSV, or PDF, just as it’s filtered on screen.
Lists can refresh on their own, so a shared queue stays current. And forms open wherever the work is: inline, in a popup, or in a side panel.
Measure
The numbers that matter, on the first screen.
A dashboard answers the question every manager opens the application with: where do things stand? It’s built from the same data the work happens in, so there’s no export to wait for.
Grants overviewThis month
128
Open requests
342
Decided this month
4.2
Avg. days to decision
Requests per week
By program
Live, not exported.
Built from the data the work happens in, and refreshed on its own. No reporting pipeline to maintain for each application.
Personal, too.
A tile can follow the person looking at it: their open cases, their team’s backlog.
Any chart you need.
KPI tiles without code, and bars, lines, pies, or anything more specialized through standard charting libraries such as Chart.js.
Brand
Your brand. Not ours.
Start from brand settings, or take full control with a custom theme. Either way, people meet your organization, not the platform underneath it.
Brand settings
- Logo
- Grants
- Application name
- Grants Portal
- Primary color
- #1464DF
- Accent color
- #001E51
- Menu text
- #FFFFFF
Your identity, throughout.
Logo, icon, application name, and brand colors carry across every page, menu, and component.
Custom themes, down to the pixel.
Need more than colors and a logo? A custom theme controls every pixel and every line of markup: layout, typography, and components alike.
A layout for each moment.
Full portal pages, focused sign-in and registration screens, and distraction-free pages with no menu at all.
Open to your designers.
Standard HTML, CSS, and Bootstrap 5, with styles site-wide or per page. These are skills any web designer already has.
Reach
Every screen. Each user’s language.
A resident on a phone, an inspector on a tablet, a reviewer on two monitors. And not all of them in the same language.
Phone to widescreen.
Layouts adapt to the device, and menus fold away on small screens.
Their language, throughout.
The interface, forms, menus, and tabs translate, and page addresses can carry the language too.
Local formats.
Dates, numbers, and money follow each person’s locale.
Beyond the browser.
Push notifications to phones and browsers, and conversations in Microsoft Teams.
Include
Easy to use. Open to everyone.
A portal for the public can’t come with a training course, and it has to work for everyone in that public, including people who rely on assistive technology.
Familiar at every turn.
Lists, forms, buttons, and menus behave the same way on every page, so what people learn once works everywhere.
Guided the first time.
Step-by-step walkthroughs point out what’s where, and remember how far each person got.
Clear in the moment.
Problems are flagged on the field that caused them, and confirmations appear right where the person is working.
Forgiving.
Work in progress saves automatically, so a closed tab doesn’t mean starting over.
Accessible to the standards you’re held to.
Portals are built on accessible components and page structure (standard landmarks, and controls labelled for screen readers) that support WCAG, Section 508, and EN 301 549 conformance. And since themes, content, and layouts are yours, each portal can be tuned to the standard your organization answers to.
Discover
Public pages that search engines can find.
A public service only helps the people who find it.
Titles and descriptions for every page.
Each page carries its own title, meta description, and keywords, and they can come from the data, so every record’s page describes that record.
Addresses people can read.
Friendly URLs in every language, one preferred address for each page, and permanent redirects that keep old links working.
Ready to be found and shared.
A sitemap for search engines, and custom themes that set every tag in the page head, from sharing previews to structured data.
Related capabilities
Show us who your users are.We’ll show you their portal.
Staff, applicants, partners, the public. Talk to us, and see each of them in a portal of their own, on one application.