File Upload & Scanning Pipeline  ·  View 03 of 21  ·  People and journeys

Actors and Their Core Journeys

Nine actors, three of them machines, and the one whose experience is the design centre.

Editable source SVG draw.io All views
The people who upload Workspace member 40 M monthly Goal — Drop a file into a conversation and have it simply be there for the people I am talking to. Core journeys Attach a file to a chat Share a folder of photos Re-download it on another device Heavy-media creator p99 object 240 MB Goal — Get a 40 GB edit uploaded from a hotel network without starting again every time the lift eats the signal. Core journeys Upload a 40 GB master Resume after a dropped link External submitter unauthenticated intake Goal — Send my CV to a company that has never heard of me, and be told it arrived. Core journeys Submit a document to a form See that it was accepted The people who answer for it Tenant security admin 12 tenants Goal — See what was blocked in my tenant, and release the one file my finance team swears is a spreadsheet. Core journeys Review and release a block Set scope policy and ceilings Platform security analyst 24×7 rota Goal — Pull the actual sample for a detection without the sample ever reaching anything that could run it. Core journeys Break-glass read of evidence Force a corpus re-scan on new intel Platform SRE on call Goal — Know the scan backlog is growing before members start asking why attachments say scanning. Core journeys Watch oldest-unscanned age Shed a lane under load Machines that are also users Desktop sync daemon background lane Goal — Push a thousand small files without being throttled into next week, and without starving a human. Core journeys Bulk-sync a changed folder Tenant migration job bulk lane Goal — Move 8 TB of a customer's legacy share in a weekend, scanned, with no latency promise at all. Core journeys Bulk import a legacy share Re-scan scheduler signature-triggered Goal — Re-judge everything recent when the signature set moves, inside the cold-read budget. Core journeys Re-scan the recent corpus Actors and Their Core Journeys Person or role Journey / task External / third party Security / platform v 1.0 · note volumes are stated assumptions

Decisions

  • The workspace member is the design centre: every other actor's work may cost them cost or capacity, none may cost them perceived latency on a small file
  • The tenant security admin is a first-class user, not an admin afterthought — the quarantine console is a product surface with its own latency and clarity targets
  • Machines are actors with lanes: the sync daemon and the migration job get admission limits and failure paths exactly as a human journey does, which is what stops a weekend migration starving a Monday attachment

The actor most designs omit

  • The external submitter — a stranger uploading to a form — has no account, no history and no reason to be trusted, and is the single most likely source of a malicious object
  • Serving them well and trusting them least at the same time is the requirement that produces the two-plane storage split
  • The re-scan scheduler is also an actor: it is the only one whose job is to disagree with a decision the platform already made

Stated assumptions

  • Volumes are assumed for a 40 M MAU collaboration SaaS, not measured
  • Twelve product tenants, each with its own destination scopes and policy
  • A 24×7 platform security rota exists and owns break-glass