Security & Backup

KnowBe4 Reporting

Bring your KnowBe4 KSAT account into Dex - browse users, groups, risk scores, and phishing and training campaign results in plain language.

Dex connects to the KnowBe4 Reporting REST API so admins can explore one KSAT account conversationally. It is read-focused: look up account details, users and their risk score history, groups and members, phishing campaigns and security tests with their recipients, and training campaigns and enrollments. This is the per-tenant Reporting app - each connection stores its own Reporting API key for one KnowBe4 account. For MSP multi-account metadata across the Partner Product Graph, use the separate KnowBe4 Partner app.

Start free →See Dex Live

What Dex does with KnowBe4 Reporting

Dex handles both admin workflows and employee self-service — all policy-guardrailed and audit-logged.

For admins (Dex Pro)

Read KnowBe4 account metadata for the connected Reporting API key
List users and look up any user, including their risk score history
List groups, read a group, and list its members
Browse phishing campaigns and drill into individual campaigns
Review phishing security tests and their recipients (paginated, since lists can be large)
List training campaigns, read a campaign, and list training enrollments

Just ask Dex

Your team types a request in plain language. Dex investigates, plans, and executes — with the right guardrails.

Admin prompts

>What KnowBe4 account is this Reporting key connected to?
>Show me the risk score history for the user jsmith@example.com
>List the members of the "Finance" group in KnowBe4
>Which recipients failed the latest phishing security test?
>How are the current training campaigns tracking - show enrollments

Policy actions

Every action Dex can take on KnowBe4 Reporting is declared, scoped, and guardrailed. Admins control which apply, who approves them, and whether they're limited to self-service.

Action	What it does	Guardrails
`knowbe4_get_account`	Read KnowBe4 account metadata for this Reporting API key	—
`knowbe4_list_users`	List KnowBe4 users	—
`knowbe4_get_user`	Read one KnowBe4 user by id	—
`knowbe4_get_user_risk_history`	Read one KnowBe4 user's risk score history	—
`knowbe4_list_groups`	List KnowBe4 groups	—
`knowbe4_get_group`	Read one KnowBe4 group by id	—
`knowbe4_list_group_members`	List members of one KnowBe4 group	—
`knowbe4_list_phishing_campaigns`	List KnowBe4 phishing campaigns	—
`knowbe4_get_phishing_campaign`	Read one KnowBe4 phishing campaign	—
`knowbe4_list_phishing_security_tests`	List KnowBe4 phishing security tests	—
`knowbe4_get_phishing_security_test`	Read one KnowBe4 phishing security test	—
`knowbe4_list_security_test_recipients`	List recipients of one KnowBe4 phishing security test (paginate; can be large)	—
`knowbe4_list_training_campaigns`	List KnowBe4 training campaigns	—
`knowbe4_get_training_campaign`	Read one KnowBe4 training campaign	—
`knowbe4_list_training_enrollments`	List KnowBe4 training enrollments	—

How to configure KnowBe4 Reporting

Onboarding takes minutes. Dex validates your credentials before saving them.

Setup steps

1
In the KnowBe4 KSAT console, go to Account Settings > Reporting API (or Account Settings > API) and create a Reporting API key for Dex.
2
Note your KnowBe4 region: us, eu, ca, uk, or de (maps to {region}.api.knowbe4.com).
3
In Dex, enable the KnowBe4 Reporting integration and paste the Reporting API key and region.
4
Dex validates the key with a live read of /v1/account before saving.

Credentials required

api_key: KnowBe4 Reporting API key for one KSAT account (secret; never echoed)
region: KnowBe4 region: us, eu, ca, uk, or de (maps to {region}.api.knowbe4.com)

Requirements

•A KnowBe4 KSAT account with the Reporting API enabled and an active Reporting API key
•The correct region for your account (us, eu, ca, uk, or de)
•Read-only surface - Dex browses account, users, groups, phishing, and training data but does not modify it
•This is the per-tenant Reporting app - for MSP multi-account Graph metadata, use the separate KnowBe4 Partner app