What does PeopleMuster depend on to run?
Attendance, leave, timesheets, projects and the capacity plan run on PeopleMuster and your own database, with no outside service in the path. Two features use outside services: meeting imports come from Fireflies, and the policy assistant and meeting signals use OpenAI. The fingerprint terminal syncs over your office network.
Knowing what a system leans on tells you what a bad day elsewhere would touch. Here the answer is short.
The core stands on its own. Attendance records, leave requests and quotas, timesheets and approvals, projects, clients and the capacity grid all live in your database.
Meetings come through Fireflies. Recordings and transcripts import on their own and file against the right project. Resync and import-by-ID actions sit on the meetings screen for any recording that needs a nudge.
The policy assistant and the meeting risk signals run on OpenAI. The prompt behind the signals is editable by an admin, versioned, and can be re-run over recent meetings.
Slack carries notifications. The scheduler shows every reminder's next run and its status, including any that failed or paused. A missed message is visible on one screen.
The terminal is local. A ZKTeco device on your office network syncs punches, and the attendance header shows how many minutes ago the last sync ran. Browser check-in, once an admin switches it on, needs no hardware at all.
Each connection is set up with you when the instance is built, alongside your modules and roles.
Related questions
Does attendance depend on Fireflies or OpenAI?
No. Attendance, leave and timesheets run on your own database. Only meetings and the policy assistant use those services.
How do I know the terminal is syncing?
The attendance screen shows how many minutes ago the last sync ran, so a stalled device is visible at a glance.
Can attendance run without the terminal?
Yes. An administrator can switch on browser check-in, which opens inside a window around each person's shift.