OpenCyber AcademyLesson map
Lesson 13 published. Map, example, EX067.
flowchart TD
B["Saturday queue at the second café"] --> C["Someone asks for the old shared till code"]
C --> R["Refuse. Separate logins stay"]
R --> L["Lock the screen when stepping away, on this shift too"]
The habit was written for busy moments, not for quiet ones.
Logical drawing
habit already set
separate till logins, not one shared code
lock the screen when stepping away
Saturday, second café, queue at the door
|
+-- "only this shift" is the exception the habit forbids
+-- a borrowed login attributes sales to the wrong person
+-- this lesson does not issue a new login on the spot
Learning outcomes
After this chapter, you should be able to:
- Refuse a one-shift return to the shared till code.
- Keep screen-locking in force during a queue.
- Hold any new login until it is that person's own, not a borrowed one.
13.1 The queue is the case the habit was for
Kwame replaced the shared till code with separate logins, and he told staff to lock the screen when they step away. On a Saturday the second café is queued to the door. A colleague asks for the old code "only until the rush ends," because finding a personal login feels slow. The rush is when a borrowed session does the most harm: a void, a refund or a card report would sit under someone else's name. Kwame refuses the old code. If a person has no login yet, they do not inherit a colleague's. Creating one is a separate step, not a shout across the counter. This lesson does not create that login.
13.2 Worked example
Lesson table; scroll horizontally to read all columns →
| Request during the queue | What the record would show | Decision |
|---|---|---|
| "Use the old shared code for an hour." | One code, many people | Refuse |
| "I will finish this order on the screen the other person left open." | Sales under someone else's login | Refuse the borrowed screen |
| Lock the screen, then unlock one's own login | The habit, on a busy Saturday too | Accept |
| "Write me a personal login after the rush." | A later account, not this sale | That waits. This lesson does not issue it |
Synthetic case. The colleague at the second café is unnamed. The example refuses a borrowed screen and adds no person to the staff file.
Errors and limits
A refusal at the counter does not open an account. A personal login still needs the owner's agreement and a notebook line before that person works the till alone. This chapter also does not divide the twelve staff between the two cafés.
Apply
- EX067 — Only this shift. Saturday at the second café, the queue reaches the door. A colleague asks for the old shared till code "until the rush ends," and also asks to finish an order on a screen another person left unlocked. What do you refuse, and what is not created here?
Show marking criteria
Rubric: 3 = refuse the old shared code and the borrowed unlocked screen; a new personal login is not created across the counter;; 2 = refuse both, and do not issue a login on the spot;; 1 = one of those;; 0 = none.