Manage Connection Values by Environment v2

Use one Connection identity across a Site while keeping test, staging, and production endpoints and credentials separate.

Plan the values

For each Environment, record the intended:

  • Service hostname, URL, database, or account.
  • Authentication identity and secret owner.
  • Certificate or OAuth authorization.
  • Network path and Cluster selection requirements.
  • Safe test operation and expected result.

Cluster selection belongs to the shared Connection identity. If different Environments need incompatible network access, consider separate Connections or Sites instead of assuming the Cluster changes with the Environment selector.

Update each Environment

  1. Open Connections and select the Connection.
  2. Select the Environment you want to review.
  3. Confirm the endpoint and non-secret settings before changing credentials.
  4. Replace only the masked values that should change. Leave unchanged redacted values in place.
  5. Upload or replace the Environment's certificate when required.
  6. Repeat these steps for every Environment you can access.
  7. Click Save changes.

Clicking Save attempts to save all accessible Environments. If the Console reports a partial save, note which Environments succeeded, correct the failure, and save again. Do not assume a failed Environment caused the successful saves to roll back.

Verify the result

After saving, select each Environment and use its available Test, OAuth, or metadata action. Connection Methods operate on persisted values and do not run while the page has unsaved changes.

Then run a small Workflow test in the same Environment. This verifies Connection resolution and the Workflow's Cluster selection, mapping, and provider behavior.

Promote safely

Workflow promotion does not copy or validate Connection values. Before promoting a Workflow revision:

  1. Confirm that the target Environment already has a usable Connection value.
  2. Confirm that the promoted Workflow uses the expected Connection key.
  3. Check that Node and Connection versions are compatible.
  4. Verify local Cluster reachability where applicable.
  5. Test the target Environment before enabling its trigger status.

Work with masked values

A masked Property is redacted when loaded into the Console. Saving the unchanged marker preserves the existing secret for that Environment. Entering a new value replaces it.

If the secret must be cleared, follow the Node's supported empty-value behavior instead of assuming an unchanged masked field will remove it. Restrict secret rotation to people who have both Connection write permission and access to the target Environment.

Work with limited Environment access

The details screen can list an Environment but show No permission instead of its Connection value. Saving skips Environments you cannot access.

Ask a Site administrator to assign the required Environment under Settings → Site users. Permission changes take effect after you sign out and sign in again.

See also