> 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/settings/global-settings/document-types/more-settings/best-practices.md).

# Best practices

## Here are some proven recommendations for using settings effectively to optimize document processing, improve data accuracy, and ensure compliance.

### Standardize templates and language settings:

* Create clear guidelines for using formatting templates and language settings to ensure all documents are consistent.
* Regularly train employees on the correct use of templates and language settings.

### Enable autocorrect and spell check:

* Encourage employees to spell check before finalizing a document to identify and correct typos and grammatical errors.

### Use versioning and change tracking:

* Use versioning and change tracking to track edit history and ensure traceability of changes.
* Carefully document changes and comments to support the review process and facilitate collaboration.

### Careful document security configuration:

* Set clear access restrictions to ensure that confidential documents can only be viewed and edited by authorized people.
* Regularly update passwords and access rights to ensure security and meet compliance requirements.

### Regular training and updates:

* Regularly train employees on how to use DocBits and its features effectively.
* Stay up to date with updates and new features and implement them as needed to improve efficiency and security.

### Documented workflows and policies:

* Create clear document processing policies and workflows that cover the use of the various settings and features.
* Document compliance requirements and ensure that all employees understand and adhere to them.

By implementing these best practices, you can increase efficiency in DocBits, improve data accuracy, and ensure that it meets relevant compliance requirements.


---

# 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/settings/global-settings/document-types/more-settings/best-practices.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.