Dashboard Guide

Navigate and master the Behavioral Insights Engine dashboard

Dashboard Structure

The BIE dashboard is organized into five main tabs, each providing specific views and controls for community behavioral analysis.

Overview

Health score, key metrics, trend indicators, and quick action widgets

Heatmaps

Activity pattern visualization by day and hour, multiple heatmap types

Incidents

Detected anomalies, severity levels, investigation tools, and resolution actions

Data Controls

Retention settings, privacy controls, exclusions, and data export tools

Settings

Configuration, notifications, alert thresholds, and team permissions

Overview Tab

The Overview tab is your dashboard homepage, displaying key health metrics and community status at a glance.

Key Widgets

Health Score Card

Large, prominent display of your server's current 0-100 health score with color coding (red/orange/yellow/cyan/fuchsia)

Click to see score breakdown and contributing factors

Trend Indicators

7-day and 30-day trend arrows showing if health score is improving or declining

Green up = improving, Red down = declining, Neutral = stable

Active Members Count

Number of members with activity in the last 24 hours

Helps gauge engagement and community vitality

Activity Summary

Messages, voice hours, reactions, and joins/leaves in last 24h

Snapshot of recent community activity

Recent Incidents

List of latest detected anomalies with severity badges

Click incident to jump to detailed investigation view

Quick Actions

Buttons to jump to Heatmaps, Incidents, or Settings

Fast navigation to commonly used dashboard sections

Set Health Score Targets

Discuss with your team what health score range is acceptable for your community type. Gaming communities might naturally have different patterns than professional networks.

Heatmaps Tab

The Heatmaps tab provides interactive visualizations of activity patterns across days and hours.

Heatmap Features

Multiple Heatmap Types

Toggle between Message Activity, Voice Activity, Member Joins, and Reaction Heatmaps to see different engagement patterns

Time Range Selection

Choose date range to view current week, last month, last 3 months, or custom range

Channel Filtering

View heatmaps for all channels, specific channel, or exclude certain channels from visualization

Interactive Cells

Hover over heatmap cells to see detailed numbers and percentages for that specific day-hour combination

Comparison Mode

View two time periods side-by-side to compare patterns and identify changes

Export Options

Download heatmap as image (PNG/SVG) or export underlying data as CSV

1

Select Heatmap Type

Choose from Message, Voice, Joins, or Reaction heatmaps

2

Choose Time Range

Pick predefined range or set custom date window

3

Filter by Channel (Optional)

Narrow to specific channel(s) or view all channels

4

Analyze Patterns

Hover over cells, note peak times, identify day-of-week patterns

5

Use for Planning

Schedule events, announcements, or discussions during identified peak times

Heatmap Color Scale

Warmer/brighter colors indicate higher activity. The color scale is normalized to your server's data, so what looks warm is relative to your typical patterns.

Incidents Tab

The Incidents tab shows all detected anomalies, with tools for investigation, correlation, and resolution.

Incident Dashboard Features

Incident List

Searchable, filterable list of all incidents sorted by date (newest first) or severity

Severity Filtering

Show only critical, high, medium, or low severity incidents, or combine filters

Type Filtering

Filter by incident type (drop, spike, cliff, mass join, pattern deviation, voice anomaly)

Status Filtering

View unresolved, resolved, dismissed, or escalated incidents

Incident Details Panel

Click incident to view full details, metrics, correlated incidents, and channel/member info

Investigation Tools

View activity heatmap during incident window, channel history, and related metrics

Resolution Actions

Mark as resolved (expected/addressed), dismissed (false positive/benign), or escalated

Notes & Comments

Add investigation notes and context for future reference and team coordination

Typical Investigation Workflow

1

Review Incident

Review incident in list (severity, type, time)

2

Examine Details

Click to open details and examine metrics

3

Check Heatmap

Check heatmap for that day/hour to assess if expected

4

Review Correlations

Review channel activity and correlations

5

Consider Context

Consider external context and take action if needed

6

Resolve Incident

Resolve incident with appropriate status and notes

Batch Actions

You can select multiple incidents to apply resolution status to many incidents at once. Useful for marking similar incidents as expected after major events.

Data Controls Tab

The Data Controls tab manages data retention, privacy, compliance, and export settings.

Data Controls Sections

Retention Policy

Set automatic data purge period (30d-2yr) and choose granularity (hourly to monthly)

Manual Purge

