Account & identity
Your Starfire account is the identity layer behind chat history, projects, organization memberships, billing context, developer access, and security state.Core identity model
Starfire’s identity system is designed around a durable account rather than a browser-local profile. The account can carry:- verified email identity
- profile information and timezone
- authentication methods
- active sessions and recognized devices
- organization memberships
- plan and entitlement context
- developer credentials
- security events and account state
Authentication
The current product line supports email/password authentication with protected server-side sessions. OAuth sign-in can also be available for supported providers depending on deployment configuration. Passwords are never treated as reusable application data. Session state is kept separate from the password itself and can be revoked without changing the account identity.Personal and organization context
A person can use Starfire personally while also belonging to one or more organizations. Those contexts are not interchangeable. A project, subscription, developer application, or usage record can belong to a personal account or an organization depending on how it was created and the feature involved.Security state
Starfire can distinguish normal account activity from restricted or security-sensitive states. Administrators can use identity and security tooling to manage sessions, devices, access, and account status without deleting the account.Authentication & recovery
Learn sign-in, verification, password recovery, and OAuth concepts.
Sessions & devices
Understand how active sessions and device revocation work.