> For the complete documentation index, see [llms.txt](https://guides.mangoapps.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.mangoapps.com/admin-guide/module-settings/chats/chat-history-ad-hoc.md). # Chat History (Ad-Hoc) ### Overview Network and Domain Admins have the capability to monitor and review the message history of ad-hoc group chats. This ensures organizational compliance and provides a clear audit trail for all private group communications within the platform. *** ### Admin Configuration To maintain privacy standards, this feature is **off** by default for most networks. If you would like this feature enabled for your domain, please contact your Account Management Team. *** ### Accessing History Authorized admins can view logs by navigating to **Modules → Chats → Chat History** (Adhoc-groups) in the Admin Portal. * **Search & Filter**: Admins can locate specific groups by name and narrow down results using preset date ranges (e.g., Today, Last 7 days, Last 30 days) or a custom date picker. * **Rich Data View**: The history log displays the sender’s name, timestamps, and full message content. It also captures inline reactions; hovering over a reaction allows admins to see up to 10 users who engaged with that message. * **File Integration**: All attachments—including images, GIFs, PDFs, ZIP files, and Office documents—are viewable directly within the portal using the built-in file viewer. *** ### Reporting and Exports For external audits or deeper analysis, chat history can be exported as a CSV file. * **Capacity**: Each export supports up to 10,000 messages listed in chronological order. * **Content**: The exported file includes the group name, selected date range, and direct links to any files shared during the conversation. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://guides.mangoapps.com/admin-guide/module-settings/chats/chat-history-ad-hoc.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.