> For the complete documentation index, see [llms.txt](https://docs.elevateelysium.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elevateelysium.xyz/running-the-platform/admin-panel.md).

# Operator panel

1. Set `ELYSIUM_ADMIN_ADDRESSES` (comma-separated wallet addresses) on the server and restart.
2. On the home page, click the small shield icon in the footer (or go to `/admin`).
3. Connect an allowlisted wallet and sign one message.

Anyone else sees a normal "Page not found".

The panel shows a progress bar, a "Next:" line and a checklist in five groups: server basics, chain, AI and features, before real money, go live. Each item has steps, a link to get the key, and where possible an input. Secrets are write-only. The executor key, database URL and session secret can only be set in the server environment. Manual items (legal review, backups, audit) are checked off by hand. Every change is logged.

Optional items include the OpenRouter key (the panel checks it with OpenRouter and warns when credit is low), Pinata, forecasting, the browser and search services, the local model runtime (Ollama) and monitoring.


---

# 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.elevateelysium.xyz/running-the-platform/admin-panel.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.