> For the complete documentation index, see [llms.txt](https://docs.itranslator.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itranslator.app/fundamentals/getting-set-up.md).

# Getting Set Up

Invite iTranslator and translate your first messages in a few minutes.

{% stepper %}
{% step %}

### Invite iTranslator to your server

Click the [invite link](https://itranslator.app/invite/go?placement=docs\&content=getting-set-up), choose your server and keep the permissions that are already selected: the bot needs them to read messages and post translations.

You need the **Manage Server** permission on the server to add a bot.
{% endstep %}

{% step %}

### Check that everything works

Run `/translate` in any channel to translate a first sentence, and `/help` to see the main commands and links.
{% endstep %}

{% step %}

### Open the dashboard

Once the bot is added, you are sent to the dashboard of your server: log in with Discord if you are asked to. To come back later, go to [itranslator.app/dashboard](https://itranslator.app/dashboard) and pick your server. Everything is configured from there, with no command to remember.

<figure><img src="https://3955709218-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuW8Vjy8RHWcWMwcAWdcy%2Fuploads%2Fgit-blob-91683613712718ca7f9b0ecd4efaf72d3740e782%2Fdashboard-servers.png?alt=media" alt="The dashboard listing the servers you can configure"><figcaption></figcaption></figure>

Prefer slash commands? Every setting has one, listed on the [Commands](/fundamentals/commands.md) page.
{% endstep %}

{% step %}

### Turn on the translations you need

Most servers start with one of these two features:

* [**Automatic-Translation**](/amazing-features/automatic-translation.md) translates every message of a channel into the languages you choose.
* [**Translation by Flag**](/amazing-features/translation-by-flag.md) lets any member translate a message by reacting with a flag.

That's it. iTranslator is ready.
{% endstep %}
{% endstepper %}

## What's next?

{% content-ref url="/pages/6sDWucYlg73r0Xyrws5R" %}
[Dashboard](/fundamentals/dashboard.md)
{% endcontent-ref %}

{% content-ref url="/pages/YxcPGWRNWZimDpSrdkNN" %}
[Features](/overview/features.md)
{% endcontent-ref %}

{% content-ref url="/pages/I1YD6sLani4DU6bg3wjc" %}
[Translation Limit](/fundamentals/translation-limit.md)
{% endcontent-ref %}

{% hint style="info" %}
Something is not working as expected? Ask us on the [Support Discord](https://discord.itranslator.app).
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.itranslator.app/fundamentals/getting-set-up.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.