> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/risk-management/threat-model-coverage/public-sharing/dropbox-playbooks-for-public-sharing.md).
# Dropbox playbooks for public sharing
To mitigate the risk associated with public sharing in Dropbox, you can define automated workflows for these use cases:
* [Change visibility of shared link](#change-visibility-of-shared-link)
* [Notify on public sharing](#notify-on-public-sharing)
* [Remove publicly shared link upon creation](#remove-publicly-shared-link-upon-creation)
* [Notify on changing a shared link to public](#notify-on-changing-a-shared-link-to-public)
## Change visibility of shared link
When someone changes the shared link visibility for a Dropbox asset, you can automatically notify the Security team and remove shared links.
1. In Workflows, select **Playbooks**.
2. Filter the playbooks according to the Dropbox app, and select the **Change visibility of shared link** playbook.
3. Give an action name.
4. Under the **Changed visibility of shared link** event, customize the relevant conditions:
* The `Get actor` condition is in a specific group.
* The `Get new visibility status` condition equals **public**.
5. Add any relevant conditions.
6. Customize the **Notify in Slack** action to notify the Security team that the public links will be removed immediately.
7. Under the **Remove shared links** action, make sure that the `Public` shared link type is selected.
## Notify on public sharing
When someone creates a public link for a Dropbox asset, you can automatically notify the Security team.
1. In Workflows, select **Playbooks**.
2. Filter the playbooks according to the Dropbox app, and select the **Notify on public sharing** playbook.
3. Give an action name.
4. Under the **Created shared link** event, customize the relevant conditions:
* The `Get target` condition equals **public**.
* Add any relevant conditions.
5. Customize the **Notify in Slack** action to notify the Security team that the actor created a public link for a specific Dropbox asset.
## Remove publicly shared link upon creation
When someone creates a publicly shared link for a Dropbox asset, you can automatically notify the Security team and remove the shared links.
1. In Workflows, select **Playbooks**.
2. Filter the playbooks according to the Dropbox app, and select the **Remove publicly shared link upon creation** playbook.
3. Give an action name.
4. Under the **Created shared link** event, customize the relevant conditions:
* The `is publicly shared` condition is **true**.
* Add any relevant conditions.
5. Customize the **Notify in Slack** action to notify the Security team that the public links will be removed immediately.
6. Under the **Remove shared links** action, make sure that the `Public` shared link type is selected.
## Notify on changing a shared link to public
When someone changes the sharing link visibility to public for a Dropbox asset, you can automatically notify the Security team.
1. In Workflows, select **Playbooks**.
2. Filter the playbooks according to the Dropbox app, and select the **Notify on changing a shared link to public** playbook.
3. Give an action name.
4. Under the **Changed visibility of shared link** event, customize the relevant conditions:
* The `Get new visibility status` condition equals **public**.
* Add any relevant conditions.
5. Customize the **Notify in Slack** action to notify the Security team that the actor shared a public link for a specific Dropbox asset.
---
# 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.docontrol.io/docontrol-user-guide/risk-management/threat-model-coverage/public-sharing/dropbox-playbooks-for-public-sharing.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.
