An account area: which paths to put in at the start

An account area in conversation sounds like a set of screens: profile, orders, documents, employees, settings. In work it is permissions, order states and the question of what a customer sees versus an employee. Draw everything at once and the first version never finishes. Draw only a profile and people do not understand why they should sign in.

What to keep in the first version

• Sign-in and access recovery. Without that the other screens do not exist.
• One finished path: orders, requests or documents. The one the account area exists for.
• A profile with only the fields a person actually changes.
• Roles, if an employee and a customer are already inside. Do not leave one role called "user" for both.
• Postpone: a notification feed, complex permissions with a tick for everything, reports that are still read in a sheet.

The API gets the same boundaries as the screen. Hiding a section while leaving a method that returns someone else's order is worse than honestly postponing the section. A log of sign-in and export is worth putting in now: later it gets bolted onto a history that is already full of holes.

Lexora designs an account area from the path, not from a map of every future menu item. What did not fit stays a list for the next queue.