Hi all - my organization has just started using the "deactivate" feature for programs and noticed you can still edit information/add objects after the program is deactivated. If the below resonates with you and your org, head over to this >idea in the idea exchange and give it a vote! "We've just started using the "deactivate" feature for programs and absolutely love it! However, one thing we noticed is that even if you deactivate a program, a user with access to that program can still add projects to it. We can't remove inherited permissions and the program manager, since that would disrupt historical reporting and prevent our users from being able to reactivate the programs themselves. Instead, we'd like to see the "deactivate" feature extended so that it "locks" the object. This would include:
Preventing users from adding other objects to the program (projects, documents, custom forms, etc)
Preventing users from editing custom form data already on the object
Only the Program Manager or a System Admin would be able to reactivate the object"
Mike McGovern Deloitte
