Workplace SSO or invite link problems

Open the invite in the same browser where you use your company login, then check the email address and organisation name. If SSO loops, try a private window and contact HR with the exact error time; never send passwords or one-time codes. Workplace care combines an employer programme with a private care relationship. Access can change when employment, programme dates, dependants, seats, or single sign-on (SSO) status changes. This article focuses on “Workplace SSO or invite link problems” and gives you a safe next step even when the normal path is unavailable.

What to do now

1. Open Workplace care and record the organisation, plan name, eligibility label, allowance, and programme dates shown to you.
2. Use the invited email or SSO route exactly as provided, then confirm whether you are booking as an employee or dependant before selecting a service.
3. Keep HR questions about employment status separate from clinical questions for your provider. Save the invitation or error text without forwarding private links.

If the usual path fails

• An employee can be active while the benefit is paused, out of seats, outside dates, or limited by country; HR and Mindara may need to check different parts.
• SSO loops often come from a different signed-in work account or blocked third-party cookies; try one private window and then contact the organisation administrator.
• A dependant invite is private and single-use. If it is wrong or expired, ask the administrator to issue a new one rather than editing the link.

When to contact Mindara

Support can check tenant configuration and platform access. HR or the employer administrator must confirm employment, eligibility, and plan policy. Include the page or booking reference, the exact error text, the time it happened, and the device/browser you used. Never send a password, one-time code, full card number, or another person’s private health information.

For this situation

SSO loops often happen when a personal and work account are signed into the same browser. Sign out of the wrong identity, open one private window, and use the exact organisation link. Record the identity provider error code, not a screenshot containing a token.

Why the result may look different

Mindara shows a status only after the relevant service has recorded it. A browser can keep an older page in memory, an email can arrive before a database update, and a bank, employer, provider, or identity check may have its own processing time. Read the status words and the timestamp together. “Pending”, “confirmed”, “cancelled”, “failed”, and “under review” are different outcomes, even when a colour or a short notification makes them look similar. If you are helping somebody else, ask them to sign in themselves rather than sharing credentials or screenshots with private details.

Before you try again

• Check the dashboard record first so a successful action is not repeated.
• Confirm the account, country, language, time zone, and role shown in the header.
• Close an old duplicate tab, then refresh once; repeated clicks can create holds or duplicate requests.
• Use a supported, updated browser with cookies, pop-ups, microphone, or accessibility settings enabled as the task requires.
• Write down the exact button label and status before changing anything.

If your circumstances are unusual

A normal step may not fit if you use an employer invitation, share a device, travel between countries, need an interpreter or assistive technology, care for someone during a session, or have lost access to an old email or phone. Say which constraint matters and ask for an accessible or safer route. Do not work around a check by choosing a false country, opening a second account, borrowing a payment method, or sending documents through an ordinary chat. Those shortcuts can make a genuine problem harder to untangle.

Keep a useful record

Make one private note with the article title (“Workplace SSO or invite link problems”), the date and local time, the page address, the status before and after, and what you tried. Redact passwords, recovery codes, full payment numbers, health details, and other people’s names. A short, factual timeline lets support investigate faster and gives you something reliable to refer back to if a session expires or a redirect takes you to the wrong page. If another person is affected, ask them to make their own request so consent and account ownership remain clear. Clear notes also help you notice whether the problem is occasional, tied to one device, or repeating after a particular action.

Keep the note somewhere private and remove it when you no longer need it. The goal is clarity, not surveillance of yourself or another person. If the issue affects care, safety, or access, say that plainly so the right team can prioritise it. A calm record is often the fastest way to get the right answer.