# About Auto-Populated Document Fields

You may notice when creating, classifying, or reclassifying documents that some document fields have a value without you entering anything. Vault automatically fills fields in several ways:

  * **System-Managed Values**: These fields are not editable by users and always auto-populated. These can be automatically populated based on Admin configurations (_Document Number_) or other non-configurable factors like the uploaded source file (_Format_, _Size_, _Created By_, _Last Modified By_).
  * **System-Defaulted Values**: Fields like _Document Name_ are auto-filled by Vault without Admin configuration, but are still editable. For example, _Document Name_ is generated from the file name of the source file.
  * **Binder-Based Default Values**: When you perform certain document actions from within a binder, Vault automatically fills in fields on the document <a href="/en/gr/16628/">based on values provided for the binder</a>. These field values are editable.
  * **Admin-Defined Default Values**: Admins can define an auto-filled **Default Value** within the <a href="/en/gr/592/">document field configuration</a>. These fields are editable, but are pre-populated to provide easier data entry.

<div class="note-border alert-important">
  <div class="alert alert-important" role="alert">
    <div><i class="far fa-exclamation-circle"></i></div>
    <div class="alert-text">
      <p><strong>Important</strong>: Vault updates the timestamp in the <em>Last Modified By</em> field whenever a user interacts with a document. However, this update does not always result in a new field value. In this case, though Vault updated the field, Vault does not log anything to the audit trail because no metadata field values changed.  For compliance reasons, we recommend users always follow the audit trail logs rather than the <em>Last Modified By</em> field to determine document metadata changes.</p>
    </div>
  </div>
</div>