Skip to content
murmurd docs

Key Concepts

This guide explains the fundamental concepts you’ll encounter when using Murmurd.

Organizational Hierarchy

Murmurd uses a hierarchical structure to organize your company:

Organization
├── Division (optional)
│   ├── Team A
│   │   └── Members
│   └── Team B
│       └── Members
└── Team C (without division)
    └── Members

Organization

The top-level entity representing your company. Each organization has:

  • Unique name and settings
  • Subscription and billing
  • Global configuration (check-in times, AI provider, etc.)

Divisions

Optional groupings for larger organizations:

  • Purpose: Group related teams (e.g., “Engineering”, “Product”, “Design”)
  • Managers: Division managers oversee all teams within
  • Settings: Can have their own timezone and question sets

Teams

The primary unit where work happens:

  • Members: People who belong to the team
  • PM (Product Manager): Receives escalations first
  • Manager: Backup for escalations, sees summaries
  • Questions: Can inherit from division/org or be custom

User Roles

Member

Standard team participant:

  • Submit daily check-ins
  • Create escalations
  • Set weekly priorities
  • View team activity (based on visibility)

Product Manager (PM)

Team-level leadership:

  • All member capabilities
  • Receive and resolve escalations
  • View team summaries
  • Manage team questions

Manager

Oversight role:

  • All PM capabilities
  • Backup for escalation routing
  • Cross-team visibility
  • Division-level summaries

Admin

Organization administrator:

  • All manager capabilities
  • Manage users and teams
  • Configure organization settings
  • Billing and subscription management

Core Features

Check-ins

Daily async updates that replace standup meetings:

  • Questions: Configurable prompts answered daily
  • Visibility: Team, Org, or Confidential
  • Delivery: Via Slack, email, or web

Escalations

Surface blockers to the right people:

  • Routing: PM → Manager → Division Manager
  • Vacation-aware: Skips people who are away
  • Resolution: PM or original reporter can resolve

Priorities

Weekly accountability without micromanagement:

  • One per team per week: Focus on what matters most
  • Outcomes: Completed, Shifted, or Dropped
  • Tracking: Personal trends over time

Summaries

AI-powered weekly digests:

  • Friday Snapshot: What happened this week
  • Monday Weekstarter: Priorities and reminders
  • Aggregated: Check-ins, priorities, escalations

Visibility Levels

Control who sees your content:

LevelWho Can See
TeamAll members of that team
OrgEveryone in the organization
ConfidentialOnly you and managers/admins

Next Steps

Now that you understand the concepts: