First admin account

Once every pod reports Ready, the deployment still has no accounts in it. The first person to sign up claims the platform. This step is the same on Helm and Embedded Cluster.

Create the platform owner

Open the URL matching your configured scheme, such as https://<your-domain>/, and create an account.

The first user to sign up is automatically enrolled in the default organization and becomes the platform owner. That account is the only one that can revoke platform-admin access from another administrator, so create it deliberately — not as a throwaway test account. Additional users can sign up directly and join the shared enterprise organization. Invitations let you choose a role and send a guided onboarding link before they sign up.

Caution

If login fails silently — the page reloads without signing you in — the configured URL scheme does not match how you are connecting. Setting HTTPS while connecting over plain HTTP causes browsers to drop authentication cookies without an error. Helm installs set this with global.scheme; Embedded Cluster sets it under Dreadnode Identity → URL Scheme.

Onboard your team

Use Settings → Members to invite users into an organization. Use Admin → Organizations to create additional organizations across the deployment.

A fresh deployment sends no email. Until you configure a relay, the API logs invitation, email-verification, and password-reset links at WARNING level so an operator can deliver them manually — see Email delivery. Configure SMTP, or an OAuth provider, before onboarding real users.

What’s next

First model deployment Add the dn/* model that every chat, agent, and evaluation surface reads from.

Users and organizations Ongoing user administration, platform roles, and signup protection.