How do organisations and environments work in Toden?

Short answer

An organisation is your team’s account boundary. Sandbox and Production are separate operating environments within that boundary. Select the intended organisation and environment before creating keys, publishing a workflow or investigating a missing record.

Organisation access

A person can belong to several organisations with a different role in each. Access in one organisation does not grant access to another organisation’s customers or settings. Console roles control signed-in people; API credentials identify their own organisation and environment.

If a colleague can see a record that you cannot, compare organisation, environment and permissions before assuming that the data disappeared. Do not share a colleague’s session as a workaround.

Sandbox and Production

The console header switches the environment whose scoped data you see. Keys, workflows, verifications and webhook endpoints are separate. Publishing in Sandbox does not publish the equivalent Production configuration.

Key prefixes distinguish test and live credentials. Identity verification uses its documented shared host with the key selecting the environment. Risk Intelligence has a separate Sandbox host. Follow the product-specific guide rather than assuming every API changes hosts in the same way.

Prepare for launch

Production verification requires the organisation’s approved business onboarding. Prepare live credentials, published live workflows, Production webhook subscriptions and sufficient credit. Verify the complete path with the intended configuration before opening it to customers.