> For the complete documentation index, see [llms.txt](https://vitrina-blogerov.gitbook.io/bloggers-showcase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vitrina-blogerov.gitbook.io/bloggers-showcase/product-docs/product-docs-en/admin-panel/initial-setup.md).

# Initial setup

After installation, the platform is already running, but before handing it over for use, it needs to be configured for a specific project: connect AI, Telegram bot, channel, bot administrators, message texts, and a secure password.

{% hint style="warning" %}
These actions are not required to launch the service itself, so they are not included in the installer. But without them, the platform will work as a technically installed product rather than a ready-made sales showcase.
{% endhint %}

### Quick checklist

1. Log in to the web admin panel.
2. Change the administrator password.
3. Connect the Telegram bot token.
4. Configure AI for showcase search.
5. Configure AI for the Telegram bot.
6. Check and adapt the prompts.
7. Add the Telegram IDs of the bot administrators.
8. Specify `CHANNEL_ID` for posts in the channel.
9. Configure the bot's welcome message.
10. Configure the final message after the results are delivered.
11. Check the showcase, Mini App, and `/start` in the bot.

```mermaid
flowchart TD
    A["Installation completed"] --> B["Password change"]
    B --> C["Telegram bot token"]
    C --> D["AI: showcase and bot"]
    D --> E["Prompts"]
    E --> F["Bot admins and channel"]
    F --> G["Welcome message and final message"]
    G --> H["Check the showcase and Telegram"]
```

### 1. Logging into the admin panel

Open the admin panel of the installed language version:

```
https://example.com/bloggers/ru/admin
```

Replace `ru` with the required version: `en`, `zh` or `ar`.

The login and password are set during installation. If access is lost, use the server-side utility to change the administrator.

### 2. Changing the password after installation

Immediately after installation, it is recommended to change the administrator password to the project owner's working password.

{% columns %}
{% column %}

<div data-with-frame="true"><figure><img src="https://162603775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuwCSpQuu1p5soxSClCET%2Fuploads%2F9155sPgSpIRXcDBSRZXS%2Fsystem-section.png?alt=media&amp;token=070db508-b2b5-41f2-a1c7-145f22237024" alt=""><figcaption><p>"System" section</p></figcaption></figure></div>
{% endcolumn %}

{% column %}

<div align="left" data-with-frame="true"><figure><img src="https://162603775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuwCSpQuu1p5soxSClCET%2Fuploads%2FheemHhYnC600SmtusTGQ%2Fchange-password.png?alt=media&amp;token=d47be0ce-fc0c-4209-b992-40977b50378b" alt=""><figcaption><p>Password change</p></figcaption></figure></div>
{% endcolumn %}
{% endcolumns %}

{% hint style="danger" %}
Do not leave the temporary password used during installation or passed between people. The admin panel controls cards, tokens, AI, the bot, and the appearance of the showcase.
{% endhint %}

Open the section `System`, then change the password. The new password should be long and unique.

### 3. Telegram bot token

The Telegram bot token connects the platform to the bot. Without it, the bot won't be able to receive messages, open the Mini App, send mailings, or publish posts.

Each language version requires a separate bot and a separate token.

{% hint style="warning" %}
One Telegram bot token cannot be used in multiple language versions. The Mini App button and Telegram polling are tied to a specific bot and a specific version.
{% endhint %}

After saving the token, check the bot with the command:

```
/start
```

### 4. AI API for search and the bot

AI is configured in two places:

{% tabs %}
{% tab title="Search agent" %}
Used on the showcase. The user writes a task in advanced search, and the agent returns suitable cards from the database.

<div data-with-frame="true"><figure><img src="https://162603775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuwCSpQuu1p5soxSClCET%2Fuploads%2FKUeqa3bcBlOI2yQaLmCa%2Fai-search-section.png?alt=media&amp;token=128c0027-dd35-43c5-84ba-fe14adada82f" alt=""><figcaption></figcaption></figure></div>
{% endtab %}

{% tab title="Telegram bot" %}
Used in dialogue with the user. The bot asks clarifying questions, selects bloggers, and sends cards.

<div data-with-frame="true"><figure><img src="https://162603775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuwCSpQuu1p5soxSClCET%2Fuploads%2FyGMPw7Y1y0WvtFOQsHQG%2Fai-bot-section.png?alt=media&amp;token=b9eebf35-03f3-46ff-a5a3-22d8557e112e" alt=""><figcaption></figcaption></figure></div>
{% endtab %}
{% endtabs %}

The platform supports several OpenAI-compatible providers, but for production use it is strongly recommended to use `Groq`.

{% hint style="danger" %}
Recommended provider - `Groq`. The other providers are present in the interface as compatible options, but they have not gone through a full test cycle in this release.
{% endhint %}

Recommended basic values:

```
Provider: groq
Model: llama-3.3-70b-versatile
```

The API key is stored in the settings of the selected language version. Separate keys can be used for each version.

### 5. Prompt tuning

Prompts determine how AI understands the user's task and how it selects bloggers from the database.

After installation, it is worth checking the default prompts and adapting them to the market:

* communication language;
* typical client niches;
* brand style;
* acceptable length of responses;
* rules for selecting bloggers;
* restrictions that AI must not violate.

{% hint style="info" %}
AI should not invent bloggers. The prompt should guide it to search the existing database and correctly return cards.
{% endhint %}

More details: [Prompt examples.](/bloggers-showcase/product-docs/product-docs-en/applications/prompt-examples.md)

### 6. Telegram bot administrators

Telegram administrators are set via numeric Telegram IDs. This is not a username and not the web admin login.

<div data-with-frame="true"><figure><img src="https://162603775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuwCSpQuu1p5soxSClCET%2Fuploads%2FwxuvBD5iwPIIk9V7TwdG%2Ftelegram-audience-1.png?alt=media&amp;token=9b37e13d-f636-45d5-8589-d54479f2136b" alt=""><figcaption></figcaption></figure></div>

Add the IDs of the people who can manage the bot from Telegram:

* send mailings;
* publish posts;
* view statistics;
* change the welcome message;
* get quick access to admin functions.

{% hint style="warning" %}
Do not add a username instead of an ID. A username can be changed, while the Telegram ID remains constant.
{% endhint %}

### 7. Channel for publications

For the bot to publish posts in the channel, you need to specify `CHANNEL_ID` and add the bot as a channel administrator.

`CHANNEL_ID` may look like the numeric channel ID. For private and supergroup channels, the format with `-100`.

After setup, send a test post from the admin panel or the Telegram admin panel.

### 8. Bot greeting

Welcome message is the first message after `/start`. It should quickly explain to the user:

* who this bot is;
* what it can do;
* how to open the catalog;
* that a request can be written in plain text.

<div data-with-frame="true"><figure><img src="https://162603775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuwCSpQuu1p5soxSClCET%2Fuploads%2FYjGYhal3TthQwYG3q7SR%2Ftelegram-audience-2.png?alt=media&amp;token=00b920dc-d463-4024-a9c2-30e96dfe9be7" alt=""><figcaption></figcaption></figure></div>

Media and buttons can be added to the welcome message.

### 9. Final message after results are delivered

The final message is sent after the AI has selected bloggers. Its job is to turn the user's interest into action.

Usually it includes:

* an offer to contact the agency;
* the contact button;
* a link to the catalog;
* a ready-made application text;
* alternative contacts.

### 10. Final check

Before showing the platform to clients, check:

* admin panel login;
* password change;
* showcase loading;
* regular search;
* advanced search;
* AI search;
* adding to cart;
* the contact button;
* `/start` in the Telegram bot;
* Mini App button;
* greeting;
* AI dialog in the bot;
* final message;
* mailing to a test user;
* test post in the channel.

<details>

<summary>If something doesn't work</summary>

First, check the correctness of the language version and tokens. Then look at the section [Possible errors](/bloggers-showcase/product-docs/product-docs-en/possible-errors/about-the-section.md).

</details>


---

# 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://vitrina-blogerov.gitbook.io/bloggers-showcase/product-docs/product-docs-en/admin-panel/initial-setup.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.