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

# Get Started with Seshy for ERLC in Under 5 Minutes

> Invite Seshy to your Discord server, run /settings to configure your modules, and start your first ERLC session — all in under 5 minutes.

Getting Seshy running in your ERLC server is a five-step process that most server owners complete in under three minutes. You'll invite the bot, open the configuration panel, pick your first module to set up, and either start a live session or enable Ares protection. Optionally, connect your ER:LC Private Server to unlock live in-game data — all without leaving Discord.

<Tip>
  After inviting Seshy, run `/settings` first. It's the single panel that controls every module, role, channel, and branding option across the entire bot. You don't need to memorize individual setup commands — everything is configurable right there.
</Tip>

## Setup Steps

<Steps>
  <Step title="Invite Seshy to Your Server">
    Open [seshy.lol](https://seshy.lol) in your browser and click **Invite Seshy**. Discord's authorization flow will open — select the server you want to add Seshy to from the dropdown, then click **Continue**.

    Review the permission request on the next screen. Seshy needs **Administrator** to function fully (this covers Ares Security, role management, and channel operations automatically). If you prefer to grant individual permissions instead, Seshy requires:

    * Manage Roles
    * Manage Channels
    * Send Messages
    * Embed Links
    * Read Message History
    * Add Reactions
    * Use Application Commands

    Click **Authorize** and complete the CAPTCHA if prompted. Seshy will appear in your server's member list within a few seconds.
  </Step>

  <Step title="Open the Configuration Panel with /settings">
    In any channel where Seshy has permission to read and send messages, type `/settings` and press **Enter**. Seshy replies with an interactive configuration panel that gives you access to every setting across all eight modules.

    From `/settings` you can:

    * Set your **staff roles** and permission hierarchy
    * Assign **log channels** for moderation, sessions, and audits
    * Configure **custom branding** — embed colors, banners, and footer text
    * Enable or disable individual modules
    * Connect your ER:LC Private Server API key

    Work through the **General** and **Roles & Permissions** sections first — these unlock the correct behavior for every other module.
  </Step>

  <Step title="Configure Your First Module">
    Two modules are the most common starting points for new servers:

    **Sessions** — if your primary goal is running structured ERLC sessions, go to `/settings` → **Channels** and designate a session announcement channel. Then go to **Roles & Permissions** and assign which roles can start a session with `/ssu`. This gets you to a fully operational session workflow immediately.

    **Ares Security** — if protecting your server is the priority, Ares is already watching with its default settings the moment Seshy joins. You can optionally go to `/settings` → **Ares** to configure your whitelist, review which protection layers are active, and set the automatic response action (ban, kick, timeout, or warn-only) for each threat type.

    You don't have to choose just one — many server owners configure both in the same sitting.
  </Step>

  <Step title="Start Your First Session or Enable Ares">
    **To start a session:** Run `/ssu` in your designated session channel. Seshy posts a branded session startup embed with your server code, pings the configured roles, and begins tracking the session. When the session ends, run `/ssd` to post the shutdown embed and close the session log.

    **To confirm Ares is active:** Run `/ares enable` to explicitly enable Ares if you want to verify the module is on, or check its status under `/settings`. You'll see all 21 protection layers listed with their current state. No additional configuration is required — Ares monitors your server in real time automatically.

    <Info>
      Ares has a response time of under one second and requires zero setup to begin protecting your server. If a compromised account attempts mass bans, channel deletions, or dangerous role grants, Ares locks it down before the next action lands.
    </Info>
  </Step>

  <Step title="Connect ER:LC Integration (Optional)">
    If you run a Private Server in ER:LC and want live in-game data flowing into Discord — player counts, team rosters, command logs, kill logs, and mod call tracking — connect your Private Server API key.

    1. Open your ER:LC game, navigate to your Private Server settings, and copy your **API key**.
    2. In Discord, run `/settings` and navigate to **ER:LC Integration**.
    3. Paste your API key into the prompt and confirm.
    4. Run the connection test to verify Seshy can reach your server.

    Once connected, Seshy pulls live data from your ER:LC server and surfaces it through the ER:LC Integration module commands. Your API key is encrypted and stored securely — it is never exposed in logs or bot responses.
  </Step>
</Steps>

## What's Next

With Seshy up and running, explore the full documentation for each module to unlock everything the bot can do for your community.

<CardGroup cols={2}>
  <Card title="Full Configuration" icon="sliders" href="/configuration">
    Master every option in the /settings panel — branding, permission hierarchies, channel assignments, and configuration backup.
  </Card>

  <Card title="Sessions Module" icon="play" href="/modules/sessions">
    Set up SSU voting, session scheduling, custom session branding, and session analytics for your ERLC operations.
  </Card>

  <Card title="Ares Security" icon="shield-halved" href="/modules/ares-security">
    Explore all 21 protection layers, configure your whitelist, set punishment actions, and review the security audit log.
  </Card>

  <Card title="ER:LC Integration" icon="satellite-dish" href="/modules/erlc-integration">
    Connect your Private Server, view live player data, track command logs, monitor kill logs, and manage bans from Discord.
  </Card>
</CardGroup>