A common scenario that is encountered is accessing other users' checks, and applying payments to them.
For some businesses, you would want the payment to record under the user who accepted the payment, for others you would not. Some users should not have access to other users' checks at all.
User can access other users checks
In the scenario where you would want a user to be able to access another user's checks, that user would need the "OtherChecks" permission associated with their POS role. This would grant a user the ability to view another users check, and apply payments, discounts, perform any other functions. If the new user who accessed the check took a payment it would record under the new user, and not the check owner.
User can access other users checks and take payments on their behalf
In the situation above, the user accepting the payment is the one that will show the reporting data for that payment. In order to have the payment record under the original check owner, the new user would need the "ManagerImpersonation" permission associated with their POS role. This would allow them to access other users checks, and take payments on their behalf. (i.e. an employee went to the restroom and their table needed to check out)
Transferring checks to another user
If an employee was going to leave for the day, or otherwise be unable to continue working, the easiest thing to do would be to transfer that check to a different user. This would require that the user have the "TransferTab" permission. If the user does not have this permission, a manager, or other equivalent user could transfer the check for them. Once a check is transferred to a different user, all future actions would record under the new check owner.
Article is closed for comments.