User Profiles

Every user in Aero2 has a profile containing their identity information. Profile data can come from social login providers, manual entry, or admin updates.

Profile Fields

Field	Type	Description
`email`	string	The user's email address (unique per application)
`name`	string	Display name
`given_name`	string	First name
`family_name`	string	Last name
`picture`	string	URL to the user's profile picture
`email_verified`	boolean	Whether the email address has been verified

Self-Service Profile Updates

Authenticated users can update their own profile using the API:

curl -X PUT https://your-app.aero2.dev/api/users/me \
  -H "Authorization: Bearer <access_token>" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Jane Doe",
    "given_name": "Jane",
    "family_name": "Doe"
  }'

Users cannot change their own email address or email_verified status through this endpoint.

Admin User Management

Administrators can manage any user account through the admin API:

# Get a user by ID
curl https://your-app.aero2.dev/api/users/:id \
  -H "Authorization: Bearer <admin_token>"
 
# Update a user
curl -X PUT https://your-app.aero2.dev/api/users/:id \
  -H "Authorization: Bearer <admin_token>" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Jane Doe",
    "email_verified": true
  }'
 
# Delete a user
curl -X DELETE https://your-app.aero2.dev/api/users/:id \
  -H "Authorization: Bearer <admin_token>"

See the Users API reference for full details.

Profile Data from Social Login

When a user signs in through a social provider (GitHub, Google, etc.), Aero2 populates their profile with data from the provider:

Name — Pulled from the provider's profile
Picture — Avatar URL from the provider
Email — Email address from the provider (marked as verified if the provider confirms it)

If the user later signs in with a different provider, the profile is updated with the latest information from that provider.

Custom Metadata

:::info Coming Soon This feature is under active development. The design below reflects our planned implementation. :::

Custom metadata will allow you to store arbitrary key-value data on each user profile. This is useful for application-specific data like preferences, subscription tiers, or feature flags.