> For the complete documentation index, see [llms.txt](https://docs.oveka.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oveka.io/promptguard/insights-and-reporting/monitoring-ai-adoption-in-your-organisation.md).

# Monitoring AI adoption in your organisation

Learn which AI services your users are engaging with.

### Overview

Oveka PromptGuard helps you understand which AI platforms people are using, how widely they have been adopted and what they are being used for.

These insights can help you decide which tools to approve, where users need guidance and whether your protection policies need to change.

### Measuring AI adoption

The Insights tab provides a high level overview of AI usage across your organisation. Here you can see the most popular platforms, your most active users and monitor usage changes over time.

This helps you track which tools are being used by people and becoming part of everyday work.

<figure><img src="https://1078805375-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FftH1qxxd9PrA9tzGguLX%2Fuploads%2FB9oYDY9PFHo1JmVteNWM%2FScreenshot%202026-10-06%20at%202.58.45%E2%80%AFPM.png?alt=media&amp;token=8daf292a-3834-4668-b693-2b943b031aa3" alt=""><figcaption></figcaption></figure>

### Identifying platforms that need attention

Keep an eye out for unfamiliar platforms that may warrant investigation. Widespread use of an unapproved tool can be helpful for identifying demand that your existing tools may not meet. \
\
Insights give you a starting point when deciding which platforms need to be investigated and whether your current tool set or access policies need to be adjusted. &#x20;

### Acting on your insights

What you learn can help you:

* Evaluate platforms that are gaining adoption.
* Address unexpected use of unapproved platforms.
* Guide users towards approved alternatives.
* Track how adoption changes after introducing a tool or changing a policy.

### FAQs

<details>

<summary><strong>Does Oveka show every AI platform used by my organisation?</strong></summary>

Yes. Oveka tracks all AI services detected on machines with PromptGuard installed.

</details>

<details>

<summary><strong>Does recorded activity mean data was successfully shared?</strong></summary>

No. Review conversation verdict to see if the action was allowed/blocked.

</details>

<details>

<summary><strong>Does a new AI platform finding mean the platform is unsafe?</strong></summary>

No. Review the platform, its intended use, and the information being shared to decide whether action is needed to comply with your organisations data protection policies.

</details>

<details>

<summary><strong>Can I block a platform after reviewing its usage?</strong></summary>

Yes. Use PromptGuard policies to control which AI platforms users can access.

</details>


---

# 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.oveka.io/promptguard/insights-and-reporting/monitoring-ai-adoption-in-your-organisation.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.
