{"id":1146,"date":"2026-11-14T14:40:00","date_gmt":"2026-11-14T14:40:00","guid":{"rendered":"https:\/\/flyaiaa.com\/blog\/?p=1146"},"modified":"2026-11-15T04:40:00","modified_gmt":"2026-11-15T04:40:00","slug":"identityops-academy-account-models","status":"publish","type":"post","link":"https:\/\/flyaiaa.com\/blog\/identityops-academy-account-models\/","title":{"rendered":"IdentityOps for Flight Academies: Three Account Models Compared"},"content":{"rendered":"<p>Aviation academies operate several systems at once: a scheduling platform, a learning portal, a maintenance log, an email suite and a payments tool. Whoever runs the technology side eventually has to choose how accounts are created and removed across all of them. Broadly, there are three working models, and each carries trade-offs. This comparison sets them side by side, using the vocabulary of IdentityOps, the discipline concerned with which accounts exist and how each proves it. The aim is to help an academy pick a model deliberately rather than inherit one by accident.<\/p>\n<h2>The yardstick: what the Atlas says good looks like<\/h2>\n<p>A fair comparison needs criteria. A publication from xOps School called the Ops Atlas supplies them in its <a href=\"https:\/\/www.xopsschool.com\/identityops\/\">overview of the IdentityOps field<\/a>. Reading across its sections, five criteria stand out: whether account changes are driven by the personnel record, whether removal reaches every application, whether sign-in strength is measured by use rather than enrolment, whether recovery follows a written script, and whether machine accounts have owners. The Atlas also cautions that the term is young, so treat these as the editors&#8217; working view rather than a universal standard.<\/p>\n<h2>Model A: manual accounts, managed by whoever is nearby<\/h2>\n<p>In the first model, each application has its own administrator who creates logins on request. A new instructor is set up in the scheduling tool by one person, in the learning portal by another, and in email by a third. Removal follows the same pattern: someone remembers, or someone does not.<\/p>\n<p><strong>Strengths.<\/strong> It requires no integration, no licence upgrades and no central expertise. For an academy with a handful of staff and two applications, it can work for years.<\/p>\n<p><strong>Weaknesses.<\/strong> There is no single list. Reconciling accounts means asking every administrator for an export, and nobody has the incentive to do it. Removal is the weak point: the Atlas names the pattern in which an account is disabled in one place and lingers elsewhere as one of its anti-patterns. Measurement is nearly impossible, because there is no timestamp trail.<\/p>\n<p><strong>Fits<\/strong> very small academies, provided they keep a written roster and review it quarterly.<\/p>\n<h2>Model B: central sign-in with just-in-time account creation<\/h2>\n<p>The second model adopts single sign-on. Staff and students authenticate through one central service, and each application creates an account the first time somebody signs in. It feels modern: no one has to create anything by hand.<\/p>\n<p><strong>Strengths.<\/strong> Sign-in strength can be enforced in one place, so a hardware-bound key policy applies across the stack. Onboarding is smooth.<\/p>\n<p><strong>Weaknesses.<\/strong> The Atlas points out an asymmetry. Creation at first login has no matching channel for removal. When someone leaves and the central account is disabled, the application account created earlier may continue to exist, and any open session may continue to work. The Atlas mentions one container-software vendor whose documentation favours SCIM provisioning with first-login creation switched off, precisely to close that gap. In a comparison, this model scores high on convenience and low on offboarding certainty.<\/p>\n<p><strong>Fits<\/strong> academies that accept the convenience and add a separate removal process, for example a periodic export from each application checked against the staff list.<\/p>\n<h2>Model C: personnel-driven provisioning with standard protocols<\/h2>\n<p>The third model treats the personnel record as the starting point. A hire, role change or departure in that system flows to a central directory, which pushes changes to applications through SCIM, the provisioning standard, and sign-in is federated through SAML or OpenID Connect.<\/p>\n<p><strong>Strengths.<\/strong> One source drives everything, timestamps are naturally captured, and sessions can be cancelled as part of the leaver sequence. The Atlas sets out that sequence: personnel termination, central disablement, session and token revocation, an inactive flag pushed to each application, and logged times.<\/p>\n<p><strong>Weaknesses.<\/strong> Cost and fine print. The Atlas observes that personnel-driven provisioning in one major directory product requires a paid tier, that lifecycle automation can require a further suite, and that many applications reserve SCIM for higher plans. There are behavioural quirks too. The provisioning specification does not say what an inactive flag must do inside an application, so each product decides, one identity provider never sends deletion requests while another does under certain conditions, and the order in which an administrator unassigns a user and triggers a push can leave an account enabled until the final push completes. Plan on testing every application rather than trusting the brochure.<\/p>\n<p><strong>Fits<\/strong> larger academies, or smaller ones where staff turnover is high and manual steps are an ongoing risk.<\/p>\n<h2>A side-by-side summary<\/h2>\n<ul>\n<li><strong>Accuracy of the roster.<\/strong> A is low, B is moderate, C is high.<\/li>\n<li><strong>Removal reaching every application.<\/strong> A depends on memory, B has no built-in route, C is designed for it.<\/li>\n<li><strong>Cost and effort.<\/strong> A is cheapest, B is moderate, C is highest.<\/li>\n<li><strong>Ease of measuring leavers end to end.<\/strong> A is hard, B needs extra exports, C is straightforward.<\/li>\n<li><strong>Machine accounts.<\/strong> None of the three solves these; each needs its own register.<\/li>\n<\/ul>\n<p>The last line matters. The Atlas treats non-human identities as a separate lifecycle with inventory, ownership, short-lived credentials, rotation and staged retirement, regardless of how human accounts are provisioned.<\/p>\n<h2>A worked scenario: the seasonal examiner<\/h2>\n<p>Consider an imaginary academy that engages a visiting examiner for three weeks each season. Under Model A, the examiner receives a login in the scheduling tool and another in the learning portal, each created separately. Three weeks pass, the examiner leaves, and the two administrators each assume the other will deal with it. The accounts survive into the next season, which at least saves some setup time but leaves two live logins for a person with no current role.<\/p>\n<p>Under Model B, the examiner signs in through the central service and accounts appear automatically. At the end of the engagement, the central account is switched off. The scheduling account stays behind in a dormant state, and it would be caught only by a dormant-account sweep with a window of several months. Under Model C, the contract end date in the personnel system triggers removal, and a log shows when each application confirmed. The same event, three outcomes, and the difference is entirely in the design of the removal path.<\/p>\n<p>The scenario is invented, yet it mirrors the pattern the Atlas describes as an anti-pattern: treating a disabled central account as proof that the person is gone. Anyone comparing models should ask each one the same question, which is what happens to the examiner on the final day.<\/p>\n<h2>Cross-cutting factors that decide the outcome<\/h2>\n<h3>Sign-in strength<\/h3>\n<p>Any of the three can enforce hardware-bound keys, but only the centralised models do it uniformly. The Atlas recommends sequencing: administrators first, staff with email, remote access or payment access second, everyone else last. It also notes that synchronised passkeys do not reach the top assurance tier because their keys can be exported, which matters for roles with the highest exposure.<\/p>\n<h3>Recovery<\/h3>\n<p>The model of provisioning does not change the need for a written recovery script. According to the Atlas, the safest pattern is self-service first, assisted recovery only after a manager confirms the person in person or on live video, and a notification after every event. Public advisories about help-desk-driven resets are the reason.<\/p>\n<h3>Skills<\/h3>\n<p>Models B and C need someone comfortable with protocols and scripting. Academies that cannot hire that skill can still build it, and resources such as <a href=\"https:\/\/flyaiaa.com\/blog\/your-complete-guide-to-mastering-tech-careers-with-devopsschool\/\">a guide to mastering technology careers through a training school<\/a> or <a href=\"https:\/\/flyaiaa.com\/blog\/enterprise-software-engineering-and-cloud-operations-roadmap-for-japan\/\">a roadmap for enterprise engineering and cloud operations<\/a> sketch learning paths that cover the underlying automation skills.<\/p>\n<h2>Which to choose<\/h2>\n<p>The decision follows size and turnover. An academy under about a dozen staff with two or three applications can stay with Model A if it writes the roster down and schedules a quarterly check. One with growing application count should move to Model B only with a compensating removal routine. One facing frequent turnover, seasonal instructors or external examiners should plan toward Model C and budget for the licence tiers.<\/p>\n<p>Whatever the choice, adopt the Atlas&#8217;s measurement habit: report leaver completion across all applications, not just at the central service, and keep a short written log of each exercise. The Atlas also advises against purchasing a governance suite before the personnel data is clean, which applies to all three models. Fix the data first, then decide how much automation you can justify.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A precise comparison of three ways an aviation academy can run accounts: manual, just-in-time sign-in and personnel-driven provisioning, judged by IdentityOps criteria.<\/p>\n","protected":false},"author":6,"featured_media":1147,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[634],"tags":[],"class_list":["post-1146","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-flight-training-tech"],"_links":{"self":[{"href":"https:\/\/flyaiaa.com\/blog\/wp-json\/wp\/v2\/posts\/1146","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/flyaiaa.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/flyaiaa.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/flyaiaa.com\/blog\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/flyaiaa.com\/blog\/wp-json\/wp\/v2\/comments?post=1146"}],"version-history":[{"count":1,"href":"https:\/\/flyaiaa.com\/blog\/wp-json\/wp\/v2\/posts\/1146\/revisions"}],"predecessor-version":[{"id":1240,"href":"https:\/\/flyaiaa.com\/blog\/wp-json\/wp\/v2\/posts\/1146\/revisions\/1240"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/flyaiaa.com\/blog\/wp-json\/wp\/v2\/media\/1147"}],"wp:attachment":[{"href":"https:\/\/flyaiaa.com\/blog\/wp-json\/wp\/v2\/media?parent=1146"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/flyaiaa.com\/blog\/wp-json\/wp\/v2\/categories?post=1146"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/flyaiaa.com\/blog\/wp-json\/wp\/v2\/tags?post=1146"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}