Documentation Index
Fetch the complete documentation index at: https://mintlify.com/zitadel/client-ruby/llms.txt
Use this file to discover all available pages before exploring further.
Overview
User models represent user entities and their associated data in Zitadel. The SDK distinguishes between human users (actual people) and machine users (service accounts).UserServiceUser
The main user model that can represent either a human or machine user.Unique identifier of the user
Metadata about the user resource including sequence number and timestamps
Current state of the user account (e.g., ACTIVE, INACTIVE, DELETED)
Username of the user, which can be globally unique or unique on organization level
List of possible usable login names for the user
Preferred login name of the user
Present if this is a human user. Contains human-specific attributes like profile, email, and phone
Present if this is a machine user. Contains machine-specific attributes
Example JSON
Example Usage
UserServiceHumanUser
Represents a human user with personal information.Unique identifier of the user
Current state of the user account
Username of the user, which can be globally unique or unique on organization level
Possible usable login names for the user
Preferred login name of the user
Profile information including name, gender, and preferred language
Email address and verification status
Phone number and verification status
User is required to change the used password on the next login
Timestamp when the password was last changed
Timestamp when MFA initialization was skipped
Example Usage
UserServiceHumanProfile
Contains profile information for a human user.Given name (first name) of the user
Family name (last name) of the user
Nickname of the user
Display name shown in the UI
Preferred language code (e.g., “en”, “de”, “fr”)
Gender of the user
URL to the user’s avatar image
Example Usage
UserServiceHumanEmail
Represents email information for a human user.Email address
Whether the email address has been verified
Example Usage
UserServiceHumanPhone
Represents phone information for a human user.Phone number in E.164 format
Whether the phone number has been verified
Example Usage
UserServiceMachineUser
Represents a machine user (service account).Name of the machine user
Description of the machine user’s purpose
Whether the machine user has a client secret configured
Type of access token used by this machine user (e.g., JWT or Bearer)
Example JSON
Example Usage
Common User Patterns
Checking User Type
Building User Display Information
Validating User Status
Related Models
These models are used in conjunction with user models:UserServiceDetails- Resource metadataUserServiceUserState- Enum for user statesUserServiceGender- Enum for gender valuesUserServiceAccessTokenType- Enum for access token types
Next Steps
- Learn about Organization Models
- Explore Application Models
- Review the User Service API for operations on users