> ## 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.

# Verify data and permissions

> Confirm that Entelligence can reach only the intended repositories, members, channels, and connected data.

A connector can authenticate successfully while a repository, channel, or member mapping is still incomplete. Test the complete path with one administrator and one normal member.

## Source-control checks

* The intended repository appears under **Settings → Code Management**.
* **Code Review → Codebases → Repositories** shows the same repository.
* A normal member can see only the repositories their workspace access permits.
* A test pull request can receive a review.
* Revoking the provider installation or token stops new access as expected.

## Member and team checks

* Invitations use the intended **Member** or **Admin** role.
* Team membership matches reporting and notification needs.
* Cursor, Claude Code, Codex, Linear, and Slack identities are mapped to the correct Entelligence member.
* An unmapped user appears as unresolved or unsynced instead of being silently attributed to someone else.

## Slack checks

* The Entelligence app is installed in the approved workspace.
* The bot belongs to each channel it needs to read or post in.
* A test message reaches the selected user or channel.
* Private channels remain unavailable until the bot is explicitly added.
* User mapping resolves direct-message recipients correctly.

## API key and CLI checks

```bash theme={null}
entelligence auth status
entelligence status
```

For CI, provide `ENTELLIGENCE_API_KEY` through your secret manager and run a non-destructive status or review test. Do not print the key in logs.

## Feature-specific checks

| Feature          | Verification                                                                     |
| ---------------- | -------------------------------------------------------------------------------- |
| Code Review      | A test PR or local diff completes with the expected output style                 |
| Agent Insights   | Synced activity appears for the correct member and time window                   |
| Ask Ellie        | The answer identifies the connected source or states that context is unavailable |
| Code Reliability | A mapped source appears on the intended repository report                        |
| Documentation    | Generation completes for the selected repository                                 |
| Model Router     | A pilot session appears under **Sessions** with routing metrics                  |
| Pulse            | **Trigger Now** delivers one report to the intended recipient                    |
| Reactor          | A matching test message runs; a non-matching message does not                    |

## When a check fails

1. Confirm the connector is still authenticated.
2. Confirm repository, workspace, or channel scope.
3. Refresh or synchronize from the relevant settings page.
4. Recheck user mapping.
5. Check whether the action requires an administrator.
6. Retry with a narrow test item.
7. Capture the workspace, repository, timestamp, action, and visible error before contacting support.

## Next step

Proceed to [Code Review](/code-review/setup), [Agent Insights](/agent-insights/setup), or the workflow you selected.