user field: your own identifier for the end user a call acts on behalf of. Dify never authenticates it, so pick a stable value per person, such as an account ID, and send it consistently.
Dify starts tracking a new user the first time it appears, and one app key serves any number of end users.
What user Scopes
user controls what each call can see and do:
- Conversations: listing, history, renaming, and deletion all operate on that user’s conversations only.
-
Files: an upload belongs to the uploading user, and referencing it under a different
userfails. -
Stopping generation: the chat-family stop endpoints act only when
usermatches the one that started the reply. A mismatch is silently ignored—the call succeeds either way, so it isn’t detectable from the response. Workflow’s Stop Workflow Task does not checkuser.
user per person across every call in a flow—upload, send, and stop all check it.