Admin stays with Rosa and Mia

Lesson map

Lesson 19. Map, example, EX065.

flowchart TD
  A["Staff role: view and pack"] --> B["Not prices, not payment settings"]
  B --> C["Admin remains Rosa and Mia"]
  C --> D{"Does the book record a lockout?"}
  D -->|No| E["Keep the check, and keep the pair"]

Checking each sign-in is how the change stays reversible. It is not a record that someone was locked out.

Logical drawing

staff may
    view orders
    pack orders
staff may not
    change prices
    change payment settings
admin, in the narrative
    Rosa and Mia, each with a second step
account tuple, still
    Rosa, Mia
not recorded
    a lockout
    the name of a busy day

Learning outcomes

After this chapter, you should be able to:

1. Separate the staff role from admin.
2. Keep Rosa and Mia as the admin pair.
3. Leave payments with Rosa, and leave any lockout unrecorded.

19.1 Fewer admins is the control. The pair is named, and the day is not.

Authorisation is what a person may do after signing in. Giving everyone admin breaks that idea, which is why most staff need only to view orders. Week four makes the limit concrete: the staff role can view and pack, and it cannot change prices or payment settings. Only Rosa and Mia keep admin, and the narrative says both have a second step. The account tuple still reads "Rosa, Mia". Dropping Mia because she is a learner, or adding the other staff because they now have logins, would rewrite either the tuple or the role. Payment settings stay inside the changes Rosa must do herself. Mia checks each sign-in before she moves on, so a busy day does not become a lockout. The book does not say that anyone was locked out, and it does not name the day. The check is a precaution that was followed. It is not an incident report. A note that grants the staff role the right to change prices, or that says the busy day ended in a lockout, adds an event the file does not contain.

19.2 Worked example

Say what the role can do, then stop at the boundary the chapter drew.

Lesson table; scroll horizontally to read all columns →

Synthetic case. No order is packed in this lesson. The busy day stays undated.

Errors and limits

A careful sequence can still be told without a casualty. The absence of a lockout is not permission to skip the check.

Apply

• EX065 — Who may change a price? The staff role views and packs orders. Admin stays with Rosa and Mia, and Mia checks each sign-in before moving on. May the staff role change prices, and was anyone locked out?
  Show marking criteria

  Rubric: 3 = the staff role may not change prices or payment settings; admin stays Rosa and Mia; no lockout is recorded; payments stay Rosa's;; 2 = the role stays narrow and no lockout is added;; 1 = the pair only;; 0 = none.