Signing in

People sign in to a Nuvelics organization in one of two ways, and software uses a third.

The two ways people sign inCopy Anchor Link

• An emailed link and code. Everyone can sign in this way. Nuvelics emails a single message with a link and a code; either one signs you in. The link and code are one sign-in: using either uses up both, and they expire fifteen minutes after they were sent.
• A passkey. After you have signed in once, you can add a passkey to a browser or device and use your fingerprint, face or device PIN instead of waiting for an email. The email method stays available, so you can still sign in if you lose the device.

Sign-in needs an invitation: an address with no account and no pending invitation is sent no email. That is how an administrator controls who gets in. Inviting someone, and withdrawing the invitation, is covered in Members and invitations.

The steps for each method, a remembered sign-in on a browser, and what to do when a link or code fails are in Sign in. Managing your passkeys is in User Settings.

Signing in beyond the web appCopy Anchor Link

• The command line. nuvelics login opens your browser to approve the tool, so it uses the same sign-in as the web app. For a script, it can take an API key instead. See Sign in to the command line.
• AI assistants. An MCP client signs you in through your browser and asks you to approve what it may do, so it needs no key. A client with no browser can use an API key. See Connect a client.
• Scripts and integrations. These use an API key, which acts for the organization rather than for a person.

Passkeys across surfacesCopy Anchor Link

You add, rename and remove your own passkeys in the web app, under Passkeys in User Settings. The API has the same operations for your own passkeys, listed under Passkeys. A passkey belongs to you, so it follows you into every organization you belong to.