I'm on Laserfiche Client 9.1. I'm working with Windows Account users and trying to allow read/browse rights to 6 people on a subfolder. So in the client, I've gone to the main folder (right under by repository) and given Read/Browse rights with the scope of This Entry Only. Then I've gone to the subfolder and given Read/Browse rights with the scope of This folder, subfolders, and documents. Most of the users can go to that subfolder and see the list of documents but when they double click to open a document, they get "Access Denied 9013." To trouble shoot, I've taken one of those users and given them every right and they still cannot open it. However, a domain test user that I've used for trouble shooting is set up exactly as the other users (as far as I can tell) with Read/Browse rights and identical scope and can open the documents no problem. Ideas?
Question
Question
Getting Access Denied 9013 error
Answer
Oh, I see. So the documents open, but then you get access denied on the page content. In that case you want to check volume security. By default everyone should have access to all volume contents, but it sounds like that might have been restricted in your case. You can check volume security in the volumes node of the administration console, it also has its own effective rights section.
Replies
Hi Roger, is it possible that they are getting deny's coming in from group membership? If you go to the effective rights tab for that user in the access rights dialog does it show that they should have access to that document? Are these documents shortcuts to another location in the repository?
That's what's really baffling. There are no groups to have deny rights; the effective rights show the needed rights (the one attachment shows access rights to the admin user, who can't open it either). And they are not shortcuts. Thanks for any help.
Oh, I see. So the documents open, but then you get access denied on the page content. In that case you want to check volume security. By default everyone should have access to all volume contents, but it sounds like that might have been restricted in your case. You can check volume security in the volumes node of the administration console, it also has its own effective rights section.
Thanks for your help. That did the trick!