Public application dashboard

One public intake surface, five governed application shells.

Residents, businesses, and public users can start applications from one public dashboard while each shell keeps its own governance, reporting, and operational flow behind the workbench.

Public application intake is available to general users.

Admin and Compliance roles still govern downstream screening and reporting.

Each shell keeps its own routing, policy pack, and operational context.

Healthcare governance shell

Healthcare shell

Clinical governance has its own shell route while execution, approvals, retrieval, and audit stay on the shared governed platform.

Clinical reviews

Healthcare teams keep PHI-sensitive work, review steps, and evidence inside a healthcare-specific shell.

Residency controls

Sector policy, geography targeting, and runtime safeguards stay aligned with the configured healthcare compliance profile.

Approvals

Governance routing and evidence continue to run through the current approval system while sector-specific healthcare surfaces evolve here.

Open public application dashboard

Government operations shell

Government shell

Public-sector teams now have a dedicated government shell so ministry groups can scale horizontally without forking the governed platform core.

Executive, finance, and public safety

Executive Council, Treasury Board and Finance, and Justice and Public Safety can grow under the government shell with shared governance, audit, and approval controls.

Health, education, and social delivery

Health, Assisted Living and Social Services, and education-linked public delivery remain visible as government groups even while healthcare and school keep their own sector shells.

Infrastructure and citizen services

Transport, environment, service delivery, municipal operations, energy, agriculture, jobs, and cultural ministries can be grouped here without falling behind other shells.

Open public application dashboard

Legal governance shell

Legal shell

Matter-aware presentation now has its own shell, while execution, approvals, retrieval, and audit still run through the shared pipeline.

Matters

Matter list and daily queue are still pending. This shell is the foundation for that focused legal view.

Ethical walls

Retrieval authorization already fails closed on unverified matter context. UI wiring remains to be completed.

Approvals

Legal-specific approval surfaces come next after configured approver routing replaces the current healthcare-specific path.

Open public application dashboard

Education operations shell

Education shell

Education teams now have a dedicated sector route while student-privacy governance continues to use the shared platform controls.

Student privacy

Student records, staff workflows, and education operations remain governed by the active education-sector compliance profile.

Operations

This dedicated route creates a clear education entry surface without diverging from the current governed execution path.

Approvals

Approval routing, evidence, and retrieval controls stay shared so education-specific surfaces inherit the latest app changes.

Open public application dashboard

Enterprise governance shell

Enterprise shell

Banking, brokerage, real estate, technology, and other business sectors now resolve into one enterprise shell while shared governance, execution, and evidence flows remain consistent.

Business coverage

Banking, brokerage, real estate, insurance, technology, retail, and other commercial sectors share one enterprise shell without losing sector-specific governance packs.

Shared controls

Privacy, approvals, and policy evidence continue to inherit the same shared controls and app updates as other sectors.

Expansion path

This route creates a dedicated enterprise shell surface for future sector-specific dashboards without fragmenting the platform.

Open public application dashboard