The admin guide
Three settings change how a whole instance behaves. Who it belongs to, the zone its days are measured in, and whether the AI reads what you write. Each has consequences this guide spells out before you change it, and the AI one has a second page for the model and the wording each job runs on.
Where this sitsBetween using the app and running the machine
This guide is the middle of three. The user's guide covers the app itself — the screens and how to work them. The owner's guide covers the machine: deploying, the protections your Claude follows, and what the AI does. This one covers the settings in the app that change how the instance behaves.
In practice that is the Settings screen, which opens onto a page per subject: Account, AI, Sleep, Tasks, Reminders, Areas, Features, Keys and Development, with Statuses sitting under Tasks. The three this guide covers are on Account and AI, and changing your password is on Account too. A fourth page goes deeper on the AI one rather than adding a setting. Some of what these pages describe is backend work instead: fixing a wrongly set-up account, switching AI off for the whole instance. Whoever runs your LifeOps does those, and each page gives the sentence to ask with. Settings holds more than these three. The user's guide covers the rest on its Settings page.
The shape of itOne instance is one person
A LifeOps instance holds one person's life. There is a single login, a single timezone, a single set of areas, and a single journal. That is the whole security model and the whole data model at once. The instance covers what that means when someone else wants in.