Personal identity
Every action is tied to a real person, not a device everyone uses.
Secure team login
Secure Team Inventory Login
Members sign in with their own Google account plus a per-business join password — so access is personal, revocable and never a shared secret.
- Google or Apple sign-in plus a business join password
- Password hashes never leave the server
- Membership created only after verification, by a server function
- Revoke one person without disrupting anyone else
Why not just share one login?
Shared logins are the default in small businesses because they are easy — and they are the single biggest reason inventory histories are useless. Every action belongs to "the tablet", nobody can be asked about anything, and the password follows former employees home.
The model here keeps joining simple without giving that up. A member signs in as themselves, then enters a join password you set for your business. A server function verifies it and writes the membership record; the client never sees the hash and cannot fabricate access.
What you get
Simple to join
One password to share verbally on day one — no invite-link chasing.
Hashes stay server-side
Team secrets are never readable by any client, by rule.
Server-issued membership
Only a Cloud Function can grant access, after verifying the password.
Independent revocation
Removing one member never forces a password reset for everyone else.
Their own dedicated login page
A separate team login keeps staff out of owner-only signup flows.
Easy to join, easy to remove
The security question that matters most is not how someone gets in — it is how quickly they can be taken out. Here it is one click, effective everywhere, instantly.
How it works
1
Set a join password
Create the member on the Team page with the permissions they need.
2
They sign in
At the team login they authenticate with Google or Apple, then enter the password once.
3
They are in
Their session is scoped to your business and their permissions, on any device.
Frequently asked questions
Is a shared password secure enough for team access?
On its own, no — which is why it is only half of it. The password proves they belong to your business; their own Google or Apple account proves who they are. Attribution comes from the identity, and revoking one person does not require changing the password for everybody.
What if the join password leaks?
Change it on the Team page. Existing members keep working because their membership is already established; the old password stops granting new access immediately. You can also remove any membership that should not exist.
Can team members sign up for their own accounts?
They sign in with a Google or Apple account they already have — no new credentials to create or forget. If they later want their own business workspace, that is a separate owner account and completely independent of their membership in yours.
Explore related features
Ready to try it?
Start free with 50 items — no credit card, no trial countdown. Import your spreadsheet and you have a working system in minutes.