Use case

Help customers find their own answers.

Give each customer a workspace for their reports, dashboards, and data questions. Set the access rules so they can explore the information relevant to them.

Customer workspacesApproved dataUseful reportsAI questions
NORTHSTAR · CUSTOMER PORTALA reporting space that feels like theirs.
Account overviewUsageReports
Active users248Across 6 teams
Adoption84%This month
Service uptime99.9%Last 30 days

When your teams are most active

Weekday usage
Monthly account review Usage, adoption & servicePDF ↗

How it helps

Customer workspaces bring approved dashboards, reports, and AI analysis together. Authorized users can explore data, customize views, and receive scheduled reports.

Recurring report demandSelf-service without raw accessCustomer-specific controlsScheduled reporting

Who this is for

  • Customer success leaders
  • Customer portal owners
  • Partner program teams
  • Enterprise data sharing teams

Why it matters

Why does customer-facing analytics matter?

01

Recurring report demand

Customers need answers more often than a monthly report can provide.

  • Live answers between the monthly reports
  • Self-service reduces the request queue
  • Portal access controlled through SSO
READY FOR THE TEAM MEETINGA decision brief, built from the analysis.
REVENUE REVIEW

What changed.
What to do next.

+$73K Gross profit change

The evidence

0100200300$240Prior+66Volume+28Price-21Returns$313Current
Focus for the next review

Check the volume increase by customer and product.

Investigate returns before scaling the same approach.

02

Self-service without raw access

Approved datasets, never raw database connections.

  • Approved datasets, not database logins
  • Dashboards, reports, and pivots per permission
  • Row and field visibility enforced on every query
Give customers their own reporting view

03

Customer-specific controls

Data is scoped by customer, role, region, account, location, or user before a single row is rendered.

  • Scope by customer, role, region, account, or user
  • Filters applied before rendering, not after
  • Same rules govern exports and AI answers
ACCESS IN CONTEXTThe same report. The right view.
JM
Jordan · Regional managerWest workspace
What Jordan can access
ContentScopeAction
Sales dashboardWestView
Revenue reportWestExport
Customer contactsRestrictedBlocked
Permissions follow the work.Apply the configured boundaries to queries, AI, and sharing.

04

Scheduled reporting

Deliver Excel and PDF outputs on a schedule — no more manual spreadsheet work for your team.

  • Excel and PDF delivery on a schedule
  • Recipients controlled by permission
  • No manual spreadsheet work for your team
Schedule an approved report

How it works

How does customer-facing analytics work?

Map customer identity through SSO, and every dashboard, export, and AI answer is filtered to their rows only.

Share a report with the right audience
  1. 1

    Prepare a report

    Choose the data and metrics to include.

  2. 2

    Choose the audience

    Select the customers, partners, or teams.

  3. 3

    Set their access

    Configure records, fields, and export permissions.

  4. 4

    Keep it available

    Offer a portal or schedule approved reports.

Each audience receives the view allowed by your configured access rules.

Ready when you are

Bring your toughest data question.

See how your AI analyst and data scientist can turn it into findings your team can review and use.

FAQ

Frequently asked questions

What is customer-facing analytics?+

Customer-facing analytics gives external customers secure access to dashboards, reports, pivots, and exports based on their permissions. It replaces recurring spreadsheet requests with a governed self-service portal.

Can customers build their own dashboards?+

Yes. Customers can be given controlled self-service dashboard, report, and pivot creation permissions — always scoped to their approved datasets and rows.

Could one customer ever see another customer's data?+

No. Customer identity is resolved through SSO into a row-level filter applied at query time, so results are scoped before they are rendered rather than hidden in the interface. The same scope governs exports and AI answers.