Security & Backup

KnowBe4 Partner

Bring KnowBe4 Partner / Multi-Account metadata into Dex - read managed account details and seat counts through the Product Graph API.

Dex connects to the KnowBe4 Partner / Multi-Account Product Graph API so admins can look up managed account metadata conversationally - account name, seat counts, and partner subscription details. Read-only for account metadata: Dex reads the account row for a tenant and, on the MSP master connection, can list managed accounts to discover their ids. This is a KnowBe4 Partner MSP global app: one Product API token from the management console is shared, and each Dex tenant is confined to its own KnowBe4 account via the account_id identifier. It is not the Reporting REST API - phishing campaigns, users, and training enrollments live in the separate KnowBe4 Reporting app.

Start free →See Dex Live

What Dex does with KnowBe4 Partner

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

For admins (Dex Pro)

Read a managed KnowBe4 account row - name, seat counts, and partner subscription fields when the schema exposes them
List managed KnowBe4 accounts on the MSP master connection to discover each tenant's account id
Map each Dex tenant to one KnowBe4 account via the account_id identifier
Deploy as an MSP global app - one Product API token, each customer confined to its own KnowBe4 account

Just ask Dex

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

Admin prompts

>How many seats does this KnowBe4 account have?
>Show me the KnowBe4 account metadata for this tenant
>List the KnowBe4 accounts managed on the master connection
>What is the account name and id mapped to this tenant?

Policy actions

Every action Dex can take on KnowBe4 Partner 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_partner_get_account`	Read this KnowBe4 Partner-managed account metadata (forced $accountId on a scoped child)	—
`knowbe4_partner_list_accounts`	List managed KnowBe4 accounts (MSP master connection only; root name unverified)	—

How to configure KnowBe4 Partner

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

Setup steps

1
In the KnowBe4 Partner / Multi-Account management console, open Account Settings > Product API (or Account Integrations > Product API) and create a Product API token for Dex. Prefer Read Only unless writes are required, and copy it once at creation.
2
Note your KnowBe4 region - us, eu, ca, uk, or de (us resolves to training.knowbe4.com).
3
In Dex, enable the KnowBe4 Partner integration and paste the Product API token and region. Leave account_id blank on the MSP master connection.
4
On a tenant-scoped connection, set account_id to the numeric KnowBe4 account id for that tenant - use the master listing or the Partner console to find it.
5
Dex validates the token with a live GraphQL probe before saving.

Credentials required

product_api_token: Product API token from the KnowBe4 Partner / Multi-Account management console
account_id: This tenant's numeric KnowBe4 account id (positive integer); leave blank on the MSP master connection
region: KnowBe4 region - us, eu, ca, uk, or de (us resolves to training.knowbe4.com)

Requirements

•A KnowBe4 Partner / Multi-Account subscription with Product API (Graph) access
•A Product API token from the management console with Graph API access for your region
•Read-only for account metadata - Dex reads account rows and lists managed accounts, but does not create or delete accounts
•Phishing campaigns, users, and training enrollments live in the separate KnowBe4 Reporting app, not this connection
•For MSPs, deploy as a global app with one shared token and per-tenant scoping by account_id