Immediately delete data for specific date ranges, channels, or members

Channel Exclusions

Exclude bot channels, announcements, or automated channels from analysis

Member Exclusions

Exclude bots, automated accounts, or specific members from behavioral analysis

Data Export

Export data in CSV/JSON formats with custom scopes and date ranges

Compliance Settings

GDPR/CCPA controls, data subject request forms, audit logs

Data Controls are Critical

Properly configured data controls ensure compliance, reduce noise, and maintain community trust. Review quarterly to ensure settings match your current needs.

Settings Tab

The Settings tab controls BIE configuration, notifications, permissions, and threshold tuning.

Key Settings

Alert Notifications

Configure which severity levels trigger alerts, notification channels (DM/channel/webhook), and quiet hours

Detection Thresholds

Adjust sensitivity for different incident types. Higher thresholds = fewer alerts, lower = more sensitive

Team Permissions

Grant dashboard access to moderators and team members with granular permission levels

Timezone Configuration

Set your server's primary timezone for accurate heatmap and time-based analysis

API Keys

Generate API keys for programmatic access and custom integrations

Integrations

Connect external services (Slack, webhooks, analytics tools) for extended functionality

Health Score Benchmark

Set target health score and track against industry benchmarks for your community type

Permission Management

Be careful with dashboard access permissions. Only grant to trusted team members who understand the sensitivity of behavioral data.

Dashboard Best Practices

Weekly Review Routine

Spend 10-15 minutes weekly reviewing health score, resolving incidents, and checking for concerning trends

Monthly Analysis

Review monthly heatmaps, compare to previous months, analyze trend direction, and plan content/events

Mark Expected Changes

When you run events or post important announcements, mark resulting incidents as "expected" to improve anomaly detection

Share Insights with Leadership

Export reports and share health trends with server leadership to demonstrate community vitality

Use Heatmaps for Planning

Base event scheduling, announcement timing, and moderation shifts on heatmap peak times

Keep Exclusions Clean

Periodically review channel and member exclusions. Remove if no longer needed to get complete picture

Tune Thresholds

After a few weeks of use, adjust detection thresholds if you're getting too many false positives or missing real anomalies

Document Patterns

Keep notes on what causes incidents in your community. Over time, you'll recognize patterns faster

Getting Started with the Dashboard

1

Navigate to BIE Dashboard

Go to Server Settings > Behavioral Insights

2

Review Current Health Score

Check the Overview tab to understand your server's current status

3

Check Recent Incidents

Review Incidents tab to see detected anomalies and their status

4

Configure Initial Settings

Go to Settings and configure alert channels, timezone, and team permissions

5

Set Up Exclusions

Go to Data Controls and exclude bot channels and automated accounts

6

Analyze Heatmaps

Check the Heatmaps tab to identify peak activity times for event planning

7

Weekly Review

Schedule a weekly dashboard check to review health, incidents, and trends

Bookmark the Dashboard

Save a bookmark to your BIE dashboard for quick access. Make it part of your regular server management routine.

Frequently Asked Questions

How do I access the BIE dashboard?
Navigate to Settings > Behavioral Insights in your server admin panel. You need server administrator or designated BIE manager permissions to access the dashboard.
What are the main dashboard sections?
The dashboard has 5 main tabs: Overview (health metrics), Heatmaps (activity patterns), Incidents (anomalies), Data Controls (settings), and Settings (configuration).
How often is the dashboard data updated?
Overview metrics update in real-time or within a few minutes. Heatmaps update hourly. Incidents are detected and displayed as they occur. Exports and reports may take longer for large datasets.
Can I share dashboard views with team members?
Yes. You can generate shareable reports and export visualizations. Team members need appropriate permissions to view the dashboard directly.
What if I need more detailed analysis?
Export data in CSV/JSON format and use external tools for deeper analysis. BIE provides APIs for programmatic access and custom integrations.
How do I know if my server is healthy?
Check the health score on the Overview tab. Scores 70+ are generally good. Review incidents, heatmaps, and trends to understand what contributes to your current score.
Can I set custom thresholds for alerts?
Yes. Go to Settings and adjust severity thresholds, notification channels, and alert filters to match your community's patterns and monitoring needs.
How do I export data for reports?
Go to Data Controls > Export. Choose format (CSV/JSON/PDF), scope (date range, channels, metrics), and granularity. Large exports are queued for processing.