A new client, end to end: contract → client & buildings → people → knowledge → SOPs. The contract goes through the same three-read review as always; KB answers feed greet and swept; every SOP is approved per building by a human. Nothing here activates a model, emails a client, or invites anyone.
Sign in
1 · The contract
Upload the management agreement (PDF). It gets three independent reads, lands as a draft model, and waits in the Models console for your review — a contract never activates itself. Already uploaded it? Skip ahead.
2 · Client & buildings
Pick the client (or create them), then tick the buildings they hold. Buildings another client already holds are marked — they're never taken silently.
3 · People & access
Who at the client sees what. management = full numbers · site = operations only, zero money · fund = top line. Adding people here never emails anyone — inviting them to the portal is a separate, deliberate act on the Owners screen.
4 · Building knowledge
Everything a team (and greet, answering guests) needs to know about the building. Answer what you can — you can come back. Answers save into the same knowledge base swept and greet read.
5 · SOPs — approved per building
The standard catalogue every building should cover. Tick to approve for this building; add custom SOPs for what only this building needs; pull candidates from Asana if it's connected (they arrive unapproved).
6 · Where things stand
Next (human) steps: review & activate the model in the Models console · invite people to the portal from the Owners screen when you're ready for them to hear from us.