Skip to main content
KnowBe4 runs security awareness training (KSAT), simulated phishing tests and PhishER, which collects the emails users report. Each of your clients that uses it has its own KnowBe4 account. Connect KnowBe4 for those clients, and Neo agents can work in it while they handle a ticket.

​
What Neo can do with KnowBe4

  • Add a new hire to KnowBe4 and to their training groups, from the same onboarding ticket as their Microsoft 365 account
  • Archive a leaver, which keeps their training and phishing history and frees the seat
  • Report who has not finished their training, who clicked or reported a phishing test, and users’ risk scores
  • Enroll a user in a running training campaign, or extend a due date
  • Add a security event, such as a compromised account, to a user’s KnowBe4 record
  • Triage a PhishER Threat ticket: read the reported email, recognise a KnowBe4 phishing test, and set the email’s category, status, tags and comment in PhishER
With the matching permission groups on, agents can also manage groups, training and phishing campaigns, templates, admins and security roles, and account settings. See KnowBe4 API for the permission groups and profiles.

​
One connection per client

Every KnowBe4 API key belongs to one KnowBe4 account, so you connect KnowBe4 once for each client, and the connection belongs to that client’s company in Neo. If you manage your clients from a KnowBe4 partner account, each client’s connection can use your partner’s Product API key with the client’s account ID. An agent working a ticket for that company uses that company’s KnowBe4 account.

​
Next steps

Connect KnowBe4

Create a client’s KnowBe4 API keys and save them in Neo.