Is it possible to lock down object deactivation? I would prefer that users only deactivate tasks within their parents (either the schedule or parent workflow) to maintain consistency and visibility. Several times recently, more novice users have deactivated jobs or workflows by unchecking the "Active" box on the Header tab. Sometimes accidentally, sometimes because they were asked to make a temporary change, but then didn't undo the change. Then when the object is scheduled to run, it doesn't because of the "inactive due to definition". Confusion ensues. Adequate communication is great and all, but is there any way I can just clamp down that box so only one or two people have the right to deactivate objects?