> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.3/ga-releases/release8.2/release-notes/collaboration.md). # Collaboration ## Data Stories ### New & Improved ### Download Data Stories as PDF In Data Stories, users could only view Data Stories within OvalEdge and had no option to download or share them outside the application. With this enhancement, users can now export Data Stories as PDF files for offline access, sharing, and distribution. The exported PDF preserves the content structure and readability of the Data Story, making it easier to share information across teams and include it in presentations, reports, or other documentation. 👉 For more details, see the [Download Data Stories as PDF](https://docs.ovaledge.com/release8.2/data-stories/operations#download-data-stories-as-pdf) section. ### Upload PDF Content to Data Stories In Data Stories, users could not add PDF documents from their local system. As a result, reports, presentations, and other document-based content had to be converted manually before being included in a Data Story. With this enhancement, users can now upload PDF files to a Data Story through the **Upload PDF** as images option in the rich text editor. When a PDF is selected, the system converts its pages into images and inserts them into the Data Story. 👉 For more details, see the [Upload PDF as Images](https://docs.ovaledge.com/release8.2/data-stories/operations#upload-pdf-as-images) section. ## Question Wall ### New & Improved ### Personalized Organization of Community Rooms and Walls In the Question Wall, Community Rooms and the Walls within them were displayed in a fixed order in the left navigation panel. Administrators could not customize the arrangement based on their priorities or frequently used content, making navigation less flexible. With this enhancement, administrators can now rearrange Community Rooms and the Walls within them using drag-and-drop controls in the left navigation panel. The customized arrangement is saved for the individual administrator and does not affect the navigation order for other users. This allows administrators to personalize their Question Wall experience and organize content based on their preferences. 👉 For more details, see the [Reorder Community Rooms and Walls](https://docs.ovaledge.com/release8.2/question-wall/features-and-operations#reorder-community-rooms-and-walls) section. ### Improved Visibility of Question Wall Room Types In Question Wall, Community Rooms were not clearly differentiated in the navigation panel, even though some rooms, such as Conversations and Curation by AI, only allowed users to reply to existing questions and did not support creating new questions. This made it difficult for users to understand the purpose of each room and navigate to the appropriate location. With this enhancement, Community Rooms are now categorized by functionality. Rooms that support creating new questions and those that support only replying to existing questions are grouped separately and include descriptive help text explaining their purpose. This improvement helps users quickly identify the appropriate room, reduces navigation confusion, and provides a more intuitive Question Wall experience. 👉 For more details, see the [Community Rooms](https://docs.ovaledge.com/release8.2/question-wall/features-and-operations#community-rooms) section. *** Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.ovaledge.com/release8.3/ga-releases/release8.2/release-notes/collaboration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.