Start with the precise job
An employee follows a message about a payslip and reaches an unexpected code prompt. The existence of payslips in Workday does not authenticate the message or the website.
Write the task in one sentence before choosing a result. “Read a payslip” and “change an hours entry” can involve related services but require different records and different permissions. This independent publication offers a dated public map; it cannot observe your employee profile, approve access or operate an employer login. Keep the distinction visible when a search engine groups many intents under the phrase “my nordstrom.”
What the public record actually shows
Nordstrom’s public resources report documents the work task and the FTC explains how a plausible message can lead to credential theft. Neither source verifies a particular incoming message or live redirect. See Nordstrom’s published employee resource guide and compare the date and audience on the document.
This is a route statement drawn from a public company document, not evidence that a protected service is available in this browser right now. A publication date matters: account screens, menus and processes may change. If your current employer guidance differs, follow the current authorized instruction and ask the service owner to reconcile the difference.
What the source cannot prove
Return to a known employee route reached independently. Check the hostname and ask official IT or the security team if a prompt has changed. A visual copy of a login screen is weak evidence.
A general website cannot confirm your identity status, location policy, classification or an individual transaction. A successful public page load does not prove that authentication or resource permission will work. Conversely, one failing bookmarked URL does not prove a company-wide outage. Record the first failing step without publishing private screenshots.
A concrete routing example
If the prompt appeared from an unsolicited email, retain the message for the employer’s approved reporting channel. If information was already entered, contact authorized support promptly.
Compare the example with your own task rather than copying it as a guaranteed procedure. If the first route differs, write down what changed: entry address from an official source, the screen displayed before sign-in, the result after sign-in and the named service for the task. These observations are more useful to support than an untested theory about why the system failed.
Who can resolve the private question
Never forward a live code to a third party or enter it into an editorial contact form. Describe the request in general terms without reproducing private tokens.
The company can inspect employee records and current access policy; an unaffiliated site cannot. Use an employer contact you already trust or one printed in a current Nordstrom publication. Do not assume a web article’s support phone number or a search advertisement is current. This site offers source links and reasoning only.
Keep the request narrow and safe
Send a brief description of the task, the first failing step and the approximate date through the employer’s approved private system. Leave out passwords, verification codes, full session addresses, account balances and medical details. If a message requests those items on an unexpected page, verify it from an independent official route. FTC phishing advice gives general context for that check.
For adjacent questions use the related route or return to the employee task map. Editorial corrections to this article can use the contact page, but this publisher has no access to Nordstrom tickets and cannot move an individual request through a private workflow. Always confirm time-sensitive details with the employer.
A short field note before you act
Write the task, not an assumed diagnosis: An employee follows a message about a payslip and reaches an unexpected code prompt. The existence of payslips in Workday does not authenticate the message or the website. From the public evidence, the route begins with this limited statement: Nordstrom’s public resources report documents the work task and the FTC explains how a plausible message can lead to credential theft. Neither source verifies a particular incoming message or live redirect. Treat both sentences as different kinds of information. The first describes why the reader arrived; the second summarizes a dated company publication. An employer representative can compare them with the actual account and current menu.
If you contact support, keep a compact timeline of the verified starting route, approximate time, earliest visible failure and the intended resource. The hypothetical example here is useful for distinguishing stages: If the prompt appeared from an unsolicited email, retain the message for the employer’s approved reporting channel. If information was already entered, contact authorized support promptly. Ask the owner for one specific next step rather than sending a full document or retrying several unfamiliar sites. Never forward a live code to a third party or enter it into an editorial contact form. Describe the request in general terms without reproducing private tokens.