HR onboards seasonal parks staff on day one and terminates others the same afternoon. What IAM lifecycle practice best limits leftover access?

Seasonal parks staffing creates rapid joiners and leavers on the same day, so identity lifecycle timing is the control that limits leftover access. Provisioning accounts when employment starts and de-provisioning them when employment ends—classic joiner/leaver workflow—ensures seasonal workers receive access aligned to their badge period and that terminated staff lose system reach the same day rather than weeks later. In municipal parks systems that may hold citizen recreation data, facility schedules, or payment-adjacent records, orphan accounts from last summer are an avoidable attack and insider-risk surface. Same-day enable and disable as part of formal IAM processes is the practice that matches that operational reality.

Leaving accounts enabled indefinitely 'in case they return next summer' maximizes orphan risk and violates least privilege across seasons. Sharing one generic parks-temp password among all hires destroys accountability and makes revocation after one bad actor nearly impossible. Creating accounts only after thirty days of employment delays needed access for legitimate work and still fails to address timely de-provisioning on termination day.

Exam caveat: joiner/leaver is necessary but incomplete without mover (role-change) handling and manager attestation for residual entitlements. Also distinguish disabling versus deleting accounts—preserve audit trails per retention policy while removing access.

Operational check: sample recent parks hire and terminate tickets, confirm Active Directory (or IdP) enable/disable timestamps match HR effective dates within the same business day, and search for accounts still active past termination with parks-system group membership.