Skip to main content
Idea

Revision history for view-only permissions

Related products:LucidchartLucidsparkLucid Suite
  • March 5, 2026
  • 5 replies
  • 69 views

Forum|alt.badge.img+1

Background: I’m primarily a Lucidchart user

Currently, it appears that viewing a document’s change history requires Edit permissions (File → Show Revision History is grayed out without Edit permissions).

As a document viewer, I’d like the ability view (and potentially compare) different versions of that document.

 

Use case:

Suppose a system’s architecture and behavior are captured using Lucidchart, and document revisions are used for different versions of that system.

Non-contributor stakeholders need the ability to understand how past versions (or the latest released version) of that system work.

Without this, viewers can only view the latest version of a document. During development, this may differ from the latest released version of the system represented by the document.

 

Suggestion:

I’m speculating that revision history is grayed out without Edit permissions to keep read-only users from potentially using the Restore or New From Version features in the revision history sidebar.

Would it possible to just gray out those options for users without Edit permissions?

Edit: Bonus points if the compare feature also works without Edit access.

March 6, 2026

Hi ​@Nelson R,

Thank you for clarifying. I apologize for any confusion regarding how revision history works for different permission levels. As you pointed out, Lucid currently requires edit permissions to access Revision History, but your feedback about making it accessible is really valuable. Thanks for sharing this suggestion with the community!

Comments

alison cheney
Forum|alt.badge.img+8
  • Lucid community team
  • March 6, 2026

Hi ​@Nelson R,

Thank you for this thoughtful idea and for providing details about your specific use case! You are correct that in order to restore a document to a previous version using Revision history, you must have edit access.

We encourage anyone else who’s interested in this to upvote this post and share any additional details about your use case or what you’d like to see in this experience. For more information about how we manage feedback in this community, please take a look at this post:

 


Forum|alt.badge.img+1
  • Author
  • March 6, 2026

Hi Alison,

Thank you for reviewing.

Just to clarify, I’m just suggesting allowing access to the Revision History without requiring Edit access - the Restore feature within it should probably still be blocked to users without Edit access.


alison cheney
Forum|alt.badge.img+8
  • Lucid community team
  • March 6, 2026

Hi ​@Nelson R,

Thank you for clarifying. I apologize for any confusion regarding how revision history works for different permission levels. As you pointed out, Lucid currently requires edit permissions to access Revision History, but your feedback about making it accessible is really valuable. Thanks for sharing this suggestion with the community!


Shahar M
Forum|alt.badge.img+1
  • May 11, 2026

In my work, I need to review architecture created by other teams, which are most often in LucidChart. These architectures evolve, and so it is beneficial for me (and my team) to be able to see past versions of the diagram and compare them. If we get edit permissions, that’s easy to do. However, with view only permissions, we can’t access the version history in the menu, and don’t have a way to do it. Viewing change history with read-only permissions (without being able to restore) is exactly what we need.


alison cheney
Forum|alt.badge.img+8
  • Lucid community team
  • May 12, 2026

Hi ​@Shahar M,

Thank you for providing those additional details. It makes total sense why viewing the revision history would be valuable for those with view-only access, especially for tracking progress without needing full edit permissions.

This feedback is especially useful for our product team. To anyone else reading, please upvote this post and share any additional details about your use case or what you’d like to see in this experience. This helps us greatly when prioritizing our roadmap!