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

Question

Question

Move documents, but not folders

Laserfiche Administration Security Version 8
Updated February 27, 2015
asked on October 21, 2014

We had an occurrence that we want to prevent from happening again.  A user was able to drag folder "A" into folder "B".  What we want to allow is for documents to be dragged from folder "A" to folder "B", but not the the entire folder.  In fact, in general, we want to allow documents to be moved, but not folders.

I am not certain of the access rights that would need to be used to accomplish this.  There doesn't seem to be any access right that addresses "moving" either documents or folders.  i assume this is accomplished with a combination of other access rights.

But how?

0 0

Answers

APPROVED ANSWER
replied on October 21, 2014

Chris and I offered two methods of achieving the same goal. To summarize, you need delete on the entry you're moving, or you need modify contents on the source folder that the entry resides in. You then need the necessary create right on the destination folder. This is the minimum security setup in terms of moving an entry from one location to another. As for applying this such that only documents get moved and not the actual folders that contain these documents, you'd just need to make sure that users don't have delete rights for the folders and that they don't have modify contents rights on the parent folder of these folders.

 

1 0
SELECTED ANSWER
replied on October 21, 2014

No. That's controlled by the "Delete" feature right set in the Laserfiche Administration Console.

0 0

Replies

replied on February 27, 2015

After having to browse Answers to solve this same problem and seeing many others with the same question, it seems that Admin documentation needs to be clearer with regards to Moving and entry access rights. I would like to request that this information be included in the Admin guide.

1 0
replied on October 21, 2014

You'd have to make sure folders were read only to accomplish this.

 

Ideally you should do this programmatically with workflow when the folder is created. If you were doing this with normal Laserfiche security you would want the changes to apply to "this Entry Only" unless everything at the folder level is also a folder.

 

0 0
View 5 previous replies
replied on October 21, 2014

That didn't work, unless I misunderstood.  What I tried was:

1. Set my rights to Browse and Read on folder "A", and set scope to "This entry only".

2. Checked my effective rights; Browse and Read.

3. Dragged folder "A" to another folder: Success; I was allowed to move the folder.

0 0
replied on October 21, 2014 • Show version history

Using the example of having two folders, A and B, where you want users to only be able to move documents between the folders, but not actually move folder A into B and vice versa, you can set up security in the following way:

  • On folders A and B
    • Add an ACL with the scope "This folder and subfolders" and allow Browse, Read, and Create Documents
    • Add another ACL with the scope "Documents only" and allow Browse, Read, and Delete Entry

 

1 0
replied on October 21, 2014 • Show version history

Oh jeez. 

 

I was overthinking this. Alex's example is easier. You have to keep it from inheriting rights from higher up but his example is easier since you only have to apply both of those to the folders. 

 

0 0
replied on October 21, 2014

But, doesn't "Delete Entry" allow users to actually delete documents (as opposed to just being able to move them?)

0 0
SELECTED ANSWER
replied on October 21, 2014

No. That's controlled by the "Delete" feature right set in the Laserfiche Administration Console.

0 0
replied on October 21, 2014

Yes, you don't need to give delete if you don't want them to delete. I think you need Modify contents (plus other things you want them to be able to do such as append data or rename).

 

Modify Contents is the important one. 

0 0
replied on October 21, 2014

Okay, thanks.  We will endeavor to incorporate the "Delete" feature right into our security model.

0 0
replied on October 21, 2014

Just to add some clarification regarding the way to implement this since Chris and I offered two options that both achieve the same goal:

 

You need delete on the entry you're moving, or you need modify contents on the source folder -- either suffices.

APPROVED ANSWER
replied on October 21, 2014

Chris and I offered two methods of achieving the same goal. To summarize, you need delete on the entry you're moving, or you need modify contents on the source folder that the entry resides in. You then need the necessary create right on the destination folder. This is the minimum security setup in terms of moving an entry from one location to another. As for applying this such that only documents get moved and not the actual folders that contain these documents, you'd just need to make sure that users don't have delete rights for the folders and that they don't have modify contents rights on the parent folder of these folders.

 

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

Sign in to reply to this post.

Details
Related Posts
Loading ...