This is the one distinction worth reading carefully, because both send alerts and they're configured in different places.
| Store contact | Member | |
|---|---|---|
| Configured on | The store | People & roles |
| Covers | That one store | A territory — stores, regions or markets |
| Can sign in | No | Yes, when their email is invited |
| Has a role | No | Yes — the role decides capability and alerts |
| Best for | The person physically at that site, who just needs the text | Anyone with responsibility across more than one store |
A store contact is the simplest possible thing: a name, a phone or email, and which levels they want. No account, no login, no role. For the shift manager who needs to know their own kitchen is dangerous, that is exactly right.
The store page's "Who is notified" panel shows BOTH: the members whose role and territory route them to this store (managed on People), and the store-level contacts added on the store itself. It uses the same resolution the alert engine uses, so what it lists is who an alert would actually reach — the "nobody would be told" warning appears only when both lists are genuinely empty.
A member is a person in your organization. Their role says what they can do and what they hear about; their territory says which stores are theirs. Members are who escalation runs through and who can acknowledge from the dashboard.