# In-App Onboarding

Walk through what happens from signup to your first connected integration in the OneHazel dashboard.

> **Prefer to integrate programmatically?** See the [API-first Getting Started](/getting-started) guide instead.

## 1. Sign Up

Head to [app.onehazel.com](https://app.onehazel.com) and click **Create Account**. You'll see a single form asking for:

- **Your name**
- **Company name**
- **Email address**
- **Password** (at least 6 characters)

The account type is set to **Operator** — Platform and Supplier roles are coming soon.

## 2. Verify Your Email

After submitting, you'll land on a "Check your inbox" page. Click the verification link in the email to activate your account.

When you return and sign in, your registration completes automatically — no second form needed.

## 3. Await Approval

New accounts start in `pending_approval` status. An admin reviews and approves your account — you'll receive an approval email with a link back to the app once you're cleared.

> Typical approval time: **< 24 hours**. If you're blocked waiting, email us.

## 4. The Onboarding Wizard

On your first sign-in after approval, a 7-step wizard appears. Each step validates itself against the OneHazel backend before you move forward, so you can't finish with a broken setup.

### Step 1: Welcome

Pick your **industry** (iGaming, FinTech, eCommerce, SaaS, or Custom) and confirm your **company name**. Your industry choice tailors the rest of the wizard — the connector recommendations, data template, and sample data all adjust accordingly.

### Step 2: Generate Your API Key

Click **Generate API Key** and copy the `oh_live_...` token shown. **This is the only time it's displayed** — save it in your password manager or secret store immediately.

The wizard makes a test call with your new key to verify it works before letting you proceed.

### Step 3: Connect Your First Integration

The wizard shows 5-8 recommended connectors for your industry (rather than the full 300+ marketplace). Pick one, enter your credentials, and hit **Test Connection**.

- A green check means credentials verified against the live provider
- A red X means you can fix them inline or activate anyway (at your own risk)

### Step 4: Configure Your Data Lake

Select a **data template** that matches your industry. For iGaming, the default `tpl_igaming` template defines:

- **Entity types**: player, operator, game
- **Event types**: transaction, game_activity, session, bonus, block, support, affiliate
- **State keys**: balance, kyc_status, risk_score, loyalty_tier
- **PII fields**: automatically encrypted at rest (first_name, last_name, email, etc.)

You can also seed sample data so your dashboard isn't empty when you first log in.

### Step 5: Set Up Webhooks

Provide a URL where OneHazel can POST events (e.g. `https://your-platform.com/webhooks/onehazel`). The wizard fires a test event and verifies your endpoint responded with a `2xx`.

All webhook deliveries are signed with HMAC-SHA256 — see [Webhooks](/api-reference/webhooks) for signature verification.

### Step 6: Verification

A 5-check health dashboard runs:

1. Operator profile active ✓
2. API key working ✓
3. At least one connector configured ✓
4. Data template applied ✓
5. Webhook subscription verified ✓

Any failures link back to the relevant step so you can fix them.

### Step 7: Completion

Summary of what you set up, links to the Analytics dashboard, and your next-step recommendations (e.g. "build your first workflow").

## 5. You're Live

After the wizard, you land in the main **Operator Shell** with these sections:

- **Marketplace** — the full 300+ connector catalog
- **Connections** — manage your integrations (edit credentials, test, disconnect, delete)
- **Workflows** — visual workflow builder for automating actions
- **Analytics** — KPIs, revenue, player/user metrics
- **Settings** — API keys, data templates, webhooks, team members

## Skipping the Wizard

You can skip individual wizard steps if you'd rather set them up later via the API or Settings pages. The wizard only blocks on Welcome and Completion.

## What's Next?

- [Workflows](/workflows) — automate actions when events arrive
- [Data Ingestion](/data-ingestion/) — send entities, events, and states
- [API Reference](/api-reference/) — full endpoint documentation