Share evidence without exposing secrets

Prepare a safe example

Support usually needs the visible result, environment, time and a reference it can locate through authorized access. A full browser capture or log file may contain more information than the issue requires.

1. Capture the relevant screen or error and the time it occurred.
2. Remove passwords, API keys, session cookies, private sign-in links and unrelated personal information.
3. Use the agreed private channel for business or order references.

• Never paste credentials into Orchesphere commands or public website forms.
• A secret reference identifies managed configuration; it is not a value to expose in a support conversation.

Redact before sending

Review the final file, not only the original screen. Include the surrounding labels needed to understand the problem, while removing account details and tokens from address bars, request headers and expanded settings.

• Keep the error wording and relevant field labels.
• Remove customer details that are not needed to reproduce the issue.
• Describe unavailable evidence rather than substituting a password or full configuration export.

If a credential was exposed

Contact the responsible administrator through the agreed security route. State what kind of credential may be exposed and where, without copying the value again. The administrator should decide containment and credential replacement through the appropriate service.

• The service, environment and approximate exposure time.
• Where the exposure occurred and who was notified.
• Any action already taken by an authorized administrator.