> For the complete documentation index, see [llms.txt](https://docs.adminremix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adminremix.com/core/fines.md).
# Fines
If your staff issues fines for assets or other devices, we have a way for you to track those fines and let your users see what they owe as well.
## 1 - Creating a Fine from the Core Menu
1. Under "Core", click on "Fines".
2. Click the "+" at the top right of the page, then click "Create".
3. Choose the User to assign the fine to by clicking the "User" box and either selecting from the list, or typing in the name of the user.
4. Enter the fine amount and if it requires payment.
5. Add any notes you would like to let the user or admin know why the fine was assigned.
6. Click "Issue Fine" and it will be entered into the user's profile.
## 2 - Create a Fine using the User's Profile
1. Click on the user you are issuing the fine to, then select "Issue Fine" under the "Info" menu.
2. Follow steps 3-6 under [#id-1-creating-a-fine-from-the-core-menu](#id-1-creating-a-fine-from-the-core-menu "mention").
## 3 - Create a Bulk Fine
1. Under "Core", click on "Fines".
2. Click the "+" at the top right of the page, then click "Bulk Create".
3. Fill in the fields and either tab to add more rows, or select the "+ Add Row".
4. Continue filling in the missing fields. The "User" is a search or drop down menu, under "Item" you can select any item the user had checked out to them.
5. Save the bulk create. You will receive and email when the bulk create is complete.
---
# 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.adminremix.com/core/fines.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.
