Skip to main content

Share a dashboard with your team

WhaTap already ships polished default dashboards for every product. You don't have to build anything new — just invite team members to the project and share a default dashboard, and your team's observability culture has already started. This guide walks through invitation to sharing in 5 minutes.

This guide is for project administrators who handle team invitations and permission management.

What you get from this guide
  • An environment where 3–5 team members work on the same project together
  • Understanding which permissions to grant at invite time (especially alert reception and settings)
  • A single link the team checks every day as the default observability screen

Prerequisites​

  • Member management permission — required to invite team members
  • Email addresses of team members to invite
  • The dashboard the team will mainly look at (for example, application dashboard, server resource board) decided

Step 1. Invite team members​

Path: Home > Select project > Management > Project Management > Project Member

  1. Click the Invite Member button at the top right.
  2. Under User role, check the permissions to grant the invitee and click the Apply button.
  3. Enter the team member's email in the email field and click the Add button. You can add multiple members in sequence.
  4. When done, click the Complete button. Invitation emails are sent.
Note

WhaTap permissions are not fixed roles like "Admin/Editor" — they are per-feature permission checkboxes. Think "what will this person actually do?", not "what role are they?".

Common permission combinations​

Table | Permission combinations by purpose
PurposeDefaultExtra permissions to check
View-only dashboard user (observer)View, View logNone
Incident responder / alert recipientDefaultAlert reception
Alert rule ownerDefaultAlert reception, Alert settings
Dashboard/setting editorDefaultEdit
Project admin (with member management)DefaultEdit, Alert reception, Alert settings, Member management
Flexboard editor/adminDefaultProject flexboard update
Alerts require permission

Without Alert reception, a user can only change their own account's reception settings and cannot manage the project-wide alert reception. Be sure to grant this permission to incident responders.

Without Alert settings, a user cannot create or edit alert rules. Do not grant this to view-only observers.

For the full permission list with detailed descriptions, see Member permissions.

Step 2. Share the default dashboard​

No need to build a Flexboard separately — share the product's default dashboard directly.

  1. Open the dashboard your team will mainly look at:
    • Application team → Application dashboard
    • SRE/Infra team → Server resource board
    • Database team → DB dashboard
  2. Set team-appropriate filters at the top:
    • Agent selection dropdown: only the servers/applications the team owns
    • Time range dropdown: last 6 or 24 hours
  3. Copy the browser URL. Applied filters are encoded in the URL.
  4. Pin it in the team Slack channel, Notion, or shared doc as a permanent bookmark.
The "daily first screen" rule

Get the team to "open WhaTap from this link first" — incident detection speed improves noticeably. Simple, but effective.

Step 3. Agree on one team rule​

Even with a shared dashboard, team observability culture won't take hold without an agreement on when and who looks at it. Add one rule to team meetings or rituals:

  • "Scan for 1 minute before every standup"
  • "Share yesterday's anomalies at the daily retrospective"
  • "Incident responder checks this screen every 30 minutes"

Verify​

  • Invited members appear under Project Member (with a Waiting for an invitation. tag if they haven't joined yet)
  • Team members accessing the shared URL see the screen with filters already applied
  • Permissions work as configured — alert reception and event rule editing available accordingly

Your shared team observability point is ready. Establishing this "default sharing" alone gets you halfway to an observability culture, before introducing any new tools.

Next steps​

Last updated on