Staff As Entities/Switch User

V5 Question
1

Hi,

One of the main differences i’ve encountered with Sambapos vs the most popular EPOS software used in the hospitality sector is the user switching capabilities.

With the competitors software when a user touches their fob or swipes their card and completes their transaction the software stays on the POS screen and does not allow further transactions until a new user touches or swipes. Is there any way to do this in Sambapos, even by using a master pin and then users as entities instead?

Failing this is there a way of having a rule so when a RFID fob is scanned the current user is logged out and the new user logged straight back in? At present i’m using the hold ticket tutorial and when another user fobs during an open order Sambapos logs out and the RFID fob has to be scanned again. I’ve tried creating a Number Pad Value rule triggering Log Out and Log In actions and have tried putting {:NUMBERPAD} in the constraints for both but it still requires the switching user to rescan the fob at the login prompt.

Many Thanks

2

A login user action was added since switch user discussions so should be possible now.

3

Thanks for your reply JTR. How would I pass the numberpad value as a constraint so it then uses that to login? I’ve tried {:NUMBERPAD} but it just logs out and then sits on the pin screen.

4

The action has name.and pin fields so you could either logout for any swipe and let the action check pin or use a script to check pin before logout so only good pin will do the logout.
There was a topic recently for seccond pin which used this and will helpm

5

I adapted JTRs setup using the login action, pretty sure I just used a program setting to store the login pin (rfid) etc

So on an open ticket swipe your fob closes the current ticket against the current logged in, stores the rfid as a program setting and logs samba out. Then usin the login rule it uses the stored program setting rfid from logging out and uses that to log in the user

Pretty sure I had to use an auto command with delay for the login as it couldn’t all be processed at once and without it the login failed

I’ll show you my setup at some point today, adapted from JTRs

6

Thanks both for your help, i’l check back later :slight_smile:

7

That makes sence, have had to delay several rules in the past when working with logout to ensure no issues like the one where you get * for user.