Three roles, one account
Your TestHive account can play three different roles. There's no separate signup — the same login lets you switch contexts.
| Role | What you do | How you switch |
|---|---|---|
| Developer | Publish a Campaign · review tester submissions · confirm app launch | Default for any account |
| Tester | Join open Campaigns · submit daily check-ins · earn Karma or T-Coin | Default for any account |
| Studio member | Run group Closed Testing as a team · share campaign rewards | Join an existing Studio or create your own |
Developer ↔ Tester
You can act as both — publish a Campaign while testing someone else's app. The two flows share the same wallet (your Karma and T-Coin balances).
The only constraint: you cannot test your own published Campaign (anti-self-fraud).
Tester ↔ Studio
A user can be active in at most one Studio at a time. Leaving a Studio takes effect immediately; joining a new one is a fresh active-membership.
Why exclusive? Because Studios share rewards and reputation — splitting your activity across multiple Studios would distort each Studio's metrics and break Google Play's fraud detection (testers across Studios would look like sock-puppets to Google).
What only support staff can do
A small set of operations stay with TestHive support (called super_admin internally):
- PayPal top-up review (manual SLA within 24 hours)
- Withdrawal processing (3-5 days SLA, 100% manual)
- High-risk appeal adjudication
- Last-resort Campaign rejection (when our automatic fraud check needs human override)
Every other operational decision is self-service — no waiting on support for daily Campaign flow.