Users
Users: creation, profile, deactivation, lookups by role or external identity, reporting lines, and the OAuth login sync.
Get current user profile
Retrieve the current authenticated user's profile information.
Get users with pagination
Retrieve a paginated list of all users, newest first unless sort_by says otherwise. Every ordering ends on the unique code, so pages stay disjoint for a client stitching them together.
Create a new user
Create a new user with the provided information.
Send the welcome notification to selected users
Sends the welcome notification to a hand-picked selection of users, the deferred half of onboarding for a tenant that has automatic welcomes switched off. Users who are already onboarded are skipped rather than sent to again, and the response reports how many of each. Sending is not gated on the notification type being enabled: that switch governs automatic delivery, and this send is not automatic.
Get user by external ID
Retrieve a specific user by its external ID.
Get users by role
Retrieve users filtered by role.
Get user by Zitadel ID
Retrieve a specific user by its Zitadel ID.
Resend onboarding invite email
Re-send the Zitadel invite email so the user can set a password and complete onboarding.
Get user by ID
Retrieve a specific user by its ID.
Update a user
Update an existing user with the provided information.
Get a user's approver footprint
Every way the user can still be resolved as an approver: static approver groups (hand-picked memberships only, never the ones derived from a role or an org unit), users reporting to them, org units they lead or deputy-lead, vacations they substitute for, and approval rules reaching them. sole_approver_rows narrows that last axis to the decision-table rows whose approvals reach this user and nobody else, resolving each "#tag" through the same live group membership the approval fan-out uses. What that costs the tenant depends on the action: a deactivate leaves those rows resolving to the user, so their approval tasks are still created and then wait on an account blocked at login, while only a delete makes the row unresolvable and falls its approvals back to an admin. rule_row_coverage counts, TENANT-WIDE across every non-deleted approval rule and NOT only the rules reaching this user, how many approver rows the scan decided (analyzed_rows, of which group_tag_rows needed a group resolved), how many it left undecided because they resolve through a ":" selector against a concrete purchase request (selector_rows), and how many it could not read at all (unreadable_rows). Read before deactivating or deleting the user; advisory only, it blocks nothing.
Deactivate a user
Soft delete (deactivate) a user by setting it as inactive.
List a user's direct reports
Retrieve all users whose reporting manager is the given user.