> For the complete documentation index, see [llms.txt](https://acoservice.gitbook.io/acoservice-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://acoservice.gitbook.io/acoservice-documentation/running-your-aco/onboarding-info.md).

# The credentials you need

The credentials your ACO needs — you enter these yourself.

{% hint style="success" %}
**You no longer send this to anyone.** ACO Service is self-serve: you create your own ACO in the [owner console](/acoservice-documentation/running-your-aco/creating-your-aco.md) and enter these credentials yourself. Nobody has to create it for you and there is no queue to wait in.

This page is still the right checklist of *what* you need — just gather it for yourself rather than for someone else.
{% endhint %}

One Discord application gives you three values and your ACO needs all three. Have them ready before you start.

## The three Discord credentials — they are not interchangeable

One Discord application gives you **three** values, and the platform needs all three. This is the single most common thing to get wrong, because two of them look similar and the third lives on a different page entirely.

| Credential        | Where it lives            | What it does                                             |
| ----------------- | ------------------------- | -------------------------------------------------------- |
| **Client ID**     | OAuth2 tab                | Public identifier for your app. Also your bot's user ID. |
| **Client Secret** | OAuth2 tab → Reset Secret | Lets members **sign in** to your site with Discord.      |
| **Bot Token**     | **Bot** tab → Reset Token | What your **bot logs into Discord with**.                |

The Client Secret and the Bot Token are different credentials on different tabs.

**If you send the first two but not the Bot Token**, your site will work perfectly — members sign in, the dashboard loads, branding applies — and your Discord server will have **no working bot at all**. No slash commands, no checkout feed, nothing. It is a confusing failure precisely because everything else looks healthy, so double-check you have grabbed the token from the **Bot** tab, not the Client Secret from the OAuth2 tab.

Your ACO's Setup page in the console shows whether the Discord bot token is saved and whether the bot is running, so you can confirm all three landed without sending anything to anyone.

{% hint style="success" %}
**Next:** enter them on your ACO's Setup page in the console (acoservice.app/owner).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://acoservice.gitbook.io/acoservice-documentation/running-your-aco/onboarding-info.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.