Team positions
Add the hotel's people by invitation, with their position, and deactivate them without erasing what they did.
What it solves
A hotel is not run by one person. Until now the only user was the owner — whoever signed up — so the whole positions policy went unused: the receptionist logged in with the manager's account and every check-in was recorded under someone who was not there.
You notice it in things like these
- The whole shift shares one password and nobody knows who did what.
- The system password lives forever in a WhatsApp chat.
- Someone leaves the hotel and their access stays alive because removing it would erase their history.
How it works
You invite, you do not create with a password
The person gets an invitation and sets their own password. Creating one with a temporary password would end with that password sent over WhatsApp and living forever in a chat.
The invitation expires on its own
It is good for a week, and expiry is worked out from the date: nobody has to walk a list marking invitations as stale. Resending it changes the link, so the previous one stops working right then.
Nobody is left without an administrator
You cannot deactivate yourself, nor the last active administrator. And deactivating does not delete: check-ins and payments point at that person, and a hotel has to be able to say who took that money.
Inviting is for whoever runs the place
Only whoever runs the hotel manages the team. A receptionist who could invite would create themselves an administrator account, and the whole positions policy would stop meaning anything.
Where it lives in the panel
- Hotel
- Team positions
What it needs first
Nothing: it works from day one, with nothing to set up first.
Carry on here
Shall we walk through it with your hotel on screen?
Half an hour, your rooms and your rates, and whatever questions you have. No commitment and no card.