Leed accounts are created by you, not by a salesperson. There is no demo to sit through and no quote to wait for: you fill in a short form at /auth/sign-up, click a link in your email, and a workspace is built for you. What makes the form slightly unusual is that it creates two things at once — a login that is yours, and a website that belongs to a company — so it asks two questions most sign-up forms do not: what your site is called, and what domain it will live on.
If you already have a login, the Already have an account? Sign in link at the foot of the form is the shortcut you want.
What you need before you start
Two things, and neither of them is a credit card.
- A work email you can open in the next few minutes. Everything about your account hangs off this address — it is your sign-in identity, and once the account exists you cannot change it.
- The domain you intend to publish on. Leed provisions your site against a hostname from the very beginning, so it asks for one up front.
Neither is checked against ownership at sign-up. Typing docs.acme.com does not prove you control acme.com, and Leed does not ask you to prove it yet — pointing DNS at Leed is a separate, later step.
There is no password to choose, no password emailed to you, and no card to enter.
Two ways an account comes into existence
Read the half that matches how you got here. If someone sent you an invitation link, the rest of this page is not your path — see Joining and Switching Workspaces.
flowchart TD
A{How did you get here?} -->|"I found Leed myself"| B["/auth/sign-up<br/>name · email · site title · domain"]
A -->|"Someone invited me"| C["/auth/accept-invitation/…<br/>name · email only"]
B --> D["Verification email<br/>Verify & Get Started"]
D --> E["Initializing screen"]
E --> F["A brand-new workspace<br/>you are the Administrator"]
C --> G{Do you already<br/>have a login?}
G -->|Yes| H["Sign in, then Accept Invitation"]
G -->|No| I["Short sign-up form<br/>or Sign up with Google"]
H --> J["An existing workspace<br/>role set by whoever invited you"]
I --> J
The self-serve path on the left creates a workspace. The invited path on the right joins one that already exists, which is why it asks for so much less.
The sign-up form
The fields appear in this order, and all five are required.
| Field | What it becomes | Changeable later? |
|---|---|---|
| First name | Your display name in the CMS and your byline on published pages | Yes, on your profile |
| Last name | The same | Yes, on your profile |
| Work email | Your permanent sign-in identity | No — the email field is read-only once the account exists |
| Site title | Your site’s title, and the name your workspace is finally given | Yes, in Settings → General |
| Domain | The hostname your published site is provisioned for, plus a staging. twin | Yes, in Settings → General — but it is the identity the workspace is provisioned under |
Below the fields sit the challenge and the Create account button. The button is disabled until the challenge resolves.
Site title
The human name of the site you are about to get. It is written into your site’s configuration, and it is also what your workspace is finally called: the organization is created under the placeholder name Provisioning... and renamed to your site title at the very end of setup. If you watch the workspace name for the first couple of minutes, that is the rename you are seeing.
Acme Docs, Northwind Engineering, Handbook — anything you would be happy to see in a browser tab. You can change it in Settings → General afterwards.
Domain
The hostname your published site will answer on. Leed guesses it for you: when you tab out of the Work email field, it takes the domain from your address and fills the field in — unless the address is on a consumer provider, in which case it leaves the field empty for you.
An accepted domain is lower-case labels separated by dots, ending in a real public suffix: example.com, docs.acme.com, www.acme.com. No scheme, no path, no port, no trailing dot.
| You type | Accepted? | Why |
|---|---|---|
acme.com | Yes | A registrable domain with a real suffix |
docs.acme.com | Yes | Subdomains are fine, and are the common case |
www.acme.com | Yes | www is just another label |
https://acme.com | No | The scheme is not part of a hostname |
Acme.com | No | The pattern accepts lower-case labels only |
acme.com/docs | No | A path is not part of a hostname |
localhost | No | No dot, no suffix |
acme.local | No | .local is not a real public suffix — the server rejects it with 400 Invalid Domain |
Two different checks are doing that work, and they produce two different messages. A shape the pattern rejects gives you The domain must be of the format "example.com" or "www.example.com". A well-shaped hostname whose suffix is not a real one — acme.local, acme.internal — gets past the pattern and is refused by the server with 400 Invalid Domain. Leed runs the actual public suffix list rather than a hand-written list of endings, so unusual but real suffixes are accepted and invented ones are not.
The challenge
The last control before the button is a Cloudflare Turnstile challenge. Create account stays disabled until it resolves, and if the challenge’s token expires while you are still filling in the form, the button goes back to disabled and the widget re-arms itself. Wait for it to settle, then submit.
Verifying your email
Submitting the form lands you on Check Your Email, which names the address you typed. Leed has created your login but has not yet built anything — nothing happens until you click the link.
The email arrives with the subject Verify your email — Welcome to Leed and a single Verify & Get Started → button.
If nothing arrives, check spam first, then confirm you typed the address correctly — the screen prints it back to you for exactly that reason. The Didn’t receive it? Try again link returns you to the sign-up form.
Every message the form and the sign-in screen can show you is cataloged, verbatim, in Sign-in Troubleshooting.
What happens when you click the link
Clicking Verify & Get Started → does three things in one step: it marks your address verified, signs you in, and forwards you to the Initializing screen carrying your site title, domain and email. From there Leed starts building.
That build is not a database row. It is a git repository, two Cloudflare Workers, two hostnames, build automation, an email sending identity and a set of starter content — here is what it is doing while the spinner turns, and what you will find when it stops.
Workspace, company and organization each mean something precise in Leed and are not interchangeable; Core Concepts draws the lines before you need them.
If you were invited to an existing workspace instead
An invitation link opens a different, shorter form: first name, last name, email, the challenge, and a Sign up with Google button above them. It asks for no site title and no domain, because the workspace already exists and already has both. Your role in it is set by whoever invited you rather than by you.
Joining and Switching Workspaces walks that path from the invitation email onward, including what each of the invitation screen’s four states means.
There is no password
Leed never asks you to choose a password, never emails you one, and has no “forgot password” link, because there is nothing to forget. Every way into Leed is a link you click, a code you type, or a connected Google or GitHub account.
That also means there is no password to leak and no reset flow to phish. If you have arrived here looking for a way to reset one, you are not missing a screen — Signing In lists the four methods that do exist and says which one appears where.