n8n - 💡(How to fix) Fix User cannot see own workflow version history - restricted to admins [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
n8n-io/n8n#29774Fetched 2026-05-06 06:35:19
View on GitHub
Comments
2
Participants
3
Timeline
9
Reactions
0
Author
Timeline (top)
commented ×2labeled ×2mentioned ×2subscribed ×2

Error Message

User has a workflow, which is shared with 3 other users. He can edit and run the workflow but when he tries to access the workflow version history, he is met with an error message stating that only admins can access it. As an admin, I can confirm I could access the version history and roll back to a previous version as he requested. Error message: Version History. Listing all users is limited to instance administrators. Filter by project to list project members

  • error: all

Code Example

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.
RAW_BUFFERClick to expand / collapse
<!-- Please follow the template below. Skip the questions that are not relevant to you. -->

User has a workflow, which is shared with 3 other users. He can edit and run the workflow but when he tries to access the workflow version history, he is met with an error message stating that only admins can access it. As an admin, I can confirm I could access the version history and roll back to a previous version as he requested.

Error message: Version History. Listing all users is limited to instance administrators. Filter by project to list project members

<img width="608" height="208" alt="Image" src="https://github.com/user-attachments/assets/7c44ba8d-7bb1-444a-a690-f1e4da30ff16" />
(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.

Share the output returned by the last node

<!-- If you need help with data transformations, please also share your expected output. -->

Debug info

core

  • n8nVersion: 2.17.5
  • platform: docker (cloud)
  • nodeJsVersion: 24.14.1
  • nodeEnv: production
  • database: sqlite
  • executionMode: regular
  • concurrency: 200
  • license: enterprise (production)

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: filesystem

pruning

  • enabled: true
  • maxAge: 720 hours
  • maxCount: 25000 executions

client

  • userAgent: mozilla/5.0 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/147.0.0.0 safari/537.36
  • isTouchDevice: false

Generated at: 2026-05-05T10:59:03.845Z

extent analysis

TL;DR

The user may need to be added as a project member or an instance administrator to access the workflow version history.

Guidance

  • Check the project membership settings to ensure the user is listed as a member, as the error message suggests filtering by project to list project members.
  • Verify the user's role and permissions within the instance to determine if they should be granted administrator access.
  • Review the instance's access control settings to see if there are any specific restrictions on accessing workflow version history.
  • Consider adding the user as a project member or granting them temporary administrator access to test if this resolves the issue.

Notes

The issue seems to be related to access control and permissions within the n8n instance, but the exact configuration and settings are not provided.

Recommendation

Apply workaround: Grant the user temporary administrator access or add them as a project member to test if this resolves the issue, as the error message suggests this may be the cause.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING