Get user within organization context
Retrieves basic user information for a user within an organization context. This endpoint verifies that both the caller and the target user are members of the specified organization before returning user data.
Security: Returns 404 (not 403) if the target user doesn’t exist or is not a member of the organization. This prevents information leakage about user existence.
Authorization: Requires read access to the organization (caller must be a member). Response: Returns only basic user fields (userName, email) for privacy.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
The unique identifier of the organization Standard identifier pattern for resource names
^[a-zA-Z0-9_ -]+$The username (email) of the user to retrieve
Response
User information retrieved successfully
Represents a user account with profile information and tutorial status
The user's username — an email address used for authentication. Matches the path-parameter form on /users/{userName}. (Previously $ref'd IdentifierPattern, which disallowed '@' and '.'; that was never enforced at runtime so production data is all emails.)
User's email address, used for authentication and notifications
User's first name. May be empty when the row was auto-created (e.g. Auth0 ensure-user path) before the user filled in their profile — UI flows that capture a name should PATCH this in.
64User's last name. May be empty when the row was auto-created (e.g. Auth0 ensure-user path) before the user filled in their profile — UI flows that capture a name should PATCH this in.
64User's business role or job title
Represents the tutorial completion status and user preferences for onboarding