**Source URL:** https://general.veevavault.dev/vault-sdk/entry-points/triggers/doctype-triggers/about-doctype-trigger-event-levels.md

# About Doctype Trigger Event Levels



Doctype trigger event levels determine if a trigger fires when data operations occur at the document version level or the document level. The majority of operations in Vault are executed against document versions, but there are some operations that are performed at the document level.

Each doctype trigger can only fire at one event level, either:

* [`DOCUMENT_VERSION`](/vault-sdk/entry-points/triggers/doctype-triggers/about-doctype-trigger-event-levels/#DOCUMENT_VERSION)

* [`DOCUMENT`](/vault-sdk/entry-points/triggers/doctype-triggers/about-doctype-trigger-event-levels/#DOCUMENT)

[Data operations that fire doctype triggers](/vault-sdk/entry-points/triggers/doctype-triggers/#What_Fires_Doctype_Triggers) fire either `DOCUMENT_VERSION` or `DOCUMENT` scoped triggers, not both, with one exception: The only operation that can fire both a `DOCUMENT` and `DOCUMENT_VERSION` level trigger is if the API or SDK is used to delete a specific document version, and that version is the last remaining version. This will fire both the `DOCUMENT` and `DOCUMENT_VERSION` level triggers.

## Document Version Events {#DOCUMENT_VERSION}

Doctype triggers scoped to `DOCUMENT_VERSION` only fire on a specific version of a document, which occur any time data on a document version changes or any time a document is upversioned. In Vault, documents are versioned much like software versioning. Document versions are in the format `{major_version}.{minor_version}`. For example, creating a new document starts at version `0.1`. There is no version `0.0`. Learn more about [document versioning in Vault Help](https://platform.veevavault.help/en/gr/162).

When creating a new draft version of an existing document, Vault increments the version number by 0.1. For example, if a document is version `1.0`, the new draft is version `1.1`. This is a document versioning event.

Some data change operations on a document which do not cause upversioning may be considered a [document-level event](/vault-sdk/entry-points/triggers/doctype-triggers/about-doctype-trigger-event-levels/#DOCUMENT), and do not fire triggers which are scoped to `DOCUMENT_VERSION`.

## About Document-Level Events {#DOCUMENT}

Doctype triggers scoped to `DOCUMENT` only fire on events that affect an entire document, rather than a specific document version. The majority of operations in Vault are executed against document versions, but there are some operations that are performed at the document level.

For example, the following operations are considered document-level events:

* Creating a new document

* Deleting a document, including delete operations on a document version if that version is the last remaining version for the document

<Aside type="note" title="Note">Not all document-level events fire triggers.

</Aside>
Not all document-level events fire triggers. Specifically, because `UPDATE` doctype triggers can only update the latest version of a document, document-level events which update a document do not fire triggers.
In other words, all `UPDATE` triggers only fire on `DOCUMENT_VERSION` events and not on `DOCUMENT` events. Document-level events which update a document do not fire triggers.

For example, archiving a document in the Vault UI is considered a document-level event, but this does not fire `DOCUMENT` triggers. However, updating the `archive__v` field of a document version would fire `DOCUMENT_VERSION` triggers scoped to an `UPDATE` event.

Similarly, document check in and check out is considered a document-level event, but this does not fire `DOCUMENT` triggers. However, if checking in a document results in a new document version, this would fire `DOCUMENT_VERSION` triggers scoped to an `INSERT` event.



---

**Previous:** [Doctype Triggers](/vault-sdk/entry-points/triggers/doctype-triggers)  
**Next:** [About Doctype Trigger Events](/vault-sdk/entry-points/triggers/doctype-triggers/about-doctype-trigger-events)