xCloud
admit_test_end_users
Allow test end users on one of your application's production realm. Destructive: needs a credential holding the destructive class (a signed-in session, or a token minted with `destructive`); the call creates a pending action, and the admission stands only after a person approves it in the browser. Approving it means any credential of your account that reaches the application can sign a test end user in on production with no mailbox; their sign-ins and verifications meter as backend actions. The admission lasts until `withdraw_test_end_users` and shows as `test_end_users_admitted_at` in `read_realm`, `configure_realm`, and `export_account`. The development realm needs no admission. Refused `test_end_users_not_admitted` under the workforce audience and `test_end_users_disabled` while the platform's `TEST_END_USERS` setting is off.
Remote (network-hosted)
Other tools also called admit_test_end_users?
See providers with this name
Input Schema
{
"type": "object",
"properties": {
"request_id": {
"type": "string",
"description": "Your request identity for this pending action: any string you choose. Repeating the call with the same request_id, from the same account, while the earlier pending action is still live — requested, approved, or executing — answers that pending action again and creates no second one. Once it has completed, failed, been declined, or expired, the same request_id starts a new one. Omitted, every call creates a new pending action."
},
"application": {
"type": "string",
"description": "The application id, from `list_applications`; one of the calling account's own. The act names the application's production realm; the development realm admits test end users with no act."
}
}
}