The thing most people get backwards: alerting does not wait for an invitation. Someone you added or imported receives alerts immediately, with no account and nothing to accept. An invitation only lets them sign in and look at the dashboard.
That distinction matters on a large rollout. A shift manager who needs the text message about their own kitchen may never need to sign in at all. The people who genuinely need an account are the ones who want to see across stores — district managers, regional VPs, the safety team.
- Import or add your people first, with their roles and territories.
- Open Invitations. It shows how many haven't been invited, how many were invited but haven't signed in, and how many are already in.
- Send. Each person gets a link that puts them straight into your organization with the role you assigned — their territory and notification settings are already attached, so there is nothing for them to set up.
- Sending is safe to repeat. The main button skips anyone already invited, and an address with an invitation still pending is left alone rather than mailed twice.
- One bad address doesn't stop the rest — rejected addresses are reported individually so you can fix a typo and re-send just those.
- Someone with no email address can't be invited, and is counted separately. They still receive SMS alerts if a mobile is on file.
Invitations must come from inside the product — don't just tell people to go and sign up. An account created outside your organization has no access to your stores, and the person lands in an empty dashboard.
In the dashboard: Invitations — Invite people to sign in and see the dashboard. Alerts already reach them without this.