{"id":1509,"date":"2026-11-14T14:15:00","date_gmt":"2026-11-14T14:15:00","guid":{"rendered":"https:\/\/pilotsindia.com\/blog\/?p=1509"},"modified":"2026-11-15T04:15:00","modified_gmt":"2026-11-15T04:15:00","slug":"flight-school-leaver-steps","status":"publish","type":"post","link":"https:\/\/pilotsindia.com\/blog\/flight-school-leaver-steps\/","title":{"rendered":"IdentityOps at a Flight School: Closing Out a Leaving Instructor"},"content":{"rendered":"<p>Last spring a small flying club in the hills lost an instructor on a Friday afternoon. He handed in his logbook, shook a few hands and drove away. By Monday morning the club&#8217;s scheduling tool still listed him as a bookable instructor, a student had reserved a Cessna with him for Tuesday, and his old login still opened the maintenance-records folder. Nobody had done anything careless. Nobody had simply owned the question of what happens to a person&#8217;s digital presence when the person leaves. That question is the heart of <strong>IdentityOps<\/strong>, and this post turns it into a step-by-step routine you can run at a flight school, a charter desk or a ground-training office.<\/p>\n<p>The ideas below are drawn from the Ops Atlas, which describes the discipline as the daily running of who exists inside your systems and how each of them proves it. I have translated them into hangar language, because pilots already understand checklists better than most IT teams do.<\/p>\n<h2>Step 1: Decide what IdentityOps covers at your school<\/h2>\n<p>Start by drawing a boundary on a single sheet of paper. In the Atlas&#8217;s framing, IdentityOps handles the existence side: the roster of people and machines, the way they sign in, and what happens when they arrive, change roles or leave. What each person is permitted to do once inside, who can approve extra rights and how those rights are reviewed are separate subjects. Keeping them separate stops the project from ballooning.<\/p>\n<p>For a flight school, the roster is wider than the staff list. It includes full-time instructors, part-time examiners, students, the front-desk team, the engineer who signs off aircraft, and a handful of machine accounts: the booking system&#8217;s connection to the payment tool, the weather-feed credential, the sync job that copies logbooks to cloud storage. Write them all down. Every row needs a human owner. If a row has no owner, that is your first finding.<\/p>\n<h2>Step 2: Name the trigger that starts a departure<\/h2>\n<p>The Atlas insists that the personnel record drives everything. In a school this means the moment the office manager marks an instructor as departing is the starting gun, not the moment somebody remembers to email the IT contact. Pick one source for that trigger and make it the only one. A sticky note on a monitor does not count.<\/p>\n<p>Think of it as the equivalent of a release-to-service entry. An aircraft is not airworthy because a mechanic felt fine about it; it is airworthy because a dated record says so. A person is not departed because everyone knows they left; they are departed because a dated record says so and every downstream system reads that record.<\/p>\n<h2>Step 3: Walk the leaver sequence in order<\/h2>\n<p>The sequence the Atlas lays out for a departure is short enough to memorise and has the same order-of-operations feel as a pre-flight walk-round:<\/p>\n<ol>\n<li>The people team records the termination.<\/li>\n<li>The central sign-in account is disabled.<\/li>\n<li>Live sessions and tokens are revoked, so a laptop left logged in cannot keep working.<\/li>\n<li>Connected applications are told to switch the user off, usually through a provisioning standard called SCIM.<\/li>\n<li>Every timestamp is written down.<\/li>\n<\/ol>\n<p>Step three surprises people. Switching off an account will not necessarily kill a session already in progress. The Atlas notes that access tokens commonly stay usable for sixty to ninety minutes out of the box, and with continuous-evaluation setups they may live for most of a day. Picture an instructor who leaves the building with a tablet still open on the dispatch screen. Turning off the account at the front door does not shut that tablet. You have to push the revocation.<\/p>\n<p>The reference also warns about ordering mistakes inside the sync tooling. In one cloud directory, if you unassign a user from an application and then push, the account can remain enabled until the final push lands. The fix is not clever; it is to test the order with a dummy account before a real departure.<\/p>\n<h2>Step 4: Chase the apps the central switch cannot reach<\/h2>\n<p>Here is where the flying club story turns. When the club finally reviewed the departure, it found three places where the central switch did nothing: an old spreadsheet-based roster, a supplier portal where parts were ordered, and an aircraft-tracking subscription that had been set up with the instructor&#8217;s personal login. The Atlas names this gap precisely: a measure that stops at the sign-in system flatters you. Its worked example involves forty departures, thirty-six handled on time, yet three of those people kept a login in some minor app. Judged at the front door alone the score reads 90 percent; judged all the way through, 82.5.<\/p>\n<p>For your own school, make a second list titled &#8220;places a person can exist that the central system does not know about&#8221;. Review it every quarter. Ask the engineer, the front desk and the chief instructor one plain question: where did you log in this week that is not the main portal?<\/p>\n<h2>Step 5: Set the clocks<\/h2>\n<p>A routine without deadlines drifts. The Atlas offers example service levels that are easy to borrow: disable the central account within four hours of the departure record, remove access from every connected application within a day, disable anything dormant after ninety days, and cap the age of any machine credential at ninety days. These are examples, not rules; a school with six staff members can be far stricter about the four-hour window simply because there are fewer places to look.<\/p>\n<p>Pair the clocks with a rhythm. The reference suggests a daily reconciliation of the roster against reality, a weekly spot check of how password and device recovery is being handled, a monthly look at expiring machine credentials, and a quarterly drill. In flying terms: daily walk-round, weekly engine run, monthly inspection, annual check. Same logic, different aircraft.<\/p>\n<h2>Step 6: Treat the robot accounts like unattended aircraft<\/h2>\n<p>A parked aircraft with no tie-downs and no log entry is an accident waiting to happen. Machine accounts are the same. The Atlas lists a lifecycle for them: inventory, register an owner and a purpose and an expiry, issue short-lived credentials, rotate them on a calendar, and retire each with proof. For retirement it recommends a disable, a waiting period and then a deletion, which mirrors how you might ground an airframe before scrapping it.<\/p>\n<p>One of the cases summarised in the Atlas involved an enterprise sign-in provider in autumn 2023, where a credential for a service had been parked in an employee&#8217;s private file storage, and tokens embedded in support files were later hijacked. The lesson for a small school is humbler: a credential for the booking sync does not belong in someone&#8217;s personal cloud folder, and when the person who created it leaves, the credential must change hands on paper first.<\/p>\n<h2>Step 7: Plan for the day someone forgets how to sign in<\/h2>\n<p>Every school has a version of the call: &#8220;I&#8217;m on the ramp, my phone is dead, I can&#8217;t get the schedule.&#8221; The Atlas treats recovery as a high-risk moment, because it is the easiest way for an impostor to become a legitimate user. Its guidance is layered. Ordinary staff recover using a second authenticator they already carry. Assisted recovery goes through a manager, who has to physically meet or visually see the person, camera on, prior to any one-time pass being issued. Privileged staff, such as whoever can change aircraft records, go through stricter in-person proofing with a second administrator present. A phone call-back is called unreliable, since phone numbers can be hijacked.<\/p>\n<p>A practical version for a school: write a half-page recovery script, tape it by the front-desk phone, and make sure nobody reads out a reset code just because the caller sounds familiar and stressed.<\/p>\n<h2>Step 8: Pick your first thirty days<\/h2>\n<p>The Atlas ends with a 30\/60\/90-day outline. For a small organisation I would compress the first month to four jobs: name an owner for the routine, draw up a register of applications and machine accounts, hand administrators hardware security keys, and draft the recovery script. Month two adds automated provisioning from the personnel record for one group, such as instructors, and a first inventory of robot credentials. Month three adds session revocation, a first leaver drill, and alerts when passwords or federation settings are changed.<\/p>\n<p>If your school is tiny, the same reference suggests you may not need a dedicated practice at all; a person, a register, a drill and a calendar reminder go a long way. And do not buy a heavyweight governance product before the underlying personnel data is clean. Garbage rosters produce garbage automation.<\/p>\n<h2>Where to read the full thinking<\/h2>\n<p>If you want the long treatment, <a href=\"https:\/\/www.xopsschool.com\/identityops\/\">the Ops Atlas entry on IdentityOps<\/a> runs through scope, standards, metrics and incident cases in far greater depth than a flight-school post can, and it openly admits the label is young, with vendors drawing its borders in different places.<\/p>\n<h2>Applying it before the next intake<\/h2>\n<p>Students are the other side of the roster. If you are building toward a career in the cockpit, the preparation habits in <a href=\"https:\/\/pilotsindia.com\/blog\/how-to-prepare-for-pilot-aptitude-tests-in-india\/\">this walkthrough on getting ready for aptitude tests<\/a> carry the same discipline: a plan, a schedule, a record. For those still weighing which route to take, <a href=\"https:\/\/pilotsindia.com\/blog\/aviation-entrance-exam-guide-for-indian-students\/\">the rundown of entrance exams for aspiring aviators<\/a> is a good companion.<\/p>\n<p>Back at the flying club, the fix took one afternoon. They named the office manager as owner, added the dated departure record as the trigger, rotated the tracking subscription onto a shared club login with a named owner, and ran a mock leaver on a spare account. The following autumn another instructor moved on. By the time he had finished his last debrief, every door he could once open had quietly closed. That is what a working routine feels like: nothing dramatic, just everything in order, the same way a clean walk-round feels like nothing at all.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A flying club learned the hard way that departing staff keep their access. Here is a step-by-step IdentityOps routine, told through hangar habits and checklists.<\/p>\n","protected":false},"author":6,"featured_media":1510,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[768],"tags":[],"class_list":["post-1509","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-pilot-training"],"_links":{"self":[{"href":"https:\/\/pilotsindia.com\/blog\/wp-json\/wp\/v2\/posts\/1509","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pilotsindia.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pilotsindia.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pilotsindia.com\/blog\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/pilotsindia.com\/blog\/wp-json\/wp\/v2\/comments?post=1509"}],"version-history":[{"count":1,"href":"https:\/\/pilotsindia.com\/blog\/wp-json\/wp\/v2\/posts\/1509\/revisions"}],"predecessor-version":[{"id":1607,"href":"https:\/\/pilotsindia.com\/blog\/wp-json\/wp\/v2\/posts\/1509\/revisions\/1607"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/pilotsindia.com\/blog\/wp-json\/wp\/v2\/media\/1510"}],"wp:attachment":[{"href":"https:\/\/pilotsindia.com\/blog\/wp-json\/wp\/v2\/media?parent=1509"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pilotsindia.com\/blog\/wp-json\/wp\/v2\/categories?post=1509"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pilotsindia.com\/blog\/wp-json\/wp\/v2\/tags?post=1509"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}