Review Knowledge Analytics

Knowledge → AnalyticsKnowledge administrators2 min read
What you’ll learnHow to use the current analytics pages to monitor Knowledge usage without exposing user content.

Open Analytics

Open /knowledge-analytics. The current navigation uses Overview, Questions, Knowledge Base, and Security. The exact data and security sub-tabs depend on your access. All views provide a From/To date range, Refresh, and the last refresh time.

Use the right view

View Use it for
Overview Read the high-level Knowledge activity and health summary.
Questions Review response time and pipeline timing, AI model use, query language, the retrieval funnel, unanswered-rate trends, and detailed question data.
Knowledge Base Review total documents and chunks, extracted images, file and chunk types, processing status, document sizes, most-referenced documents, and unused documents.
Security Review access decisions, policy classification and coverage, rejection reasons, denied documents, audit records, and policy data.

Use the search, date, and table controls shown in the selected view to narrow the result. Analytics is for investigation; it does not change an assistant, a document, or a user's access by itself.

Read Overview

Start with KPI cards and trends to understand volume and change over the selected period. The overview includes questions answered over time and high-activity information such as active users. Clickable KPIs can open a detail drawer with search, sorting, and pagination.

Review Security & Audit

Security contains these sub-tabs:

  • Dashboard for KPIs, access decisions over time, policy classifications, rejection reasons, most denied documents, and policy coverage for Documents, Pages, and Nodes;
  • Audit Log for searchable and sortable access records;
  • Rejections for denied or failed retrieval decisions; and
  • Policies, visible to administrators, for policy records.

Use the table search and sorting before exporting or escalating a finding. A denial can be an expected policy decision, so verify the user, resource, time, and applicable policy before treating it as a defect.

Good practice

Use aggregate patterns first. When you investigate an individual item, follow your organization's privacy policy and use only the access you need.

Still stuck? See Get Help with Support or reach your workspace administrator.