Team

Team at /team is the people surface: who is on the tenant, what they own, and how to reach them. Membership itself — invites, roles, offboarding — runs through People; this workspace is the working view, not the admin console.

• Each card carries a photo, name, title, and team chip.
• Agents and system identities sit in the same grid as people. The team includes non-humans; ownership works the same.
• Cards without photos still carry title and team. Reachability needs a name and a team, not a headshot.

• Ownership on every row needs a name. Unassigned work is nobody’s work; the team surface shows where the gaps are before they become overdue.
• Position catalog and titles live under Job Roles. Member list, teams, and manager columns live under Org members.
• Staffing against time runs through Scheduling: who is available when is a calendar question, not a directory question.

What next

• Groups: how these members are organized.
• People: member list, invites, and offboarding.
• Job Roles: the position catalog behind titles.
• Scheduling: availability and coverage over time.
• My Tasks: the personal slice once ownership is set.