Created By field and Modified By field and People Picker field values are hidden to other Users

Question

Hi,
We have a strange permission issue in one of the MOSS-2007 server farm. The users are not able to see each other name in "created by" and "modified by" column value in lists and libraries. For example if "User A" create an item in a list then if "User B" opens that item then he cannot see "created by" and "modified by" column value and vice-versa. But they can see their name in "created by" and "modified by" column but not others. Both the users has contribute access to that list, so both can edit each other data but cannot see each other name.
This become a bigger issue, if any of tje list has people picker column, then thay cannot see that column value(if that column value does not his/her own name). This means this column value will be always empty for "user A" when that peopel picker value is anything other than "User A". This happens for all the lists and libraries. 
Even "User A" and "User B" are owner of that site, it behaves the same. But site collection administrator can see  "created by" and "modified by" for all items for all the users.
It seems very strange for me. any help on this will be appreciated.
Thanks in advance,
Sanban

Answer 1

Hi,
You can try to create a new standard view, then select “created by” and “modified by” column under columns, next apply this view, finally check the effect.
Did you customize the permissions of the list or document library? Did you customize the permission of the item? For example, break the permission inheritance form its parents. If so, try to inherit permission from its parents, after that create a new standard view according to the steps above, then check the effect.
By default, permissions on lists, libraries, folders, items, and documents are inherited from the parent site. However, you can break this inheritance for any securable object at a lower level in the hierarchy by editing the permissions on that securable object (that is, creating a unique permission assignment) . For example, you can edit the permissions for a document library, which breaks the permissions inheritance from the site.
You can also try to create a new document library, then create a new document with user A, after that log into with user B, check the effect.
For more information about  SharePoint : page level permissions, please refer to the following article:
SharePoint : page level permissions
http://blogs.msdn.com/brettrobinson/archive/2009/04/24/sharepoint-page-level-permissions.aspx
For more information about control access to sites, please look into the following articles:
About controlling access to sites and site content
http://office.microsoft.com/en-us/sharepointtechnology/HA101001441033.aspx
Permission levels and permissions
http://office.microsoft.com/en-us/sharepointtechnology/HA101001491033.aspx
For more information about how to create a view, please refer to the following article:
Create or change a view
http://office.microsoft.com/en-us/help/HA100215771033.aspx
Hope this helps.
Rock Wang
Rock Wang– MSFT