Permissive Log Redaction for Agent Studio

How are we improving the product?

Standard log redaction protects sensitive information, but it can also hide request and response details that developers need to troubleshoot HTTP actions. Permissive Log Redaction gives Agent Studio admins a more flexible option: preserve useful payload details in logs while continuing to redact header values.

This helps development teams diagnose integration failures faster, reduce trial-and-error during testing, and better understand how an HTTP action behaved.

How does it work?

A super admin can enable Permissive Log Redaction as a security setting in Moveworks Setup. When enabled, Agent Studio logs use value redaction for HTTP headers rather than applying standard redaction to additional parts of the request and response.

Developers can then inspect more of the logged HTTP action details, including request and response payload information, when debugging integrations.

Licensing restrictions

Permissive Log Redaction is available as an Agent Studio security setting. Contact your Moveworks account team if you have questions about availability for your environment.

Technical restrictions and security considerations

Enabling this setting increases the amount of request and response data that may appear in logs. Sensitive information included outside HTTP headers—such as an access token placed in a request body—may be logged.

Before enabling Permissive Log Redaction, customers should review how their integrations handle credentials and sensitive data, ensure secrets are passed through headers where appropriate, and confirm that the additional logging aligns with their security and compliance requirements.

Documentation

Learn more about log redaction in Agent Studio: Log redaction.