Skip to main content
The route /ce/analytics does not render a dedicated analytics hub page in the current codebase. Individual analytics views are mounted at sub-paths: /ce/analytics/pipeline, /ce/analytics/partners, /ce/analytics/calls, /ce/analytics/campaigns, and /ce/analytics/activities.

​
Overview

No component is mounted at the bare /ce/analytics path. All CE analytics are accessible via their specific sub-routes listed below. This documentation page serves as a navigational overview until an analytics hub is implemented. Available analytics routes:

​
Who it’s for

Access follows your organization’s role and module configuration. Each sub-route has its own permission gate.

​
Before you start

Navigate directly to one of the sub-routes listed in the table above.

​
Steps

1

Choose an analytics view

Select the relevant analytics sub-route from the CE sidebar or the table above.

Community Engagement

Community Engagement core overview.

Governance & parity

This page documents shipped product behavior. It is not medical, legal, or billing advice. Verify against your organization’s policies and applicable regulations before using it for clinical, compliance, or billing decisions. Protected health information (PHI) shown in the product is governed by your tenant’s access controls and is never exposed in this documentation.
  • src/routes/ce.tsx
  • src/cores/ce/pages/PipelineDashboardPage.tsx
  • src/cores/ce/pages/PartnerScorecardPage.tsx