In HR software, an employee's view is often opened by someone else: a manager who approves, an assistant who enters a director's leave, an administrator looking for a setting. Lucca has handled this case since its first products through impersonation: you pick an employee and the screen becomes theirs, with no separate administration view. In 2025 the suite had eighteen products, each with its own team, and the mechanism was applied everywhere without any written rule saying what it requires. I had seven days to write one.

The inventory

Fifteen screenshots from the Lucca suite, shrunk and blurred
  • Leave
  • Expense reports
  • Timesheets
  • Reviews
  • Objectives
  • Skills
  • Training
  • HR file
The starting point of the board: some fifteen screenshots of the screens where a user acts for another, one product after the other. The screenshots show the customer's interfaces with user names: they are shrunk and blurred here, and the list alongside says what they cover.

The same person picker, the same gestures, and from one product to the next, differences nobody had decided: the mode was more or less visible, getting back to one's own screen more or less easy, the page title changed or did not.

The framing, in three sentences

The board notes: the three-line framing, the misuse of the word, the ten interface rules and the expected benefits
The board notes, as they are. On the left, the framing then the interface rules; on the right, what is gained.

Three sentences fix what impersonation is at Lucca, and above all what it is not. The right to impersonate is carried by roles, so there is nothing to invent: the question “who can see for whom” is already settled elsewhere. Impersonating gives read access, and nothing else. The audit trail does not depend on the mode: it is handled by permissions and stays independent.

My first note on the subject: the word comes from computing, and it is a misuse of language. In English, to impersonate means to take on someone's identity. Here nobody takes anyone's identity: you look at someone else's screen, and every action stays signed by the person who did it.

What belongs to the interface, what belongs to roles

The board's decision notes: view as belongs to the interface, edit on behalf of belongs to roles, no alternative interface for managers, history as a sub-pattern of the audit trail, the naming rule for menus
“View as”An interface question. This is what the pattern covers.
“Edit on behalf of”A question of roles and permissions. Outside the pattern.
Don'tNo alternative interface for managers. A manager sees what their team member sees, in the same screen, or does not see it.

This split settles most of the cases the teams were asking about. If the question is “can I act in someone's place”, the answer is in the roles. The history of what was done for someone becomes a sub-pattern of the audit trail, not a feature of impersonation.

Ten interface rules

  1. Use the space on focus.
  2. Show the mode more clearly.
  3. Return to the normal state easily.
  4. The audit trail is fundamental for actions.
  5. Transparency about who sees what.
  6. Understand the scope and the permission.
  7. The mode affects the page title.
  8. Link with the workflow: the home is the dashboard, so the start of the workflow.
  9. Only on pages centred on an employee. The HR Core is centred on records, not on the employee: it is excluded.
  10. Name menus after the resource, its status or the action. No more “My leave” when the screen may be someone else's.

The rules are written so that every team in the suite can apply them without me. They say what the interface must be, clear, transparent, easy to leave, without drawing the screen.

What is gained

No more pointless navigation views Simpler navigation Less code Internal support without a test database

The last point is the one support was waiting for: to understand what a customer sees, viewing as them is enough, instead of reproducing their case on a test database.

What we do not know

The board dates from March 2025 and the pattern was handed to the teams. I have no measure of what it has changed since: a pattern is judged over years, by the number of administration screens that never get built. A design file named Impersonation appeared in Lucca's cross-functional team the same year; that it takes up this framing is plausible, not verified.