Dashboards, alerts and digests

DevGlimpse comes to where your team already works. Compose dashboards from report cards, share them, save the filters you use often, and get told when a team metric slips instead of checking a chart. Alerts and digests always show team and group totals, never one person.

Dashboards

A dashboard is a layout of report cards. Each card still shows only the numbers of the person looking at it, so sharing a layout never widens anyone’s access.

To create one (manager or org admin):

1. Open Home → Dashboards.
2. Type a name in New dashboard name and select Create.
3. Select Add Report, search the cards, and add the ones you want.
4. Use the controls on each card to move it earlier or later, switch it between half and full width, or remove it.
5. Rename the dashboard from its title when you need to.

Select Pin to nav on a dashboard to keep it in your left navigation. Only the owner can edit a dashboard. Developers see the dashboards shared with them.

Share a dashboard

1. Open the dashboard and select Share.
2. Under Who can open it, choose Only me, Everyone in the workspace or Specific groups.
3. Optionally, as an org admin, set it as the default landing page for Developers, Managers or Admins. One dashboard per role. A default must stay visible to the whole workspace.

External link for someone without an account

1. In the Share dialog, find External link.
2. Set Expires after (days). The default is 7 and the most is 90, or less if your org admin set a lower limit.
3. Select Create link and copy it. It is shown once.

The person who opens it gets a read-only viewer session. They see team and group totals only, never individuals. The link stops working when it expires or is revoked.

Org admins control the policy under Admin → Share links: turn Allow external share links on or off, set the longest lifetime, and Revoke any link. Managers see their own links there.

Saved views

A saved view is a report plus the filters you set in the filter bar.

1. Set up the filters on a report.
2. Select Views in the filter bar.
3. Type a View name and select Save.

Open Views later and select a view to return to the same report and filters. Select the bin icon to delete one. Views are private to you. A report that needs a specific team or person in its address cannot be saved as a view.

Alerts

Get told by email, Slack or Microsoft Teams when a team or group metric misses its target or crosses a threshold. Managers see and manage their own rules. Org admins see all rules.

1. Open Admin → Alerts and select New rule.
2. Choose a Metric: Cycle time, Coding time, Pickup time, Review time, Review latency, PRs merged, Commits or Reviews given.
3. Choose the Team or group to watch. You can only watch teams and groups you belong to, unless you are an org admin.
4. Under Alert when the metric, choose a condition:
   • Misses its target: the metric is on the wrong side of the benchmark target for that team or group. Available for cycle, coding, pickup and review time.
   • Crosses a threshold: set Is above or below and a Threshold.
   • Is an anomaly: the nightly anomaly detection flags the day. Available for cycle time, review latency, PRs merged, commits and reviews given.
5. Set Weeks in a row (1 to 12). For anomalies this counts days.
6. Under Deliver to, tick Email me, and choose a Slack channel or a Teams team and channel if your workspace has connected them.
7. Set a Cool-down (hours) and, if you like, Quiet from (UTC) and Quiet until (UTC).
8. Select Create rule.

Rules are checked every night against completed weeks. Each breach fires once, and the cool-down spaces the next one. Alert history lists the last 20 alerts of each rule with their status: Delivered, Waiting for quiet hours, or Suppressed by cool-down.

Connect Slack and Microsoft Teams

Slack and Teams channels appear in the rule form only after an org admin connects them for the workspace.

An org admin connects Slack, Microsoft Teams, or both, and approves the consent screen. DevGlimpse asks for bot scopes only. Then create or edit an alert rule and pick the channel. Slack lists public channels.

Only an org admin can set Slack and Teams channels, and only on their own rule. If a channel is not connected, the form says “Slack is not connected” or “Microsoft Teams is not connected”.

Anomaly detection

Each night DevGlimpse checks daily metrics against their usual seasonal band. Days that fall outside it are marked on the chart for that team or group. Markers respect your visibility setting and the minimum group size. In Business hours mode, markers on cycle time and review latency are hidden, because they were detected on calendar time. Use Is an anomaly in an alert rule to be told when it happens.

Weekly digests

Digests arrive without a visit to DevGlimpse. They are sent on each workspace’s Monday, in the workspace time zone, for the week that ended Sunday.

• Team digest: emailed to every active manager and org admin, covering their teams and groups. Org admins get all of them.
• Personal digest: emailed to members who opt in, with their own trends. It respects your visibility setting, so a setting that hides you from yourself sends nothing.
• Channel digest: posted to a public Slack channel, one team or group per channel setting.

Every email has a one-click unsubscribe link for the digest category.

Working hours, holidays and time zone

Durations can be measured in business time. An org admin sets the calendar under Admin → Settings → Working hours and holidays:

1. Tick the Working days.
2. Set Start and End in local time. A working day cannot run past midnight.
3. Tick Public holiday calendars for your regions. They cover national public holidays for 2025 to 2032.
4. Under Company holidays, pick a date in Add a day off and select Add. Up to 400.
5. Select Save working hours.

Everyone can read the calendar, and only org admins change it. In the filter bar, switch Time to Business hours to see durations that count only these hours. A calendar change recomputes history, which can take up to an hour.

The workspace time zone decides which day an event belongs to, and what “this week” means. The week always starts on Monday. Changing the zone recomputes history.

Team targets

Targets are the lines your teams are measured against. Open Efficiency → Industry Benchmarks to see each metric with its default target and its citation. An org admin can select the pencil on a target to set your own value and whether lower or higher is better, or reset it to the default. A target is per metric, so changing it moves every team’s row. Alert rules that use Misses its target follow the target in force for the team.

A team or group can also have its own target that overrides the workspace target, and alert rules follow it.

Related

• Reports
• Privacy and control
• DORA and benchmarks
• Roles