Account and team
Understand sign-in, organizations, roles, service access and invitations.
Your SiteOS account identifies you. An Organization owns projects and connects the people who work on them. Signing in does not grant access to another team's projects.
Sign in from the app or CLI
The application signs you in with a one-time code sent to your email or with Google. An agent can also guide CLI email sign-in, including your verification step. Browser, CLI and remote MCP sessions are separate; signing into one does not automatically authorize the others.
During early access, SiteOS is available by invitation. Request access if you do not have an invitation yet. After approval, open the invitation email, sign in with the exact invited address and accept the invitation. If you signed in through the CLI first, accept the invitation in the browser before using that Organization from the CLI.
Use siteos auth status --json to check CLI sign-in and siteos auth organizations --json to list organizations available to that account. siteos auth select --organization <id> --json changes the CLI's default Organization; a repository's project selection keeps its own.
Work with your team
Choose the intended organization before selecting a project. The Organization settings page contains General, Members, Integrations and Usage & limits. See Integrations for shared provider connections and notification channels, and Usage and limits for credits and allowances.
Owners can invite admins or members; admins can invite members. In Members, choose the role and, for a member, the access to each service. The recipient must sign in with the exact invited email address. Invitations expire after 48 hours, and you can cancel a pending invitation.
Owners and admins can use Preview access beside Invite member to see how SiteOS would look with a proposed role and service selection using your real Organization data. Changes are disabled while the preview is active, and no invitation is created. Choose Restore my access to return to your own access.
Roles and service access
Each member has a level for each service: No access, Viewer, Editor or Manager. A level applies across all of the Organization's projects and environments. Viewer reads saved data and reports. Editor also makes ordinary changes, such as editing drafts or starting routine checks. Manager also publishes, manages keys, connections and notifications, and runs higher-impact operations such as paid SEO research. The Members screen describes each service's levels when you edit access.
The same access applies in the application, the CLI and remote MCP. Some areas, such as Analytics People and personal notification channels, remain limited to owners and admins. If an action is unavailable, check your selected organization and ask its owner or administrator about access.
What Auth means in SiteOS
Auth is the account and authorization layer for SiteOS itself. These guides do not describe a customer-login SDK for visitors to your website. Connecting Forms or Search does not replace your website's own authentication.
See Projects and environments for project scope and AI & MCP to manage which organizations your agent connections can use.