> 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/analytics.md).

# Analytics

### When you’re flying first class, you want to be able to enjoy all the good things that come with that privilege. dope.swg has added analytics on Policy, Productivity, and Shadow IT that set it apart from coach class. Why miss out?

{% hint style="info" %}
To enjoy all these benefits and make the most of your dope.swg experience, you need to have imported your users/groups into the console.
{% endhint %}

Have you already imported all your organization’s users?

If you haven’t imported users/groups into the console, you’ll see this at the bottom of the overview dashboard...

![](/files/uVv62Sq0681x7Prm9LxZ)

…with no information on Productivity or Shadow IT. This means you will have limited access to analytics data unless users/groups are imported into the console.

You can continue without importing users or groups but you will have limited access to analytics data. To make the most of dope.swg, ensure you import your organization’s users and groups.


---

# 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://inflight.dope.security/dope.console/analytics.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.