A good way to Restrict access to Db via Notes Client

I have an application certain Admin users will maintain documents and they are the only ones who should be able to access the database via the Notes Client. The rest of the user have access to the documents via a web browser and they need Author access to create special requests regarding the database. We have a PostOpen event in the Database Script that checks to see if its the Notes Client and if the person has a certain Role before allowing access. This works good except when there is a doclink to a document in the database. It doesn’t recognize the person as having the Role and if the doclink is being launched from the Mail database, it closes the Mail database instead of the database that has the DB Script PostOpen event.

Code in the PostOpen Db Script:

@If(@ClientType = “Notes” & @IsNotMember(“[DocAdmin]”;@UserRoles); @Do(@Prompt([Ok];“Open Application from Web Only”; “This database must be opened using a Web Browser.”); @Command([FileCloseWindow])); “”)

If anyone has a better way to do this, I’d appreciate you sharing it.

Subject: A good way to Restrict access to Db via Notes Client

If you are stuck using one server, the new R6 function ‘@UpdateFormulaContext’ may help you.

hth

Tony

Subject: A good way to Restrict access to Db via Notes Client

The general response is likely to be along the lines of “put the database on the server to which ordinary users do not have client access”. That’s how we do it here – replicas of such a database would exist on our web server(s), which are not client-accessible except by our admins, and our admin server (again, no ordinary client access, but no web access either).