> ## Documentation Index
> Fetch the complete documentation index at: https://doc.entelligence.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Agent Insights privacy and appropriate use
> Understand Agent Insights collection paths, computed fields, identity mapping, visibility, and responsible enterprise use.
Agent Insights can show individual and team-level activity. Before rollout, document what is collected, who can see it, and how the organization will use it.
## Know the collection path
The local CLI reads supported session data and computes analytics before sync. Provider, platform, OpenTelemetry, and observability connections can follow a different path.
For the local CLI path, computed fields can include token counts, tool names and counts, retry signals, efficiency, and context-health metrics. Raw prompts, responses, and tool input/output are not part of that sync path.
Confirm the current field schema, retention, storage region, access controls, and deletion process for your workspace. Do not infer them from a dashboard label.
## Protect identity mapping
A wrong mapping can assign sessions, spend, or outcomes to the wrong person.
* Limit who can change mappings.
* Review new and changed provider identities.
* Leave uncertain identities unresolved.
* Give members a way to report attribution errors.
* Record mapping changes when auditability is required.
## Define visibility and purpose
Decide:
* Who can access workspace, team, project, and member views
* Whether reports may be exported or redistributed
* Which metrics are appropriate for coaching
* Which uses are prohibited
* How members can challenge or correct the data
Use Agent Insights to improve systems, context, training, and tool choices. Do not turn a derived score into an employment decision.
## Preview local data
```bash theme={null}
entelligence insights sync --dry-run
```
To remove a scheduled local sync:
```bash theme={null}
entelligence insights schedule --remove
```
Disabling a local sync does not stop another configured provider or telemetry source.
## Security basics
* Store provider keys in approved secret storage.
* Use the narrowest available scope.
* Rotate credentials under change control.
* Keep credentials, prompts, and source code out of screenshots and support messages.
* Test member and administrator offboarding.
## Next step
Use the [administrator checklist](/get-started/admin-checklist) and [troubleshooting guide](/agent-insights/troubleshooting) during rollout.