> For the complete documentation index, see [llms.txt](https://docs.movebot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.movebot.io/using-movebot/permissions-and-metadata/scanning-permissions.md).

# Scanning permissions

As part of a scan, permissions will be scanned from the source. You can then use the scan results to inspect the permissions on the source. Make sure check **Enable File/Folder Permission Preservation** during setup to use this feature. 

To check the permissions on an individual file or folder, go to **Discovery Scan** within your project, highlight your target item, and click **\*Details**, then **Sharing**. 

 

### **Downloadable reports**

Additionally to the reporting available in the front end, you can download two reports on file permissions:

| Permissions Report         | A CSV export of all permissions detected on the source by file and folder. |
| -------------------------- | -------------------------------------------------------------------------- |
| Applied Permissions Report | A CSV export of applied permissions                                        |

<br>


---

# 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://docs.movebot.io/using-movebot/permissions-and-metadata/scanning-permissions.md?ask=<question>&goal=<endgoal>
```

`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.