Key Concepts

Murmurd is easiest to configure when everyone shares the same vocabulary. These are the concepts that shape the product.

Organization Structure

An organization is the top-level workspace. It owns:

Divisions group teams together. They are useful for:

New organizations start with a default Main division.

Teams are where day-to-day work happens. Check-ins, escalations, priorities, and summaries are all team-based.

Submits check-ins, creates escalations, sets weekly priorities, and views items allowed by visibility rules.

Receives escalations first and can receive leadership-specific questions and digests.

Acts as the second escalation target and receives the same leadership-specific prompts as Team Leaders.

Configured at the division level. Murmurd uses this person as the final escalation fallback and as a recipient for division-level digests.

Admins manage rollout and settings. Owners also handle organization-level actions such as SSO, SCIM, and organization deletion.

Murmurd uses the same three visibility levels across check-ins, priorities, and escalations:

Confidential content is only visible to the author and managers, and it is excluded from AI summary generation.