Workplace and team automation
Automating access when staff join, move or leave
Write an NZ staff access workflow that gives a new starter the right tools, changes permissions on a transfer and verifies removal when a contractor finishes.

A contractor finishes a council digitisation project on Friday and starts a different assignment with the same organisation on Monday. A checklist that says “disable account” could interrupt legitimate work. A checklist that says “retain access” could expose the old project. Design the workflow around assignments, their dates and the permissions each assignment actually needs.
Who can ask for access, and who can approve it?
Start with a named manager, an identified person and a defined role. Reuse an existing identity when the organisation has verified that it belongs to the same person. Capture the dates and sponsor of the assignment. A project team can describe what work a person needs to do, while the owner of a sensitive application decides whether to grant access to it.
Translate broad labels into actions. A records assistant might need to upload scans to one collection, read its index and report errors. A reviewer might confirm a batch or return it for correction. Ask the application owner to demonstrate both roles using fictional accounts. Keep exception permissions individually approved with a reason and an end date.
What happens when someone changes teams?
Model the move as an end to some responsibilities and a start to others. Where a permission comes from several active assignments, describe how the workflow determines whether it is still needed. Check separately for permissions added directly in an application. A tidy role list in the staff directory can hide an old invitation in an external tool.
Use a rehearsal in which both teams need access to a shared calendar but only the first team needs a records collection. End the old assignment and ask the owner to check the actual application. Confirm the calendar still works and the former collection is unavailable. A delayed update should create a visible exception with an owner who can complete the change manually.
Handover also matters for work the person created. List reports or approval queues that need a new accountable owner. A manager should be able to transfer responsibility for tomorrow’s report without giving the replacement access to unrelated material in the departing colleague’s mailbox.
What proves that a departure is complete?
Protective Security Requirements guidance describes departure activities such as returning passes. Use the relevant points when designing a checklist for your organisation. A sent email or completed ticket is evidence of a request. For high-impact systems, ask the system owner to record when removal actually took effect and identify anything still awaiting action.
Test an early departure, a postponed end date and a cancellation before a new starter arrives. Include the laptop, building pass, shared work queue and ownership of scheduled reports. Give the manager a list of outstanding actions with responsible people and due times, while limiting sensitive departure details to those who need them. At handover, rehearse one departure with the staff member who will operate the process and retain a sample completion record for future reviews.