How to add a login to your business app

A login lets each person see their own data: a parent sees their child's fees, a staff member sees today's jobs, the owner sees everything. In AppCub, sign-in works with email and password once you connect your own Supabase database from the chat.

Updated 2026-11-09

Do you need a login?

If only you use the app on your own phone, you probably do not. The data stays on that phone and the phone's own screen lock protects it.

You need a login when more than one person uses the app on their own phones and they should not all see the same things: staff who should not see the day's cash total, parents who should see only their own child, customers who see only their own orders or bookings. A login is also what lets a customer come back on a new phone and find their history.

Why a login needs a database

A login checks who someone is and then shows them their data. That data has to live somewhere every phone can reach, not on one phone. In AppCub, you connect your own Supabase database from the chat; your app's accounts and data are kept there, in your account, not in AppCub's. Supabase has a free plan that is enough for many small businesses to start.

Plan who sees what

Owner: everything, plus settings, prices and staff
Staff: their own jobs, bookings or classes, without totals or other staff's data if you prefer
Customers or parents: their own orders, bookings, fees, marks or receipts
Write it as a small table before you ask AppCub: who, which screens, can edit or only view

Good practice

Ask customers to sign up with an email they can open, so a forgotten password can be reset
Give each staff member their own account; never share one login among staff
When a staff member leaves, remove their account the same day
Ask only for data you need; a parent's phone number and child's name is usually enough
For clinics and counsellors, keep patient data private to staff, and follow your professional body's rules on patient data

What to expect

Sign-in in an AppCub app is with email and password. Phone OTP sign-in and sign-in with other accounts are not promised, so plan around email. The first time a parent or customer uses the app, they create an account or use one you made for them; after that they stay signed in on that phone.

With AppCub

Ask, for example: "Add sign-in with email and password. Owner sees all screens. Teachers see attendance and marks for their batches only. Parents see their own child's attendance, marks and fees." AppCub asks you to connect your Supabase database, shows the screens for each person in the plan, and builds them. Test it with an owner and a parent account on two phones.

Questions

Can my app have a login?

Yes, email and password sign-in, once you connect your own Supabase database from the AppCub chat.

Does a login cost extra?

Supabase has a free plan that suits many small apps. Your AppCub plan covers building the screens.

Can customers sign in with their phone number and OTP?

Not promised. AppCub apps use email and password sign-in.

Where are my customers' accounts stored?

In your own Supabase database, in your account, not in AppCub's.

Can staff see different screens from me?

Yes. Say who sees which screens, and AppCub builds the screens for each role.

Does an owner-only app need a login?

Usually not. The data stays on your phone, protected by the phone's screen lock.

What happens if someone forgets their password?

Ask for a Forgot password option and check it in the plan. Ask people to sign up with an email they can open.

Make yours with AppCub

Seeing the plan is free. Building starts with a 2-day trial for ₹99.

Start building