Fields to understand
Environment entries include a key, value, description, secret flag and applied state. Use the exact names your code reads and a short description of what each value configures. For private connections, use the private host/port of a product in the same org.
Secrets
Protect database passwords, Redis passwords and access keys as secrets. Keep them out of frontend/public framework variables, committed source and logs. UI masking does not stop your code from printing sensitive values.
Apply changes
Check whether the entry has been applied to the runtime. After changing important env, redeploy or update the deployment so the process reads the new values. Frontend values embedded at build time require rebuilding. Verify behavior without printing secrets.