> For the complete documentation index, see [llms.txt](https://docs.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.screendesk.io/screen-recorder/review-and-share.md). # Review and share Review your capture before sending it to your workspace. ## Check the capture After ending a recording, taking a screenshot, or saving an Instant Replay, Screendesk opens a review screen. * Play back recordings and replays. Adjust the trim range if you only need part of the capture. * Check screenshots and annotations. For a cropped screenshot, check whether the surrounding full screenshot is also included. * Review attached technical context, including console logs and network requests, for information you do not want to share. A desktop recording can show applications outside Chrome, but its browser diagnostics describe the browser page, not those other applications. ## Add details and upload Add a clear name and description. Choose a folder, labels, or an assignee where those options are available in your workspace. Select **Upload** and wait for it to finish. Screendesk creates a shareable link for the uploaded capture. Copy the link into a message or ticket, or use your connected integration. Access to the shared capture depends on your workspace and recording sharing settings. Check those settings before sending the link outside your team. ## Continue later Choose **Close** to keep an unfinished capture as a local draft. Use **Delete** when you want to discard it. An unfinished local draft does not have a shareable workspace link until you upload it. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.screendesk.io/screen-recorder/review-and-share.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 `build a script that syncs our docs to a CMS` 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.