Reports

Enterprise reports for managers, teams, and auditors.

Kommento Reports is the management workspace behind the portal: user activity, failed logins, time spent in the workspace where captured, team usage, scan volume by day or week, domain coverage, API usage, and export history with audit-ready context.

  • Executive, team, user, scan volume, and API usage reports
  • Failed login, audit event, actor, target, and IP visibility
  • CSV, JSON, PDF, TXT, and print-ready exports by permission
See The Builder Plan Reporting
Portal report builder

Choose a management report, set the period, then inspect usage and audit signals in one workspace.

The public page now mirrors the real portal flow: pick a template, filter by team, user, usage type, or period, then review manager-grade metrics instead of treating reporting as a domain-only summary.

Report Builder Ad hoc reporting workspace

Account, team, user, scan-volume, individual scan, API, and audit reporting.

Audit ready
ExecutiveWorkspace summary TeamsTeam totals UsersActivity and domains Scan VolumeDay, week, month API UsageCalls and keys Audit EventsActors and targets
Report nameManager Activity Review PeriodLast 7 days TeamOperations UserAll users Usage typeAll activity Group byUser + day
User activity 31 active users
Time in workspace 184h captured sessions
Failed logins 9 needs review
Domains scanned 58 this period
Scans this week 412 across 6 teams
Scan volume Daily usage trend
Mon Tue Wed Thu Fri Sat Sun
1,284 audit events 37 exports 14 API keys tracked
Signal Actor or team This period Audit state
User activityLast login, actions, time Priya M. 94 min, 18 actions Pass
Failed loginSecurity event marcus@client.test 3 attempts, 2 IPs Review
Scan volumeTeam workload Team Atlas 128 scans, 17 domains Pass
API usageDeveloper key activity Production key 1,840 calls Tracked
Report exportCSV and PDF Maya S. 2 exports Recorded

Enterprise scope

Reports answers the questions managers actually ask.

Domain detail still matters, but the reporting area is bigger than domain evidence. It is for accountable teams that need to understand people, volume, permissions, events, exports, and operational pressure.

User Activity

Who used the workspace?

Review active users, last activity, last login context, actions taken, time-in-workspace indicators, and user-linked scan activity.

Login And Security

What needs review?

Surface failed logins, high-signal security events, actor and IP context, target details, and event types that need administrator attention.

Scan Volume

How much work happened?

Report total scans, domains scanned, team usage, daily and weekly buckets, all-time usage, and period-over-period operating load.

API And Exports

What left the system?

Track API calls, key activity, report exports, export permissions, and audit records so managers can explain data movement cleanly.

Report templates

Start with the report type, then narrow the people, period, and usage lens.

The portal templates are built for enterprise reporting workflows: executive rollups, team comparisons, user accountability, scan volume, individual scan rows, developer API activity, and audit review.

Executive Summary

Workspace-level scans, domains, teams, users, and usage totals for leadership review.

  • Period scans and domains
  • Team and user counts
  • Summary, trend, and detail sections

Team Reporting

Compare team scan totals, user participation, domain coverage, and all-time usage.

  • Team-linked ownership
  • Usage by selected period
  • Coverage and activity rows

User Reporting

Show user activity, domains touched, last scan, last login context, and detail rows.

  • User and email columns
  • Activity and scan totals
  • Last activity visibility

Scan Volume

Measure usage by period, team, user, or domain to understand daily and weekly load.

  • Daily and weekly buckets
  • Domain and scan counts
  • First and latest activity

Developer API Usage

Report API calls, key activity, active buckets, status, prefixes, and all-time calls.

  • Tracked API keys
  • Period and all-time calls
  • Developer usage visibility

Audit Logs

Review administrative, API, scan, team, security, and investigation activity by actor and target.

  • Action, actor, target, and IP
  • Security event review
  • Export and permission evidence

Auditing and permissions

Reports is built for accountable teams, not just prettier scan summaries.

Enterprise reporting needs to explain access, exports, user actions, API activity, and security events. The portal uses report and audit permissions so administrators can control who views reports, who exports them, and who can inspect sensitive event history.

  • Use report.view to control who can access reporting
  • Use report.export to control downloads and export limits
  • Use audit.view to review administrative, login, API, scan, and team events
  • Record export activity so managers know when a report was downloaded
  • Filter audit events by action, actor, target, search text, time, and IP context
Audit workspace Full event history
Security events Failed logins, login activity, CSRF, canary, API, scope, path, and target-block events.
Administrative activity Team changes, user actions, permission-sensitive events, and investigation history.
Export accountability Report downloads can be logged with actor, time, format, target, and workspace context.
Manager filters Action, actor, target, search, date, IP, severity, and event type help teams find the right evidence fast.
Reports downloads

Export the manager-ready view without losing the audit trail.

Reports downloads are tailored for the audience: Visual PDF for leadership, Client-Safe PDF for outside sharing, JSON for systems, CSV for analysis, and TXT for ticket notes. Export permission and audit records keep the handoff accountable.

Workflow

The reporting path turns portal activity into a manager-grade answer.

Managers should not have to ask five people for five spreadsheets. Reports keeps the template, period, team, user, usage type, source rows, and export controls in one builder.

1

Choose a template

Executive, team, user, scan volume, individual scan, API usage, or audit-focused review.

2

Set filters

Select the period, team, user, usage type, grouping, and sections to include.

3

Inspect activity

Review users, logins, time, domains, scans, API calls, and audit events.

4

Export evidence

Download the right format while keeping export permissions and history visible.

FAQ

Reports questions.

Is Reports only about domains?

No. Domain coverage is one part of the story, but Reports is for enterprise managers who need user activity, team usage, login/security context, scan volume, API usage, exports, and audit records.

Can managers see failed logins?

Where the workspace captures those events and the user has audit permissions, failed login and related security events can be reviewed with actor, target, time, IP, and event-type context.

Can Reports show scans by day or week?

Yes. Scan Volume reporting is designed around selected periods and grouping, so teams can review scan counts, domain counts, first activity, latest activity, and usage buckets.

What can user reporting show?

User reports can show user identity, email, scans, domains, last scan, last activity, last login context, and source detail rows available to the reporting workspace.

Can API usage be reported?

Yes. Developer API usage reporting can show API calls, key status, prefixes, active buckets, period calls, all-time calls, and tracked keys.

Who should use Reports?

Reports is for managers, administrators, team leads, compliance reviewers, security reviewers, client success teams, and operators who need a clear answer from portal activity.

Manager-ready reporting

Give leadership the report, and give administrators the audit trail.

Kommento Reports helps teams move from raw portal activity to accountable summaries: who used the platform, what was scanned, which domains were covered, what failed, what exported, and what needs review.

Plan Reporting Review Audit Controls