Summary
Decide between between single API site key or multiple keys grouped by domain/project.
Background
We need to plan how to configure hCaptcha Enterprise for the trial. Open questions:
- Should we use a single API site key or multiple keys grouped by domain/project?
- For now, we are going to use a single sitekey for all of the projects.
- Should the puzzle always be suppressed (focus on bot detection only)?
- We are using 99.9% passive and invisible modes.
- Who needs access to the hCaptcha trial configuration (likely SRE)?
- We've enabled Okta sign-in (T388896) to handle access to configuration in dashboard.hcaptcha.com. SRE has access to private configuration related to the proxy.
A separate task will handle implementation (T397793).
User story
As staff, I want to decide the hCaptcha trial configuration so we can set it up correctly.
Specification
- Decide API key structure (single key vs. grouped keys)
- Decide puzzle suppression settings
- Identify which team members (e.g. SREs) need access to configure the trial
Acceptance criteria
- Decision made on API key structure
- Decision made on puzzle suppression
- Trial configuration access list confirmed