payloadcms / payloadcms/payload

Account page: "Document locked" by self + logout after saving own user profile

Open
#15,669 0 comments 0 reactions 1 assignee View on GitHub

@PatrikKozak is already working on this.

Since Feb 18, 2026.

invalid-reproduction
Dominant language
TypeScript
Stars
44.8k
Forks
4.2k
Avg merge
2d 21h
Merged PRs (30d)
53

Description

Link to reproduction

N/A — reproducible on a standard Payload 3.x project with default document locking enabled.

Describe the Bug

When editing my own user profile via /admin/account, two issues occur:

  1. "Document locked" by myself: Upon navigating to the account page, a modal appears saying my own email is currently editing the document. I have to click "Take over" to proceed.

  2. Logged out after saving: After saving, the update succeeds (toast shows "Updated successfully") but I'm immediately redirected to /admin/logout-inactivity?redirect=%2Fadmin%2Faccount with the message "You have been logged out due to inactivity." I can log back in immediately.

This only happens when editing my own user via the account page. Editing other users via /admin/collections/users/:id works fine with no lock warning and no logout.

Screenshots
To Reproduce
  1. Log in to the admin panel
  2. Navigate to /admin/account
  3. Observe the "Document locked" modal (locked by your own email)
  4. Click "Take over"
  5. Change any field (e.g. first name)
  6. Click Save
  7. Observe "Updated successfully" toast, followed immediately by redirect to /admin/logout-inactivity
Expected behavior
  • The account page should not show a "Document locked" warning for your own user
  • Saving your own profile should refresh the auth token and keep you logged in
Payload Version

3.64.0

Adapters and Plugins
  • @payloadcms/db-postgres
  • @payloadcms/storage-s3
  • payload-oauth2 (Google + Microsoft)
Additional context
  • Auth config uses tokenExpiration: 1209600 (2 weeks), useAPIKey: true, verify: false
  • Document locking is at default (enabled) — no custom lockDocuments configuration
  • Possibly related to #8589 and #13576
  • Multiple browser tabs may be open but the issue reproduces consistently even with a single tab

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.