Sending a bulk workplace invitation

Bulk invitations are powerful and easy to misroute. Prepare a clean roster, use the approved import or invite tool, and protect the file like employee data.

What to do now

1. Confirm each email, employee reference, country, programme, and start/end date before sending. Remove duplicates and former staff.
2. Send a small test batch, check the landing page and privacy wording, then send the remaining invitations once.
3. Track delivery, acceptance, expiry, and bounced addresses without storing clinical information in the roster.

If the usual path fails

• A file contains extra columns: remove health or salary data before upload.
• An employee receives two invites: revoke the older one and tell them which email to use.
• A mailbox bounces: verify the address through the organisation, not by forwarding a private invite.

When to contact Mindara

Provide the organisation, batch timestamp, count, and error summary. Never attach a raw employee roster to a general ticket. 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.

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 (“Sending a bulk workplace invitation”), 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.