> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/administration-and-setup/setup/document-training/training-line-fields-table-training/save-and-delete-rules.md).
# Save and Delete Rules
Once you’ve completed the training or correction of a table, it’s important to **save your rules** so that DocBits can apply them automatically to future documents from the same supplier.
### Saving Rules
After defining all columns and corrections:
1. Click the **SAVE RULES** button at the top.
2. A rule counter will confirm how many extraction rules have been saved.
This ensures DocBits will automatically use your trained layout the next time it sees a similar document.
Save Rules stores the rules; the counter shows how many rules exist.
### Deleting Rules
You can remove saved rules using the **DELETE RULES** button if they were configured incorrectly or if the document layout has changed significantly.
**Warning**: Deleting rules affects all documents from the same supplier with the same layout. You will need to **retrain the table extraction from scratch**.
Deleting rules has to be confirmed.
---
# 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.docbits.com/administration-and-setup/setup/document-training/training-line-fields-table-training/save-and-delete-rules.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.
