One calendar. Nothing else.
It asks Google only for calendar.app.created, the narrowest permission there is. It can manage the calendar it
created and cannot read, change or delete any of your other calendars.
ADP Shifts copies your Workforce Now schedule into a Google Calendar it creates and owns, then keeps it current on its own. No passwords. No servers. Nothing else touched.
Works with any employer on ADP Workforce Now. Chrome, Edge, Brave and other Chromium browsers.
Three short steps the first time. After that the extension keeps your calendar in step with ADP while you go about your day.
Use Workforce Now in this browser the way you already do. The extension rides on that session and never asks for your password.
Visit your schedule one time so the extension can learn which Position is yours. It never looks up anyone else.
Approve one consent screen. The extension creates a calendar called ADP Shifts and fills it with your schedule.
From then on it checks daily and syncs whenever the last update is more than three and a half days old.
Every decision starts from one rule: do exactly one job, and never touch anything that isn't yours to touch.
It asks Google only for calendar.app.created, the narrowest permission there is. It can manage the calendar it
created and cannot read, change or delete any of your other calendars.
Each Sync creates, updates and removes shifts from today onward to match ADP. Shifts that already happened are history and are never rewritten.
Department, job, location and pay code come along in each event, plus your employer's holidays.
Uses your browser's time zone by default. Working somewhere else? Set an override in Settings.
ADP sessions expire. When one does, you get one notification. Click it, sign in, and the Sync finishes.
There is no ADP Shifts server. Everything runs inside your browser, so there is nowhere for your data to leak to.
ADP is called the same way the schedule page calls it, using the session already in your browser.
Google access is a short-lived token kept in local extension storage. No client secret ships in the code.
No tracking scripts, no telemetry, no data sold or shared. Not in the extension, not on this site.
Disconnect revokes the Google token and clears everything the extension stored.
Automatic Sync to a dedicated Google Calendar that stays current on its own. Everything described on this page.
The ADP Schedule Export userscript runs in Tampermonkey and downloads your schedule as an .ics file you can import into
Apple Calendar, Outlook or anything else. It never deletes anything.
No. ADP Shifts is an independent, open-source project. It is not affiliated with, endorsed by, or sponsored by ADP, Inc. or Google LLC. It reads the same schedule data the Workforce Now My Schedule page already shows you.
No. Google grants it the calendar.app.created scope only, which limits access to calendars the extension itself created.
Your personal, work and shared calendars are out of reach.
ADP ends sessions when you quit the browser or after a period of time, and it offers no way to stay signed in. When a Sync is due and the session has ended, you get a single notification. Click it, sign in normally, and the Sync completes.
The extension checks once a day and when you visit Workforce Now. It runs a Sync when the last successful one is more than three and a half days old. Press Sync now in the toolbar popup at any time to update immediately.
The ADP Shifts calendar mirrors ADP, so the next Sync puts upcoming shifts back the way ADP has them. Put your own events in another calendar. Past events are never touched.
The extension syncs the Position whose schedule you opened. If you switch Positions, open My Schedule for the one you want, and the next Sync follows it.
Open the extension's Settings and choose Disconnect and clear data. That revokes Google access and erases all local data. Removing the extension also deletes its local data. The ADP Shifts calendar stays in your Google account until you delete it there.
Set it up in about a minute. Your calendar takes it from there.