> For the complete documentation index, see [llms.txt](https://academy.shade.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.shade.inc/sharing-and-collaboration/sharing-folders-and-files.md).

# Sharing Folders and Files

Sharing is just as easy as right clicking on any file or folder and sharing to any email. You can also publish a link to any folder or file.

Published links support analytics, so you can review link activity after sharing.

Published links can also be protected with passwords, expiration dates, and view limits.

### File/Folder Access

The most granular and secure approach for external collaboration. When you share specific files or folders, collaborators become **guests** at both the workspace and drive level. They'll see only what they need while maintaining a clean, professional experience.

This level is ideal for:

* Clients reviewing specific deliverables
* Freelancers working on individual assets
* External QA teams reviewing specific content
* Stakeholders who need access to presentation materials<br>

### Shared with me

If you've been given access to specific files or folders in a drive rather than the whole drive, clicking that drive in the left sidebar opens its **Shared with me** page. It lists everything in that drive that has been shared with you, so you can get to your items without browsing the rest of the drive. You can also open it from the command palette with **Go to shared with me**.

{% embed url="<https://youtu.be/zLlWyAg_A5Y?si=nAbfbguy2SPKTjyQ>" %}


---

# 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://academy.shade.inc/sharing-and-collaboration/sharing-folders-and-files.md?ask=<question>&goal=<user_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.