payloadcms / payloadcms/payload
Account page: "Document locked" by self + logout after saving own user profile
@PatrikKozak is already working on this.
Since Feb 18, 2026.
- 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:
-
"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.
-
Logged out after saving: After saving, the update succeeds (toast shows "Updated successfully") but I'm immediately redirected to
/admin/logout-inactivity?redirect=%2Fadmin%2Faccountwith 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
- Log in to the admin panel
- Navigate to
/admin/account - Observe the "Document locked" modal (locked by your own email)
- Click "Take over"
- Change any field (e.g. first name)
- Click Save
- 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-s3payload-oauth2(Google + Microsoft)
Additional context
- Auth config uses
tokenExpiration: 1209600(2 weeks),useAPIKey: true,verify: false - Document locking is at default (enabled) — no custom
lockDocumentsconfiguration - Possibly related to #8589 and #13576
- Multiple browser tabs may be open but the issue reproduces consistently even with a single tab
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.