> For the complete documentation index, see [llms.txt](https://docs.rhinofcp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rhinofcp.com/secure-access/what-is-secure-access.md). # What is Secure Access? **Secure Access** enables direct access to row-level data via a zero-footprint mechanism implemented within the FCP. This allows a user to view data loaded onto their Rhino Client through the Rhino FCP cloud application without having the data leave the Rhino Client. Secure access can be extremely useful for use cases such as annotation on distributed data. By default, a user can only use Secure Access on data that belongs to their workgroup. You'll need enable to Secure Access to view and/or annotate a dataset's tabular data or to view and/or annotate a dataset's image data within the OHIF view. However, if a user would like to access a collaborator's data, they should ask their collaborators to create a **Secure Access List** and grant them time-limited access to the data. A remote Collaborator can select exactly which rows from a Dataset they would like to share, with whom they share the data, and for how long they would like to share 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.rhinofcp.com/secure-access/what-is-secure-access.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.