SeedEnvSeedEnv Documentation
Editing cohort directions
Use Edit directions on an active cohort in the console. You can update existing step titles and directions, not rewards, proof types, step order or payment terms. Every save creates a permanent version with the developer account and UTC timestamp. An accepted tester keeps the version assigned at acceptance, even after a revision request. New assignments use the latest directions. Existing testers see an update notice, but later requirements do not change their reward eligibility. View instruction history to compare versions; manual reviewers see the assigned version alongside evidence and subsequent edits. For existing cohorts, the first archived version is the baseline available when versioning was introduced.
New to recruiting testers? Start with the beta testing guides for audience selection, TestFlight preparation and Google Play closed testing.
TestFlight Setup Guide
Upload a testing build to App Store Connect, complete Apple's required beta review where applicable, and create an external-testing group. Supply a working TestFlight invitation link in your cohort brief. Include the supported device/OS versions, test accounts, and any sandbox credentials. Never include production passwords.
Telemetry Format
Reports should include device model, OS version, app build, reproduction steps, expected and observed results, and relevant proof. Screenshots, permitted screen recordings, and crash/network logs must exclude personal data, tokens, and credentials.
{
"deviceModel": "iPhone 15 Pro",
"osVersion": "iOS 18",
"build": "1.4.0 (42)",
"steps": [
"Open test invitation",
"Sign in",
"Return to invitation"
],
"expected": "Invitation remains available",
"actual": "Redirect returns to home",
"attachments": [
"reproduction.mp4",
"redacted-crash.log"
]
}Escrow & Fees
Custom drops are pay-per-tester from a prepaid balance. Top up from Billing or at launch; the card is charged exactly the amount added, with no processing or top-up fee. Each time you accept a tester, that tester's reward and the 20% platform fee (the $15 per-cohort minimum is taken on the first acceptance) are drawn from the balance, with a PDF receipt per tester place. Eligible platform-fee waivers and promo codes reduce the fee, not the tester reward. Optional auto-reload charges your saved card when an acceptance would exceed the balance. Paid places freed by withdrawn, expired or finally denied testers are reused first. A developer denial holds the unpaid reward and place until manual review; those funds cannot be refunded or reused during the hold. Ending a cohort, or reaching its 30-day expiry, returns unused paid places to your balance, while claimed places and rewards under review remain reserved. Available balance can be refunded to your card. New flat bundles (Google Play 14-Day at $96, Flash Concurrency at $210) use the same 20% platform fee with a $15 minimum. They are prepaid with fixed slots, rewards, and fees enforced server-side at checkout, and activate only after signed payment confirmation. Existing paid cohorts retain their recorded terms. Approval and successful payment transfer are distinct events; pending transfers remain visible.
48-Hour Review Window
Each submitted proof shows an auto-approval countdown in the console. Approve, deny, or request a revision within 48 hours of submission. Proofs with no decision after 48 hours are approved automatically, unless a manual-review hold applies. A revision request pauses the window; the tester's resubmission starts a new 48-hour window. Every developer denial sends the submission to manual review and holds its unpaid reward. Automatic approval, editing and reward reuse are paused until an operator approves the work or confirms the final denial. Work must meet the original cohort instructions and acceptance criteria. See the Terms of Service for the review policy.
Payout Schedule (Stripe)
Connect Stripe Express to receive approved cohort payments. The connected account's live schedule determines bank payouts and settlement. Weekly payouts and 48-hour availability are not universal defaults. Tax forms, including US 1099 forms when applicable, depend on geography, eligibility, and the platform's Stripe tax configuration.
Validator Guidelines & NDA
Use your own testing evidence, follow the cohort acceptance criteria, and report reproducible results. Keep unreleased builds and confidential developer details private. Platform confidentiality obligations are covered by the Terms of Service; a separate NDA must be agreed by the parties where required. SeedEnv does not generate a signed NDA by merely displaying this guide.