Chapter 16 — Shared workstations

Chapter 16 — Shared workstations

Lesson map

Lesson 16 published. Map, example, EX046.

flowchart TD
  N0["Learning outcomes"]
  N1["16.1 The reception problem"]
  N2["16.2 Fast individual sign-in"]
  N3["16.3 Balancing needs"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4
  N4 --> EX["Worked example"]
  EX --> Q["Exercise EX046"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["16.1 The reception problem"]
  N2["16.2 Fast individual sign-in"]
  N3["16.3 Balancing needs"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX046"]

[Learning outcomes]
    |
    v
[16.1 The reception problem]
    |
    v
[16.2 Fast individual sign-in]
    |
    v
[16.3 Balancing needs]
    |
    v
[Synthesis]
    |
    v
[Worked example] --> [Exercise EX046]

Learning outcomes

You will (1) explain shared device risks; (2) design fast individual sign-in; (3) balance speed and accountability.

16.1 The reception problem

Reception desks are busy: several staff use one workstation in a shift, often with a client waiting. Historically Fernhill used one shared sign-in, so every booking change showed the same name. When a client complained about a wrongly cancelled appointment, nobody could tell who made the change. Shared sign-in also means a leaver's knowledge of the shared password survives their departure. Kai treats the reception problem as both an accountability issue and an access issue. He discusses the problem with reception staff first, who agree it frustrates them too.

16.2 Fast individual sign-in

Kai trials individual accounts with fast user switching and a tap of a staff badge or a short PIN plus a registered device. Sign-in takes a few seconds, and the screen locks automatically after two minutes idle. The booking system, connected through single sign-on, then records each change under the right name. Staff at the north clinic test it for two weeks and report that it is barely slower than the old shared account, which helps adoption elsewhere. Staff badge registration is added to the joiner runbook.

16.3 Balancing needs

Some staff worry about being locked out mid-task. Kai sets the idle lock to two minutes at reception but ten in consulting rooms, where vets are often away from the screen while examining an animal yet the room is not public. He documents the reasons for each setting. Security that ignores how work is done gets bypassed, for example by propping open sessions, so fitting settings to each area produces better real protection. He reviews the settings after three months with clinic managers, and adjusts them where staff report problems.

Worked example

Individual reception sign-in is trialled at the north clinic for two weeks and rolled out; idle lock is 2 minutes at reception and 10 in consulting rooms.

Synthetic case. Clinics and settings are synthetic.

Errors and limits

Imposing very short lock times everywhere encourages staff to defeat them.

Exercises

• EX046 — Complaint issue. What could not be determined after the cancellation complaint? Rubric: 3 = who made the change;; 2 = who;; 1 = when;; 0 = none.
• EX047 — Lock settings. What idle lock times were set? Rubric: 3 = 2 minutes reception, 10 consulting rooms;; 2 = two and ten;; 1 = one;; 0 = none.
• EX048 — Trial clinic. Where was the trial run? Rubric: 3 = north clinic;; 2 = north;; 1 = east;; 0 = none.

Synthesis

Fast individual sign-in on shared devices gives accountability without slowing busy staff.

Continue studying — chapter 16 of 30

← Chapter 15 (draft) · Course chapter index · Chapter 17 (draft) →