Project, team, and user
Core resource vocabulary for the preview.
Project
A project is the top-level tenant or deployment boundary. It owns branding, users, sessions, flows, schemas, teams, apps, and configuration.
Team
A team is a tenant-grouping inside a project. It can represent a paying customer or a B2B end-customer depending on which project it lives in.
User
A user is an identity inside a project. Users can be self-owned or team-owned depending on lifecycle policy.
Preview note
Some design docs still describe target claim and platform lifecycle behavior. Claim is implemented server-side: a claimed project is one that carries an active owning-team grant, and the CLI, the OpenAPI endpoints, and the server handlers are all shipped. The console claim page is not shipped yet, so the browser leg of the flow has no guided UI.