Managing Teams
Teams are the core unit of organization in Murmurd. Each team has its own check-ins, priorities, escalations, and summaries. This guide covers team management for admins.
Creating a Team
-
Navigate to Teams
Go to Settings → Teams
-
Click Create Team
Open the team creation form
-
Enter team details
- Name: Clear, recognizable team name
- Description: What this team does (optional)
- Division: Which division it belongs to (optional)
-
Assign leadership
- Product Manager (PM): Required, receives escalations first
- Manager: Optional, backup for escalations
-
Save
Team is created and ready for members
Team Settings
Click on a team to access its settings:
General
| Setting | Description |
|---|---|
| Name | Team display name |
| Description | Team purpose/scope |
| Division | Parent division (can be None) |
| Active | Whether team is active |
Leadership
| Role | Purpose |
|---|---|
| PM | First escalation contact, owns team summaries |
| Manager | Backup for escalations, receives summaries |
Check-in Settings
Teams can override organization defaults:
| Setting | Options |
|---|---|
| Prompt time | Inherit from org/division or custom |
| Working days | Inherit or custom |
| Questions | Inherit, extend, or override |
Questions
Manage team-specific questions:
- Go to team settings → Questions
- Choose inheritance mode:
- Inherit: Use org/division questions
- Extend: Add questions to inherited set
- Override: Use only team questions
- Add/edit/remove questions as needed
Adding Members
-
Go to Team Members
Click on team → Members tab
-
Click Add Member
Open the member selection
-
Select users
Choose from organization members
-
Assign roles
Set each member’s team role:
- Member: Standard participant
- PM: Product Manager (if not set)
- Manager: Team manager (if not set)
-
Save
Members are added and will receive prompts
Removing Members
To remove someone from a team:
- Go to team → Members
- Find the member
- Click the remove icon
- Confirm removal
Removal effects:
- Stops check-in prompts for this team
- Removes from team activity feed
- Historical data remains
Team Roles
Member
Standard team participant:
- Receives daily check-in prompts
- Can view team activity (based on visibility)
- Can create escalations
- Can set weekly priorities
Product Manager
Team leadership role:
- All member capabilities
- Receives escalations first
- Can resolve escalations
- Receives weekly summaries
- Manages team questions
Manager
Oversight role:
- All PM capabilities
- Backup for escalation routing
- Cross-team visibility (if on multiple teams)
- Receives division summaries (if Division Manager)
Multi-Team Membership
Users can belong to multiple teams:
- Each team has its own check-ins
- Priorities are per-team-per-week
- Escalations are team-specific
- Dashboard shows all teams
Best Practices for Multi-Team Users
- Limit teams: 3-4 max for sustainable participation
- Clear boundaries: Different responsibilities per team
- Stagger timing: Consider different check-in times
- Priority focus: One priority per team, not per person
Team Visibility
Control what team members can see:
| Content | Default Visibility |
|---|---|
| Check-ins | Team (changeable per item) |
| Priorities | Team |
| Escalations | Team (changeable per item) |
| Summaries | PM and Manager only |
Archiving Teams
To archive a team that’s no longer active:
- Go to team settings
- Toggle Active to off
- Save
Archived teams:
- Stop sending prompts
- Don’t appear in navigation
- Keep all historical data
- Can be reactivated later
Deleting Teams
To permanently delete a team:
- Go to team settings → Danger Zone
- Click Delete Team
- Confirm by typing team name
Team Analytics
View team health metrics:
| Metric | Description |
|---|---|
| Response rate | % of prompts answered |
| Average response time | How quickly people check in |
| Priority completion | % of priorities completed |
| Escalation volume | Open vs resolved over time |
Access analytics via team → Analytics tab.
Troubleshooting
”Team member not receiving prompts”
- Verify they’re added to the team
- Check their vacation/pause status
- Confirm Slack/email connection
- Check team’s active status
”Can’t add member to team”
- User must be invited to org first
- Check you have admin permissions
- Verify team isn’t archived
”Escalation not routing correctly”
- Verify PM is assigned
- Check PM’s vacation status
- Verify Manager backup exists
- Check escalation’s team assignment