Administrator guide
Connect clients
Connect OpenCircle clients to the intended Server and prove the account works.
Deployment is finished only when the right person reaches the right Server. Do not test against a convenient browser tab and assume it belongs to the profile you just deployed.
Verify the active target
Terminal
opencircle profile list opencircle status --profile circle-server
Replace circle-server with the intended deployment profile and compare its instance identity and Server URL against your deployment receipt. profile current shows the saved active profile, which may be a different target — it is not a substitute for an explicit --profile on any operation.
Connect a person
Give the person the exact client-facing Server URL and their own sign-in instructions — never your owner password or a first-owner claim link.
| Client | Start here | Expected result |
|---|---|---|
| macOS Desktop | Install Desktop, launch it, and enter the Server address | The intended Server is selected and the person signs in as themselves |
| Web | Open the Server URL in a browser | The Server's own workbench opens, not a marketing site |
| iPhone or Android | Follow the mobile connection guide | The phone verifies the Server and opens its own sign-in flow |
Administrator CLI sign-in is separate
Terminal
opencircle login --profile circle-server opencircle whoami --profile circle-server --format json
opencircle login authenticates the administrator CLI on a workstation; add --remote for device-flow sign-in on a headless machine. It does not install Desktop, sign another client in, or open a chat terminal by itself.
Acceptance checklist
- The Server identity matches the selected profile.
- The owner login is known — no default or invented password.
- Setup state is ready.
- At least one intended model route works.
- A second client, when used, reaches the same room and durable history.
If the Server is fresh and unclaimed, stop and return to the Administrator quickstart rather than silently creating an unrecorded owner.