One Intranet Platform. Every Department Keeps Its Own Space.
Employee portals sit on the same platform, the same data model and the same permission model as your customer-facing portals — with department-specific single sign-on, role-based access and record-level scoping enforced by the platform rather than rebuilt per audience.
Why Internal Audiences Belong on the Same Platform
External and internal, one data model
User Groups and row-level security allow one platform to serve external customers, partner organisations and internal staff from one underlying data model — with access and experience tailored per group, rather than a separate platform instance per audience.
Department-specific single sign-on
Each department or agency authenticates against its own identity provider behind a common Cognito layer. Adding a department becomes a configuration change, not an integration project.
Scoped to the right cohort
Row-level security scopes staff to a defined cohort — a program, a region, a care team, a subsidiary — enforced on every request at the platform level rather than through custom code per user type.
Data segregation inside one tenant
Business Units split a single tenant into separate scopes for pages, campaigns, forms and files per brand, region or team — while approved templates and shared assets stay governed centrally.
Internal comms without another product
Content, pages, forms, and email and SMS notifications are native to the same platform. An internal campaign or a staff notification is not a separately licensed tool to integrate.
Brand and policy consistency, structurally
Editors work within pre-approved sections and a governed theme rather than free-form design tools, so an off-brand or off-policy page is prevented by the platform rather than caught in review.
How a Multi-Department Portal Is Assembled
A content home per department
Each portal or microsite gets its own Stack9 Pages content repository — its own pages, media, assets and site settings, isolated from every other site, administered through one shared editorial workflow.
Identity per department, one portal
Department-specific SSO is configured behind the portal’s identity layer. Staff sign in with their own organisational credentials and inherit their organisation’s MFA policy.
Model the internal domain
Cases, requests, records and approvals become entities with workflow states — so an internal process is a trackable record, not an email thread.
Hand the day-to-day to the business
Content, branding, navigation, forms, notifications and journeys are owned by the teams that use them. Engineering is reserved for genuinely new building blocks.
Internal Portals in Production
Including the one April9 runs its own business on.
Stop Running a Separate Platform for Your Own People
The intranet, the partner portal and the public site can share one data model, one permission model and one vendor — with one point of accountability across platform, implementation and support.