MODULE 02 · Onboarding · 50 MINUTES
Workspace access and information stewardship
Learn the principle. Practice the work. Preserve what you learn.

Your learning goals
- Use the established onboarding and workspace destinations.
- Classify information before creating or moving it.
- Prepare a practical access and file-handling record.
Preparation
Enter through the established pathway
Begin with the existing Welcome Hub and the approved internship onboarding destination. Use your assigned identity and the access granted for your actual role. Access is specific to a person, organization, system, and task; a working link alone establishes none of these permissions. Read the instructions supplied within the assigned environment and resolve access problems through the designated program channel. Record the resource name, intended task, observed access state, and useful next step. Keep access requests focused on the work you need to complete. The learning exercises in this curriculum use fictional, public, or synthetic information so progress can continue while an assigned access question is resolved.
Classify the information before using it
For each input, record its origin and intended handling. Useful categories are public source material, organization-owned working material, licensed material, participant-supplied material, and restricted operational information. These categories describe handling needs; actual permissions come from the governing source and assigned workflow. Keep participant information inside the authorized program environment and use the minimum information necessary for the assigned purpose. Use synthetic records for training, screenshots, prototypes, and portfolio examples. A name removed from a detailed story can leave the person recognizable. Examine dates, locations, rare experiences, and combinations of attributes before deciding that an example is suitable to share.
Make files understandable and recoverable
Use the project’s existing folder structure, naming convention, and version history. Where the assignment has no established convention, a clear proposed filename contains the project, artifact, version, and date. Keep the editable source connected to any distribution copy and record the authorized destination. Preserve citations, rights information, and source evidence alongside the work while maintaining their appropriate access. Before submitting a link, open the intended version and test the destination using your authorized access. Report whether the record was created, saved, submitted, or published according to observed evidence. A screenshot of a success message can supplement a saved record, while the actual saved item remains the source of truth.
Worked example
Worked example: access issue with useful progress
Synthetic situation: an intern can read the Q45 mission page but receives an access message for an assigned project folder. The intern records the folder label, attempted action, time, and exact visible error without including credentials. The next action is a focused access request through the existing program channel. Meanwhile, the intern drafts a source table using public references and fictional exercise records. The submission states “draft prepared; project-folder access pending.” The intern avoids describing the draft as saved in the shared project until a successful save is observed.
Your practical assignment
Build a workspace and information map
- List the Welcome Hub, approved onboarding destination, assigned project environment, and current submission route.
- For six fictional inputs, classify the information, purpose, permitted destination, and access needed.
- Create three descriptive versioned filenames and explain how source and distribution copies relate.
- Write an access issue record and a safe independent next action.
Evidence to prepare
- A workspace map with observed access states.
- A six-row information-handling table.
- A versioning example and one access issue record.
Assignment scoring guide
Use these criteria for self assessment and feedback. Each criterion contributes 25 points to the 100-point assignment rubric.
| Criterion | Points | Evidence |
|---|---|---|
| Destination accuracy | 25 | Canonical links remain exact and assigned destinations are verified or labeled pending. |
| Information judgment | 25 | Classifications consider provenance, purpose, sensitivity, and access. |
| Version clarity | 25 | Files and copies are distinguishable and recoverable. |
| Practical recovery | 25 | The access record supports a concrete, appropriately scoped next step. |
Reflection
- Which types of information in your assignment require the most careful handling?
- How will another contributor identify the current source version?
Scoring and revision guidance
Evidence is absent or cannot be assessed.
Limited evidence; substantial guidance and revision are needed.
Partially demonstrated; a material element needs revision.
The essential requirement is met; minor corrections remain.
Complete, accurate, traceable, and usable evidence for the criterion.
Review the explanation for each missed question, revisit the relevant lesson, and retry. Revise practical work against the rubric and document the change.
Connected learning
Knowledge into practice
Answer all five questions, then view the explanations. Practice target: 80%. Revisit any lesson and try again.
Preserve your work
Sign in in a new tab for saved learning. Return to this tab to continue your work and save.
Each save creates a dated record. Keep a copy in your approved project workspace until the saved confirmation appears. Sensitive personal, clinical, donor, and participant records belong in their designated systems.