smee
Smee utilizes internal connections to provide advanced scheduling assistance to schedulers based on facility requirements.
It reads who's available and what each site needs, then drafts the schedule. A person reviews it and publishes. Nothing goes live on its own.
What it does
Schedulers spend most of their time on the same arithmetic: who can work, who asked for time off, who's qualified for which position, and how many bodies each site actually needs on a given day. smee does that first pass. It pulls those inputs from the facility's own Agendrix workspace and proposes a week of shifts — assignment by assignment, with the reasoning attached — for a scheduler to accept, adjust, or throw out.
The scheduler stays in charge of every decision. smee proposes; a human disposes.
What it accesses in Agendrix
smee connects to your facility's Agendrix workspace over OAuth 2.0, with the narrowest set of permissions it can do the job with. Two scopes, and here's exactly what each one is for:
read to understand the week
- Team members and their availability
- Positions and who's qualified for them
- Sites
- Approved time off
- Demand projections (how busy each site expects to be)
- Shifts already on the calendar
write to save drafts only
smee creates proposed shifts as drafts. It never publishes them. A scheduler opens Agendrix, looks each one over, and publishes the ones they want. If a shift would land in the past — which Agendrix publishes automatically — smee refuses to create it rather than put something live behind your back.
Where your data goes
smee runs inside the facility's own environment. The only connection it makes off-site is to the Agendrix API you authorized — that's it. Scheduling data isn't sold, isn't shared, and isn't sent anywhere beyond the workspace it came from.
- Access is yours to revoke. OAuth tokens are stored locally by the facility's installation. Disconnect the app in Agendrix and smee can no longer read or write anything.
- Every write is logged. Each draft smee creates is recorded in a local audit trail, so there's always a record of what it did and when.
- It keeps only what the job needs. smee reads the inputs required to build the schedule a scheduler asked for, and nothing more.
How it stays safe
- OAuth 2.0 over HTTPS — no passwords handled, no credentials stored in the integration.
- Least-privilege scopes: read to plan, write only to save drafts.
- Draft-only by design. Publishing is always a human action inside Agendrix.
- A full audit trail of every write.
- One facility per deployment — data doesn't cross between organizations.
Contact
Questions about how smee handles your facility's data, or a privacy request? Reach us at jay@chkdsklabs.io.