Sofia
Connect Tanda
Connect Tanda from Sofia settings. Tokens stay on the server. If Tanda is disconnected, the adapter fails closed — Sofia will not write a roster she cannot see.
If the venue already lives in Tanda, you do not have to rip it out. Sofia can connect and write through Tanda when Call Sofia or the adapter needs a roster of record.
Connect
- Open Sofia settings as an admin.
- Start Tanda OAuth.
- Finish the Tanda consent screen.
- Map this Sofia location to a Tanda location id.
Tokens stay on the server. They are not in the browser, not in a screenshot, not in a CSV export.
Fail closed
If Tanda is disconnected, the adapter fails closed. Sofia will not write a roster she cannot see, and she will not pretend a Tanda write succeeded. That shows up as an error or an escalation, not a silent local-only edit that drifts from Tanda.
Reconnect before you expect the 6am line to publish into Tanda again.
What still lives in Sofia
Native Schedule, Auto-Fill, the time clock, Cover waitlist, and fair-workweek ledger are Sofia documents. Connecting Tanda does not move payroll, POS, or award interpretation into either product — Sofia still does not calculate Modern Awards or push Xero.
Native roster without Tanda
If you are not on Tanda, skip this page. Build the week in Sofia and publish there. Call Sofia writes the native roster through the same rules.