Workflows, files, runs, webhooks, signing secrets, integration credentials,
and usage records live in exactly one environment. A test credential cannot
read or mutate production resources; cross-environment lookups return
404.
Credentials
The credential selects the environment. Not a header, not a base URL, not a CLI flag.Base URL
RETAB_API_BASE_URL selects the Retab deployment: hosted API, local dev
server, private region. It does not select test or production.
CLI Targeting
Local CLI profiles are just names for stored credentials:retab env switch changes only your local default profile. It never changes
server state and it never changes what a credential can access.
Credential resolution is strict:
If an explicit key and an environment flag disagree, the CLI fails instead of
guessing. Run
retab auth status to see the resolved environment before a
dangerous command.
Production Safety
High-risk production writes, such as publishing, deleting, rotating secrets, or retrying jobs, require confirmation. In CI or any non-interactive shell, pass--confirm explicitly.
retab env switch production in CI. Pass the production key
in the command environment so the target is visible in the script.
What Is Isolated
See webhooks and secrets for the
environment-scoped webhook and secret model.