Automation workflows often refer to credentials, but a workflow definition should not contain the credential value itself. FlowKeyOps treats workflow structure and secret values as separate concerns.
What you can see
The control panel may show safe metadata such as a credential name or reference, type, target environment, synchronization state, and last update time. This information helps an operator confirm that a dependency exists without displaying the protected value.
What you should not expect to see
- Passwords, access tokens, private keys, or complete connection strings
- A button that reveals an existing secret value
- Secret values embedded in workflow comparisons, audit events, or support exports
References are not values
A workflow version can contain a credential reference that identifies which credential the runtime should use. The referenced value is supplied separately to the authorized target environment. This allows the same workflow structure to move between environments while each environment keeps its own credential.
Operate secrets safely
- Use a different credential for each environment when practical.
- Grant only the permissions required by the workflow.
- Rotate credentials according to your security policy.
- Review metadata and synchronization status after a change.
- Never paste a secret value into a support request or workflow description.
The exact secret providers and controls available to your workspace depend on your enabled service configuration.