Yes, please!

So, thought: very important all these conditions are met, BUT - if
a) you're not using archived accounts to track historic data (i.e. you don't need to know than that the old program manager filled out a report instead of the new one)
b) there's nothing assigned to the account, and
c) you really want to get rid of the account,

1. Make a dummy account in your own organization (e.g. we already have one called "Test Person" so we can screenshot and make instructions for live processes without cloning everything over to our sandbox).

2. Transfer the account that you want to delete into your own organization.

3. Merge the two accounts, keeping the dummy account as the information that stays.

I have to agree with both the organization and user deletion. If an organization creates an account and never uses it, we still cannot delete it. Why do we have the delete button then?

Adding a comment to my original idea of Deleting Users. We keep all of our requests as "UNASSIGNED" - or - if absolutely necessary - only assigned to the Organization's Primary Contact. So it would be great to be able to delete users that have absolutely no requests assigned to them.

WARNING - this is discouraged by Foundant - but I will usually edit and replace the name and contact info of an old contact with a new. However, this new name will now be attached to old applications the previous person submitted - which is not a big deal for us but can be a headache for others. I think this is one of the reasons that they archive and not delete - to keep the history correct.

It would also be helpful to be able to delete organizations that set up accounts erroneously and have no application history associated with the account.