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

Question

Question

Permissions to Prevent Moving a Folder

Laserfiche
Updated November 8, 2024
asked on May 21, 2021

We have this recurring problem where staff members move folders into other folders.

As near as I can tell, they are moving their mouse when the double-click, so it ends up being a click-drag-click move instead of a double-click move.

The problem is, multiple times, this has impacted some of the most important parts of our repository - things that have a lot of automation and workflows impacting them - so it causes tons of grief cleaning them up.

I've been trying to set-up permissions to prevent this from happening, but I just can't seem to make it work.

I've got permissions on the folder set for the Everyone group (which all staff have) to deny "Modify Contents" and "Rename" for this entry and its immediate children.  Yet they are still able to drag this whole folder into another folder.

Has anyone encountered a similar issue and know how to prevent this from occurring?

Thank you.

1 0

Answer

SELECTED ANSWER
replied on May 21, 2021

I figured something out.

I'm thinking that because it is "Modify Contents" and not just "Modify Entry" it doesn't impact the ability to move the folder itself.  So I need to go up one level and set permissions to that folder denying the ability to "Modify Contents" - then none of the folders at this level can be moved.  It's working in my testing.

I really did want to limit it to just this folder, but I can live with it limiting everything else at the same level - it's high-enough in the stucture that staff shouldn't be messing with the folders anyway.

0 0
replied on May 27, 2021

I tried this to isolate a single folder, maybe it's redundant, maybe I have some odd permissions set that differ from yours. Everyone group has all folder, sub, docs set with full at the root. The first example is the folder 1 (this entry only) higher than the isolated folder. The second 2 examples at the folder being isolated. I also wasn't satisfied with with all of the folders being locked, I wanted just the one. I'm not sure how this worked, but it does for me. Is there something that would make this better and I'm just missing it? Thank you for your contributions and consideration.

1.PNG
2.PNG
3.PNG
1.PNG (21.77 KB)
Download
2.PNG (27.58 KB)
Download
3.PNG (27.88 KB)
Download
0 0

Replies

replied on May 21, 2021
0 0
View 1 previous reply
replied on May 21, 2021 • Show version history

That's basically it - but I can't figure out why it isn't working for me - which is why I did a new post instead.

The only real difference I see is that I have allowed the ability to annotate and do metadata, while denying the ability to modify contents and rename.

I would assume that the ability to move a folder is related to "Modify Contents", which I've denied - but that doesn't seem to be the case.

0 0
replied on May 21, 2021

I tried with a different folder (one that wouldn't cause issues to test with), denying all of the Modify rights for the Everyone group, and it still let me drag the folder into another folder, despite not having any modify permissions.

0 0
replied on July 11, 2023

I suppose you have yet to figure out a solid solution to this?  I am having the same issue.

0 0
replied on November 8, 2024

@Vikki

 

This might be what you're looking for: VERS Classification Levels

Folders of a higher classification level cannot be moved to a folder of a lower classification level. 

0 0
replied on November 8, 2024

I'm not an expert, but instead of permissions, it may be helpful to set up VERS classification levels in your repository. I sounds like this does what you're hoping to achieve. 

 

https://go.laserfiche.com/support/webhelp/Laserfiche/9.0/en-US/AdminGuide/LFAdmin.htm#VERS_Classification_Levels.htm

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

Sign in to reply to this post.

Details
Attachments
Related Posts
Loading ...