People is the workspace view of who is in, which delivery identities belong together, and who is waiting to get access.

Members

Members are Warestack seats and roles. A member can belong to teams, and their role controls which administrative actions they can perform.

Identities

Identities connect a GitHub account with the Slack person who can receive attributable DMs. Linear identity is also used when assigning issues.

Identity is supporting context, not a second member record:

• A GitHub login is not automatically a Slack handle.
• An owner with no confirmed Slack binding cannot receive Review SLA escalation.
• /warestack whoami shows the current binding; /warestack link starts self-confirmation.
• Admins can inspect and manage identity readiness, but confirmation protects the person boundary.

See Identities and owners for the routing contract.

Requests and invitations

Requests show people waiting for workspace access and pending team invitations. Team invitations use a private confirmation link and preserve the inviter’s intended team and role.

The signed-out or wrong-account confirmation flow does not silently accept for another GitHub identity. Permission failures remain visible; they are not reduced to a transient snackbar.

Permissions

Members can see the surfaces their role allows. Administrative People views — including identity management and access requests — stay role-gated. A direct URL without permission returns an explicit permission state while keeping the user signed in.

Why this matters to automation

Vanta remains responsible for HR, IdP, laptop, and access-control tests. Warestack identities route delivery evidence; they do not replace those systems.