KnowBe4 Training Campaign Management

Overview

KnowBe4 training campaigns deliver security awareness content to users through structured enrollment workflows. Training can be assigned manually, triggered automatically after phishing test failures, or scheduled on a recurring basis. Each campaign tracks enrollment status, completion rates, and compliance deadlines. The training content library includes interactive modules, videos, games, assessments, and policy documents.

Anti-triggers

• A bare "campaign" question — KnowBe4 has two campaign types with

separate ID spaces and near-identical lifecycles. If the subject is a simulated phishing test, its templates, or who clicked, it is knowbe4-phishing; this skill covers only training campaigns and enrollments.

• The phishing failure that triggered an auto-enrollment — the

trigger is configured here, but the failure data itself is knowbe4-phishing.

• Completion rates rolled up across campaigns or departments — this

skill reads individual campaigns and enrollments; aggregates and compliance dashboards are knowbe4-reporting.

Key Concepts

Training Campaign Lifecycle

CREATED ──> SCHEDULED ──> ACTIVE ──> CLOSED
                │                       │
                └──── CANCELLED         └──> ARCHIVED

• Created: Campaign configured with content and target groups
• Scheduled: Queued to begin enrollment at a future date
• Active: Users enrolled and training in progress
• Closed: Campaign deadline passed, final completion recorded
• Cancelled: Campaign aborted
• Archived: Closed campaign moved to archive

Enrollment Statuses

Training Content Types

Auto-Enrollment Triggers

Training can be triggered automatically based on:

Field Reference

Training Campaign Fields

Training Enrollment Fields

Store Purchase Fields

MCP Tools

Two shape notes that change how these get used:

`knowbe4_training_enrollments_list` is account-wide and takes no filters. There is no campaign_id and no status argument. "Overdue enrollments for the HIPAA campaign" is a full paginated read filtered client-side on the campaign and status fields of each record — not a query. Budget the request count accordingly (see api-patterns), and pass per_page=500 rather than accepting the default of 100.

There is no training-module catalog tool. Nothing here lists the modules available to assign or reads a single module by ID. knowbe4_store_purchases_list is the nearest real capability and it answers a different question — what content this account has purchased from the ModStore, not what modules exist or what a campaign could use. knowbe4_training_campaigns_get names the modules already attached to a campaign. Choosing content for a new campaign is console work.

Common Workflows

Create and Monitor Training Campaign

1. Review owned content using knowbe4_store_purchases_list — this

shows what the account has bought, which constrains what a campaign can assign. Browsing the full module catalog is console-only.

1. Select target groups -- choose which user groups need training
2. Set completion deadline -- allow adequate time (2-4 weeks typical)
3. Launch campaign -- schedule or start immediately
4. Monitor enrollment status -- check completion rates weekly
5. Send reminders to users with "not_started" or "in_progress" status
6. Review final completion after deadline

Track Compliance Status

1. List campaigns with knowbe4_training_campaigns_list, then filter

to the active ones yourself — there is no status argument

1. Read enrollments with knowbe4_training_enrollments_list (account-wide;

match them back to campaigns on the enrollment record)

1. Filter by status to find incomplete/past_due enrollments
2. Identify non-compliant users -- group by department or manager
3. Escalate users who are past due on required training

Post-Phishing Remediation Training

1. Identify failed users from phishing campaign results
2. Find appropriate remedial module matching the phishing scenario
3. Create targeted campaign for failed users only
4. Set short deadline (1 week for remediation)
5. Track completion and re-test with follow-up phishing simulation

Quarterly Security Awareness Review

1. Pull all completed campaigns for the quarter
2. Calculate overall completion rate across all campaigns
3. Identify departments with lowest completion rates
4. Review training content -- are modules current and relevant?
5. Plan next quarter based on gaps identified

New Hire Onboarding

1. Create onboarding training campaign with essential modules
2. Enable auto-enrollment for the "New Hires" group
3. Set relative deadline (e.g., 14 days from enrollment)
4. Include baseline phishing test after training completion
5. Move to regular groups after onboarding completion

Error Handling

Common API Errors

Data Considerations

Best Practices

1. Set realistic deadlines -- Allow 2-4 weeks for standard training, 1 week for remediation
2. Send reminders -- Notify at 50% and 75% of deadline elapsed
3. Keep content fresh -- Rotate training modules quarterly
4. Match training to threats -- Use phishing failure data to select relevant modules
5. Track completion trends -- Completion rates should improve over time
6. Segment by audience -- Executives, IT, finance, and general staff need different content
7. Combine with phishing -- Always follow training with a phishing simulation to validate
8. Use gamification -- Games and competitions increase engagement
9. Report to stakeholders -- Share completion rates with department managers
10. Automate remediation -- Auto-enroll phishing test failures in relevant training

Related Skills

• KnowBe4 Phishing - Phishing simulation campaigns
• KnowBe4 Users - User management and groups
• KnowBe4 Reporting - Training completion metrics
• KnowBe4 API Patterns - Authentication, pagination, and rate limits