Currently, when a chat, agent, or workflow generates a document or file-based deliverable on the Hatz.ai platform, it produces a randomly generated AWS link. This link is publicly accessible to anyone who has it, which constitutes "security by obscurity" which is not a recognized or acceptable security control.

This creates several critical concerns for enterprise and regulated customers:

• Data Exposure Risk

o Generated files are not access-controlled, meaning sensitive outputs could be accessed by unintended parties.

• No Integration with Customer Storage

o There is currently no ability to write outputs directly to customer-owned storage repositories such as Microsoft 365 (SharePoint/OneDrive) or internal/external file systems.

• Compliance & Regulatory Gaps

o Without the ability to route files to governed storage, customers cannot maintain their compliance posture or meet data residency and handling requirements.

• Security Framework Control Failures

o This limitation makes it difficult or impossible to satisfy technical controls required by frameworks such as SOC 2, ISO 27001, NIST, HIPAA, and others.

Requested Features:

Implement access-controlled, authenticated file links (at minimum) to replace open AWS URLs.

Enable native integrations with customer storage repositories, starting with Microsoft 365 (SharePoint/OneDrive) and common file systems.

Allow customers to define where file outputs are stored, ensuring data stays within their governed environments.

This is a foundational capability for enterprise adoption and security-conscious customers. Thank you for considering this request!