​
Overview

Reports let you scan indexed content across connected data sources to find broadly shared or externally exposed sensitive content based on criteria you define. Use them for point‑in‑time audits, exports to CSV, and investigations where you don’t need ongoing dashboard workflows. Note: Reports are on-demand or weekly CSV exports for ad‑hoc audits and offline analysis on content that is already searchable. Policies are saved, scheduled rules that scan continuously or weekly and surface findings in the Sensitive findings dashboard for in‑product triage and remediation.

​
Access and prerequisites

  • Access is restricted to admins with appropriate governance privileges (for example, Super Admin or Sensitive content moderator), as configured by your organization.
  • If you use Infotype scanning and your Glean deployment is on AWS, you must connect a Google Cloud DLP API key before running reports that include Infotypes.

​
Where to find Reports

  • In the Admin Console, go to Glean Protect → Reports.

​
Generate a report

Prerequisites

  • You must be a super admin or have the sensitive content moderator role enabled to create and view reports. If you’re running Glean on AWS and want to generate info type reports, your organization must have configured AWS for info type scanning with GCP.
  1. Go to Glean Protect → Sensitive findings → Reports and click Create report.
  2. Name the report and choose a frequency:
    • One‑time
    • Weekly (runs automatically once per week)
  3. Configure scope (data sources, time window, permission filters) and sensitive content criteria (see “Report configuration options” below).
  4. Click Generate. The report will appear in the Reports list with its status. When complete, download the CSV.

​
Report configuration options

You can tailor a report to reduce noise and focus on real risk:

​
Scope

  • Select all content or narrow by data sources.
  • Choose a time window (for example, created/updated/viewed in the past 30/90/365 days).
  • Permissions/visibility filters
    • Accessible via link to anyone within your organization.
    • Publicly searchable on the Internet.
    • Shared with N+ people internally or externally.
    • Limit by user emails, groups, or domains to check exposure for specific cohorts (for example, contractors).

​
Sensitive content criteria

  • Predefined Info types (PII, PCI, etc.).
  • Custom terms.
  • Regex patterns.
  • Specify terms that should not be flagged by this policy.

​
Limits and behavior

  • Concurrency: You can generate up to 5 reports at a time (including queued weekly runs).
  • Manage runs: From the Reports list, you can view status, see the parameters used, cancel an in‑progress run, or cancel a weekly series.
  • Scheduling: Weekly reports run automatically once per week. For continuous or near‑real‑time monitoring and in‑product remediation, use policies instead.

​
Output and fields

  • Download format: CSV.
  • Typical fields include document identifiers and metadata, visibility signals, and matched sensitive content attributes to help triage and remediate. Exact columns may vary as capabilities evolve.

​
Troubleshooting

  • Report isn’t starting or appears blocked
    • Check if you already have multiple reports generating or queued (respect the concurrency limit).
    • Confirm your role/permissions grant access to Sensitive findings and Reports.
  • No results or unexpected volume
    • Narrow the time window, refine permission filters, or switch from broad terms to precise Info types / regex.
    • Run smaller, data‑source‑specific scans to validate criteria before expanding.
  • Info types not matching

​
Supported info types

see Supported info types
Last updated: August 2025