I like a nice clean user interface, unencumbered by extraneous options. I also like to restrict access to modules and fieldsets that our institution isn’t currently using, as a way of preventing “rogue” data entry. The Insurance Policy module is one such example, with our blanket policy there is no need for tracking this in the database. And even if we did, there would only be a handful of users that would need access to this information. So I’m going to modify my security profiles to restrict access to this module.

Open Database Configuration, and go to Manage » Security Groups. Select a security group, and then unset all the settings under the “Insurance Policies” node. (Remember that right-clicking the node will give you the option to set the subhierarchy security).

Congratulations, you have just disabled a module in TMS! If you login to the system using the security group you just modified the umbrella icon will be disabled. However, you will still find vestiges of the module in the system. Removing rights to the module alone will prevent the users from being able to access said module, but does not address the navigation options within other modules. For instance, you will find “Insurance Policies” options under Hierarchy View, and the Related tab and menu in Objects.

These options have no validity, since the user cannot see the Insurance Policy record, even if one existed. These should be removed to provide the users with a cleaner interface.

Going back into the Security Group Maintenance, open the same security group, and find the “Insurance Policies Object Xrefs” subnode under the “Objects” node. Unset all the settings here, and in the subhierarchy as well.

Now those options under Hierarchy View, and the Related tab and menu in Objects will no longer be available to the user.

Insurance Policy records could also have Constituents linked to them, so it is important to update the security for “Policy-Related Constituents,” which is a subnode to “Constituent Xref Details,” which is itself a subnode of “Constituent Alternate Names” under, not surprisingly, the “Constituents” node.

There is also an “Insurance Policy” subnode under the “Media Xrefs” subnode of the “Media” node. Once security is updated here, the user should not see any references to the Insurance Policy module in the interface.

The Insurance Policy is fairly easy to excise from the interface, because it is only linked to three other modules. Nevertheless, this should give you an idea about how to address other modules that you might not be using, or do not wish to extend rights to your entire user-base. Good luck!