We were developing a new web site for a customer when we had an odd request – they wanted no Notes access whatsoever to the application. They wanted to force their users to access the application through a web browser. Normally, at least some kind of administrative access would happen through Notes, but that wasn’t even wanted in this case. How did we satisfy this requirement?
The first thing we’ll point out is that experienced Notes users will find a way around anything, so it’s very difficult to make the application 100% inaccessible to Notes. But these tips make it very difficult to access the application through Notes, and will stop 95% or more of the users (novice to intermediate experience levels) from accessing the application through Notes.
Read more…
Viewed 338 times by 107 viewers
I always thought that “Deny Access” was the be-all, end-all. But apparently not. If someone is listed in both the “Full Access Administrators” list and the “Deny Access” list for the server, they will still be able to access the server. The “Full Access Administrators” trumps the “Deny Access” setting.
From the Administrator Help file, here’s information on the Full Access Administrators field:
Read more…
Viewed 295 times by 103 viewers
So how does the Notes database work?
Basically the Notes database contains a header, and then just one type of data object, called a Note. There are different types of Notes, one for ACL (Access Control Lists), one for Design elements, and one for Data notes. View indexes, built when a view is indexed, are also kept in Notes. View indexes don’t replicate. As it says in Inside Notes
One pillar of Notes/Domino design is the use of a single and simple data structure, called a note, to store all information — including design elements such as forms and views, as well as standard user documents — within a Notes database. This simple design feature leads to an incredibly powerful benefit: NOS (Notes Object Services) implements a single set of note-oriented services to create and manage all the different types of information that can be in a database.
Read more…
Viewed 340 times by 132 viewers
The following are some tips for making applications/views that perform well even with reader access controlled documents:
- Embedded view using Show Single Category. This is the winner, hands down. If your data is structured so that users can see all the documents in a category, then you can display just the contents of that category very quickly to the user. In some cases, it may make sense to let the user switch categories, in which case you have to consider whether or not he can see the contents of the other categories. But in most cases, the view would be something like My Sales and would show all the sales documents for the current user. The caveat for this kind of view is that the user interface for the Notes client is not quite as nice as the native view display. For Web browsers, it is just as good, and we have never seen a reason not to use this kind of view for Web browser applications. In fact, the performance is so good that it’s faster to open one of these with reader access controlled documents than to open a native view without reader access controlled documents!
Read more…
Viewed 306 times by 97 viewers
