Test vs live
Every organization has two separate environments. Switch between them with the toggle at the top of the console.
| Test | Live | |
|---|---|---|
| Keys | trw_test_… |
trw_live_… |
| Available | As soon as you create the organization | After Trowyn approves the organization |
| Phones | Only phones linked with a test link code | Only phones linked with a live link code |
| On the phone | Your name with [TEST], "TEST sign-in request", a TEST badge | Your name |
| Webhooks, logs, stats | Separate endpoints and data | Separate endpoints and data |
| Limits | Same as live |
The environments never mix: a test key can't send to a live link, read a live approval, or see live webhooks, and the other way round. A phone can be linked in both (it shows two entries).
Before going live: create a live key, store it in your production secrets, and have users link with a live link code (a test link stays test). Remove test links you no longer need in Phones.
Organization status
| Status | Means |
|---|---|
| Pending review | New organization: test only |
| Active | Test and live |
| Denied / Disabled | No API access. Contact support |
Policies (per organization)
Console → Settings (admins and owners). Applies to new requests in both environments.
| Policy | Default | |
|---|---|---|
| Request timeout | 120 s | 30–300 s |
| Number matching | On | The phone asks for the number your page shows. Strongly recommended |
| Require Face ID | On | Face ID or passcode before answering |
| Show location | On | Show the location you send |
| Show IP address | On | Show the ip_address you send |
Roles
| Role | Can |
|---|---|
| Developer | See everything; use test keys, link test phones, send test pushes, manage test webhooks |
| Admin | Also live keys, live webhooks, policies, and invite or remove developers and admins |
| Owner | Also manage owners and the organization's name. An organization always keeps at least one owner |