Who Can Delete a Student Record? AccessOps for Flight Schools

Who Can Delete a Student Record? AccessOps for Flight Schools

Marisol had been a scheduler at a small flight school for six years when the owner asked her a question she could not answer: who exactly could delete a student’s training record? She counted the logins on her fingers, lost track at nine, and realised nobody had ever written the list down. That evening she went looking for a name for the problem and found AccessOps, a label for the daily craft of handing out, limiting and reviewing elevated access. What follows is the set of questions she asked, in the order she asked them. Marisol is a made-up composite, and nothing here describes a real school.

What does AccessOps actually mean for a small training operation?

It is the practice of deciding who may do powerful things in your systems, for how long, and with what record. The Ops Atlas, which is xOps School’s reference catalogue, describes it as the operational side of requested and privileged access. In its own words the term is not an official standard, so treat it as a handy name for practices that already exist: approvals, temporary elevation, vaulted credentials, emergency accounts and periodic reviews.

For a school, powerful things include editing flight-hour totals, changing an aircraft’s status in the dispatch tool, exporting student data and resetting other people’s passwords.

Is that not just a matter of giving people the right roles?

Roles answer a different question. The Atlas separates three ideas: who exists in the system, what each person is allowed to do, and how and when extra access is handed over. Marisol’s roles were tidy. Instructors could see their own students; she could edit the schedule. The messy part was the exceptions. Every time somebody needed something extra for a week, a manager said yes in the corridor and the extra rights stayed forever.

What is the “eligible, not active” idea?

Instead of leaving heavy rights switched on, you let a person qualify for them and switch them on only for a task. Think of an instructor who is rated to sign off a checkride: the rating stays in the wallet, but the authority applies only on the day of the ride. The entry suggests keeping a short record for every grant: the person, the power, the reason, the end date and who approved it. Marisol turned that list into a small form and taped a copy beside her keyboard.

How long should extra access last?

The Atlas offers a rule of thumb by sensitivity. Its most delicate tier is limited to a short stretch of an hour or two, the next gets a few hours more, while routine requests lapse after three to six months unless someone justifies them again. Marisol’s school was small, so she simplified: a few hours for anything that could ground an aircraft on paper, a month for the rest, and an annual look at everything permanent.

She also learned that ending a grant does not always end the work. The entry describes a lab where a terminal session kept running for twenty seconds after its certificate expired. A closing-time chime does not stop a student who is already in the circuit, so she added a step to her routine: when a short grant ends, confirm nothing is still open.

What is the emergency account people keep mentioning?

It is the spare key behind glass. When normal approvals are unavailable, say the one person who can approve is on a long-haul sector, a break-glass account lets the school keep operating. The Atlas insists such accounts stay permanently usable, that there should be at least two, that every use should raise an alarm, and that someone should verify they still work at least once per quarter. Marisol picked two senior staff members to hold the sealed credentials and set a reminder every ninety days to confirm the envelope was intact.

The Atlas also warns against treating the emergency path as a shortcut. A quoted line from AWS describes that habit as something that can be considered a backdoor. If staff reach for the glass every Friday because approvals feel slow, the real problem is the approval flow.

Does anybody really get caught out by this?

Big organisations do, and the entry lists a few public examples. A stolen, already-authenticated session at a software company handed an attacker the same token-making rights as the engineer it belonged to, and production access had to be closed to almost everyone afterwards. A telecoms-adjacent social platform saw more than a thousand staff holding account tools that phishers managed to reach. Neither story involves an exotic trick; both involve broad power that lasted longer than the task.

Marisol’s school is nowhere near that size, but the pattern scales down well, and the fix costs mostly attention rather than money. One shared admin login passed around the front desk is the same mistake in miniature.

What did she do first?

Her first fortnight looked like this:

  1. Listed everyone who could edit training records or aircraft status, and found two former contractors still on it.
  2. Removed rights nobody could justify, writing the reason in a shared note.
  3. Set up temporary elevation for the owner and the chief instructor, with a stated reason each time.
  4. Created the two emergency logins and tested one in front of the owner.
  5. Diarised a review every quarter and a deeper one each year.

The Atlas frames a similar journey as thirty, sixty and ninety day stages: first inventory the most sensitive access and rehearse the emergency path, then pilot time-limited eligibility with a reason attached, then add dual approval and recording for the highest tier.

Where do the rest of the school’s habits fit in?

Good access hygiene sits alongside everything else a student pilot learns about discipline. If you are new to the training side, our write-up on how student pilots can study weather without drowning in charts shows the same preference for small, repeatable routines, and the walkthrough of ways to accumulate logged hours in a sensible order pairs naturally with record-keeping you can trust.

Where can she read more?

Marisol bookmarked the full AccessOps entry in the Ops Atlas, which goes much deeper into tiers, review cycles and the pitfalls of automation than a school needs on day one. Her favourite takeaway was modest: for any powerful login, be ready to explain its purpose, its end date and which person would spot misuse.

Six months later the owner asked the old question again. This time the answer fit on one page, and the page had dates on it.