Environments

Create environments, rotate their credentials, and understand what "primary" means.

Agent > Environments is where an app's Production, Staging, and other environments are created and managed, each with its own Token/Secret credential pair. See API key security for what the Token and Secret each protect.

Creating an environment

New environment takes just a name, up to 60 characters. On creation, a reveal-once panel shows both the Token and the Secret together. This is the only time the Secret is ever shown. Only its ciphertext is stored afterward, so there's no way to display it again.

Renaming

Renaming only touches the label; the Token is untouched, so every existing install keeps working.

The primary environment

Exactly one environment is marked Primary. It's where data lands when ARCY can't resolve which environment a request belongs to, and it's the only one whose traffic is checked against your verified Origins. Setting a different environment as primary is reversible; the previous primary keeps its own Token and data. The primary environment can't be deleted directly, since deleting the app is how you delete the primary.

Rotating credentials

Rotating the Token and rotating the Secret are two separate actions, and they behave differently:

Rotate Token takes effect immediately. Every page still running the old Token fails to start ARCY until you update the snippet with the new one.
Rotate Secret also takes effect immediately for identity verification, but your pages are unaffected since the Secret never runs in the browser. A reveal-once panel shows the new Secret the same way creation does. As covered in the Quickstart, the previous Secret keeps verifying for 24 hours so a deploy can catch up.

Deleting an environment

Deleting an environment is permanent: its Token stops working, and every session, event, user, and account recorded in it is deleted with it.

Element screenshots

An admin-only toggle per environment. On, picking an element in a flow stores a small cropped screenshot so it's recognizable on the flow canvas. Off disables the capture entirely; flows still author and run normally either way.