Is there a way to prevent spam registrations to events?

Hi ​@dkreiger - Yes this was in EF Events. Thank you for this information - for the recaptchaMinScore how do we determine what to set it to - my understanding is the options are from 0 to 1 and the default is 0.4 - what do the numbers signify and I am assuming if the default is 0.4 then that is the recommended value. 

For the stronger registration controls, what does EF provide? You mentioned email verification - how is that set up in EF?

Thank you,

Anuya

Hi ​@akamat, 

1) Google reCAPTCHA: what the score represents, and how to pick recaptchaMinScore

What the score numbers represent (0 → 1)

In Eightfold’s event registration configuration, recaptchaMinScore is defined as a threshold score between 0 and 1. The intent is: the system uses reCAPTCHA to detect malicious activity in registration and then compares the returned score to your threshold to decide whether to allow the submission. 

• Eightfold’s event registration reCAPTCHA is controlled by planned_event_config -> landing_json -> registrationConfig -> recaptchaEnabled.
• The threshold is planned_event_config -> landing_json -> registrationConfig -> recaptchaMinScore.

How recaptchaMinScore is used in Eightfold events

• In the Events schema, recaptchaMinScore is described as the minimum score required to allow the registration submission to pass reCAPTCHA checks.
• In the implementation PR, the default behavior is:
  • recaptchaEnabled defaults to false.
  • recaptchaMinScore defaults to 0.4.

A practical example from the test plan: if you set recaptchaMinScore to 1, normal submissions are expected to fail with an error like “Too many requests, please try again later” (i.e., treated as bot-like).
 

Is the default 0.4 “recommended”?

In our internal docs and schema, 0.4 is documented as the default, not explicitly as a “recommended best” value. In other words, I’d treat 0.4 as a starting point Eightfold ships with (and that you can tune), rather than a universal recommendation. 
 

How I’d choose a threshold (practical approach)

Based on how the configuration is defined and tested in Eightfold:

• If you’re seeing bot/spam registrations: raise the threshold above 0.4 (tighter). The PR explicitly demonstrates tightening to 1.0 will cause the system to reject more traffic. 
• If you’re seeing legitimate registrants blocked: lower the threshold below 0.4 (looser). The schema confirms the full 0–1 range is valid.
• Tune per workflow: Eightfold supports reCAPTCHA independently in at least two places—Apply and Event registration—with separate config keys, so don’t assume one threshold fits both.

2) Stronger registration controls in Eightfold: what features exist, and how email verification works

Eightfold provides several “stronger registration / auth controls” for external candidate-style experiences, depending on which surface you mean (PCSx vs. Events vs. Community registration).
 

A) PCSX (Personal Career Site) candidate registration controls

Eightfold supports multiple candidate authentication methods for PCSX:

• Email + password (with an explicit email verification step).
• Email + OTP (one-time code).
• Optional social sign-in (Google, Microsoft, LinkedIn, Facebook).
• Optional access code gating on login/registration pages (customer-controlled).

Specifically: how email verification is set up / works in PCSX

From the PCSX process doc, the email verification behavior is part of the standard email-based registration flow:

• Candidate creates an account (email + password or OTP / social, depending on configuration).
• Candidate then verifies email via a verification email/link/code.
• After verification, the user is redirected back into the logged-in PCSX experience.

So, in PCSX, “setting up email verification” is essentially choosing a registration method that includes it (notably email+password) and ensuring the PCSX registration flow is enabled/configured for “verify your email.”
 

B) Event registration controls (Engage → Events)

For event registration, Eightfold supports adding reCAPTCHA to the candidate registration flow:

• Config: planned_event_config -> landing_json -> registrationConfig -> recaptchaEnabled (default false).
• Threshold: planned_event_config -> landing_json -> registrationConfig -> recaptchaMinScore (default 0.4).

C) Talent Community “public landing page” self-registration controls

For community self-registration via a public landing page, Eightfold has candidate-facing endpoints that support:

• Public landing page discovery (unauthenticated GET) and registration (POST).
• Gate control via ta_community_candidate_experience_gate.
• Optional reCAPTCHA validation in that registration flow (called out as “optional reCAPTCHA validation”).