+3I've noticed that any time we view a document it creates a new version even though there are no changes. This makes it difficult to identify the current version of the document.
How can we manage read only access even though we have write permissions so we can maintain a consistent awareness of the current document state?
Best answer by alison cheney
Hi
Thank you for responding in this thread!
I understand your concerns and wanted to provide a few suggestions here:
Please let me know if you have any additional questions! If you feel the suggestions above don’t currently support your workflow, we appreciate your idea on this post and we’d love it if you could add any additional details or create a new idea and be sure to include details about your use case or what you’d like to see in this experience. This will also allow other users with similar requests to discover and upvote it, then add details of their own.
Finally, for more information on how Lucid manages feedback via this community, take a look at this post:
+7Hi Robert
Thanks for posting in the community! Our Revision History feature is designed to store a new version each time the document is saved. You can navigate these versions more easily by naming each version you would like to access in the future. You can name specific versions on the Revision History by clicking on the three dots to the right of each tile and then typing in a name. You can then choose to see only versions you have named by toggling "Show named versions only".
If anyone else has questions about Revision History you can find an overview in this Help Center article.
Hope this helps!
+1Apologies for resurrecting an old thread, but I feel like the solution proposed might not fully address the concern.
A contributor to the document may forget to create a new version after changes are made, and those changes end up getting lost in the pretty long revision history that ends up being created when files are saved every few minutes.
It would be great if the document isn’t saved unless you actually change something in it.
+8Hi
Thank you for responding in this thread!
I understand your concerns and wanted to provide a few suggestions here:
Please let me know if you have any additional questions! If you feel the suggestions above don’t currently support your workflow, we appreciate your idea on this post and we’d love it if you could add any additional details or create a new idea and be sure to include details about your use case or what you’d like to see in this experience. This will also allow other users with similar requests to discover and upvote it, then add details of their own.
Finally, for more information on how Lucid manages feedback via this community, take a look at this post:
A Lucid or airfocus account is required to interact with the Community, and your participation is subject to the Supplemental Lucid Community Terms. You may not participate in the Community if you are under 18. You will be redirected to the Lucid or airfocus app to log in.
A Lucid or airfocus account is required to interact with the Community, and your participation is subject to the Supplemental Lucid Community Terms. You may not participate in the Community if you are under 18. You will be redirected to the Lucid or airfocus app to log in.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Your privacy choices
