> 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/advanced-functions-and-tools/sql-access/sql-access/organisation-document-type.md).

# Organisation document type

## Spalten

* `id`: internal
* `org_id`: ID to organisation
* `document_type_id`: internal
* `document_type_key`: internal
* `document_locale`: internal
* `classification_method`: internal
* `is_active`: boolean
* `extraction_type`: internal
* `created_by`: integer
* `created_on`: timestamp with time zone
* `last_modified_on`: timestamp with time zone
* `is_deleted`: boolean
* `sub_org_id`: internal

## Analyse & Beschreibung

```markdown
# Technical Documentation for Table `public.organisation_document_type`

## Introduction

The `public.organisation_document_type` table is designed to manage and store information about various document types associated with organizations. This includes details such as the document type key, locale, classification methods, and the status of the document type (active, deleted, etc.). It appears to serve as a mapping between organizations and the types of documents they utilize or manage, alongside metadata about these documents.

## Column Descriptions

### id
- **Meaning**: Unique identifier for each record in the table.
- **Role**: Primary key.
- **Typical Contents**: A UUID string that uniquely identifies a document type entry.
- **Note**: Essential for distinguishing each record.

### org_id
- **Meaning**: Identifier for the organization related to the document type.
- **Role**: Foreign key, likely referencing an organization table.
- **Typical Contents**: A UUID string.
- **Note**: Connects the document type to a specific organization.

### document_type_id
- **Meaning**: Identifier for the document type.
- **Role**: Foreign key, possibly linked to a document types reference table.
- **Typical Contents**: A UUID string.
- **Note**: Allows mapping to specific document types.

### document_type_key
- **Meaning**: A key or code representing the document type.
- **Role**: Descriptive field for document type classification.
- **Typical Contents**: A string that acts as an identifier or label for the document type.
- **Note**: Used to identify the document type in a human-readable form.

### document_locale
- **Meaning**: Locale or language setting for the document type.
- **Role**: Descriptive field for locale specification.
- **Typical Contents**: A string, often 'auto', indicating automatic determination of locale.
- **Note**: Useful for internationalization and localization purposes.

### classification_method
- **Meaning**: Method used for classifying the document type.
- **Role**: Descriptive field indicating how the document is classified.
- **Typical Contents**: A string, often 'auto', suggesting automatic classification.
- **Note**: Important for understanding the classification process.

### is_active
- **Meaning**: Status indicating if the document type is active.
- **Role**: Boolean status field.
- **Typical Contents**: `True` or `False`.
- **Note**: Determines whether the document type is currently in use.

### extraction_type
- **Meaning**: Type of extraction method used for the document.
- **Role**: Descriptive field for extraction process.
- **Typical Contents**: Strings like 'FIX_COORDINATES', 'FLEX_COORDINATES', or `None`.
- **Note**: Provides insight into how data is extracted from documents.

### created_by
- **Meaning**: Identifier for the user who created the record.
- **Role**: Technical field for auditing purposes.
- **Typical Contents**: An integer representing a user ID.
- **Note**: Useful for tracking changes and accountability.

### created_on
- **Meaning**: Timestamp of when the record was created.
- **Role**: Technical field for auditing purposes.
- **Typical Contents**: A timestamp with time zone.
- **Note**: Important for tracking the creation date and time of the record.

### last_modified_on
- **Meaning**: Timestamp of the last modification to the record.
- **Role**: Technical field for auditing purposes.
- **Typical Contents**: A timestamp with time zone.
- **Note**: Useful for tracking updates and changes to the record.

### is_deleted
- **Meaning**: Status indicating if the record has been marked as deleted.
- **Role**: Boolean status field.
- **Typical Contents**: `True` or `False`.
- **Note**: Helps in implementing soft-delete functionality.

### sub_org_id
- **Meaning**: Identifier for a sub-organization related to the document type.
- **Role**: Possible foreign key, adding hierarchical organization structure.
- **Typical Contents**: A UUID string or `None`.
- **Note**: Provides additional context for organization structure.

```


---

# 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/advanced-functions-and-tools/sql-access/sql-access/organisation-document-type.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.
