Having the ability to delete an employee is huge. Here is one reason:

Let’s say that the owner wants to change their duties to be less involved and they want to "trade" positions with another person who is/was an employee, (their state does not matter in this instance). Since that employee record is never deleted, there is NO way to modify the owner email field with the other employee. (an error occurs stating: “A record with that email already exists”).

The owner email cannot be modified to an email of a past or present employee.

The Owner name cannot be changed.

This causes issues in the appointments module as well. In the appointments module, oddly, if you delete an employee, (which there you can) ALL client history is also deleted that was associated with that employee account.

This seems counter intuitive. Why would square ever delete client history even if it was tied to an employee? The client is and the history should be tied to the BUSINESS first, and the employee second. Disk space is cheap. NEVER delete history.

So, in the square main module, you can never delete an employee causing problems. In the appointments module, you can delete an employee and loose ALL the client history tied to that deleted employee.

Please look into the consistently issues and walk through the processes to see where the process gaps are. These two are obvious.

The best possible solution is to allow us to delete employees and have Square upgrade their history tables. Practically everything should be written to history. There is no good reason to ever delete history in applications like square or its modules.

Here is a possible solution:

1. Allow employees to be deleted, completely.
2. Write the employee data to a history table, just make a copy of the employee table and call it employee_history
3. Allow history to be filtered on certain tables: Past employees, Past appointments, Past food items, Past coupons, etc...
4. Allow the history to be exported to excel (already able) but with more details, (or all fields)

If there is some reason that you never delete an employee, please share it. But why "never delete an employee" but you do delete other data tied to an employee (again think appointments module).

I agree with these questions... I have mobile staff that can't remember how to login to square. I need to resend them the invitation. and thus the steps for them to take payments on my behalf. Can't believe something so simple ends up so difficult.

HELP!