My account
EveryoneYour own sign-in, POS PIN and devices. Your name, email and role are managed by the Owner in Settings › Team (§5.1).
Profile
- Name
- Joel Merciadez
- Sign-in email
- joel@localcraftfood.ph
- Role
- Owner
- Locations
- Main Branch, BGC
Change password
Password
Managed by your company sign-in. Change it with your company’s IT, not here (§5.1a, D76).
POS approval PIN
You enter this on a terminal to approve a Staff void, discount or cash-out (§5.1, D37). Five wrong tries lock it on that terminal for 15 minutes.
Google Calendar D145
See your own appointments in your Google Calendar. One-way: SchedHubPH stays the calendar, and moving an event in Google doesn’t move the booking. Clinics: titles show only “Appointment · first name”.
Google asks you to allow SchedHubPH to add events to one calendar you pick. We never read your other events.
✓ Connected · paula.reyes@gmail.com · calendar “Clinic” · last sync just now
Where you’re signed in
- Chrome on Windows · MakatiThis device
- Safari on iPhone · Makati2 hours ago
- Counter 1 tablet · Main Branchyesterday
Implementation notes for Cursor
Entities: User (password_hash, password_changed_at), Staff.pos_pin_hash (Owner/Manager only), refresh-token families (§5.1).
Key states: Password change needs the current password, rejects reuse and short passwords, revokes every other refresh-token family, and sends the “password changed” message (§20a). With SSO on, the password block is replaced (D76); the PIN still works because it is a terminal approval, not a sign-in. Staff have no PIN block.
Forbidden inventions: no editing own role, Locations or email here (Owner does that in Team); no showing the old PIN; no password hints.
Governs: §5.1, §5.1a (D76), §20a, D37, D79, PLAN-226.