Deleting Resources

JPAC places tight restrictions on the deletion of data.

In many cases JPAC only allows data to be deleted by a user with an Admin account.  

Many resources are linked to other resources, and deleting one thing can have a cascading effect that causes related resources to also be deleted. For example, deleting a Person would also delete all the Records that Person has. In the same way deleting a Requirement would also delete all the Records and policy requirements linked to it.

The other important aspect of deleting resources in JPAC is that it is permanent - there is no undelete. 

For these reasons, deleting is usually restricted to being performed by an admin, as it is expected that admins will have the appropriate understanding about the consequences of deleting resources.

The recommended practice is to not delete resources, but rather to make them Inactive. This behaves similar a "soft delete" allowing the resource to be restored by setting it to Active again.