> 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/workflows/define-workflow-settings/action-settings/remediate/dropbox-remediation.md).
# Dropbox remediation
DoControl provides your organization with an automated way to detect and prevent unnecessary or dangerous exposure on Dropbox.
Using the following remediation actions, you can implement automated workflows across Dropbox permissions and assets.
## Remove shared links
You can define a workflow to remove shared links from Dropbox assets. Using a remediation action, users can choose if they want to remove public sharing links, team folder sharing links, or all sharing links.
This allows your organization's security team to control asset exposure, and track individuals who change the sharing link visibility from internal to public.
#### To remove shared links from Dropbox:
1. In your workflow, define a trigger related to Dropbox.
2. From the Actions pane, select **Remediate > Dropbox > Remove shared links**.
3. Drag the action into the canvas and connect it to the previous action.
4. For Asset ID, use the default macro or type your own query.
5. Select the shared link type: public, team folder, or all.
Add a remediation action to remove shared links from Dropbox
---
# 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/workflows/define-workflow-settings/action-settings/remediate/dropbox-remediation.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.
