To configure this feature:

1. Ensure X-Pages is configured.
2. Navigate to Admin > Users & Groups > Permission Sets.
3. Select the appropriate permission set.
4. Select Objects.
5. Grant the following permissions:

   Object	Object Permission	Object Types	Fields	Field Permission
   html_report__v	CRE	prompt_overlay__v	name__v object_type__v platform__v prompt_context__v logo__v	Edit

6. Navigate to Admin > Configuration > Objects.
7. Select html_report__v.
8. Select the Layouts tab.
9. Create a layout for the prompt_overlay__v object type.

To configure this feature:

1. Ensure X-Pages is configured.
2. Navigate to Admin > Users & Groups > Permission Sets.
3. Select the appropriate permission set.
4. Select Objects.
5. Grant the following permissions:

   Object	Object Permission	Object Types	Fields	Field Permission
   html_report__v	CRED	prompt_overlay__v	name__v object_type__v platform__v prompt_context__v logo__v	Edit

To configure this feature:

1. Ensure X-Pages is configured.
2. Navigate to Admin > Users & Groups > Permission Sets.
3. Select the appropriate permission set.
4. Select Objects.
5. Grant the following permissions:

   Object	Object Permission	Object Types	Fields	Field Permission
   html_report__v	R	prompt_overlay__v	name__v object_type__v platform__v prompt_context__v logo__v	Read

Content developers can develop chatbot interfaces using standard web technologies and the X-Pages library using the getOverlayContext() method to retrieve details about the current Vault CRM context, for example, the active record ID or the current page, and implement custom navigation using deep linking to close the Prompt Overlay UI automatically.

Business admin users can manage which CRM contexts trigger the custom AI interface by creating prompt overlay pages, depending on their requirements. Each page can have one or multiple prompt_context__v selected. For example, a customer might create the following records:

• A Home page for home__v , top_level_xpage_1__v , and top_level_xpage_2__v
• A specialized page for top_level_xpage_3__v
• An Account page for account__v and account_plan__v

To configure a prompt overlay page:

1. Navigate Business Admin > Objects > HTML Reports.
2. Select Create.
3. Select the Prompt Overlay object type.
4. Select Continue.
5. Select the Prompt Context. This is the page from which the overlay should display. The following options are available:
• Home
• Account
• Call
• Account Plan
• Top Level X-Page 1
• Top Level X-Page 2
• Top Level X-Page 3

  See Using the X-Pages Top Level Entry Point to enable this feature.

6. Select Mobile_Device for the Platform.
7. Upload a JPEG or PNG file to the Logo field to display a custom brand image in the overlay header. For best results, use an image 22px tall and up to 250px wide. This step is optional.
8. Select Save.
9. Select Upload in the Attachments section.
10. Select the appropriate content zip file.

    Each record should only have one zip file attached. Attachments must be zip files and must contain the index.html file directly in the zip. The attachment limit is 32 MB. Delete previous files if more room is required.

11. Navigate to Business Admin > Objects > VMobile Object Configurations.
12. Ensure a VMOC is enabled for the html_report__v object for the appropriate mobile device.

Users can access company-specific AI guidance directly within their standard Vault CRM workflow by navigating to a supported Vault CRM context, for example, an Account page or the Home screen, and selecting the prompt overlay action, which is visually identical to the standard AI Chat icon.

Users can only view one prompt overlay X-Page at a time. If multiple records are configured, the first record by name displays.

If a prompt overlay X-Page is available for the current entry point, for example, the Account page, and the user selects the prompt overlay action, the prompt overlay displays. Otherwise, the standard Veeva AI Chat displays if available and enabled.

Persistence of data such as conversation history is the responsibility of the external system. X-Page content does not persist when a user closes the chat window or when a user navigates to another window. The chat window reloads the next time the button is selected.