Guide · staff & PINs

Har staff ka apna PIN — kaun kya kar sakta hai, aap tay karo.

The EasyKOT Desktop App should know who is standing at it. Give every person their own PIN and a role that matches their job, and the Desktop App does the enforcing for you: the new cashier cannot write off cooked food alone, the waiter's phone cannot hand out discounts unseen, and the kitchen screen can never wander into the money. Set up once in the dashboard; it works offline forever after.

Start free — ₹0 todayDemo on WhatsApp
The walkthrough

Dashboard se Desktop App tak — chaar steps.

1

Create the person in your dashboard

Staff live at easykot.com, not on the Desktop App: open Staff in the owner dashboard, add the name, pick the role, and set a PIN, 4 to 12 digits, typed or generated. The list syncs down to every Desktop App and captain phone on its own. There is deliberately no 'add staff' on the Desktop App itself: hiring is an owner's desk job, not a rush-hour key.

The EasyKOT owner dashboard Staff & pay page: an owner and a captain in the roster, with Pay, Edit and Reset PIN actions and Connect phone on the captain row

Staff & pay keeps each person's role and PIN private; captains also have Connect phone.

2

Pick the role that matches the job

Owner and Manager can do everything on the Desktop App, Settings included. Cashier bills, settles and discounts, and starts a refund that a manager's or owner's PIN then approves; voids a dish the kitchen already cooked by picking a reason, and never sees Settings. Captain takes orders and fires KOTs from the phone, with money keys held behind a manager's approval. Chef is the narrowest of all: the PIN that turns a screen into the kitchen display and nothing else.

3

Sign in, lock, switch — all on the PIN pad

The Desktop App greets a staffed store with a PIN pad: 'Enter your PIN to start your shift'. It checks the PIN against the Desktop App's own synced list, entirely offline: the internet being down has never kept anyone out. Mid-shift, the header's Lock key drops back to the pad so the next person signs in as themselves; whoever rang the sale is on the sale.

The EasyKOT Desktop App's sign-in screen: the EasyKOT mark, 'Enter your PIN to start your shift', a masked PIN field and a large touch keypad

Step 3: the pad checks the PIN against the Desktop App's own list, offline.

4

Let the Desktop App ask for a manager when it should

A cashier refunding a settled bill, or a captain giving a discount on the phone, does not need to hunt anyone down or swap accounts: a manager-PIN prompt opens on the spot. The manager types their PIN, the action goes through, and their name rides the event. The person who asked stays signed in; the approval is one line on the record, not a shift change. Voiding a dish the kitchen already cooked is not on this list: it takes a reason, recorded under whoever is signed in.

3 mahine free · bina card detailsDemo on WhatsApp
The roles

Five roles, one honest comparison.

  • Owner & Manager, everything: billing, refunds, voids, discounts, Settings, the floor builder, and the dashboard. Managers are also the PIN that answers every approval prompt.
  • Cashier, the job at the Desktop App: orders, KOTs, bills, settle, discounts, and starting a refund. Cannot approve that refund alone (a manager's PIN does), voids a fired dish with a reason under their own name, cannot open Settings. This is the right role for almost everyone behind the counter.
  • Captain, the phone job: tables, orders, fire. A discount at the table asks a manager to type their PIN on the spot. See the captain app setup.
  • Chef, one capability: the kitchen board. Sign a paired screen in with a chef PIN and it is the KDS, locked: every other screen on the device leads back to the pass. See the kitchen screen setup.
  • Every approval is a record, not a favour. When a manager types their PIN over someone else's action, the event carries both names: who asked, who approved. The review month reads itself.
Staff questions

Straight answers.

Do PINs work when the internet is down?
Yes, completely. PINs are verified against the Desktop App's own local copy of the staff list, so sign-in, lock, switching and manager approvals all work in airplane mode. The only staff action that needs the internet is creating or editing people, because that happens in the dashboard.
What exactly can each role do?
Owner and Manager: everything, including Settings and layout editing. Cashier: take orders, fire, settle, discount, start a refund; the refund needs a manager's or owner's PIN, a void of an already-fired dish needs only a reason, and Settings never appears. Captain: orders and firing from the phone; discounts and cash actions ask for a manager. Chef: sees the kitchen board, full stop. A chef PIN locks its device to the kitchen screen.
Does a cashier need a manager to void a dish that was already fired?
No. The kitchen cooked it, so a fired void is written-off food, and written-off food is where leakage hides; that is why it always takes a reason from a fixed list, recorded under the cashier's own name. A cashier can also just reduce a quantity the guest returned. The record is only worth something if every person signs in with their own PIN, so never share one.
What happens if no staff have downloaded yet?
The Desktop App keeps an empty-roster store sellable with a temporary unstaffed owner session, then returns to the PIN pad as soon as any staff row arrives. A Desktop App connected with Owner sign-in stays open as the owner until someone locks it. An enrolled Captain phone stays on the PIN screen until its staff list downloads; it never creates that owner session. If the owner removes a staff member in Staff & pay, that person's phone returns to sign-in as soon as the deletion syncs.
Can someone brute-force a 4-digit PIN?
Four wrong tries are free: fat fingers happen. From the fifth, the pad enforces a growing cooldown, fifteen seconds up to a minute per try, shared across sign-in and every approval prompt on that device. There is deliberately no hard lockout: a locked Desktop App during Saturday rush is a worse failure than a slow guesser, and the cooldown makes guessing impractical anyway.
Can I record what each person is paid?
Yes, the same Staff & pay page. Set a monthly salary, a daily wage, an hourly rate or mark someone as contract; give an advance mid-month and, on payday, the salary is prefilled net of it so the advance is taken back in the same entry. Monthly pay is spread across the days it covers in the P&L, daily-wage staff count what you actually paid them, and nothing about pay ever reaches a Desktop App: the Desktop App only ever sees names, roles and PINs.
Staff PIN bhool gaya toh?
An owner or manager resets the PIN in the dashboard's Staff page and it syncs down within moments. Locked out of the Desktop App right now? The pad's 'Can't sign in?' door accepts any owner or manager PIN, and an owner can always unlock with their easykot.com email and password while the Desktop App is online.
3 months free · ₹0 today · no card

3 mahine try kare, phir plan chune.

Restaurant ka kaam hum samajhte hain, kyunki shuruaat bhi wahin se hui. 3 mahine free try kare, bina card details. Hamari kahani padhe.