Admin access to Waydev, authentication credentials for the tools you want to connect, and your team hierarchy data (an org chart, spreadsheet, or HRIS export showing who belongs to which team and who the team leads are).

Connect integrations, set up your team hierarchy, add users, link user accounts, add attributes, and configure deploy and incident rules. Reports depend on this order, since without at least one integration there is no data to report on, and without detection rules Waydev cannot calculate DORA metrics.

Waydev recommends connecting source control, issue tracking, and AI coding tools to get the most complete picture of your engineering workflow.

Azure DevOps, Bitbucket, GitHub, GitLab, Jira, ClickUp, Azure Boards, Slack Bot, and AI tools including AugmentCode, Claude Code, Cursor, Devin, GitHub Copilot, OpenCode, and Windsurf. The Entire CLI is also available as an optional integration for AI session tracking.

Navigate to Settings > Integrations, click + Add Integration, select the service from the Provider dropdown, then follow the authorization steps for that provider.

For Azure DevOps, Bitbucket, and GitHub, yes. Select the OAuth credential type and click Connect. Make sure popups are allowed in your browser, since the authorization window opens as a popup.

Yes. Use the + Add credentials button to add multiple credential sets to the same integration.

Open the Actions menu (···) on the integration row and select Test Connection. This runs a connectivity check and is useful after credential changes or if a sync has been failing.

Open the Actions menu and select Details. The Overview tab shows key stats plus expandable More stats categories for Structure, Resources, and Ratios. The Activity tab shows a log of recent sync jobs with job name, data types, date range, start time, status, and duration.

On the integration's Settings tab, use Repositories import mode (for code integrations) or Projects import mode (for ticketing integrations). Both default to Allow all.

No. Deleting permanently removes the integration from Waydev and cannot be undone.

No. Only one token is needed for both.

Work Items (read), Build (read), Code (read), Graph (read), Identity (read), Project and Team (read), Release (read), and Task Groups (read). Choose Custom defined rather than Full access, and click Show all scopes since some are hidden by default.

The single-organization token is scoped to one Azure DevOps organization and requires you to enter the Organization Name. The all-organizations token covers every organization in your account and does not require that field.

OAuth, Workspace Token, and Atlassian API Token. The Atlassian API Token method also requires the Atlassian Account Email.

Yes. If you authenticate with a Personal Access Token, you must authorize the PAT for SSO in order to access internal resources. This must be repeated every time you generate a new token or regenerate an expired one.

Four. Username and Password, Token, Jira Service Account OAuth 2.0, and Jira Service Account API Token. All four require a Base URL.

Atlassian Service Accounts are non-human accounts designed for machine-to-machine integrations. They do not consume standard user licenses and their permissions are scoped to only the tasks they need, which improves security and auditability.

read:me, read:jira-work, read:jira-user, read:project:jira, read:board-scope:jira-software, read:sprint:jira-software, and read:issue:jira-software.

No. Scopes are immutable once the credential is created. You must delete the credentials in the Atlassian Admin Console and create a new set.

The OAuth token is missing a scope required by the endpoint. If projects sync but boards fail, the missing scopes are usually read:board-scope:jira-software or read:sprint:jira-software. Delete the credentials and create a new set with both the Jira and Jira Software scopes enabled.

Authentication and scopes are correct, but the service account user does not have permission to view the projects or issues. Add the service account to your Jira projects with the Browse Projects permission.

No. The Service Account Email must be the exact email address of the service account itself, not a personal email address.

It enables Waydev to receive usage data from Claude Code via OpenTelemetry. This powers token-level metrics, model usage, and cost tracking in the AI reports.

No. The token is shown only once. If you lose it, you need to delete and re-add the integration.

Each developer needs the JSON configuration applied on their own machine, with their correct user email set in OTEL_RESOURCE_ATTRIBUTES. That is how activity gets attributed in the dashboard.

Either manually one at a time via + Add user, or in bulk using Import users CSV from the ··· menu on the Users page.

Four built-in roles: Workspace admin (full administrative and product access), Team lead (report access across the platform), Contributor (team members who are subjects of surveys and reports).

