Unique identifier for the approved document record within the system, typically auto-generated and used as a primary key.

Specifies the object type of the approved document, as defined by Vault's object model. Commonly reflects the classification or template used.

System-generated identifier used to uniquely represent the document across all Vault instances and integrations.

System URL link that provides direct access to view or download the approved document in Vault.

The official name or title of the approved document, typically stored in the 'name__v' field in Vault.

Indicates the current approval or workflow status of the document, such as Draft, Approved, or Obsolete.

The username or system identifier of the user who initially created the document entry in Vault.

The timestamp indicating when the document record was first created in Vault.

The username or identifier of the last user who updated the document entry.

The timestamp of the most recent modification made to the document record.

Specifies whether the document can be associated with any product fragment without restriction. When set to true, all fragments are permitted.

A comma-separated list of Vault document IDs that are explicitly allowed for association or referencing. Format: id1, id2, id3.

Defines the intended audience for the document, which can include specific roles, territories, or user groups.

List of users or groups to be blind carbon copied when the document is distributed. Stored as a comma-separated string.

Indicates whether consent validation is required before distributing or displaying the document to users.

A detailed textual description of the document's contents, purpose, or context as defined by the owner or creator.

The fully qualified URL of the host or server that stores the approved document, typically external to Vault.

External identifier assigned to the document for integration with external systems. Often aligns with a source system's reference.

The date and time when the document metadata or content was last updated within Veeva Vault specifically.

Indicates whether documents can be included as attachments or links in outbound emails. This setting governs whether document distribution via email is permitted.

Specifies the domain used in the sender's email address when distributing approved content, such as @pharma-company.com.

The email address that appears in the 'From' field of outbound communications containing approved documents. This is used to indicate the source of the message.

The display name shown in the 'From' field of outgoing emails. This is typically represents a department, brand, or user responsible for the email.

The email address that recipients should reply to when responding to emails with approved documents. This can differ from the sender address for routing purposes.

The display name that accompanies the 'Reply-To' address in the email header. Helps clarify the intended contact for replies.

The subject line used in emails distributing approved documents. This is typically includes campaign-specific or document-specific context to inform recipients.

The Vault document ID referencing the footer fragment used in email templates. Commonly contains legal disclaimers, opt-out information, or branding.

The document ID used within Veeva Engage for remote detailing or rep-triggered email. Connects this record to its Engage content counterpart.

Indicates the specific subtype of an events management scenario that this approved document is associated with. Helps categorize document usage in event contexts.

The document ID for the Important Safety Information (ISI) document that must accompany promotional content. Required for compliance.

A comma-separated list of Vault document IDs representing additional supporting documents associated with the approved content (for example, 12345, 23456, 34567).

The document ID of the Prescribing Information (PI) file that provides essential medical guidance and must accompany certain promotional assets.

The document ID of the primary promotional piece. Serves as the anchor document for the rest of the content in this record.

Specifies how the approved document is distributed, such as email, download link, or embedded content. Controls the method of delivery.

Represents the workflow status of the approved document within Vault (for example, Approved, In Review, or Retired).

Identifies the sales or regulatory territory for which the approved content is authorized. This is used to enforce geographical compliance rules.

The unique identifier for the document within Vault. Links this record to the actual document stored in the Vault platform.

The identifier of the specific Vault instance where the document resides. This is useful in multi-instance environments or integrations.

Describes the category or classification of the approved content, such as Email Template, Sales Aid, or PI Document.

References the product detail group associated with the approved document, used to classify content under a specific therapeutic or promotional group within the Veeva Vault environment.

Points to the approved key message linked to this document, which is typically a standardized, regulatory-compliant communication used in marketing or sales materials.

Identifies the primary product that this approved document supports or promotes, aligned with commercial or medical messaging strategies.

Indicates the survey or feedback mechanism related to this document, often used to assess message recall or HCP engagement.

Specifies the user ID of the Vault owner responsible for this document, generally the person accountable for content management or lifecycle control.

Contains the identifier used in legacy Customer Relationship Management (CRM) systems to associate this document with historical records, supporting system migrations and data lineage.

Flag or reference indicating whether the content is Veeva-managed, enabling integration with downstream modules such as CLM or Vault PromoMats.

Denotes the intended platform(s) for document deployment such as CRM, Approved Email, or external channels like websites or apps.

Indicates the language in which the document content is authored, ensuring correct localization and regulatory compliance for international markets.

Boolean flag indicating whether this document is hidden from general user access or reporting views, often used for archival or admin-only content.

Specifies whether this document is enabled for use in the Veeva Email Builder tool, allowing modular email content assembly.

References the specific email builder configuration associated with this document, such as a template or content block used in multichannel campaigns.

Captures the date and time when the document was last activated or triggered by an automated or manual workflow event.

Path or identifier for the HTML file used as an email content fragment, designed for modular reuse within Veeva Approved Email.

Path or identifier for the main HTML file representing the complete email body that gets sent to recipients through Veeva systems.

Path or identifier for the HTML file used as the email footer fragment, containing regulatory disclaimers, contact info, or unsubscribe links.