Give your whole team their own login — with roles and permissions

Most apps begin as a tool for one person — you. Then they grow up. The salon app you built to keep your own bookings straight now needs to let three other stylists each see their own day. The shop app you made for the counter needs a cashier who can ring up sales but can’t quietly change the prices. The tutoring center needs every teacher to manage their own students, and no one else’s.

That moment — when an app stops being yours and becomes your team’s — is where most build-it-yourself tools quietly fall apart. Suddenly you need logins. Passwords. Who can see what. Who’s allowed to change what. It’s a whole second app hiding inside the first one, and it’s the part that’s easiest to get dangerously wrong — the kind of wrong where a part-time helper can read every customer’s details, or wipe a day of orders by accident.

whacka builds that part for you. Describe a team, and your app gets a real staff login system — accounts, roles, and permissions that hold where it counts. You don’t design a login screen. You don’t write a single rule about who can do what. You just say who’s on your team and what each person should be able to do.

Everyone gets their own login

You — the owner — are already signed in as yourself, and you’re automatically the top admin. There’s no setup step, no “make me the admin” to remember. From there, you bring your team in whichever way matches how you actually work:

• Send an invite link. Pick someone’s username and role, send them the link, and all they do is set a password. Best for staff you can reach with a message.
• Set their login on the spot. Type a username and a password — or let whacka generate a temporary one — and hand it over in person. Best for the cashier standing right at the counter.
• Bring your whole roster at once. Already have your staff in a spreadsheet? Upload it and every account is created in one pass, each with its own password. Best for opening day, or moving a team over from wherever they are now.

Your staff don’t need a whacka account of their own, an email signup, or yet another password to keep track of across the internet. They sign in with just a username, on a screen that already looks like your app — and that login belongs to your app alone. The “ahmed” who signs into your shop has nothing to do with any other app, anywhere.

Roles decide who sees and changes what

A team is nothing without roles, and in whacka a role isn’t just a label next to someone’s name. When you describe the roles your work has — manager, cashier, server, receptionist, technician — each one decides what that person can see and change:

• A manager sees everything and can run the team — add people, set roles, reset a forgotten password.
• A cashier rings up their own sales and sees their own drawer, not everyone else’s takings.
• A server sees their own tables; a technician sees only the jobs assigned to them; a receptionist books appointments while each doctor sees only their own patients.

When your app has clear roles like these, you assign them from a simple list — you pick the role, you don’t retype it — so what you choose always matches what the app actually enforces.

Passwords get the same care. They never sit inside your app’s own data for someone to stumble onto — they’re stored hashed and apart, the way passwords are supposed to be, and repeated wrong guesses get locked out automatically.

A team front desk you didn’t have to build

Everything above lives in one place: a Manage team screen whacka builds into your app for you and your managers. Open it and you see everyone at a glance — names, roles, who’s active, who signed in last — and you can change someone’s role, reset a password, or switch a person off and back on.

By default your team is closed: only you and your managers create logins, which is exactly what you want for a shop or a clinic. But when you’d rather let people ask to join — a class where students request access, say — you can turn on self sign-up with a single switch. Then newcomers tap “request to join,” land in a pending list with no access at all, and get in only once you approve them. One tap approves; one tap clears a whole pile of requests if you’re ever flooded.

And when someone leaves, you switch them off — their login stops working and their access ends that instant, not whenever some session quietly expires.

Made for the way your business actually runs

None of this assumes a tech company. It’s built for the businesses that actually need it:

• A barbershop or salon owner giving each stylist their own login to manage their own bookings.
• A shop or mini-market with an owner, a manager who can fix anyone’s mistakes, and cashiers who each see only their own sales.
• A restaurant where managers see every order and servers see their own tables.
• A clinic with a receptionist at the front desk and doctors who each see only their own patients.
• A tutoring center or small school where the owner sets up a login for every teacher, and each teacher manages their own students.
• A repair or field-service business where a manager hands out jobs and each technician sees only what’s theirs.

It works in any language your team speaks — Arabic and other right-to-left scripts included — and the words on the sign-in and team screens are yours to set, so the whole thing reads the way your staff expect.

The honest limits

A few edges, because we’d rather you hear them from us. Adding staff doesn’t cost you a per-seat fee — bring your whole team — but teams are part of the paid, more serious side of whacka, and building any app with AI still runs on your credits. The sign-in screen can wear your colors and your words, but it keeps a small “powered by whacka” mark; it isn’t a blank-slate white label. And these are logins for your app’s team — a staff roster you control — not a public “sign in with your account everywhere” system.

That’s the shift. Your app no longer has to be a one-person tool that breaks the moment a second person needs in. It can be the thing your whole shop, clinic, or classroom runs on — each person with their own way in, seeing exactly what they should, and nothing they shouldn’t.

Open your app — or start a new one — and say it in a sentence: “My staff each log in; managers see everything, cashiers see only their own sales.” whacka builds the team.