Team

The Team page is the workspace's people directory, both a list of who's around and the allocation board for features and initiatives.

What you'll see

• List view: name + role, ID, team, status, capacity bar, assigned features, assigned initiatives, skills, email; an Avg capacity stat sits above the table
• Org chart view: the manager hierarchy as a tree; reassign a manager from the card's dropdown
• Capacity: each member's bar is the sum of their feature allocation percentages for features in in-progress or testing, capped at 100. Blocked and planned work doesn't count

Row drawer

• Full name, email, role, team, avatar
• Capacity (0–100; the % of a workweek they have available for product work)
• Skills (string tags)
• Manager: set from the org chart, not the drawer
• Feature allocations (with an allocation_pct each)
• Initiative links

Common actions

• New member button in the toolbar (creates a team_members row, distinct from inviting an auth user, which lives under Settings → Members & Roles)
• Open a member to edit their feature allocations in the drawer (the capacity bar in the list is read-only)
• Org chart button in the toolbar opens the tree view

Merging duplicates

When the same person is on the roster twice, fold one into the other: Merge into… in a row's right-click menu, or in the More actions menu of an open team member. Only admins and the owner can, as with any roster change. Pick the team member who stays, and the review shows what would move before anything is written: Work and initiative assignments (keeping each one's role and allocation), the Work items they lead, the people who report to them, sprint capacity, invitations, comments and files. Keep the other one swaps which stays. Ctrl/Cmd+Enter merges.

The one who stays keeps their own name, role and capacity, takes skills they did not have, and fills an empty email, photo, team or manager from the duplicate. If only the duplicate is linked to a sign-in, that sign-in moves over. Two team members linked to different sign-ins cannot be merged: they are two people, so unlink one first if they really are the same person. The duplicate goes to the trash, and its ID now opens the one who stays.

Team member vs. workspace member

Two different concepts:

• Team members: people who do product work, tracked here. They may or may not have ProductOS access.
• Workspace members: people with a ProductOS login + role (owner | admin | member | commenter | viewer). Managed under Settings → Members & Roles.

A team member can be linked to a workspace member via profile_id so allocation appears on their profile.

How the link is established

• Automatically on invite-accept. When someone accepts a workspace invitation, ProductOS first looks for an existing team member with that email (and no link yet) and attaches the new profile to it, preserving any role/team/skills the admin already set. If no matching row exists, a fresh team member is created with role: "Team Member", status: "active". This means newly-joined users are immediately assignable as a feature Lead or an initiative owner.
• Manually from the detail dialog. Open any team member's detail dialog → the linked profile section shows the linked user, or a picker of unlinked workspace profiles when none is attached. The same dialog offers an unlink action.
• Manually from Settings → Members & Roles. Each workspace member row shows an "In roster" / "Add to roster" badge. The "Add to roster" action creates a roster row already linked to that profile.
• Removal cascade. When an admin or owner removes someone via Settings → Members & Roles, the linked team member is unlinked and flagged status: "offboarded": features and initiatives that name it as Lead or owner keep doing so, and historical assignment data stays intact.

A workspace member can be linked to at most one active team member; a second link is refused.

Related

• Team-members API reference
• Workspaces and roles: what each role can do
• Members & Roles: inviting and removing people