Security and Access

Owner login and secure authentication

One account sits above the rest: it creates the others, decides what they can do, and is the one worth protecting properly.

All plansAndroid · iOS · Web · Windows

The account that controls the others

The owner account is not simply the first login. It is the one that adds staff, defines roles, changes settings and locks periods — which makes it the single point that everything else in the security story depends on.

Two habits follow from that. It should not be the account the counter uses daily, because a shared owner login makes roles meaningless. And the number it is registered to should be current, since that is what sign-in and recovery rely on.

Keeping it sound

  1. 1Keep it to yourself

    The counter gets its own login, not this one.

  2. 2Keep the number current

    Sign-in and recovery depend on it.

  3. 3Create staff accounts

    With roles that fit their jobs.

  4. 4Watch the alerts

    New sign-ins are worth noticing.

Inside Security and Access

Who can open the books, on which device, and what they are allowed to do once inside. Staff get accounts of their own rather than a shared password, and what each of them can reach is set screen by screen.

Most of it is set up once, early, and then only noticed when something changes — a new device signs in, a bill is cancelled, a role needs tightening.

Add-ons for this feature

Extra WhatsApp Notifications (own number) — 1,000₹50

per year

From Growth

What it works with

Everything it governs.

Reports it feeds

Audit logs · Login history

Every feature, by plan →

Questions people ask

Should staff use the owner login?

No. Shared, it makes roles unenforceable and the audit log anonymous — the two things that protect you.

What can only the owner do?

Create staff logins, define roles, change settings and lock closed periods.

What if I change my phone number?

Keep the registered number current — sign-in and recovery both depend on it.

Protect the account that controls the rest

Everything else in the security story assumes this one is not shared.