Alert on every access change in both directions, and treat the removal side as the important half. Access grants are visible because somebody asked for them. Removals are invisible because nobody asks, which is how stores accumulate active accounts belonging to people who left months ago.
Why this one is worth an interruption
Nobody forgets to give a new starter access, because they cannot work without it and they will say so. Everybody forgets to remove it, because nothing breaks when you do not and no one complains.
The people whose access is most often left in place are the ones who were most peripheral: a seasonal hire, a contractor on one project, an agency that finished six months ago. Peripheral is not the same as harmless.
The threshold
Not a threshold so much as a set of events worth recording.
| Condition | Set it to | Why that number |
|---|---|---|
| Joined | on invitation accepted | The record starts here |
| Role changed | on any change | Scope creep happens by increment |
| Left | on removal | The event most worth having a record of |
| End date reached | on the agreed date | Only fires if the date was set at grant time |
| Dormant | no activity for 60 days | Usually someone who has already left |
Who should receive it
Whoever owns access, which should be one person even in a small team.
- Whoever administers the workspace.
- The person who requested the access, so they see the end date arrive.
- Not everyone. Access changes are administrative, and broadcasting them adds nothing.
What to do when it fires
- Set an end date at the moment access is granted, not later. This is the single change that makes offboarding routine.
- On a leaving event, check the other places that person had access to, because the workspace is rarely the only one.
- On a dormant flag, ask whether the person still needs it rather than removing silently.
- Review anyone with elevated permissions quarterly, whether or not anything fired.
When not to set this alert
There is little case for switching this off, but there is a case for keeping it quiet. If it is announcing every routine change to a room full of people, move it to a weekly digest and keep only the leaving and role-change events as alerts.
If your team is two people who sit together, the alert adds nothing you do not already know.
Common questions
Why does offboarding get missed?
Because nothing breaks when access is left in place and nobody complains. Onboarding is self-correcting, since a new starter cannot work without access and will say so. Removal has no equivalent forcing function.
What is the single best fix?
Agree an end date at the moment access is granted rather than deciding later. It turns removal from a judgement call into a diary entry, which is the difference between it happening and not.
Do staff need a Shopify staff account to be in the workspace?
Yes. Store Huddle runs inside Shopify admin, so a team member needs a Shopify staff account to reach it. The Store Huddle role then controls what they see once they are in the workspace.