> For the complete documentation index, see [llms.txt](https://inflight.dope.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://inflight.dope.security/dope.console/dope.swg-policy/cloud-application-control-cac.md).

# Cloud Application Control (CAC)

### Traveling first class is all about putting your needs first, right? dope.swg lets you keep control of all of your users’ cloud apps to ensure your organization enjoys the safest possible internet experience.

dope.swg lets you control your users’ access to the following cloud applications:

* O365
* Google
* Dropbox
* Slack
* Box
* Salesforce
* WebEx
* ChatGPT
* Claude
* GitHub

With dope.swg Cloud Application Control (CAC), if any of your users try to access cloud apps accounts that have not been allowed, dope.swg will block access. Any policy created will inherit the dope.swg Base Policy on CAC.

If you want to add domains your users can use to access selected cloud apps, that’s no problem either.

{% hint style="info" %}
The CAC policy supersedes the restriction level set at category level, e.g. if you have blocked “File Storage” at the subcategory level but have enabled Dropbox or Box control in cloud application control, the selected user will be allowed access to both.
{% endhint %}

Configuring cloud apps is simple and works pretty much the same way for Office 365 and Google. Configuring WebEx, Box, Dropbox, Slack, and Salesforce varies slightly, but it is just as easy.


---

# 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://inflight.dope.security/dope.console/dope.swg-policy/cloud-application-control-cac.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.
