AI Tool Tracking

Which AI tools are employees using?

Start with an account or hostname. See which assistants and coding tools appeared on a managed Windows device, which files were selected, and where a paste triggered a sensitive-data finding.

Alex Morgan’s individual activity report shows event times, four AI destinations and the observed actions.
Individual AI usage in the fictional Northstar workspace. Select a receipt in the demo to see its source.

Follow the question you came with.

Did someone select this document?

Search a filename and open the receipt. Read the observed gesture, destination and any related HTTP outcome before deciding whether a transfer can be established.

Investigate a document →

Where did a paste trigger a finding?

Look for a category such as an API key pattern or email address. Use the source device and time to route the finding to the right reviewer.

Investigate a sensitive paste →

Were these AI tools approved?

A Cursor process, a Claude paste and a Kimi file selection need three different decisions. Compare the receipts with a dated list of approved tools and workspaces.

Get the worked AI register →

Can you attribute the activity to one person?

A workstation can have a local Finance session and a remote support session open at the same time. Follow one Claude paste from its hostname to a reviewable case note.

A CLEAR PLACE TO START

Plan your AI visibility pilot.

Create a brief for your team. Your answers stay in this browser and are included in your download.

AI tools in scope
More supported tools

This creates a planning document. It does not enroll devices or submit a request.