> ## 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.
# Code Review permissions and troubleshooting
> Fix missing repositories, absent reviews, noisy findings, wrong context, provider permissions, and incomplete analytics.
Diagnose Code Review from the outside in: **provider access → repository sync → repository enablement → trigger → context → output**. This order finds the broken layer without changing unrelated settings.
## Fast diagnostic
Verify that the Git integration can see the repository and pull request.
Check **Settings → Code Management**, then locate the repository under **Code Review → Codebases**.
Open **Show details** and verify **PR Review** is enabled.
Comment `@entelligence review` on a non-draft pull request. This separates trigger problems from review-engine problems.
If the review runs but looks wrong, check guidelines, Learnings, Markdown context, linked codebases, exclusions, priority, and comment style.
## Common problems
| Symptom | Likely cause | Fix |
| ----------------------------- | ----------------------------------------------------- | ----------------------------------------------------------------- |
| Repository is not listed | Provider scope or synchronization | Reconnect the provider, then synchronize **Code Management** |
| Pull request is not listed | Wrong repository, filter, time window, or draft state | Clear filters and verify the PR state and repository |
| Explicit review does not run | Review disabled or bot lacks access | Enable **PR Review** and verify provider permissions |
| Automatic review does not run | Trigger is disabled | Enable the intended open, ready, or every-commit behavior |
| New commit is not reviewed | **Auto Review on Every Commit** is off | Enable it if desired, then push a test commit |
| Too many comments | Priority bar is too low or cap is too high | Raise the threshold or lower **Max Inline Comments** |
| Only one summary appears | Comment style is **Single summary comment** | Switch to inline comments if repository policy allows |
| Expected summary is missing | Generated-content control is off | Enable **High Level Summary** or the required artifact |
| Finding conflicts with policy | Context is wrong or stale | Check guidelines, Learnings, Markdown files, and linked codebases |
| Important file is skipped | An exclusion matches the path | Narrow or remove the exclusion and re-review |
| Approval fails | Provider permission or branch policy | Reauthorize access and inspect protected-branch rules |
| Ticket is not linked | Jira or Linear scope is missing | Verify the connector, project mapping, and ticket key |
| Analytics look incomplete | Collection, time range, mapping, or sync | Verify filters and source coverage, then refresh |
## Permission model
Code Review needs read access to repository and pull-request content. Posting reviews, replying, resolving threads, submitting approvals, linking tickets, and creating changes require the corresponding write capability.
Your Git provider remains the authority for branch protection, required checks, merge rules, and repository membership. Entelligence approval does not merge a pull request.
## Reduce impact while investigating
* Disable **Auto Review on Every Commit** to stop repeated runs.
* Disable **PR Review** for the affected repository to pause automation.
* Restore the recorded previous guideline, Learning, linked codebase, exclusion, or output setting.
* Revoke provider access only when the integration must stop immediately.
* Identify dependent clients before deleting or rotating credentials.
## Send support a useful report
Include:
* Workspace and repository
* Git provider
* Pull-request URL and commit SHA
* UTC timestamp and local timezone
* Expected trigger and current repository setting
* Exact visible error text
* Whether `@entelligence review` reproduces the issue
* Screenshots with secrets and unrelated private data removed
Never send access tokens, API keys, private source, or raw credentials through an unapproved channel.
## Next step
Return to the [Code Review quickstart](/code-review/setup) after the connector or setting is corrected.