“Is this required?”
Yes. The rollout is mandatory, with effective dates by brand, because stronger identity controls support data security and PCI compliance.
Translate a security requirement into action
The article gives owners a direct path through the change: how to log in, add staff, resolve username conflicts, and complete account verification. Reassurance appears exactly where people worry—for example, removing a username does not deactivate the staff profile.
01Verify accessConfirm the owner account and multi-location access.
02Add staffCreate the profile and assign a unique email login.
03Resolve conflictsRemove the login without deleting the profile.
04Complete setupUse verification and password-reset emails.
Answer the real objections
“What if someone will not use a personal email?”
A separate address can be created, but it must be unique and active because verification and password-reset messages go there.
“Will logging in feel different?”
Only the first post-rollout login adds verification. After that, the process is familiar—using an email address as the username.
Define loaded words
UniqueAn email address not assigned to anyone else in the brand.
ActiveAn accessible address that receives verification and reset messages.
StaffAn individual person, distinct from a resource or shared use case.
The glossary also separates a full staff profile from the login attached to it and defines tightly restricted non-staff logins.
Writing principle
Clear terminology, practical reassurance, and honest answers make a mandatory change easier to understand—and much less likely to become a preventable support issue.