IDEALIT Passport
Menu

Passport search

Find a lesson or fix

Type at least two characters.

    Browse help by symptomBrowse all references
    How to start
    Public course previewThis is not your assigned passport. No identity, answers, or completion progress are stored here.How to start your passport
    Guided lesson
    02 / 02About 25 minutesaccess planning

    Plan Handover And Offboarding

    Plan a fictional departure without losing project records or removing access before its replacement works. No real credential or account is changed.

    Where you will workOn this web page
    1. 1Understand
    2. 2Try it yourself
    3. 3Check and submit

    Before you start#

    Offboarding is the planned transfer of work and removal of access when someone leaves. The information and system owners govern those actions. Verify that an authorized successor can continue before you remove access.

    Three dependencies remain in this fictional project: an active job, a useful result in temporary storage, and a project-owned service. A successor needs the reviewed code/environment, approved data and verification instructions. A real exposed credential is an incident: use the incident procedure immediately, not this planned-departure exercise.

    Which dependencies would break if the account disappeared today? Review them before choosing the seven-action order and handling unfinished work.

    Compare your departure sequence

    Inventory; transfer ownership; verify the successor's access and agreed check; close active work and preserve useful temporary results; let the service owner rotate project-owned credentials; remove unnecessary access; record owners, remaining actions and dates. Retention is an owner decision, not blanket deletion.

    Verify the transfer before removing access; record unfinished actions with an owner and date.

    Start the practice

    Practice

    Work through the decisions

    Follow in order

    Steps

    Reason about the fictional departure only. No account, credential, job or real project is changed. Keep unfinished decisions visible with an owner and date.

    1. 01

      Inventory project dependencies

      Read and answer on this web page

      List repositories, durable and temporary data, environments, services, shared credentials, devices, scheduled jobs, documentation, and undocumented knowledge.

      Look forThe inventory covers every project dependency tied to the departing person.

      Explanation and help
      What this means
      Assign an authorized successor.
      Safe recovery
      Keep access unchanged until the inventory is complete.
    2. 02

      Transfer ownership

      Read and answer on this web page

      Move repositories, service ownership, durable data responsibility, and operational knowledge to named authorized people or project-owned accounts.

      Look forNo required asset depends on the departing person's private account or laptop.

      Explanation and help
      What this means
      Verify code, data, and documentation.
      Safe recovery
      Do not remove the departing owner's access yet.
    3. 03

      Verify the handover

      Read and answer on this web page

      Decide what the fictional successor needs to locate and reproduce the agreed check: exact revision, environment, main data copy, command, expected result and limitations. This lesson does not perform that real check.

      Look forThe successor can reproduce the agreed verification command and result.

      Explanation and help
      What this means
      Handle credentials and active work.
      Safe recovery
      Complete the handover before revocation.
    4. 04

      Close active compute and temporary storage

      Read and answer on this web page

      Decide who safely stops or transfers the fictional active job, verifies useful output in durable storage and owns temporary-copy deletion dates. Do not launch or cancel a real job for this exercise.

      Look forNo required output remains only in temporary storage.

      Explanation and help
      What this means
      Rotate shared credentials.
      Safe recovery
      Preserve state and ask the relevant system owner before deletion.
    5. 05

      Rotate shared credentials

      Read and answer on this web page

      Rotate project-owned shared secrets where permitted and remove personal tokens or keys from services. Never ask the departing person to publish a secret.

      Look forRemaining users have valid individually accountable access.

      Explanation and help
      What this means
      Remove unnecessary access.
      Safe recovery
      Escalate privately to the service owner.
    6. 06

      Remove access after verification

      Read and answer on this web page

      Revoke repository, storage, compute, machine, AI-service, and group access according to each system owner's process.

      Look forUnneeded access is removed without deleting retained project records.

      Explanation and help
      What this means
      Record completion and retention decisions.
      Safe recovery
      Do not improvise destructive cleanup.
    7. 07

      Record completion

      Read and answer on this web page

      For the fictional case, choose the correct sequence and decide how each unfinished or retained item is owned and dated.

      Look forEvery completed and unfinished action has an accountable owner and date.

      Explanation and help
      What this means
      Complete the scenarios and run Check my work.
      Safe recovery
      Keep the case open with a named owner for every unfinished action.

    Finish the lesson

    Check and submit

    Answer these 7 questions, then confirm the work you checked.

    To pass: 100% and every safety question. Completion appears after the automatic GitHub check passes.

    01Put the main offboarding phases in the safe order.Safety-critical
    02What dependency must be removed from the project?Safety-critical
    03A departing researcher still owns a running Euler job. What should happen before account removal?Safety-critical
    04Required output exists only on scratch or Blade D:. What comes before cleanup?Safety-critical
    05A project-owned shared credential may have been known by the departing person. What is the safe action?Safety-critical
    06Should offboarding delete every record immediately?
    07One offboarding action cannot be completed today. How is the case recorded?
    Before submitting
    Open my real passport first

    You can check sample answers here. Open your local Passport to check your practice files and submit the lesson.

    Preview onlyYou can try the questions here. This page does not store or submit your answers.
    Need help?Open recovery steps and AI-review guidance

    If Blocked#

    Preserve data and access state while ownership or retention is unclear. Do not perform broad deletion to “clean up.” Use the project handover lab and escalate to the relevant owner.

    Useful references:

    Understand Before Accepting AI Output#

    An agent cannot approve deletion, retention, ownership transfer, or access revocation. The named owner of each system must confirm its own action.