I need to add the role of creating public or shared folders to a user with depositor access. By standard that option is shaded and not available so I figured I can just create a role to do it. Anyone have any idea how to go about doing this?
Subject: I am not aware that this is possible
Hi, Victor. I am not aware of any way of giving users with depositor access the ability to Create shared folders and views. I don’t understand why you would want someone to be able to create a shared folder or view but not allow them to read documents in the database. To effectively design a view or folder, it’s really important to be able to be able to see documents in that view or folder. My suggestion is to give this user at least reader access in the acl.
Subject: I have an agent
I have an agent that copies documents over to a new database where the user running the agent has limited access. I don’t want the user to view the database but I want the agent the user is running to be able to move that document over the a different folder. Not sure if that is possible using a created role
Subject: Have a separate agent?
If I’m understanding you correctly, you should use a pitcher-catcher type of coding pattern, having your existing code create the document and triggering a second, secure agent to take it from there.
1: Have your code create the document into the main database, with a field named “PutInFolder”
2: Write an agent that runs on new/modified documents that iterates NotesDatabase.UnprocessedDocuments and if it finds a PutInFolder field it creates folders and puts the documents in them as appropriate. Either way, it should call UpdateProcessedDoc on each doc it looks at or else it will watch it again the next time it’s run.
4: Change your code to call NotesAgent.RunOnServer on this new agent after putting the document in place.
This second agent will run on the server with permissions of whoever signed the agent last.
Good luck!