Lesson video coming soon. The player below contains a sample video, not this lesson. You can use the written lesson and slide guide now.

Open video on YouTube ↗

Download slide guide (PDF)10 pages · 4.1 MB

Work through the lesson

Use these explanations alongside the slide guide. Expand any section to read its full explanation.

Before the demonstration

• Your assigned responsibility
• The correct training record
• Evidence of the result

Today’s outcome
Account identity and operational reporting scope are correctly distinguished.

Read the full explanation

Before we begin, check these prerequisites: C01; approved fictional users, roles and unit design. The intended outcome is: Account identity and operational reporting scope are correctly distinguished. Keep a note of the training identity and date so that you can recognize the result. We will pause before any action that your role or the exercise does not authorize.

Account and staff links

• Open Admin > Users and create/edit the approved training account with active status, role and linked staff IDs

In this step
Review the account identity, active status, assigned roles and linked Staff IDs as separate fields. A staff link affects whose work the account represents. It should match the approved onboarding record.

Read the full explanation

Open Admin > Users and create/edit the approved training account with active status, role and linked staff IDs. Review the account identity, active status, assigned roles and linked Staff IDs as separate fields. A staff link affects whose work the account represents. It should match the approved onboarding record. I will pause here so you can identify the control or result that tells us where we are in the workflow.

Account changes

• Review identifiers and roles before saving
• reset password or deactivate only with authority

In this step
Check the proposed changes before saving. Password reset and deactivation belong to authorized account administration. Existing users should not become disposable training examples just because their records are convenient to open.

Read the full explanation

Review identifiers and roles before saving; reset password or deactivate only with authority. Check the proposed changes before saving. Password reset and deactivation belong to authorized account administration. Existing users should not become disposable training examples just because their records are convenient to open. I will pause here so you can identify the control or result that tells us where we are in the workflow.

Bulk onboarding

• For bulk onboarding export/use the supported CSV format, upload and inspect preview, then confirm validated training rows

In this step
Use the supported format and inspect every preview error before confirmation. Duplicate identities and invalid links need correction at the source. Confirm only validated fictional rows in the approved exercise.

Read the full explanation

For bulk onboarding export/use the supported CSV format, upload and inspect preview, then confirm validated training rows. Use the supported format and inspect every preview error before confirmation. Duplicate identities and invalid links need correction at the source. Confirm only validated fictional rows in the approved exercise. I will pause here so you can identify the control or result that tells us where we are in the workflow.

Unit relationships

• As organization.manage holder open Admin > Units, create/edit the unit and assign members and eligible supervisors/managers

In this step
Unit membership and supervisor or manager relationships help determine visibility. Those assignments require eligible roles and organization-management authority. Account-security administration alone does not automatically grant unit administration.

Read the full explanation

As organization.manage holder open Admin > Units, create/edit the unit and assign members and eligible supervisors/managers. Unit membership and supervisor or manager relationships help determine visibility. Those assignments require eligible roles and organization-management authority. Account-security administration alone does not automatically grant unit administration. I will pause here so you can identify the control or result that tells us where we are in the workflow.

Visibility verification

• Inspect visibility preview and verify representative allowed/denied report access with training accounts
• deactivate referenced units rather than deleting them

In this step
Use the visibility preview and representative sessions to verify the result. Test an allowed report and a boundary the account should not cross. Keep referenced units in their supported lifecycle rather than deleting history to simplify the exercise.

Read the full explanation

Inspect visibility preview and verify representative allowed/denied report access with training accounts; deactivate referenced units rather than deleting them. Use the visibility preview and representative sessions to verify the result. Test an allowed report and a boundary the account should not cross. Keep referenced units in their supported lifecycle rather than deleting history to simplify the exercise. I will pause here so you can identify the control or result that tells us where we are in the workflow.

Common problems

• Treating display name as staff ID
• assigning a role without unit relationship
• changing canonical units through attendance free text
• deleting a referenced unit

A useful support report
The task and record
The expected result
The actual message
The authorized next step

Read the full explanation

Let us consider the mistakes that can disrupt this workflow. Treating display name as staff ID; assigning a role without unit relationship; changing canonical units through attendance free text; deleting a referenced unit. Describe what you expected and what the application actually showed before choosing a remedy. Preserve the relevant record and error. The role responsible for a review or configuration change should make that decision. Do not borrow broader access simply to finish the exercise.

Guided practice

• Onboard a fictional account with one staff link and verify it; admin additionally assigns the unit relationship and checks visibility preview
• Demonstrate duplicate/invalid import as an exception

Evidence to show
The correct training case
The result or permitted decision
Your explanation of the next step

Read the full explanation

Now it is your turn. Onboard a fictional account with one staff link and verify it; admin additionally assigns the unit relationship and checks visibility preview. Demonstrate duplicate/invalid import as an exception. Work within the assigned training role. When you finish, show the result and explain which identity and date it belongs to. If the exercise includes a restricted action, explain the decision and its authorized owner rather than carrying it out without approval.

Practice debrief

• Correct context and permitted action
• A result you can trace
• A clear next step if blocked

Expected result
Account identity and operational reporting scope are correctly distinguished.

Read the full explanation

The expected outcome is: Account identity and operational reporting scope are correctly distinguished. Walk me through the record you used and the result you found. Explain these workflow checkpoints in order: Open Admin > Users and create/edit the approved training account with active status, role and linked staff IDs. Review identifiers and roles before saving; reset password or deactivate only with authority. For bulk onboarding export/use the supported CSV format, upload and inspect preview, then confirm validated training rows. As organization.manage holder open Admin > Units, create/edit the unit and assign members and eligible supervisors/managers. Inspect visibility preview and verify representative allowed/denied report access with training accounts; deactivate referenced units rather than deleting them. For an exception, name the evidence you would preserve and the person with authority to take the next action.