> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wiresocket.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Onboarding

> Get your account ready for production in three simple steps.

Welcome to WireSocket. This guide walks you through setting up your account and preparing your first application for real-time synchronization.

***

## 1. Create a Tenant Account

Every organization starts by creating a Tenant account. This serves as the administrative hub for your collaborative ecosystem.

* Go to [dashboard.wiresocket.com](https://dashboard.wiresocket.com).
* Sign up using your email or GitHub account.
* **Initial State**: Your account will start in a **Pending** state while we complete the initial setup.

***

## 2. Account Approval & Activation

To ensure security and proper resource allocation, each new Tenant requires a one-time approval from the WireSocket team.

* **Verification**: Our team reviews your registration.
* **Provisioning**: Upon approval, the system generates your unique **Asymmetric Signing Keys** and prepares your billing profile.
* You will receive an email once your account is **Active**.

***

## 3. Set Up Your First App

An App contains the configuration and credentials your backend uses to authenticate users and connect to WireSocket.

<Steps>
  <Step title="Create Application">
    Click on **Apps** in the sidebar and select **Add Application**.
  </Step>

  <Step title="Region & Data Residency">
    Provide a name (e.g., `production-editor`) and select your **License
    Region**. WireSocket automatically provisions a regional database to store
    your app's metadata.
  </Step>

  <Step title="Security Configuration">
    In the app settings, add your **Allowed Domains** (e.g., `localhost:3000`,
    `myapp.com`). This is a critical security step that prevents token theft.
  </Step>

  <Step title="Capture Credentials">
    Once created, you will see your `client_id` and `client_secret`. **Copy them
    immediately.**

    <Warning>
      The `client_secret` is only shown once. If lost, you must regenerate it,
      which invalidates any service currently using the old secret.
    </Warning>
  </Step>
</Steps>