Controlling Status Changes

Within the world of Microsoft Dynamics CRM certain entities have "close" and/or status/state functionality. On activities this close pushes the activity into history and on Opportunity this close function completes or closes an opportunity as Won or Lost. On Accounts the status functionality Activates or Deactivates .. so there are a number of great uses to this design. 

You can even do more with these statuses applying the same consistent pattern to many other standard and/or custom entities.

The challenge becomes how to setup the CRM security model around who can change an entity from active to inactive (aka giving a user access to READ/WRITE/UPDATE but perhaps limiting their access to changing statuses) Some functionality is supported, but not all. Yet