Orgs, invites, API keys and CLI login
After signing up you now choose what happens: accept a pending invite, or create your org, which comes with the
project default and, for your first org with a verified email, the $30 starter credit. Invites last 72 hours,
count against your 10 seats and can be re-sent up to three times. Only Owners grant the Owner role, and an org always
keeps one.
nodus login signs the CLI in through the console and stores one 90-day key per org you pick; nodus login --device does the same from a machine without a browser. API keys take scopes and projects, never exceed your
role, and stop working within 30 seconds of being deleted. Keys bound to a service account keep working when their
creator leaves. See API keys and scopes and
Members and roles.
Add your SSH public keys once under Account › SSH keys and use them in the Workspaces of every org you belong to; deleting a key ends its live sessions (SSH keys). MCP clients you connect show up under Connected agents, where disconnecting one takes effect within 30 seconds (Connected agents).
Owners can require multi-factor authentication for their org; member, key and settings changes then need a
session verified with a second factor, and so does approving a CLI login as an Owner or Admin
(MFA). Admins see sign-ins and every access
change in the org’s activity log, and nodus get quota default shows each limit with what is in use.