A
Actions Menu
An Actions menu (gear icon) allows you to perform various actions on some kind of element in the vault: a document, report, or object, for example. Typically, we refer to the document Actions menu, which provides access to document actions. Available items in the document Actions menu vary by vault configuration, the document/binder’s lifecycle state, the document type’s Create permissions, your security profile, and your role-based permissions on the document.
Related Articles:
About the Document Actions Menu
Admin
See Administrator or Admin Area.
Admin Area
The Admin area is where you’ll find configuration options and administrator-level actions in Vault. To see this area, you must have at least read access to one part of the Admin area through your security profile and permission set.
Related Articles:
Vault Admin Overview
Administrator
Administrators or Admins are users who have permissions (through their security profile) to the Admin area in Vault. The level of access depends on the permission sets. For example, one administrator may have read-only access to all parts of the Admin area except Business Admin, whereas another user may have broader access that allows her to create new document lifecycles, users, permission sets, etc.
Related Articles:
About License Types & Security Profiles
About Permission Sets
Creating & Managing Users
Anchor
See Document Linking.
Annotations
Annotations are comments and markings made within the document viewer to provide feedback on the document.
Related Articles:
Annotating Documents
About the Doc Info Page
Using Document Links & Anchors
API
Application Programming Interface – Vault’s REST-based API that allows for programmatic access to most Vault functions and configurations. Refer to the API Help site for detailed information.
Approved Email
Approved Email is a Veeva product that manages approved emails sent to customers and healthcare providers from Veeva CRM. This tool both ensures that only approved content is distributed and tracks the distribution of specific documents, including prescribing information and promotional pieces. In Approved Email, Vault is the system for configuring and maintaining the email template and fragments of content. The process of selecting documents (as “email fragments”), inserting them into the email template, and choosing recipients happens in Veeva CRM.
Related Articles:
About Approved Email
Audit Log
Audit Logs display a history of actions within your vault. Audit Logs include Document Audit History, Domain Audit History, Login Audit History, and System Audit History.
See also: Document Audit Trail.
Related Articles:
Viewing Audit Logs
Audit Trail
Audit trails are a list of all actions performed in the system. Vault provides audit trails at the document, system, login, and domain levels.
Related Articles:
Viewing the Document Audit Trail
Viewing Audit Logs
B
Base Document
Base Document is the highest level in the document type hierarchy — the parent of all document types. A document or binder cannot be a “Base Document” because this level exists only for configuration purposes. When configuring a setting at the Base Document level, all other document types inherit that setting, unless an Admin defines an override at the individual type, subtype, or classification level.
Related Articles:
Configuring Document Types
Binder
Binders allow you to organize and group documents in a flexible structure. Binders are comprised of sections, which can nest to build a hierarchical structure, and links to documents in Vault.
Related Articles:
Binders Overview
Binder Section
Binder sections provide a method of creating and organizing a hierarchy for the binder’s content. A section contains a name and (optionally) number.
Related Articles:
Binders Overview
Binder Template
Binder templates contain the structure (binder sections) of a binder and “planned” documents serving as markers for documents that should be in the binder.
Related Articles:
About the Document & Binder Template Page
BRD
Business Requirements Definition – List of functional requirements for an area of Vault.
Business Admin
Business Admin is a section within the Admin area. From here, users can access ongoing administration options, such as product or study object records, document templates, and picklist options.
Related Articles:
Vault Admin Overview
C
Catalog
Catalog (or catalogue) refers to a past version (pre-V9) of what is currently called a “Vault Object.” See Object.
Classification
Classification is the lowest level of the document type structure (Type > Subtype > Classification).
Related Articles:
Configuring Document Types
CLM Integration
Closed Loop Marketing (CLM) integration allows you to publish documents and binders to CLM and iRep from within your vault. Vault’s CLM integration replaces the older version of iRep integration.
Related Articles:
Using CLM Integration (PromoMats & MedComms)
Compact View
Compact View is a Library layout that organizes documents into rows and displays a small thumbnail.
Related Articles:
Using Library Layouts
About Vault Library
Content
Content refers to the items that a vault can hold, both individual documents and binders.
Related Articles:
Adding Documents to Vault
Creating Binders
Working with Content Placeholders
Controlling Field
The controlling field is a document field whose value dictates the behavior of other fields in a field dependency configuration. For example, the Readiness Date field is only visible and editable if the For External Use field is set to “Yes.” In this dependency, For External Use is the controlling field.
Related Articles:
Managing Dependent Fields
CTMS
See Medidata CTMS Integration.
CrossLink
CrossLinks (aka CrossLink documents) enable content from one vault to be used in another vault within the same domain. A CrossLink document in your vault uses the viewable rendition from a source document in another vault.
Related Articles:
CrossLinks Overview
D
Dashboards
Dashboards provide an at-a-glance understanding of key metrics. Each dashboard contains one or more dashboard components and each component displays metrics from a report.
Related Articles:
Creating & Editing Dashboards
Data Record
See Object Data Record.
Dependency Rules
Dependency rules define the behavior of dependent fields in a field dependency configuration. For a single condition on the controlling field, the dependency rules may dictate behavior for several dependent fields. Dependency rules can make a field editable, read-only, or hidden. They can also limit the allowed values in a picklist or yes/no field.
Related Articles:
Managing Dependent Fields
Dependent Fields
Dependent fields are those whose behavior (editable, hidden, limited allowed values) is dictated by the current value in another field. For example, the Readiness Date field is only visible and editable if the For External Use field is set to “Yes.” In this dependency, Readiness Date is the dependent field.
Related Articles:
Managing Dependent Fields
Detail View
Detail View is a Library layout that lists documents in rows. Each row shows a thumbnail of the document and important document fields.
Related Articles:
Using Library Layouts
About Vault Library
Doc Info
The Doc Info (or DocInfo) page is the main page that displays information about a document, including document fields, security settings, versions, renditions, related documents, and the document content itself within an embedded viewer.
Related Articles:
About the Doc Info Page
Document
Within Veeva Vault, a document is an object consisting of both content and fields (metadata). The document content is created using an authoring application (e.g., Microsoft Office), and the document fields are entered through the Veeva Vault interface based on specific organization business rules.
Document Audit History
The Document Audit History is a list of all changes affecting a document, including creation, updates to fields or files, and views.
Related Articles:
Viewing the Audit Trail
Viewing Audit Logs
Document Inbox
The Document Inbox shows unclassified documents. The Document Inbox is located in the left-panel of the Library page and is only displayed if the feature is enabled or if you have unclassified documents. Unclassified documents are those that need to have a type, subtype, and/or classification assigned.
Related Articles:
About Vault Library
Document Lifecycle
A document lifecycle is the sequence of states (Draft, In Review, etc.) that a document goes through during its life. Each lifecycle has associated business logic, including workflows and permissions for specific user roles.
Related Articles:
About Document Lifecycles
Defining Document Lifecycles
Document Lifecycle State
Lifecycles are a sequences of states (Draft, In Review, etc.) that a document goes through during its life. For each individual state, Admins can configure various settings, including entry criteria, automated document actions, user-initiated actions, and user permissions. A document’s current state appears in the Status field.
Related Articles:
About Document Lifecycles
Defining Document Lifecycle States
About Special States
Document Linking
Document links allow you to link specific pages or paragraphs between documents in your vault. When a user creates a link, Vault then creates a reusable anchor on the target document. Once created, other users can reuse that anchor for links from other documents. Users to add multiple anchors to a single link annotation. For example, a specific chart in a promotional piece could use multiple other documents as references. The user could create a single link annotation and add as many different anchors to it as needed.
Related Articles:
Using Document Links & Anchors
About Document Relationships
Document Owner
Document Owner or “Owner” is a standard user role that applies to all documents and binders. Vault automatically assigns this role to the user who creates a document, but that user or an Admin can reassign the role to another user. This is a single-user role, so for a given document, only one user may be in the role at a time. Permissions available to this user are based on security matrix settings.
Related Articles:
Sharing Documents
Configuring Document Role-Based Permissions
Document Package (eTMF)
Document packages are a way to link multiple documents together and simultaneously start workflows on that set of documents.
Related Articles:
Enabling Document Packages & Setting Up Defaults
Working with Document Packages
Document Relationship
Document relationships are a way of linking two documents; relationships show up in the fields panel of the Doc Info page and in the Where Used view. Some relationships are created automatically (for example, when users make a copy of a document, there is a relationship between new document and original document).
Related Articles:
Using Document Links & Anchors
About Document Relationships
Document Role
A document role is a way of assigning users a specific set of permissions on a specific document. Each document has multiple roles to which users belong. You can see who has each role from the Sharing Settings panel in the Doc Info page.
Each user’s role on a document, combined with the document’s current lifecycle state, dictates that user’s document-level permissions. For example, the user in the Owner role may be able to delete the document in Draft state, but not in Approved state. A user in the Viewer role may never be able to delete the document.
Related Articles:
Sharing Documents
Creating Custom Roles
Configuring Document Role-Based Permissions
Document Sharing Settings
Sharing Settings is a panel in the Doc Info page where you can see the users currently assigned to roles on the document and make changes to these assignments.
Related Articles:
Sharing Documents
Configuring Document Role-Based Permissions
About the Doc Info Page
Document Template
Admin-configured document templates allow users to create a document using the template’s source file rather than uploading new content. Templates are associated with a specific document type.
Related Articles:
About the Document & Binder Template Page
Document Thumbnail
Thumbnails are a small image version of a document’s viewable rendition that appears in some of the Library layouts (detail, compact, and tile view).
Related Articles:
About Vault Library
Document Type
Document type refers both to the structure of hierarchical fields (Type > Subtype > Classification) that determines the relevant document fields, rendition types, and other settings for a document, and to the highest level in that hierarchy.
Related Articles:
Configuring Document Types
Document Version Number
A document’s version number is in the format x.y where “x” is the major version and “y” is the minor version. There is a lifecycle state entry action that will increment a document’s major version and reset the minor version back to zero. The document version number is a standard field used to track version history for documents. Depending on your vault’s field-level security, users may be able to modify the initial version number when creating new documents.
Related Articles:
Managing Document Versions
Document Viewer
The document viewer is a portion of the Doc Info page where Vault displays a document’s viewable rendition and users can add or view annotations.
Related Articles:
Annotating Documents
Viewing Annotations in Notes View
About the Doc Info Page
Document-Level Comments
Document-level comments are a mechanism to provide feedback on a document that is not related to a specific portion of the document. Document-level comments are tied to a specific version of a document.
Related Articles:
Using Document-Level Comments
Annotating Documents
Domain
A domain is an instance of Veeva Vault that belongs to a single customer and shares several settings. Each company using Vault has one or more domains and each domain has one or more vaults. Domains with more than one vault are often called “multi-vault domains.” Some settings, including many security settings, apply at the domain level.
The domain is reflected in the vault’s URL (“pharm” in “https://pharm.veevavault.com”) and in each user’s login name (“pharm.com” in “tibanez@pharm.com”).
Related Articles:
About Veeva Vault Domains
Domain Admin
Domain Admin is a user-level setting that, along with the correct permissions, grants users access to edit domain-level settings and to manage users across vaults. Each domain has at least one user with this setting.
Related Articles:
About Veeva Vault Domains
Managing Users Across Vaults
About Permission Sets
Domain Audit History
The Domain Audit History page displays changes that occur at the domain level, including updates to user details, security policies, and network access rules
Related Articles:
Viewing Audit Logs
Dynamic Access Control (DAC)
Dynamic Access Control for documents and objects is a way of making access control more programmatic and less manual.
Related Articles:
About Dynamic Access Control on Objects
About Dynamic Access Control on Documents
E
Editor
See Document Role or Object Record Role.
Electronic Signature
See eSignature.
Entry Action Formulas
These are document lifecycle state entry actions that use the action type Set field with using formula. This action sets the value of a number, text, or date field using a formula expression.
Related Articles:
Setting Fields with Formulas
Defining Document State Entry Actions
eSignature
An eSignature (or electronic signature) is a way for users to officially “sign” a document in Vault by re-entering their usernames and passwords. Admins can configure Vault to prompt for an eSignature as part of a workflow. Admins can also set Vault to auto-generate signature pages through the Signature Manifestation feature.
Related Articles:
Managing eSignature Manifestation
Configuring Workflow Steps
Engage Integration
Engage integration allows you to publish documents to Engage from within your vault. Veeva’s Engage application is an integrated customer relationship management (CRM) and closed-loop marketing (CLM) solution which enables life sciences organizations to interact with healthcare professionals (HCPs) using the Internet on mobile devices.
Related Articles:
Using Engage Integration (PromoMats & MedComms)
Enhanced Checkout
Enhanced Checkout is a feature that allows Vault to automatically download files to a known location on a user’s machine and launch a default application (determined by file type) upon checkout.
Related Articles:
Managing Document Versions
Enabling Enhanced Checkout
Configuring Enhanced Checkout
eSignature Template
See Signature Page Template.
eTMF
Vault eTMF is an end-to-end application to manage the set of documents contained within a Trial Master File (TMF).
Related Articles:
eTMF Application
External User
External User is a license type for users outside your company who have slightly limited access; these users have most functionality, but cannot use reports, use dashboards, or provide eSignatures. Note that the domain in the user’s email address cannot match the vault’s licensing domain.
Related Articles:
About License Types & Security Profiles
Creating & Managing Users
F
Federated ID
Federated ID allows Vault to associate the user with an external user ID for single-sign-on or other system integration purposes.
Related Articles:
Single Sign-On Basics
Configuring Single Sign-On
Field
Fields include both Admin-configurable and standard fields which hold additional details/metadata for each document or object; document fields can apply to all documents or specific document types/subtypes/classifications and can be required/optional.
Field Layout
The field layout defines how the document fields and field sections are displayed in the Doc Info page. This is Admin-configurable.
Field Level Security
Field-level security allows Admins to set fields as read-only, hidden, or editable for specific users or groups. Field-level security can only further restrict security applied at the document level via the security matrix and sharing settings. It cannot give a user more permissions on a specific field than they would otherwise have.
Related Articles:
Configuring Field-Level Security
Form 2253 (FDA)
Form 2253 is an FDA form for submitting promotional pieces. In Vault, users can use a Compliance Package binder and attached promotional pieces to generate and populate an FDA Form 2253. This feature is only available on vaults that use the PromoMats application.
Related Articles:
Generating Form 2253 (PromoMats)
Formula Field
Formula fields are custom document fields that use a formula to calculate a numeric value. These are only visible in reports, not in the Doc Info page or through the API.
Related Articles:
Creating Custom Reporting Metrics with Formula Fields
Full User
Full User is a license type for standard users. This license type does not block access to any functionality. Users with this license type may be end users or administrators. This is the only license type that allows access to Admin functionality.
Related Articles:
About License Types & Security Profiles
Creating & Managing Users
G
Gear Menu
See Actions Menu.
GMT
See UTC.
Group
A group is simply a named list of users. By defining groups that reflect the teams and business functions in your company and assigning those groups to document roles, you can manage document access more easily.
Related Articles:
Creating & Managing Groups
GxP
GxP is an acronym for Good “X” Practices, where “X” could be Clinical, Manufacturing, Laboratory, etc.; this is a general term used in life sciences used to describe the standard practices to be followed by a company to ensure compliance with regulatory and corporate standards.
H
Home Page
See Home Tab.
Home Tab
The Home tab is the area that Vault typically loads when a user logs in, also called “Vault Home.” From here, users access their assigned tasks, notifications, and active workflows. Note that this is called the Tasks tab on some vaults.
Related Articles:
About Vault Home
Hover Card
When hovering over certain elements (document names, object labels, etc.) for more than a second, Vault displays a summary of the element’s information in a small pop-up “hover card”. These are available in many areas of Vault, including Library, Home, and Reports tabs. In the Doc Info page, hover cards display for object-type document fields (Product, Study, etc.) and for selected users. The ability to view information in a hover card or to click through (when available) to its source is controlled by user permissions.
Hovercard
See Hover Card.
HTTPS
Hypertext Transfer Protocol Secure (HTTPS) is a communications protocol for secure communication over a computer network, with especially wide deployment on the Internet. Technically, it is not a protocol in and of itself; rather, it is the result of simply layering the Hypertext Transfer Protocol (HTTP) on top of the TLS protocol, thus adding the security capabilities of TLS to standard HTTP communications. The main motivation for HTTPS is to prevent wiretapping and man-in-the-middle attacks.
I
Identity Provider
An Identity Provider (IdP), also known as Identity Assertion Provider, is responsible for issuing identification certificate and the entity responsible for authenticating a user before allowing the user access to Vault via Single Sign-On (SSO). See Single Sign-On below for more information.
Related Articles:
Single Sign-On Basics
Configuring Single Sign-On
Identity Provider Certificate
See Identity Provider.
Related Articles:
Single Sign-On Basics
Configuring Single Sign-On
IdP
See Identity Provider.
Integration User
In Vault’s various integration features, an “integration user” is a user account set up for use by the integration. For example, if an integration syncs documents, the new document creation or versioning action occurs using the integration user’s account and is subject to that user’s security settings, etc. The audit logs attribute these actions to the integration user.
Related Articles:
About Public Content Distribution
About Medidata CTMS Integration
Investigator Portal
The Vault Investigator Portal is an add-on feature for eTMF vaults that enables Sponsors/CROs and Investigator Sites to collaborate by securely exchanging study documentation. This tool provides behavior tailored specifically for coordinators, investigators, and other clinical study site personnel.
Related Articles:
Using the Vault Investigator Portal
iRep Integration
iRep integration allows you to publish documents and binders to iRep from within your vault. Veeva’s iRep application is an integrated customer relationship management (CRM) and closed-loop marketing (CLM) solution developed exclusively for the iPad and Windows 8 devices.
Related Articles:
Using iRep Integration (PromoMats & MedComms)
L
License Type
License type is a user attribute that Vault uses as the first level of access control for the user. License type trumps any access granted through the user’s security profile or through a document’s sharing settings and security matrix.
Related Articles:
About License Types & Security Profiles
Creating & Managing Users
Lifecycle
See Document Lifecycle or Object Lifecycle.
Lifecycle State
See Document Lifecycle State or Object Lifecycle State.
Lifecycle State Entry Actions
A lifecycle state’s entry actions are a configurable set of system actions that Vault automatically performs on a document or object record when it enters the lifecycle state. Admins can set up entry actions for each individual lifecycle state. Available actions are different for object and document lifecycles. For documents, these include sending notifications, deleting annotations, and setting date fields on the document. For object records, these include sending notifications.
Related Articles:
Defining Document State Entry Actions
Configuring Object Lifecycles
Lifecycle State Entry Criteria
A lifecycle state’s entry criteria are a configurable set of conditions that a document must meet before moving into the state. For example, to enter In Review state, a document must have a viewable rendition. When users move a document from one state to another, Vault confirms that the document meets the new state’s entry criteria and does not allow the change until the criteria are fulfilled.
Currently, entry criteria are not available for object lifecycles.
Related Articles:
Defining Document State Entry Criteria
Lifecycle State User Actions
User actions for lifecycle states are configurable actions that allow users can perform on documents or object records. For documents, these include starting workflows and moving documents to other states. Additional types of user actions are available for specific features and applications, for example, Send to CLM for the CLM Integration feature. For object records, user actions can move the record to another state or execute a custom action.
Once active, user actions appear in the Actions menu for documents/binders or object records that are in the selected state.
Related Articles:
Defining User Actions for Document States
Configuring Object Lifecycles
Locale
Locale is a user-level setting related to localization and the user’s language. This setting controls the display of dates and numbers.
About Localization Settings
Creating & Managing Users
Login Audit History
The Login Audit History page displays the history of user authentication events for a particular vault, including users’ logins, failed login attempts, and password changes; for each event, users can see the timestamp, user making the change, affected item, and description.
Related Articles:
Viewing Audit Logs
Login Message
The login message appears in a pop-up dialog for every user upon logging into a vault; general uses include displaying corporate privacy policies and “safe harbor” messages.
M
Major Version
See Document Version Number.
Manual Assignment
For objects that use Dynamic Access Control, manual assignment is the way to add users/groups directly to roles on a specific object data record, without setting up sharing rules.
For documents, manual assignment is the variety of ways to put users in document roles without using Dynamic Access Control.
Related Articles:
About Dynamic Access Control on Objects
About Dynamic Access Control on Documents
MedComms
Vault MedComms is an end-to-end application to manage medical affairs content, such as literature references, advisory board materials, responses associated with medical information inquiries, health economics outcomes research, and medical grants.
Related Articles:
MedComms Overview
Medidata CTMS Integration
Medidata CTMS Integration is a feature that allows organizations to use Medidata CTMS as the source for Study, Study Country, Study Site, and Location data in an eTMF vault and also automatically syncs visit reports from Medidata.
Related Articles:
About Medidata CTMS Integration
Merge Fields
Merge Fields is a standard, shared document field with two functions. By associating the field to a document type, Admins indicate that the document type supports the Merge Fields for MS Word feature. Vault will auto-populate this Yes/No field based on the contents of a document’s source file. Learn more.
Metadata
“Metadata” in Vault generally refers to information about a document other than the document’s source file, like document field values.
Related Articles:
About the Doc Info Page
Editing Fields for a Document
Editing Fields for Multiple Documents
About Auto-Populated Document Fields
Managing Document Fields
Minor Version
See Document Version Number.
Multilingual Labels
As part of Vault localization, Admins can enter or import (Bulk Translation feature) multilingual labels for various configurable elements, including documents fields, templates, and roles.
Related Articles:
About Localization Settings
N
Network Access Rules
Network access rules allow Admins to limit the IP addresses from which specific users can log into Vault, based on those users’ security policies. Each rule can apply to either a single IP address or an IP range. Network access rules are configured at the domain-level.
Related Articles:
Configuring Network Access Rules
Configuring Password Security Policies
Non-Vault User
A non-vault user is a person accessing documents through Vault who does not have a user account. These users can only view documents sent using the Send as Link feature.
Related Articles:
Using Send as Link
Configuring Send as Link Settings
O
Object
Objects (similar to “catalogs” in previous versions) are a customizable and extensible part of the application data model. They allow you to create a type of item (an object) and individual instances of that item (an object data record). Each instance then has its own set of metadata values. In some ways, objects function similarly to picklist document fields, but with additional metadata. For example, Product is an object. When users select a product for a document, they also associate all of that product’s metadata (compound ID, therapeutic area, etc.) with the document.
Related Articles:
About Vault Objects
Configuring Vault Objects
Object Data Record
Each vault has a data model consisting of objects, their fields, and their relationships. Object data records are pieces of data within this model. For example, Product is a standard Vault object, while WonderDrug is a data record for that object.
Related Articles:
About Vault Objects
Managing Object Data Records
Object Lifecycle
An object lifecycle is the sequence of states (In Approval, Approved, etc.) that an object record may go through during its life. Each state can have associated user actions and entry actions. An object lifecycle may be configured for most objects in your vault, but not all objects use lifecycles.
Related Articles:
About Object Lifecycles
Configuring Object Lifecycles
Object Lifecycle State
Object lifecycles are a sequences of states (In Approval, Approved, etc.) that an object record may go through during its life. For each individual state, Admins can configure various settings, including entry actions and user-initiated actions. States are linked to the object record’s Status, so some states will make a record active, while others will make it inactive.
Related Articles:
About Object Lifecycles
Configuring Object Lifecycles
Object Record Role
For objects using Dynamic Access Control, these are system-defined roles (Viewer, Editor, Owner) on each object data record that control access to the record, including access to select the record when editing document fields.
Related Articles:
About Dynamic Access Control on Objects
Object Record Sharing Settings
For objects that use Dynamic Access Control, Sharing Settings is a section in the object record details that shows all sharing rules and manual role assignments that apply to the record.
Related Articles:
About Dynamic Access Control on Objects
Optional Workflow Task
Optional tasks are those which an Admin set as optional during step configuration. When a task in a workflow is marked as “optional,” the user who starts the workflow can choose whether to include that task or not. The ability to skip tasks is useful when a document has been through a workflow more than once and you do not want to repeat completed tasks.
Related Articles:
Configuring Optional Workflow Tasks
Starting Workflows
Managing Tasks & Participants for Active Workflows
Overlay
Overlays dynamically apply information to a viewable rendition when users download it from Vault. This information can appear in the header, footer, and/or diagonally across the page, but only appears on downloaded renditions and does not affect source files.
Related Articles:
Managing Overlays
Overlay Template
See Overlay.
Owner
See Document Owner or Object Record Role.
P
Permission
“Permission” can refer to two different types of permissions. The first type of permission is applied through a permission set and security profile. These permissions grant application-level access, for example, access to create reports or view the Admin > Settings > General Settings page. The second type of permission is applied through document roles. These permissions grant document-level access, for example, users in the Owner role for a document in Draft state can upload a new source file for that document. Permissions granted to each document role vary based on the document’s lifecycle state.
Related Articles:
About User-Level Security
About License Types & Security Profiles
About Permission Sets
Sharing Documents in Vault
Configuring Document Role-Based Permissions
Permission Set
Permission sets allow organizations to grant application-level access to certain features, particularly system administration functions such as user management or object record creation. Vault applies permission sets to individual users through the users’ security profiles.
Related Articles:
About License Types & Security Profiles
About Permission Sets
Picklist
Picklists allow users to select a value for a field from a range of predefined options.
Related Articles:
Managing Picklists
Planned Document
A planned document is any document in Planned lifecycle state, generally placeholders created as part of a binder template.
Related Articles:
Working with Planned Documents
Portal User
Portal User is a license type for users who have access to the Vault Investigator Portal. These users have most functionality, but cannot access Admin, or use reports and dashboards. When creating documents or using the Study Selector, they can only see Study, Study Country, Study Site, and Product records to which an Admin has granted them access.
Related Articles:
About License Types & Security Profiles
Using the Vault Investigator Portal
Primary Navigation Bar
The primary navigation bar is the orange bar that appears near the top of the page in Vault. Both your permissions and your vault’s configuration can modify what appears in this bar, but many users see at least Home, Library, Reports, and Dashboards. If your vault uses custom tabs, you may see additional options or the options may appear in a different order.
PromoMats
PromoMats is a Vault application to manage the process of creating, reviewing, and approving promotional materials, claims, and supporting information.
Related Articles:
PromoMats Overview
Public Content Distribution
Public Content Distribution allows you to integrate Vault content with your branded sites, using an embeddable external viewer. This feature uses the same external viewer as Approved Email and some of the same supporting functionality.
Related Articles:
About Public Content Distribution
Public Key
Public keys are names that developers can use to access objects, fields, relationships, etc. through the API. For example, status__v for the Status field. In the Admin area, these values are typically called “names.”
Related Articles:
Veeva Vault Developer Network
Q
QMS
Vault QMS (Quality Management System) is an application that manages global quality processes across an organization and its external partners.
QMS Overview
QualityDocs
QualityDocs is an end-to-end application to manage documentation associated with a quality system. Vault QualityDocs provides administration functionality to define product details along with associated country specific details.
Related Articles:
QualityDocs Application
QualityDocs Overview
R
Read & Understand
See Read & Understood.
Read & Understood
Read & Understood refers to a set of functionality in Vault designed to support training and compliance processes that require users to read documents and verify they’ve done so. Documents are assigned to users through tasks in a Read & Understood workflow.
Related Articles:
Configuring Read & Understood Workflows
Working with Read & Understood Workflows
Read & Understood Workflow
Read & Understood workflows have a special workflow type that allows you to assign Read & Understood tasks to users. See Read & Understood.
Read-Only User
Read-Only User is a license type for users with extremely limited access. These users can only view documents (including annotations), download documents, and participate in Read & Understood workflows.
Related Articles:
About License Types & Security Profiles
Reclassify
Reclassifying a document refers to changing the document type, subtype, and or classification after it has been created.
Related Articles:
Reclassifying Documents
Reference Link
Document references allow you to link specific pages or paragraphs between documents.
Related Articles:
Using Document Links & Anchors
Reference Link Annotations
When establishing a reference link, you can optionally provide a comment or annotation.
Related Articles:
Using Document Links & Anchors
Rendition
Renditions are files, other than the source file, that are attached to documents. A document can have multiple renditions.
Related Articles:
Working with Renditions
Role
See <a href="http://vaulthelp2.vo