# Onboarding Wizard

When a new org is created, its first owner is routed to the Setup Wizard at `/org-setup`. The wizard gets the workspace into a usable state without any guesswork — identity, voice, goals, and connections — in a guided flow.

### Structure

The wizard has two phases:

**Core Setup (8 steps)** — required before the dashboard is useful:

1. **Workspace Identity** — org name, timezone
2. **Company Profile** — org type, industry, short description
3. **Social Platforms** — handles for X, Facebook, Instagram (skippable)
4. **Analytics Ingestion** — pick how data flows in: manual CSV upload or connected accounts (skippable)
5. **Primary Goals** — what you want from social (reach, engagement, leads, etc.)
6. **Primary Audience** — who you're talking to
7. **Publishing Behavior** — frequency, channels, content mix, publish mode, generation priority
8. **Brand Voice** — voice description, example posts, forbidden phrases, starter hooks; optionally auto-generate a Brand Voice profile from any existing post history

After step 8 you hit a **Core Complete** screen where you can finish now and start using the app, or continue into advanced setup.

**Advanced Setup (up to 5 steps)** — all skippable, all revisitable later from their respective pages:

1. **Competitors** — competitor accounts to track
2. **Team Members** — invite editors and admins by email
3. **Telegram Bot** — enable and allowlist a chat for the Telegram integration
4. **Approval Workflow** — enable approval and set the minimum role (only shown if your plan supports it)
5. **RSS Feeds** — feed URLs for Algorithm Watch

### Web3 Project orgs

If your org type is **Web3 Project**, the wizard inserts an additional structured setup path after **Core Complete** and before the standard advanced setup steps:

1. **Web3 Project Profile** — project name, category, chain, website, docs, positioning, and account posture
2. **Positioning & Audience** — differentiators, narratives to own, audience maturity, and topics to avoid
3. **Team Directory** — public team members used in spotlight and credibility content
4. **Current Roadmap** — planned, in-progress, and completed roadmap items
5. **FAQs & Objections** — reusable answers, objections, and misconception handling

These steps give the org a structured project knowledge base that powers Web3-specific generation flows later on. See [Web3 Projects](/thecontentforge-docs/feature-guides/web3-project.md).

The wizard ends on a **Done** screen.

### Resume

If you leave mid-wizard, the next sign-in resumes where you left off. Progress is stored against your org, and you won't be pushed backward if you reload.

### Going back

Inside the wizard, a back button returns you to the previous visited step within the same session. Once you exit, the wizard resumes from the last saved step.

### Skipping

Steps marked skippable show a **Skip** button. Skipped data just isn't saved — you can fill it in later from the matching page in the app (Brand Voice, Social Connections, Users, Settings, Algorithm Watch).

### Where to go next

Once onboarding is complete, continue with [Your First Login](/thecontentforge-docs/getting-started/first-login.md) to tour the sidebar, generate your first post, and start ingesting data.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://thecontentforge.gitbook.io/thecontentforge-docs/getting-started/onboarding-wizard.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.