Skip to Content
AdminManaging Compliance Tracks

Managing Compliance Tracks

Compliance Tracks define the requirements that apply to different categories of team members. This guide explains how to create, configure, and assign tracks.

Understanding Compliance Tracks

A Compliance Track is a collection of requirements that “stack” onto a member. Examples:

TrackRequirementsAssigned To
Core MemberBackground Check, CPR, Policy AcknowledgementAll members
Armed (Civilian)+ Firearms Qualification, Range Training, Liability WaiverCivilian armed members
Armed (LEO)+ Proof of LEO Status, Training RecordLaw enforcement members
OnboardingQuestionnaire, Interview, Background CheckNew applicants

Members can have multiple tracks assigned. Requirements from all tracks apply.

Accessing Compliance Configuration

  1. Navigate to Admin in the sidebar.
  2. Click on Compliance or Compliance Tracks.
  3. The configuration screen shows all tracks and their requirements.

Track Components

Each track contains:

ComponentDescription
Track NameDescriptive name (e.g., “Civilian Armed”)
RequirementsList of compliance items in this track
Auto-Assign RulesOptional: Auto-apply based on role

Requirement Types

Tracks can include various requirement types:

TypeDescriptionVerification
DocumentUploaded proof (certificate, license)File upload
CertificationTraining completion with expirationDate entry
QuestionnaireForm responsesSurvey completion
VerificationManual leadership confirmationAdmin marks complete
PolicyPolicy document acknowledgementSignature

Creating a New Track

  1. Click Add Track (or the + button).
  2. Enter the track name and description.
  3. Add requirements to the track.
  4. Configure auto-assign rules (optional).
  5. Click Save.

Adding Requirements to a Track

  1. Open the track for editing.
  2. Click Add Requirement.
  3. Configure the requirement:
FieldRequiredDescription
Name✅ YesDisplay name (e.g., “Background Check”)
Type✅ YesDocument, Certification, etc.
Renewal PeriodOptionalMonths until expiration (0 = never expires)
DescriptionOptionalInstructions for the member
BlockingOptionalWhether this blocks readiness if missing
  1. Save the requirement.

Changes to requirements affect all members with this track. Plan carefully before modifying.

Assigning Tracks to Members

Tracks can be assigned:

Manually

  1. Open a member’s profile.
  2. Navigate to the Compliance section.
  3. Click Manage Tracks.
  4. Add or remove tracks.
  5. Save.

Automatically

Configure auto-assign rules to apply tracks based on:

  • Global Role (e.g., all “Members” get “Core Member” track)
  • Account Status (e.g., “Applicant” status gets “Onboarding” track)

Expiration Logic

Requirements with renewal periods:

  1. Valid — Current and not expiring soon.
  2. Expiring — Within 30 days of expiration (Yellow indicator).
  3. Expired — Past expiration date (Orange indicator).
  4. Missing — Never uploaded/completed (Orange indicator).

The system sends reminder emails 30 days before expiration (if notifications are enabled for the member).

Best Practices

  • Layer Tracks — Use a base track for all members, add specialized tracks for subgroups.
  • Clear Names — Make requirement names self-explanatory.
  • Realistic Periods — Set renewal periods that match real-world requirements.
  • Document Changes — Keep notes when modifying track configurations.
  • Test First — Assign a new track to yourself or a test account before broad rollout.

Common Configurations

Church Safety Team Example

TrackAuto-AssignRequirements
Core MemberRole = MemberBackground Check (24mo), CPR (24mo), Core Policies
Armed CivilianManualFirearms Qual (12mo), Range Training (12mo), Armed Policy
Squad LeadRole = Squad LeadLeadership Training
OnboardingStatus = ApplicantQuestionnaire, Interview, Background Check

See Also

Last updated on

Need More Help?

If you can't find what you're looking for, our mission support team is standing by.

© 2026 N4 Safety. All rights reserved.