Admin operations
Admin surfaces
Choose the right place to run Team OS admin work.
Use the simplest surface that fits the task.
| Surface | Use it for |
|---|---|
| Command Centre, Team > Teams | Create and manage Teams, Company Admins, Full access grants, requests, and ownership. |
| Command Centre, selected Team | Manage members, invites, clients, skills, secrets, memory, and sync. |
| Interactive terminal menu | Run guided tasks for the selected Team. |
| Maintenance commands | Bootstrap the first owner, recover missing ownership, automate setup, or troubleshoot. |
| Hosted API | Enforce authenticated Company, Team, client, skill, memory, and file access. |
Command Centre uses the same saved Team OS login as the terminal menu when
AGENTIC_OS_TEAM_CONFIG_DIR points to the same folder.
Maintenance flags such as --by identify the actor whose authority is checked
and written to the audit trail. They do not let a hosted client choose its
identity. Hosted requests always use the authenticated server session.
In local PGLite, stop the API before running maintenance commands. PGLite allows only one process to hold the local store.
Hosted Postgres does not have that local lock limit.
Next: First Team and owner