Before you start
A signed-in NodeFox workspace. Use synthetic data and prepare outputs before enabling external writes.
01Separate secrets from examples
Use placeholder names in written samples and the product’s intended credential configuration for real keys. Do not put a secret into a global merely because it is convenient to reference in a prompt.
02Review data destinations
Reader and Writer configuration, model calls, Code fetch and tools can involve external services. Browser-local orchestration does not eliminate these data transfers. Send only the fields needed for the task.
03Inspect logs and exports
Treat execution artifacts, screenshots and downloaded reports as potentially sensitive. Check whether inputs or headers appear in evidence before sharing it. Use synthetic data throughout instructional recordings.
04Assign ownership
Define who can configure integrations, rotate keys and authorize writes in your deployment. Do not assume the illustrative approval screen alone establishes your organization’s access-control policy.
If the result is wrong
If a key appears in an export or recording, remove the artifact from sharing and rotate the exposed key under your organization’s procedure.