This content has been marked as final. Show 10 replies
The most obvious comment is your system should not allow a user to change the settings unless they have the requisite permission. They may be able to find out how but the system permissions should recognise they do not have the necessary authority and prevent them. Are you sure an ordinary user can change their settings? If they can, then the system would seem to be flawed.
It may be the system does prevent what you suggest but a client is insisting that notwithstanding they do not want end users to see the instructions, that is a different situation. Could that help not be located in a different folder to which your developers control access by a password?
I'm technically just rephrasing the original question, but was wondering specifically if there is any way to password protect specific topics with a project?
Our software doesn't allow users to alter settings if they don't have the proper permissions to see and alter them...but if they find out where and how such settings exist, they may find a way of getting such permission by using another user's account.
I think the main thing we're wanting is to ensure that, even in a situation where a user obtains access to these settings, they wouldn't know how to manipulate them.
If you are using WebHelp, you could have your web admins configure specific folders so that only those with proper authority may see them. You would then ensure those sensitive topics were moved into those folders. There are many different approaches you might take with the help in this case. I just thought I'd toss this out for you to ponder.
If you are using compiled CHM files, you could simply create a merged setup where only if the CHM containing the sensitive information is available, the user sees it. Then distribute the sensitive CHM to only those that need it.
Tech Writer is using CHMs as per the first post.
If the system allows access in any way other than the use of passwords, then the only way in is knowing those passwords. If the SysAdmin is going to allow anyone to learn those, then the SysAdmin deserves the resulting mess they have to sort out.
In the absence of changing to WebHelp which would involve your developers changing the calls to the help at least, then putting your CHM into a folder controlled by permissions seems the only option except for one thing. The concern here is a user who finds out how to crack permissions! :-)
Multi-tasking is for women!
LOL, not according to my wife! Her definition of multitasking is:
Doing several things at once. NONE of them well at all.
She hates it with a deep and simmering purple passion typically reserved for the ilk of the Corporate Nazgul.
Originally posted by: Captiv8r
Thanks for the link!
I'm not sure what support there might be in my office for moving to a different Help format, but increased security is probably a good selling point for a different format like WebHelp.