Analytics Access and Setup
Open Analytics from Codity Platform. When embedded Analytics is enabled for your deployment, use the product switcher to open it under /analytics. Otherwise, the Analytics navigation entry hands off your signed-in session to the standalone Analytics deployment. Use that entry rather than opening an embedded page URL directly.
Access Requirements
Your active plan must include advanced analytics, and your developer must have the applicable Analytics seat/access level. A locked entry can indicate a missing plan feature or missing seat. Ask the account administrator to check both under Subscription.
Use the intended provider account and team. Analytics data remains scoped to the authorized account and permitted repositories; changing a browser URL does not grant access to another organization's data.
Connect Your Provider
Complete the current provider connection and repository enabling flow first. GitHub uses an App installation; GitLab.com uses its configured PAT; Azure uses an organization PAT; Bitbucket uses OAuth. Do not reuse the old Analytics-specific scope lists in place of the current provider guides.
| Provider | Connection to check before investigating Analytics |
|---|---|
| GitHub | The App installation includes the intended repositories and the correct personal/organization account is selected. |
| GitLab.com | The saved PAT is valid and the intended projects are enabled in the selected personal/group scope. |
| Self-hosted GitLab | The connected instance and personal/group scope match the repositories being inspected. |
| Azure DevOps | The selected organization has a valid shared PAT and the intended repositories are enabled. |
| Bitbucket | OAuth authorization is valid and the repository belongs to the selected workspace. |
These checks establish the underlying connection. Available Analytics history still depends on provider ingestion and your authorized data scope.
Opening Analytics
- Sign in to Codity Platform and select the account you intend to inspect.
- Open Analytics. If a preview/lock is shown, check feature and seat access.
- Start at Pulse, then use Flow, Impact, Developers, Security, Code Quality, AI Analytics, Digest or Reports.
- Check the active team/repositories and timeframe before interpreting results.
Settings and Account Selection
Analytics Settings includes preferences and time thresholds. In embedded deployments, its route is /analytics/settings; other /analytics/... routes in these guides also refer to embedded deployments. In standalone deployments, use the corresponding Analytics navigation entry. Threshold edits have explicit Save/Reset behavior; check the save result. Account switching and team scope are separate from time-range selection.
Choose a Consistent Scope
- Start with the intended provider account. A similarly named organization on another provider is a different scope.
- Check the active team and repository selection. Repository selections are saved for the individual member; teammates can have different selections.
- Select the timeframe offered by the view, such as the last 7 or 30 days.
- Keep those parameters consistent when comparing Pulse, Flow, Impact and contributor views.
For example, a 7-day view of one team's repositories should not be compared directly with an account-wide 30-day view. When a value looks surprising, first reproduce it with the same repository set and period, then inspect the underlying PRs.
Repository selection scopes Analytics reads; it does not enable a repository for reviews or change provider access. A team selection also does not grant access to another account.
Verify the First Results
After opening Analytics, confirm that the expected repositories are available. Choose a period containing known PR activity and inspect a source PR alongside its recorded data. If a card is empty, determine whether the relevant timestamps, reviews or scan results are available. Some views need more than repository connection alone: for example, Code Quality displays recorded quality scans.
Use Analytics Settings for threshold changes. A threshold changes how a duration is interpreted, not the recorded PR timestamps. Check the saved state before interpreting a new status color.
Troubleshooting
Empty charts: check the selected repositories, team and time range, and whether provider ingestion has produced data. Empty data is not proof that a team has done no work.
Access denied: check the provider identity, active account, plan and Analytics seat. Sign-in alone does not grant Analytics access.
Provider data unavailable: verify the underlying connection using its provider guide before changing unrelated Analytics settings.
Troubleshooting Checklist
| Symptom | Checks and next action |
|---|---|
| Analytics entry is locked | Ask the account administrator to verify both the plan feature and your Analytics seat/access level in Subscription. |
| Sign-in works but Analytics refuses access | Check the active identity/account and seat assignment. Repeatedly entering an embedded URL cannot grant access. |
| Expected repository is absent | Check the account, team and repository selection, then inspect its provider connection and authorized repository scope. |
| Charts are empty for a known active repository | Select a period containing the activity and inspect ingestion/provider errors. Missing source history is different from zero activity. |
| Teammates see different totals | Compare individual repository selections, active teams, periods and available permissions before comparing metrics. |
| A review or scan card is empty | Check whether the relevant review/scan ran and whether its result matches the selected scope and period. |
| Threshold edits appear ineffective | Check the save result and return to the affected view with the same scope and timeframe. |
For support, include the provider/account, affected view, selected scope, period and a non-sensitive error reference. Do not include access tokens. Deployment configuration errors should be handled by your administrator rather than by copying secrets or callback settings into Analytics preferences.

