Dashboard reference
Understand every dashboard area, its purpose, and the first action to take there.
Overview#
The workspace home combines KPI totals, recent feedback, pending reviews, activity, and status distribution. Start here to identify what needs attention, then open the underlying item instead of treating the cards as a separate data source.
- 1
Confirm the workspace and reporting period
- 2
Review open and overdue feedback
- 3
Open pending reviews
- 4
Use Recent feedback to continue triage
Feedback#
The workspace-wide inbox lists reports from every project. Combine text, project, status, priority, type, assignee, and environment filters; then open a report to review its screenshot, replay, console, network, device, comments, AI suggestions, and activity.
- 1
Narrow the list with project and status filters
- 2
Open the report and inspect visual evidence
- 3
Set type, priority, and assignee
- 4
Move it through the configured workflow
#A18C2FCheckout payment failsBug · DevelopmentOpenProjects#
Projects separate websites or applications and own their environments, public client keys, members, workflow, integrations, reviews, releases, UAT readiness, and data controls.
- 1
Create or open the correct project
- 2
Add Development, Staging, and Production environments
- 3
Copy the public client key from Setup
- 4
Run a test report before Production
Reviews#
Reviews are the quality gate for feedback that needs validation. Inspect evidence and discussion, approve a valid result, or return it with a clear reason so the team knows what must change.
- 1
Open the pending review
- 2
Compare the fix with the original evidence
- 3
Approve or request changes
- 4
Record a useful review note
Releases#
Releases group resolved work by version or deployment. Draft a release, attach the relevant feedback, track completion, mark it deployed, and keep archived releases available for history.
- 1
Create a versioned draft
- 2
Attach resolved feedback
- 3
Check release progress
- 4
Mark deployed only after the real deployment
Analytics#
Analytics compares volume, type and status distribution, owners, response trends, overdue work, problematic pages, and AI summaries. Always state the date range, project, and environment when sharing a conclusion.
- 1
Choose the date range
- 2
Apply project and environment filters
- 3
Compare volume, resolution, and overdue trends
- 4
Open the source reports behind an anomaly
Notifications#
Notifications collect assignments, mentions, workflow changes, invitations, and release activity relevant to you. Open the target item before marking it read; use notification settings to reduce noise, not to hide important workflow events.
- 1
Filter unread notifications
- 2
Open the linked report or release
- 3
Mark reviewed items as read
- 4
Tune delivery preferences in Settings
Team#
Workspace owners invite members, resend or cancel pending invitations, change roles, suspend access, and remove members. Project membership can further limit what a person can do in one project.
- 1
Invite the member’s work email
- 2
Assign the least-privileged role
- 3
Check pending invitations
- 4
Review access when responsibilities change
Give Owner access only to people who must control workspace security, billing, and membership.
Integrations#
Workspace integrations connect providers such as Slack, Telegram, and webhooks. Project integration settings then decide where that project sends events. Connect, test, scope permissions, and disconnect unused providers.
- 1
Connect the provider at workspace level
- 2
Complete its authorization safely
- 3
Choose the project destination
- 4
Send a test event and verify delivery
Settings#
Settings covers profile and workspace details, notifications, security, enterprise controls, API keys, webhooks, AI usage, billing, and data management. Availability depends on your role and plan.
- 1
Open the exact settings section
- 2
Review the current value before editing
- 3
Save one controlled change
- 4
Verify the visible result and audit entry
Audit Log#
Audit Log records security-sensitive and administrative actions with actor, action, target, and time. Use it to investigate changes; do not treat it as a replacement for application monitoring or report history.
- 1
Set the relevant date and action filter
- 2
Identify the actor and target
- 3
Open the event details
- 4
Correlate the time with the affected report or setting
Monitoring#
Monitoring shows operational health signals and recent metric trends for owners and admins. Investigate warnings by time window, then correlate them with audit events, integrations, and affected feedback.
- 1
Check the current health state
- 2
Inspect the metric sparkline and time window
- 3
Compare the warning with recent changes
- 4
Escalate with timestamps and sanitized evidence
Audit Log and Monitoring are restricted to roles with administrative access.