Yes. Navigate to Settings > Users > Roles and click Create Role. Grants are grouped by category (AI, Dashboards, Delivery, Diagnose, Health, Planning, Settings) with a Select all or Deselect all link per category.

When set to Yes, the identity fields of all other users are masked with *** in API responses returned for that user. The user's own identity is never masked.

Remove the Contributor Insights grant from their role, and enable Anonymize Others. Only aggregated, team-level data remains visible.

Waydev links users automatically by email where possible. When automatic linking does not apply, activity from that integration cannot be attributed to the user. Go to Settings > Users > Link accounts to map accounts manually.

Yes. A user can have multiple provider identities under the same Waydev profile.

Yes. Teams can be nested to mirror your organization's hierarchy, for example a Devs team containing Frontend and Backend sub-teams.

Attributes define custom user properties for segmentation and filtering in reports, for example Seniority, Location, or AI assistant usage. They come in Admin-managed and Waydev-managed types, with a Self-reported type noted as not yet released.

No. Waydev-managed attributes such as Seniority are predefined and their options cannot be edited.

Go to Settings > Users > Single Sign-On, set Single Sign-On to Enabled, and provide a Connection Identifier. Waydev then displays the ACS URL, Audience URI, and NameID Format values to enter in your identity provider. Click I finished my SAML configuration once the IdP is set up.

Through deploy and incident rules under Settings > Aggregation > Deploy & Incident Rules. There are three detection types: PR merge, API push, and Repository tag.

Use PR merge when merging into a branch directly triggers a release. Use Repository tag when tagging a commit signals a release. Use API push when you have custom release tooling or need full control over what counts as a deployment.

No. Each repository can only be assigned to one detection rule at a time. Repositories already assigned to another rule do not appear in the selection list.

A Personal Access Token, plus the /deployments endpoint. API tokens are managed under Settings > Aggregation > API.

By keyword matching. For PR merge rules you choose whether the keyword is matched against the pull request Title or the Branch name, and the value accepts regular expressions. A match flags the previous deploy as a failure.

Set an Exclusion regex under Settings > Aggregation > PR Exclusion. Any pull request whose title matches the pattern is excluded from all metrics and reports, for example ^dummy|WIP. Leave the field empty to disable exclusion.

Yes. On the PR Exclusion tab, Lead Time calculation lets you choose between Only Deployed PRs and Merged and Deployed PRs.

By matching the deployment message against a case-insensitive regex under Settings > Aggregation > Hotfix Detection. The default pattern is hotfix. This powers the Hotfix Deployments and Hotfix Rate metrics.

It maps directories in your repositories to named segments, so you can separate statistics along lines that neither Teams nor Repositories provide on their own. Once configured, a segment appears as a selectable Root Path attribute in Goals and report filters, across GitHub, GitLab, and Bitbucket.

States left in the Unmapped column on the Issue States board are not included in workflow-based calculations. Drag them into the correct stage column (Backlog, To Do, In Progress, QA, Done, or Cancelled). Mappings apply immediately, with no separate save step.

Admin (full control over the workspace), Stats (read access to stats and reporting data), and Deployments / Incidents (access to send deployment and incident data). Copy the token immediately after generation, as it is not shown again.

Lead Time for Changes, Deployment Frequency, Change Failure Rate, and Mean Time to Restore. All four appear on the DORA Overview with a current period trend and a previous period comparison.

Coding Time (first commit or PR creation to ready for review), Pickup Time (ready for review to first review), Review Time (first review to merge), and Deploy Time (merge to deployment).

Yes. Clicking a team's median value in a report table opens a drilldown listing the individual pull requests or failed deployments that contributed to the calculation.

A pull request approved without meaningful review activity. It is tracked on the Merge Quality report alongside Unreviewed PRs, Merged PRs, and Traceability.

The percentage of pull requests linked to a ticket or issue.

A measure of how well knowledge is distributed across the team through code reviews. It appears on the PR Insights Resolution tab and in Contributor Insights.

Lines of code rewritten or deleted shortly after being written.

The split between traceable and untraceable pull requests across your active repositories, with a per-repository table showing Total Commits, Total PRs, Unlinked PRs, and Unlinked percentage.

Use the Benchmarks report under Health. Each column is a team and each row is a metric, with values color-coded to highlight differences. Six metrics are shown by default and there are 30 available in total.

