Skip to content
wiki.fftac.org

14 Participants Database Integration

**Site relevance:** Anti-Christ.org

**Memory type:** docs archive

**Source path:** Wiki.FFTAC.org/raw/system-archives/anti-christ.org/docs-archive/2026-05-10/docs/14-participants-database-integration.md

**Size:** 3.3 KB

Summary

Participants Database Integration

Source Headings

  • Participants Database Integration
  • Ownership
  • What Syncs
  • Backfill
  • Readiness
  • Practical Rule

Source Preview

This source file is short enough to preview directly on its source-memory page.

# Participants Database Integration

Anti-Christ.org integrates the third-party Participants Database plugin as an operational mirror for FFTAC intake and member profiles.

## Ownership

- Canonical intake storage remains in Foundation Core private post types:
  `fftac_signal_signup`, `fftac_contact_message`, and `fftac_program_interest`.
- Participants Database stores a roster-oriented mirror for admin sorting, CSV workflows, and manual follow-up.
- The bridge lives in `wp-content/plugins/fftac-foundation-core/inc/participants-database.php`.
- Do not edit `wp-content/plugins/participants-database/` for FFTAC behavior.

## What Syncs

Future public submissions sync automatically when Participants Database is active:

- Signals Briefing signups
- Contact Desk messages
- Program Intake inquiries
- WordPress member profiles created or updated through the Membership Portal

Each mirrored Participants Database row includes native fields where possible:

- `first_name`
- `last_name`
- `email`
- `mailing_list` for Signals signups

Foundation Core also creates FFTAC-owned mirror fields:

- `fftac_site_project`
- `fftac_record_kind`
- `fftac_intake_source`
- `fftac_intake_record_id`
- `fftac_intake_post_id`
- `fftac_intake_lane`
- `fftac_intake_context`
- `fftac_intake_subject`
- `fftac_intake_message`
- `fftac_intake_notes`
- `fftac_member_record_id`
- `fftac_wp_user_id`
- `fftac_wp_user_login`
- `fftac_member_status`
- `fftac_member_registered_at`
- `fftac_member_public_alias`
- `fftac_member_profile_summary`

The `fftac_intake_record_id` value is stable as `{source}:{post_id}`, such as `signals:401`.
The member profile record key is stable as `member:{wp_user_id}`, such as `member:42`.

## Backfill

Use `Tools -> FFTAC Launch Readiness -> Participants Database Bridge` to sync existing private intake records and WordPress member profiles into Participants Database.

The backfill action is admin-only and does not delete local intake posts or change WordPress accounts. It updates the local post meta with:

- `_antichrist_participants_database_id`
- `_antichrist_participants_database_record_key`
- `_antichrist_participants_database_status`
- `_antichrist_participants_database_synced_at`
- `_antichrist_participants_database_error`

Member profile mirror status is stored in user meta:

- `_antichrist_member_participants_database_id`
- `_antichrist_member_participants_database_record_key`
- `_antichrist_member_participants_database_status`
- `_antichrist_member_participants_database_synced_at`
- `_antichrist_member_participants_database_error`

## Readiness

The launch-readiness page reports whether Participants Database is installed, active, whether FFTAC fields are present, and how many local intake records and member profiles are already linked to mirrored rows.

The launch handoff TXT export includes the same bridge status so operators can see whether roster mirroring is ready before public promotion.

## Practical Rule

Use Foundation Core private posts and admin CSV exports as the audit trail. Use Participants Database as a working roster for triage, list review, and external handoff preparation.

WordPress remains the authority for authentication, password reset, and protected content. Participants Database mirrors the roster-facing profile and intake details so staff can sort, export, and triage without turning Participants Database into the login system.
Website health report