> For the complete documentation index, see [llms.txt](https://aurexgold.gitbook.io/aurexgold-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aurexgold.gitbook.io/aurexgold-docs/admin-features.md). # Admin Features The Aurex Gold Admin Panel includes specialized tools for platform administrators to manage users and communicate important updates. ## Admin Reward Distribution The Admin Panel includes an option for the administrator to send rewards to individual users manually, whenever required. This allows the admin to distribute rewards or incentives directly to a selected user through the platform. * Manual reward distribution to individual users * Flexible timing — admin can send rewards at any time * Direct platform delivery — rewards appear in the user's account * Full audit trail of all admin-initiated distributions ## Admin Announcement / Popup Banner An additional popup announcement/banner feature allows the admin to display important information to users. The admin can create and publish an announcement, notification, or promotional message, which will appear as a popup/banner on the user's dashboard. * Create and publish platform-wide announcements * Popup/banner display on the user dashboard * Suitable for important updates, reminders, or promotional messages * Real-time visibility — announcements appear immediately for all users --- # 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://aurexgold.gitbook.io/aurexgold-docs/admin-features.md?ask=&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.