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 end to end: a claimed project is one that carries an active owning-team grant, and the CLI, the OpenAPI endpoints, the server handlers, and the console claim page (the guided UI for the browser leg of the flow) are all shipped.
A local project skips that browser leg by default. zitadel start creates a local admin, admin@zitadel.localhost, with a team of its own, and zitadel setup --server local attaches the new project to that team, so a local project is owned by the local admin from the moment setup finishes.