Lotus Domino time sheet database cannot view documents

HCL Domino Domino Forum
1

The database we are using allows users to create and submit time sheets and allow managers to approve time sheets. Different users have different access to these documents and may not see them in the views.

PROBLEM:

The overall problem is that no one is able to access the time sheets that were created before they were given access to those time sheets. That means if we were to hire a new manager on day x, this manager would only be able to see the appropriate time sheets starting from day x. No time sheets created before day x is available to him even if he has the appropriate access.

ANALYSIS:

I’m not sure where the problem lies. I have noticed a “$Readers” field in the time sheet document form that contains a list of names. But that doesn’t seem to be it, because I remove my own access and confirmed that I’m not in the readers list but I’m still able to view that document. After much searching, I still wasn’t able to find where the db determines who sees what in a particular ‘view’. If I can find the location of the logic that determines what documents are shown to a user in the view, I can start to work with that.

DESIRED SOLUTION:

Find where the database determines who can view a document in a ‘view’.

Find a superuser access that can view all documents.

This database was written by someone a long time ago, there isn’t much documentation on how to use it. I’m not very familiar with Lotus Script or these databases. So, if anyone has an idea of how this works, I would greatly appreciate it. Thanks!

2

Subject: more readers fields?

There can be more than one field with Reader access. When looking at the document properties, you can click on each field on the left, and on the right it displays not only the content but the type. Look for a type=authors or readers on a field other than the $Readers one.

As far as making sure a new person gets access to the old documents…you will need to write an agent to replace one name with another, and then run it against existing documents. If you are talking about members of management having access, you should use Groups in the readers fields, so that when you change out group members the new members have access.

3

Subject: Also, reader name security only work on server based databases.

Another thing to keep in mind when troubleshooting readers security is that it only works when you open the data on a server or use the “Enforce consistent ACL”.

Generally, if you have a local copy, it will not kick in.

-Kyle Huang