Team standups

Your team’s daily updates.

Who can use this page

Who: managers, meaning anyone with direct reports, and anyone who can view people across the organization.

Roles that have it by default: HR Manager, HR Associate and People Manager.

Superusers can always open it. Your administrator can also give the permission to a custom role.

Team standups shows your team’s updates in one place.

Extra working day requests from your direct reports appear in your approvals. See Requests inbox.

Default standup project and optional updates

A person may belong to several projects while sending their daily standup to one Default standup project. One active assigned project with a configured Slack channel is selected automatically. If several are eligible, a person manager must choose; if none are eligible, ask a person manager to check membership dates, project status and Slack configuration. Saving an update still works while routing is unresolved; it is not broadcast to all projects.

Person managers can review these settings in the person's detail view and in the project's team list. Manage standup settings opens the controls; Review changes names the person, current destination and new destination before Save standup settings applies the change. Cancel leaves the saved policy untouched. Project management alone does not grant permission to override another project's default. Employees cannot exempt themselves.

Standup required → Optional makes updates optional from today in the organization's timezone. Time tracking and attendance hour thresholds still apply. When ending the day, choose Submit update & end day or Skip update & end day. Blank skips create no standup; skipping a written draft requires discard confirmation. Failed requests preserve the draft. Voluntary updates remain visible and use the same validation and default-project routing as required updates.

Optional dates are Not required, rather than missing, in the team overview and are excluded from missing-standup alerts and reminders. Earlier dates retain their expectations. Requiring updates again starts from the change date. Changes record the editor, prior policy and effective date; a stale edit must be reloaded and reviewed again. Open tabs refresh policy on focus and periodically.

Changing a default does not replay earlier updates or redirect an already queued delivery. Each saved standup keeps its original destination (including unresolved routing); retries use that recorded destination. Existing memberships are preserved on upgrade, and unambiguous single-project defaults are initialized without sending Slack messages. A default that becomes unavailable falls back only to a sole eligible project; otherwise a manager must choose a replacement.