Design a Secure Internal Employee Self-Service Portal
Design a portal where employees start onboarding, reset a password, ask for restricted information and raise IT support requests, with every request checked, every read of a confidential report recorded, and each workflow released on its own.
Problem statement
For this exercise, assume a large financial firm with about 30,000 employees wants one online portal for four everyday tasks. Each task is handled by its own part of the system, any part can be released on its own, and the confidential information the portal holds must stay protected. Design the portal.
The firm already runs an identity system. That system signs employees in, keeps their accounts and passwords, and knows whether each employee is active, locked or has left. The portal is new. It has four workflows, each run by a different team: - Onboarding. HR starts a checklist for a new hire.
Each step has one owner (the new hire, their manager, or a team such as IT) who marks it done. The checklist is finished when every step is done. - Password reset. An employee who cannot sign in asks for a reset and proves who they are with a one-time code sent to a contact the firm already holds.
A correct code lets the identity system issue a one-time link for choosing a new password. This is the only workflow used by someone who is not signed in. - Information requests. An employee asks for a restricted document, such as a financial report. The owner of the document approves or refuses the request.
If it is approved, the employee may read the document for a limited time. - IT support requests. An employee opens a request, an IT agent takes it, they add comments for each other, and the agent closes it.
Also assume all of this is confidential: the reports are financial records, and the onboarding checklists hold personal details. Every request must be checked for who is calling and what they may do before it has any effect, and every input must be checked before it is used.
Every change in any workflow, and every read of a confidential report, must be recorded in a trail that cannot be altered afterwards and is kept for seven years. A workflow that is down, or being released, must not stop the other three. Assume one region.
The identity system's inner workings, file attachments, and the loss of a whole region are out of scope.
What to build
- HR starts an onboarding checklist for a new hire, each step's owner marks it done exactly once even if they send it twice, and HR and the new hire can always see which steps remain.
- An employee who cannot sign in proves who they are and gets a one-time, expiring way to choose a new password, and the portal never reveals whether an employee account exists.
- An employee asks for a restricted document, its owner decides the request once, and an approved employee can read the document only for a limited time, with every read recorded.
- An employee opens an IT support request, an IT agent takes it, both add comments, and the agent closes it, and only the requester and IT agents can see it.
At scale
- For this exercise, assume about 30,000 employees and up to 300 requests a second across the four workflows in the busiest minute, mostly reads, and assume each workflow must be available 99.9 percent of a month.
- For this exercise, assume 95 percent of requests are answered within 500 milliseconds, and that working out who is calling and whether the input is valid may use at most 50 milliseconds of that.
- For this exercise, assume an employee who leaves the firm, or whose account is locked, must lose all access within 1 minute, even if they hold a sign-in that has not yet expired.
- For this exercise, assume each workflow is released on its own several times a week, no request may fail because of a release, and a bad release must be undone within 5 minutes.