Nobody self-serves here. An operator invites an address and decides its seat before the account exists, so an account that arrives on its own reaches no engagement at all and every page it opens is empty. That is the product working, and it is a poor way to look at a build.
These two seats are already in the world: five engagements, one live discovery session, briefs with version history, and fourteen months of sessions behind the charts. The companies are invented and so are the people; the records are real rows, produced by the same pipeline a real session writes through.
The full book of business. Start here.
The same build, from one client’s chair.
Both passwords are the same, and both are published on purpose. They open a demo world of five fictional companies and nothing else; the keys that matter never leave the server.
Then sign out and come back as Marguerite. One engagement, no admin area, nothing else in the database visible to her: the isolation is a database policy, not a hidden menu.
The seats above are seeded identities in a seeded world, provisioned by this build's own seed script. Signing in as one is an ordinary sign-in: the app holds no demo mode, no bypass and no address it treats specially. When Autolace carries a real client, the seed and these identities are deleted together and this page goes with them.
The rest of the product is where it says it is: documentation explains how a session runs and what a brief owes, and support reaches a person.
Every engagement in this build is walled off to the people attached to it, in the database itself, so an anonymous reader matches nothing. A list here would have to be invented, and an invented list is the one thing this product will not put on a screen. Sign in with a seat above and this becomes what that seat can actually reach.