Skip to main content
  • Check your email and password carefully — both are case-sensitive.
  • If you see “Invalid login credentials”, the password is wrong. Try the Forgot password? link if your org has SMTP set up.
  • If the Forgot password link is missing, ask your admin to reset your password directly (they can edit your user and temporarily set a new one).
  • If you’re a brand new user, your admin created you with a temporary password — confirm they’ve told you the right one.
The admin Users page was briefly broken — if you see this, refresh. If it persists, check that you have the users.view permission and that RLS policies on profiles are in place. See the Users admin docs.
  • Confirm SMTP is Enabled in Admin → SMTP/Email.
  • Run a Send test from the SMTP page. If that fails, your SMTP config is wrong.
  • Common Exchange 365 issue: SmtpClientAuthentication is disabled for the tenant. See the SMTP troubleshooting section.
  • Check your spam folder. “Reset your iWorkWhen password” sometimes lands there on fresh setups.
  • The schedule they were in might still be in draft. Employees only see published schedules.
  • Supervisor/Admin: check /app/admin/schedules and publish the relevant schedule.
  • Alternatively, a shift might have been deleted — check the schedule history (schedule.history.view permission).
  • If you addressed it to a specific person, confirm they actually exist (and are active) in Users.
  • If you left it open, the app doesn’t notify anyone — they’ll see it on the trades page when they look.
  • Email notifications require SMTP to be set up (Admin → SMTP/Email).
  • Race condition edge case — refresh both parties’ schedules.
  • Check trade_requests table: status should be approved and the two shifts should have their user_id fields swapped. If not, ask an admin to re-approve.
  • After approval, balances update server-side. Refresh the Time off page.
  • If it’s still wrong, an admin can manually correct in Admin → Time banks.
  • If you see a denied absence that still deducted, ask an admin to re-credit manually.
  • On screens under 900px wide, the sidebar is hidden by default. Tap the hamburger icon in the top-left.
  • If the menu doesn’t open, check for a Chrome extension or content blocker interfering.
Happens if your session cookie is partially corrupted. Open devtools → Application → Cookies → clear all sb-* cookies for iworkwhen.com, then reload. Sign in again.
You need the Admin role (or a role with admin permissions). Ask an admin to add you.
  • For admins managing the repo: check that all 5 env vars are set (see the README or Security).
  • Build logs in Vercel will show the actual error — usually a missing env var or a Supabase connection issue.

​
Still stuck?