Connections
Third-party systems
Business connections
Only real operating integrations are listed here. The table is the setup plan; the test panel below reads the live backend status.
| System | Purpose | Status | Next step |
|---|---|---|---|
| Shared database | Shared records, login, and protected owner actions | Connected | Move remaining browser-only state into tables |
| Square | Roster and timecard import for labor review | Ready for token | Add SQUARE_ACCESS_TOKEN with Team and Labor read access, then preview from Staff Directory and Financials |
| GroupMe | Team schedule posts and coverage messages | Keys needed | Add bot token and group ID in Vercel |
| Resend | Morning brief, email reminders, and policy packets | Keys needed | Verify sending domain and owner recipient |
| Web push | Browser reminders for shifts and tasks | Ready to test | Ask staff to allow notifications on their device |
Channel tests
Send and sync checks
Run safe dry-runs first. Live tests use owner channels only.
Owner setup accessUnlock once, then protected owner actions work automatically.
CheckingChecking owner setup access.Production values
What still needs account secrets
These names go into Vercel Environment Variables. The app never asks employees to paste provider tokens.
RESEND_API_KEYRESEND_FROM_EMAILOWNER_EMAILTWILIO_ACCOUNT_SIDTWILIO_AUTH_TOKENTWILIO_FROM_NUMBEROWNER_PHONEGROUPME_FRONT_BOT_IDGROUPME_BACK_BOT_IDGROUPME_ACCESS_TOKENGROUPME_DRY_RUN_ONLY=falseSQUARE_ACCESS_TOKENSQUARE_LOCATION_IDSQUARE_ENVIRONMENTSQUARE_API_VERSIONSquare setup
Team-member sync rules
Square is the source for who is employed. Oh! Cha stays the source for schedules, checklists, scorecards, and reminders.