> For the complete documentation index, see [llms.txt](https://logix.gitbook.io/logix-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://logix.gitbook.io/logix-docs/logix-admin-pay-logging-p.md).

# Logix - Admin Pay Logging \[P]

Please follow the steps below to setup admin pay for your server

**Step 1: Setting up the Admin Pay Logging System**

1. **Run the `/admin-pay-setup` command:**
   * This command initializes the setup process for the admin pay logging system.
   * When you run the command, the bot will guide you through creating categories and defining settings.
2. **Create Categories:**
   * **Category Name:** Choose a name for the category that will hold the logs (e.g., "Admin Pay Logs").
   * **Price per Log:** Set the price that an admin will be paid for each log generated. This amount will be credited to the admin after a log is created.
3. **Save Configuration:**
   * Once you’ve created the category and set the price, save your settings. The bot will store these settings for use when generating logs

**Step 2: Configure Admin Pay Logging Channel**

1. **Run the `/config` command:**
   * Use this command to select the channel where admin pay logs will be sent.
   * The bot will prompt you to choose a channel from your server to receive the updates once a log is generated.
   * This is also where the log transcript will be sent after each `/log-ticket` command.
2. **Choose the Channel:**
   * Select the appropriate channel for the logs to be posted (e.g., a dedicated #admin-pay-logs channel).
   * Confirm your selection, and the bot will automatically update the configuration

**Step 3: Generating a Log Ticket and Transcript**

1. **Run the `/log-ticket` command:**
   * Once the admin has completed the task for which they need to be paid, the `/log-ticket` command should be used in the appropriate ticket channel.
   * The bot will generate a transcript of the conversation or logs from that ticket channel.
2. **Choose the Category and Channel:**
   * The bot will ask you to select the category and the channel where the transcript will be posted (this is determined during the `/admin-pay-setup` step).
   * Select the correct category, and the bot will automatically process the transaction and post the transcript in the designated channel

**Step 4: Pay Logging and Finalizing**

1. **Update the Admin’s Pay:**
   * After the log is generated, the bot will update the admin’s pay based on the price set during the `/admin-pay-setup` step.
   * The admin's pay will be logged and updated in the channel you specified under the configuration step.
2. **Pay Confirmation:**
   * The bot will confirm that the admin’s pay has been updated, and it will show a message in the log channel with the details of the transaction, including the price per log and the admin’s updated balance


---

# 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://logix.gitbook.io/logix-docs/logix-admin-pay-logging-p.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.