Manage Environment
Manage environment (the account dropdown) is where you configure things that belong to the Environment as a whole — shared by every project in it. For the concept see Environment; this page is the practical tour of the modal's three tabs.
Manage Environment is Environment-Access only. A Project-Access admin sees "Only administrators with 'Environment Access' can view and manage this data." See Administrators & Access Levels.
Environment variables​
Environment-wide configuration values, including:
- the Spec ID — the identifier for your External Services configuration that your app passes to the SDK; and
- the captcha keys (Kerberus, Friendly Captcha, reCAPTCHA).
See Initialize the Cardinal SDK for how these values plug into your application.
External services​
The email / SMS / captcha gateways your authentication processes use to send one-time codes — managed here once and reused by every project. If only the onboarding Demo setup is configured, a banner reminds you to add your own gateway for real traffic. See External Services.
Operation tokens​
Generate and manage the one-time operation tokens used to receive a project transferred from another environment ("Import External Projects into Your Environment"). The receiving environment generates the token and shares it with the source owner; each token is valid for one transfer only. See Transfer ownership.
Where to go next​
- Environment — what an Environment is and what lives at its level.
- External Services — configuring the gateways behind the External services tab.
- Transfer ownership — the operation-token flow end to end.
- Manage Account — your personal account (vs. the environment here).