> For the complete documentation index, see [llms.txt](https://help.besmart.software/besmart-connector/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.besmart.software/besmart-connector/troubleshooting/known-limitations.md). # Known limitations Here are the known limitations of the ACC-Bluebeam Connector * File transfer is limited to only PDF files * Markups from Bluebeam are not considered as markups in ACC * Technologies being used are different, so the markups are visible, but cannot be edited. * File origin is not stored * User must navigate to the right folder in ACC Docs or Bluebeam Studio, to overwrite the old file. * After slip sheeting, markups end up being locked in Studio Session * Because the markups were done in the old version of the PDF, Bluebeam Studio Session doesn't allow markups being edited * In case old markups are irrelevant, those may be deleted via Bluebeam Studio Project * The connector is limited to Bluebeam Studio United States server * Studio servers in Australia and Germany are available for beta testing, but not all the functionalities are supported. --- # 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://help.besmart.software/besmart-connector/troubleshooting/known-limitations.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.