Team Insights is a per-team detail view with Snapshot, Workload, Work-Log, and Performance tabs. Benchmarks is a cross-team comparison table.

Yes. On a contributor's Performance tab, use the Benchmark against dropdown to select a team. Percentile bars show where the contributor falls relative to the 25th, 50th, and 75th percentiles.

There are 165 available metrics. Click + Add new metric to add them, or Reset all to restore the default set.

Reviewing where engineering effort goes. The Investment View shows FTE by issue category over time, and the Category View groups allocation by Issue Types, Issue Labels, or Epics. The Settings tab lets you create custom allocation categories mapped to work types and labels.

AI Adoption covers adoption rates and per-vendor usage. AI Impact covers Code to Production and AI Checkpoints. AI ROI covers Token Usage and Vendor ROI.

By active user frequency threshold, selectable in the Adoption filter: DAU (active at least once per day), WAU (at least once per week), or MAU (at least once per month).

A side-by-side comparison of AI vendors across AI Adoption, Weekly Active Users, PR Throughput Impact, Cycle Time Impact, PR Review Speed, and Rework Rate. Values are color-coded to highlight the best and worst performing vendors.

Accepted in IDE (AI-generated lines accepted by developers in their editor), Merged (lines merged into a branch via pull requests), and Deployed (lines that reached production).

A checkpoint captures an AI coding session in full. As an AI agent runs, the session is recorded in the background, and when the developer runs git commit a permanent checkpoint is created with its ID attached to the commit as an Entire-Checkpoint: trailer. Session data is stored in the entire/checkpoints/v1 branch.

No. Entire is optional and is what ties AI attribution to a specific commit and author. AI Adoption, Code to Production, and Token Usage all work from your existing integrations without it.

Yes. Enable it with entire enable --local --skip-push-sessions --telemetry=false, which sets push_sessions to false and telemetry to false in .entire/settings.local.json. Waydev recommends keeping telemetry disabled when working with sensitive repositories.

Run entire --version to confirm installation and entire status to confirm the repository is enabled. Also check that .entire/settings.local.json has the correct configuration and that .githooks/wd_commit_hook exists with the hooks path configured.

Total tokens used, monthly spend, average tokens per developer, and cost per PR, broken down by tool and by team.

An AI agent that answers questions about your engineering data in natural language. It queries your connected integrations, runs analysis, and returns results as text, charts, or both.

Yes. Each graph response includes an SQL Query label. Click it to expand the query, then click Edit to open the SQL editor, where you can browse available tables, format the query, and re-run it.

A system skill that generates dashboard widgets from a chat prompt. When active, the widget preview appears inline with an + Add to Dashboard button.

Specialized instructions that Waydev agents activate on demand, uploaded as SKILL.md files with YAML frontmatter. Waydev ships several system skills including Developer Experience Auditor, Executive Mode, Resource Allocation, Token Optimization, and Widget Creator.

Not directly. Duplicate it from the ··· actions menu and edit the copy.

An AI-evaluated notification system that monitors engineering data and sends alerts as a Slack DM or email on a configured cadence. Eight signals are available, including PR Quality Guardian, Incident Predictor, Capacity Planner, and Team Health Pulse.

The signal was evaluated successfully but had nothing to report for that period.

An interface that gives AI agents access to your Waydev engineering context. It exposes developer metrics, PR analytics, DORA metrics, team performance, AI metrics, AI impact, AI ROI, AI tokens, and AI checkpoints.

Claude Desktop, Claude Code, Cursor, VS Code with GitHub Copilot, ChatGPT, Codex, Windsurf, and other MCP clients.

Metric Card, Metric Radial Bar, Metrics Table, Chart, Metric Focus, Heatmap, and Composite Time Metric. Each has a maximum number of metrics it supports, for example Metric Card supports one.

Yes. Widget-level filters override dashboard-level filters, so you can show different time ranges or team scopes side by side.

Dashboards are Private or Public. On a private dashboard, use Manage access from the ··· menu to grant Can View or Can Edit per user. Granting edit automatically grants view, but removing edit does not remove view, so both need to be turned off separately to fully revoke access.

Clone it to create your own editable copy.