Dear,
A Document Author want to assign user A and user B to see his document X in view when he create document X by form, meanwhile,others can’t find docuemnt X in view. next time,this document author would like to assign user C and user B to see his document Y when he create document Y by the same form but others can’t find document Y in view.
Who knows how to accomplish this? anybody ever coded this?
thanks for your help
Landy
Subject: Document authorized access
This can be easily code in notes by using Readers and Authors fields. Look in designer help on how to use them.
Subject: RE: Document authorized access
Tom,I meant others can’t find Document in view, I didn’t mean wether user can access this Document or not.
it’s obvious difference referring to reader and author field method.
Did anyone try to use view selection method to accomplish this ? any direction to consider?
Subject: RE: Document authorized access
Tom just gave you the answer. Given the information you’ve posted the easiest method you’ll have is to use Readers and Authors fields.
Readers fields control who can see a document.
Authors fields control who can see and edit a document for users with Author level access.
The help db goes into detail on using these fields and there are quite a few posts in this and the R4/5 forums about using both types of fields.
You can’t (easily) build true dynamic view selections. The view index is controlled by the server not the user unless you’re using a Private view.
Subject: RE: Document authorized access
There is also a great article in the forum FAQ called “The Compleat Authors and Readers Field Troubleshooter” that makes things a little clearer than the help DB does:
http://www-10.lotus.com/ldd/46dom.nsf/0/e0359d10a2307d1885256c61000707b7
Subject: RE: Document authorized access
So you don’t want users to be prohibited from seeing the document in other views or from retrieving data from it via lookups, etc? You just want to let one user control which other users can see which documents in one view? Then your question now becomes a variation on that ages-old chestnut: How do I write a user-sensitive view selection formula? In this case, I’d say that a desktop-private-on-first-use view is the best solution, with the selection formula depending on whether @ismember(@username; FieldThatListsAuthorizedViewersByName). If no document will ever be visible to everyone, you could also get away with a shared view categorized by that field, and display that view embedded in a form using a single category formula or else use @setviewinfo – but that’s a pretty big “if.”