From signup to your company workspace

1. Sign up — one form, no credit card

The signup form asks for five things: your name, work email, your organization's name, roughly how big your plans run, and what you're coming from. Submitting it plants exactly one record on our side — resubmitting later (say, the email didn't arrive) just sends a fresh link, never a duplicate. The optional product-news checkbox is unticked by default and stays that way unless you tick it.

2. Verify your email

We send one email with one link. It works once and expires after 24 hours; if it ages out, re-enter your email on the signup page and a new one arrives. The link opens a confirmation page with a single button — that button, not the click on the link, is what opens your workspace, so corporate mail scanners that pre-open links can't use it up on your behalf.

3. Sign in with your company identity

Foreweave authenticates through your organization's identity provider via OpenID Connect — the same sign-in your team already uses elsewhere. Password policy, multi-factor, and leaver offboarding stay where they belong: with your IT, not with another vendor password.

4. Your organization becomes a tenant

Completing sign-in creates your organization in Foreweave — a hard isolation boundary that owns your projects, people, and settings. You, the person who signed up, become its first administrator and the owner of its first project. Nothing inside that boundary is ever visible to anyone outside it; isolation is enforced in the database itself, not by application code remembering to filter.

That boundary is the same for everyone today: one shared schema, with row-level security in the database as the enforcement point. If your mandate calls for something stronger, talk to us before you commit — we would rather scope it honestly than sell you an isolation model we haven't built.

5. Grow the first plan

Three ways in, pick by mood:

• Import your existing MS Project XML — tasks, links, calendars, and assignments come across, and the import report tells you exactly what to double-check. (The import guide.)
• Start on a blank Gantt — drag your first bar; the critical path shows up as soon as two tasks are linked. (The quickstart.)
• Describe the program to the AI agent (if your admin has enabled it) — the draft arrives as a reviewable scenario, never as silent edits to a plan. (Drafting with the agent.)

However you start: capture a baseline before you close the laptop. It's what makes next month's "are we slipping?" answerable.

6. Invite the team

Roles come in two layers, and the distinction is doing real work:

• Organization roles — Admin (manages members and org-wide switches like the AI agent) and Member.
• Project roles — Owner, Editor, Viewer, set per project. The same person can be Owner of one plan and Viewer on another.

A default that works for most teams: planners get Editor, the program lead gets Owner, and stakeholders get Viewer — they see the Timeline, not the database.

7. Optional: switch on the extras, deliberately

• The AI agent is off for every new organization until an Admin opts in — and the activation screen tells you exactly what that means (an external model provider, zero-retention terms, confidential names redacted in transit). While it is in preview each account is enabled individually too, so ask us to switch yours on. Details on the security page, and the whole planning pipeline on the features page.
• Everyone in a workspace belongs to your organization — by invitation or through your company directory. There is no way for an outside account to see a project, which is the honest answer to "can I show this to our client?" today.