Workday SSO for Old Navy Team Members: What Actually Happens When You Try to Log In
The Gap Inc. single sign-on portal routes Old Navy employees through Workday as the primary authentication gateway. Your credentials don't live in an Old Navy-specific system anymore. They live in Workday's identity provider, and everything else—payroll, benefits, time clocks, the internal directory—pulls from that same source. This means the login page you see depends entirely on which app you're trying to reach first. I spent about three weeks untangling this after a regional policy change pushed some associate accounts through a different identity provider than expected. The short version: if you're accessing Old Navy's employee resources through the corporate portal, you sign in at the Workday login page using your corporate credentials. After authentication, Workday's SSO hands off a token to whatever application you selected, and you're in without another password prompt.
The Gap Inc Workday Sign In Your Old Navy Access Guide Streamlining Employee Portals
Here's how the actual flow works. You navigate to the Gap Inc. employee portal landing page, usually something routed through your company's intranet or a direct URL provided by your manager or HR. You select Old Navy from the app launcher or the list of available services. Instead of seeing an Old Navy login form, you get redirected to a Workday sign-in page. You enter your corporate username and password there. Once Workday authenticates you, it redirects back to Old Navy's platform with an SSO token attached. The whole thing should take maybe ten to fifteen seconds if your credentials are current and your browser isn't clearing cookies aggressively. If you get a "credentials do not match" error after entering your password, the issue is almost never your password itself. It's usually one of three things: your account is provisioned under a different username format than you're entering, your account is in a suspended or re-enabled state from a recent hire transfer or name change, or you're hitting a cached redirect from a previous login attempt that used different credentials. Clear your browser cache for the workday.com domain and the oldnavy.com employee subdomain, then try again. If that doesn't resolve it, check with your HR representative about your current provisioned username. It may not be the same as what you used before the portal migration. One thing most people miss: Workday uses role-based provisioning. Just because you can log into Workday doesn't mean you can see every Old Navy internal tool. Your access is determined by the role your hiring manager or HR assigned during onboarding. If you're an hourly store associate, you'll see the timekeeping, schedule, and payslip modules. If you're in corporate operations, you might also see learning management, expense reporting, and performance review tools. Trying to navigate to an app you don't have access to will give you a generic access denied message that doesn't tell you why. It just won't load. Request additional access through your manager's portal or your local HR contact rather than repeatedly clicking the link.
There's also a mobile app situation worth noting. The Workday app on iOS and Android handles SSO differently than the browser version. Some companies configure it so the app remembers your authentication state better than a browser session will. I've found that if you're constantly getting logged out on desktop but the mobile app keeps you authenticated for days, switching to the mobile app for routine checks like my pay statement or my schedule saved me a significant amount of time over a few months. The mobile experience is less feature-complete for some administrative tasks, but for day-to-day access it's more reliable when your SSO token is expiring too quickly on web. A specific problem I ran into: after my name was updated on file due to a legal name change, my old Workday credentials stopped working for the Old Navy portal specifically, even though they still worked for the main Workday dashboard. The fix wasn't resetting my password. It was that the identity provider maintained a separate attribute mapping for the Old Navy sub-application, and the name change triggered a re-provisioning delay. Until that completed—which took about three business days depending on how fast HR processed the update—I had to use the recovery flow and select the option to sync my identity attributes across all integrated applications. Once that ran, everything came back online. If you're experiencing the same thing after any profile update, don't assume your account is broken. Check whether a recent change triggered a provisioning recalculation. Password reset flow goes through Workday's standard recovery process. You click "Forgot Password" on the Workday sign-in page, enter your corporate email or employee ID, and follow the steps. This resets the password across all Workday-authenticated applications simultaneously, including Old Navy. You don't reset passwords separately for each portal anymore. That's one of the main points of the consolidation.
Get the Full Details
There are situations where this system completely fails you. If your device isn't on the corporate network and you're trying to access certain internal tools that require a VPN or a specific network token, Workday SSO alone won't get you through. You'll authenticate fine but then hit a network-level block. This is common for remote associates trying to access scheduling tools or internal communication platforms from home without the proper network setup. The workaround is connecting through the corporate VPN first, then launching the application from the portal. Another failure mode: if your account was created through a staffing agency or a contingent worker onboarding path, your Workday access might be limited to a read-only subset of applications. You won't get prompted about this during sign-in. You'll just find that editable fields are grayed out or entire modules are absent from the launcher. In that case, the issue isn't your credentials. It's your worker type classification in the HRIS. Multi-factor authentication is configured at the Workday level, not per application. If your company requires MFA, you'll be prompted for it during the Workday sign-in step before any SSO token is issued. Make sure your authenticator app or phone number is registered in Workday before attempting to access Old Navy resources. If MFA enrollment is pending or expired, the SSO handshake fails silently and you get a vague authentication error that points you nowhere useful. Check your Workday security settings first if you're stuck at the login stage. The main downside of this consolidation is that when Workday has an outage or a maintenance window, every integrated application goes dark with it. Old Navy's own systems might be fine, but you can't reach them because the authentication layer is down. This happens a few times a year during scheduled maintenance, usually on weekends, but it's moved to weekday off-hours occasionally. Plan around it. Don't try to access your pay stub or submit a request right before a scheduled maintenance window if you can avoid it.
If you need the direct access point, the portal URL is distributed through your employee handbook, your onboarding packet, or your manager. There's no public-facing login page for employee-only resources. Attempting to guess the URL will just land you on Gap Inc.'s public corporate website, which has no authentication function. Use the link provided by your organization or contact your HR help desk for the current URL, as these occasionally change during platform migrations.
