You are viewing limited content. For full access, please sign in.

Question

Question

Laserfiche versions - Access denied when reverting version

asked on August 30, 2019 Show version history

Hi,

We have users set up with a full license with all user access rights, feature rights and privileges set up. 

These users go into a document with different versions and have a need to revert to older versions, when they target one and click "revert" in the web client it just comes up with Access Denied 9013.

Outside of rights I can't think what would be causing access denied, I have checked volume security and all that looks fine for the same users.

Am I missing some feature it requires to allow users to revert versions?

0 0

Replies

replied on August 30, 2019

Something to note/check is that the user needs the rights to make any changes that will occur as a result of reverting the document. For example, if a field is changed/removed, they need to be able to change/remove it, or if a page or electronic file was added/deleted, then they need rights to make that kind of change as well.

One way you could narrow it down is to create a test document with minimal fields/content to see if they can revert that one. For example, enable versioning, then only change one field that everyone can edit to see if it allows them to revert. Start with things that differ in the old versions of your problem documents.

0 0
replied on September 3, 2019

The users can perform every action manually in the document such as generating pages or changing fields etc. It looks completely narrowed down to reverting. 

 

We did add these old versions in via SDK as part of a migration so not sure if that's somehow locked away the rights to revert back?

0 0
replied on September 3, 2019

When you say they can perform every action manually, does that mean they have rights to edit/add/remove all templates and fields in the repository?

Having access rights to change document metadata does not necessarily mean they have access to change the value of every available field.

There's not really any specific rights for reverting; it is pretty much just a matter of having the rights to make whatever changes that involves.

As I said, I would compare the two versions to narrow things down as it is almost certainly related to one of the differences.

0 0
replied on December 3, 2020

I have a user experiencing the same issue.

They are an LF Admin with all features and privileges.

Full Perms to the folder/document in question

They have allow rights to the template/fields associated with the document

Appreciate the feedback,

Jeff Curtis

0 0
replied on December 3, 2020

I'd say the first step is still to compare the differences between the two documents. Every time I've had a user unable to revert it was because one of the changes associated with reverting was outside of their allowed actions.

For example, if reverting changes the fields, they need the ability to add/remove/edit any affected fields. If reverting changes the pages, they'll need permissions to delete/create pages too.

It just depends on what changes are involved so comparing the versions is the best way to narrow it down and pinpoint the source of the problem.

0 0
replied on December 3, 2020

Thanks Jason,

I will have the customer check the two version side by side.

Jeff Curtis

0 0
replied on December 9, 2020

Hey Jason,

This might sound odd, but the revert they want to do is, taking the current version, which is an Excel file and revert to an earlier version, which was a PDF...not sure that is possible and how the doc morphed in this manner.

Appreciate the feedback, if you have any.

Jeff Curtis

0 0
replied on December 9, 2020

I believe making changes to the electronic file falls under the "Modify Contents" access right for the entry. So, if the only difference between the two versions is that it changed from a PDF to an Excel file, then the user would basically need the same rights as they would if they were going to delete the Excel file and add the PDF.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.