Hi Carl,
Thanks for the post.
I guess my response is based on what you mean when you say "documents". Are you referring to the document in OnBase (ie the metadata in the database and the files in the Disk Groups) or the files as they exist in the Disk Groups? if you are referring to the documents then I would say that you could manage the users security in OnBase so that only specific users have the permissions to alter the documents.
If you are referring to the files which exist in the Disk Groups, I would ask, what are you trying to accomplish with this? In general, files in the Disk Groups are not altered unless done outside of OnBase. Altered files (ie markups, revisions, etc) create new files in the Disk Groups stored in the latest volume. If you are looking to prevent users from altering files, you could use Distributed Disk Services (DDS) for Thick Client user in order to limit access to the Disk Groups. DDS will allow you to create a proxy for the Thick Client users in order to prevent users from having direct UNC access. Users using the Core products via the Application Server are already accounted for as they don't have direct access to the Disk Groups.
Hopes this helps.
