Team and access
Staff management where every action has a name on it
Roles enforced in the database, invites and revocations tied to real emails, and an activity log that answers 'who did this' with a record · trust, verified.
- shield_person
Roles the database enforces
Owner and staff are not labels on buttons · they are rules enforced inside the database itself, so what staff cannot do stays impossible even if a screen misbehaves.
- mail
Invite by email, at a level you choose
New staff get an invite to their own email at the access level you pick · no shared passwords taped under the counter, no accounts that outlive the person.
- person_off
Revoke without erasing history
When someone leaves, revoke their access in one action · their account closes but everything they did stays on record, attributed to them.
- history
An activity log with names on it
Sessions started, invoices voided, prices changed · the log says who did what and when, which turns 'someone must have' into a lookup.
- gpp_good
The last owner is protected
The one account that can do everything cannot be removed by accident · a small guard against the biggest possible mistake.
- lock
Member data behind role walls
Contact details are never world-readable, and row-level security in the database keeps each role seeing exactly what its job needs.
The counter runs on trust · the software should verify it
A gaming café hands its counter, its drawer and its member list to staff every shift. Most of the time trust is enough; software exists for the times it is questioned. Role separation means the till operator cannot quietly change the rate card, the activity log means every void and every price edit carries a name and a time, and the difference is felt most on the day something looks wrong · when the answer is a record instead of an argument.
Access that starts and ends with employment
The lifecycle is built in: invite a new hire by email at the level their job needs, and revoke the account the day they leave · without deleting the history they created while employed. No shared logins means no ex-employee who still knows the password, and no mystery about which of three people sharing 'admin' did the thing.
What this page does not promise
This is access and accountability, not HR: there are no shift rosters, attendance clocks or payroll runs here. Staff wages log cleanly as categorised expenses so the P&L stays honest · but rota-making stays wherever you make rotas today.
Frequently asked questions
What staff roles does Respawna have?expand_more
Owner and staff, enforced in the database itself rather than just hidden in the interface · staff run the floor and the till, owners additionally control pricing, settings, team membership and the money views.
How do I add and remove staff?expand_more
Invite by email at the access level you choose; the person gets their own account. When they leave, revoke in one action · access ends, but everything they did stays on record under their name.
Can I see who voided an invoice or changed a price?expand_more
Yes. The activity log records who did what and when · voids, price changes, session actions · so operational questions resolve by lookup rather than by suspicion.
Does it handle shifts and payroll?expand_more
No · deliberately. It manages access and accountability. Wages log as categorised expenses so the month's P&L is truthful, but rosters and payroll belong to tools built for them.
What does it cost?expand_more
Plans start at ₹299 a month, and every plan begins with a 14-day free trial, no card. When the trial ends you either pay to carry on or stop · nothing renews by itself, because we hold no card. Current plans and prices are on the pricing page.