Skip to main content
User operations cover the SDK methods your app uses after user identity is defined. Start with standard login-based user creation, use repository methods for reads and profile updates, and reserve token management for trusted workflows that need generated access tokens.
The pages in this section focus on SDK behavior. Admin-only actions and server-only workflows are called out when the client SDK does not expose the operation directly.

Operation Map

Create User

Create or authenticate a user through the SDK login flow.

Get User Information

Retrieve one user, batch lookup users where supported, or query user collections.

Search and Query Users

Search by display name or browse paginated user lists.

Update User Information

Update the current user’s profile fields.

Flag and Unflag Users

Report or clear reports on users for moderation workflows.

User Token Management

Create user access tokens for trusted or server-controlled workflows.

Delete User

Understand user deletion boundaries and admin/API requirements.

Choosing an Operation

NeedStart hereNotes
Sign in or create a userCreate Userlogin creates the user if the userId does not already exist.
Show a known user’s profileGet User InformationUse single-user reads when you already know the userId.
Build a user picker or directorySearch and Query UsersSearch by display name for keyword flows; query users for paginated browse flows.
Let users edit their own profileUpdate User InformationClient SDKs update the active user’s profile.
Add moderation reportingFlag and Unflag UsersReporting actions are available from SDK user repositories.
Generate an access tokenUser Token ManagementUse only from trusted workflows; normal SDK login does not consume these tokens directly.
Remove a user accountDelete UserDeletion is handled through admin/API workflows, not regular client SDK calls.