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

# Create your bot

> BotFather, the token, and how Ace Up handles it.

Your venue runs on a bot you own. You create it, you keep control of it, and you
can revoke Ace Up's access at any time by rotating the token in BotFather.

**1. Create the bot in BotFather**

Open [@BotFather](https://t.me/BotFather) and send `/newbot`.

Give it a display name and a username. This is what your members will see, so
use your community's name rather than anything mentioning Ace Up.

BotFather replies with a **token** — a long string of digits, a colon, then
letters. That token is the bot: treat it like a password.

**2. Start /newvenue**

Open [@Aceupgamebot](https://t.me/Aceupgamebot?start=venue) and send
`/newvenue`.

You are shown the owner agreement first and asked to accept it before a venue
exists at all. Then you are asked for your venue's name.

**3. Paste the token**

Paste the BotFather token into the chat when asked.

What happens next, in order:

1. Ace Up calls Telegram's `getMe` with it, to confirm it is a real bot token
   and to read the bot's ID and username.
2. The token is **encrypted at rest** under a key used for nothing else.
3. **Your message is deleted** from the chat.

The token is never written to a log. A dump of the whole database does not
reveal it.

**4. Wait for activation**

Your venue sits as **pending** until a person at Ace Up approves it. Nothing
runs under your bot before that.

See [Activation](https://aceup.mintlify.site/owners/activation.md).

## Rotating or revoking the token

You own the bot, so you can take it back whenever you like.

* **Revoke** — `/revoke` in BotFather invalidates the token. Your venue pauses
  automatically, because the bot stops answering, and you get a message from
  @Aceupgamebot telling you so.
* **Rotate** — get a fresh token from BotFather, send `/newtoken` to
  [@Aceupgamebot](https://t.me/Aceupgamebot) and paste it. A bot that was
  activated once goes **straight back live**: same venue, same links, the
  connection reinstalled, no second approval. A bot that was never activated
  waits for the admin card as usual.

One venue per owner: sending `/newvenue` again points you at `/setup` and
`/newtoken` instead of creating a second venue. A second group is linked to the
same venue and bot, not to a new one.

> [!NOTE]
>
> Token rotation is done **in the bot chat**, never in a web form. A token typed
> into a web page lands in browser history and autofill, which is exactly where a
> bot token should not be.

## If Ace Up revokes your bot

A platform admin can mark a bot revoked — it stops immediately and no instance
runs for it. You recover with `/newtoken` and a fresh token from BotFather.

> [card] [Activation](https://aceup.mintlify.site/owners/activation.md)
>
> What happens when a person approves your venue.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.