Use this file to discover all available pages before exploring further.
The setUserAttributes mutation updates the DATABASE-sourced attributes for an existing user. Use this to update persistent key-value pairs that control parameterized connections and row-level data access.
This mutation replaces all DATABASE-sourced attributes on the user. Any attributes not included in the new list will be removed. JWT-sourced attributes (from SSO claims) are not affected. See User attributes for the difference between attribute sources.
The complete new set of DATABASE-sourced attributes. This replaces all existing DATABASE-sourced attributes — include every attribute you want the user to have after the call, not just the ones you’re changing.
For attributes that are stable (e.g., account_id), set them once at creation via userAttributes in createUsers. For session-scoped overrides that should not be persisted, use attributes in impersonateUser instead.