Validation Suites¶

Starting Point¶

Full Validation Suite¶

Phase 1: Admin Baseline¶

Log in as Admin.

Phase 2: Core Cloud Uploads¶

Log in as Internal User A.

Use Record A.

Use the Lightning record page that contains both Google Client record components:

Uploader component
Attachments component

Run the full file-type upload set from the Uploader component first. Files uploaded from the Uploader component should be validated from the Uploader component. Do not assume they appear in the Attachments component.

Phase 3: Uploader Preview and File Actions¶

Continue as Internal User A.

Use the files uploaded through the Uploader component in Phase 2.

Use the Uploader component as the main entry point for Preview in this phase. Do not use the Attachments component for these Uploader-uploaded files.

Log in as Admin.

Enable Open in Google Drive in Advanced → File Management

Log in as Internal User A.

Confirm Open in Google Drive is offered in Preview for an owned file
Open the file in Google Drive and confirm it opens
Confirm the file opens read only and the folder around it cannot be reached
Confirm Open in Google Drive is not offered for a file owned by another user

Phase 4: Attachments Preview and File Actions¶

Continue as Internal User A.

Use only files uploaded through the Attachments component.

Use the Attachments component as the entry point for Preview in this phase. Do not use Uploader-uploaded files for Attachments-specific checks.

Phase 5: File Explorer¶

Continue as Internal User A.

Use the File Explorer Lightning tab only for this phase. Do not use the record page Uploader or Attachments components for File Explorer-specific checks.

Open File Explorer
Confirm Owned files tab renders correctly
Confirm Shared files tab renders correctly
Confirm files uploaded from the Uploader component appear under Owned files where expected
Confirm files uploaded from the Attachments component appear under Owned files where expected
Open Preview from File Explorer
Upload a file from the File Explorer upload action
Confirm the file uploaded from File Explorer appears in File Explorer
Confirm the file uploaded from File Explorer is placed in the expected default/root Google Drive folder

Use an account with more files than fit on a single page for the list behaviour checks.

Log in as Admin.

Open Advanced → User Interface
Add and reorder columns, then save
Confirm a maximum of 7 columns can be selected
Confirm Title cannot be removed
Add a valid Google File Version field API name as a custom column and save
Add an invalid field API name as a custom column and save

Log in as Internal User A.

Confirm File Explorer shows the configured columns in the configured order
Confirm the valid custom column shows its values
Confirm the invalid custom column renders empty and the list still loads

Log in as Admin.

Restore the default column selection

Continue as Internal User A.

Use one owned file that was uploaded through the Attachments component on Record A.

Use the Attachments component on Record A to open Preview and Share.

Open Preview from the Attachments component
Open Share modal from Preview
Share the file with Internal User B as Viewer
Confirm sharing completes successfully

Log in as Internal User B.

Use the Attachments component on Record A to verify access.

Log in as Internal User A.

Use the Attachments component on Record A.

Open Share modal again from Preview
Change Internal User B access to Collaborator or equivalent edit-level access
Confirm sharing update completes successfully

Log in as Internal User B.

Use the Attachments component on Record A.

Open Preview for the shared file from the Attachments component
Confirm Edit behavior is applied
Confirm collaborator can upload a new version
Confirm collaborator can edit details

Phase 7: Public Link¶

Log in as Internal User A.

Use one owned file that was uploaded through the Attachments component.

Use the Attachments component on Record A to open Preview and Public Link.

Open Preview from the Attachments component
Open Public Link modal from Preview
Create a public link
Open the link in a separate browser/session without Salesforce login
Confirm the public link opens successfully
Revoke the public link
Create a public link & set an expiration date
Confirm the link no longer works after the expiration date

Phase 8: Attach Existing Files¶

Log in as Internal User A.

Use these records:

Record A: original linked record
Record B: additional linked record
Record C: unrelated record

Use the Attachments component for Attach Existing Files. Do not use the Uploader component for this phase.

Phase 9: Multi-Record Security¶

Use the file linked to Record A and Record B.

Use the Attachments component on each record to validate record-based visibility.

Log in as a user who has access to Record A only.

Confirm the file is visible on Record A in the Attachments component
Confirm the file is not visible from unrelated Record C in the Attachments component
Open Preview from the Attachments component on Record A
Confirm resolved access level matches Record A access

Log in as a user who has access to Record B only.

Confirm the file is visible on Record B in the Attachments component
Confirm the file is not visible from unrelated Record C in the Attachments component
Open Preview from the Attachments component on Record B
Confirm resolved access level matches Record B access

Log in as a user who has access to Record C only.

Confirm the file is not visible on Record C in the Attachments component
Confirm the file is not returned in search results
Confirm direct Preview URL does not open the file
Confirm direct File Details URL does not open the file
Confirm file actions cannot be executed from any entry point

Log in as Admin or record owner.

Remove the association between the file and Record A
Confirm users with access only to Record A no longer have record-based access
Confirm users with access to Record B still have access

Phase 10: File Details Page and Global Search¶

Log in as Internal User A.

Use the File Details page directly for this phase.

Open File Details page for an owned file
Confirm file details display correctly
Confirm linked records component renders correctly
Confirm linked records are shown only when the current user has access to those records
Confirm the Salesforce record name is shown in full, including for the record whose name is assembled from several fields
Confirm file actions respect the current user's resolved access level
Open File Details page for a file the current user should not access
Confirm access is denied or safe fallback behavior is shown

Use Salesforce global search for this part.

Search for an owned file by name in global search
Confirm the file is returned in the results
Open the file from the search result
Confirm the Google Client file details page opens rather than a standard record layout
Confirm standard record buttons and the highlights panel are not shown
Confirm the same page opens when the file URL is entered directly
Confirm preview, sharing, versions, and linked records all work from this page
Confirm Open in Google Drive is offered for an owned file and opens the file

Phase 11: Privileged Access¶

Log in as Admin.

Assign the permission set containing Google Client: View All Files to Internal User B

Log in as Internal User B.

Open File Explorer
Confirm a single All Files view is shown instead of the Owned and Shared views
Confirm files owned by other users appear in the list
Confirm the Access column shows View for files that would otherwise be inaccessible
Confirm search and sorting work across the whole list
Open Preview for a file owned by another user
Confirm read-only actions are available and edit-level actions are not

Log in as Admin.

Replace the assignment with the permission set containing Google Client: Edit All Files

Log in as Internal User B.

Confirm the Access column now shows Edit
Confirm edit-level actions are available on a file owned by another user

Log in as External User E.

Confirm no additional files became visible on Experience Cloud pages

Log in as Admin.

Remove both permission set assignments from Internal User B

Log in as Internal User B.

Confirm File Explorer returns to the Owned and Shared views
Confirm files owned by other users are no longer visible

Phase 12: Experience Cloud¶

Log in as External User E.

Use the Experience Cloud test record.

Use the Experience Cloud Uploader component for upload checks and the Experience Cloud Attachments component for file list, View All, and Preview checks.

Log in as Internal User A.

Use the internal Core Cloud Attachments component on the Experience Cloud test record.

Open Share modal for a file linked to the Experience Cloud record from Preview
Enable external visibility for the related record
Save sharing changes

Log in as External User E.

Use the Experience Cloud Attachments component.

Refresh the Experience Cloud record page
Confirm the externally visible file appears in the Experience Cloud Attachments component
Open Preview from the Experience Cloud Attachments component
Confirm Viewer behavior where expected
Confirm unrelated linked records are not exposed

Phase 13: Folder Structure¶

For each folder structure configuration, log in as Admin first, change the folder structure, then log in as Internal User A and validate upload/attach behavior.

Use these component rules for this phase:

Record-page Uploader component validates upload behavior from Uploader and Uploader-only file visibility
Record-page Attachments component validates upload behavior from Attachments, Attachments-only file visibility, and Attach Existing Files
File Explorer validates File Explorer upload behavior separately

No Folder Structure / Default Folder Only¶

Log in as Admin.

Configure No folder structure / Default folder only

Log in as Internal User A.

Upload a file from the Uploader component
Confirm the file appears in the Uploader component
Upload a file from the Attachments component
Confirm the file appears in the Attachments component
Upload a file from File Explorer
Confirm the file appears in File Explorer
Confirm files uploaded from Uploader, Attachments, and File Explorer are placed in the default/root configured folder
Attach an existing file to another record using Attach Existing Files from the Attachments component
Confirm no record-specific or user-specific folder is created

Folder per Record¶

Log in as Admin.

Configure Folder per Record

Log in as Internal User A.

Upload multiple files at once to a record that has no Google files yet, using the Uploader component
Confirm the files appear in the Uploader component
Confirm exactly one folder was created for that record
Confirm every file of that upload is placed in the same folder
Upload another file to the same record using the Attachments component
Confirm the file appears in the Attachments component
Confirm the existing record folder is reused
Upload a file to a different record using the Uploader component
Confirm a different record folder is used

Log in as Internal User B while Internal User A uploads to the same new record at the same time.

Confirm both users' files land in the same record folder
Confirm no duplicate folder is created for that record

Continue as Internal User A.

Attach an existing file to a record that has no Google Drive folder yet, using Attach Existing Files
Confirm the record folder is created under the configured upload folder
Confirm the record folder is not created inside the folder of the attached file
Confirm the expected Drive representation is created in the target record folder

Folder per User¶

Log in as Admin.

Configure Folder per User

Log in as Internal User A.

Log in as Internal User B.

Upload a file from the Uploader component
Confirm the file appears in the Uploader component
Confirm file is placed under Internal User B folder
Upload a file from the Attachments component
Confirm the file appears in the Attachments component
Confirm Attachments upload is placed under Internal User B folder
Confirm Internal User A and Internal User B use different user folders

Folder per Record → User¶

Log in as Admin.

Configure Folder per Record → User

Log in as Internal User A.

Upload a file to a record using the Uploader component
Confirm the file appears in the Uploader component
Confirm file is placed under Record → User path
Upload a file to the same record using the Attachments component
Confirm the file appears in the Attachments component
Confirm Attachments upload is placed under the same Record → User path
Attach an existing file to another record using Attach Existing Files from the Attachments component
Confirm expected Drive representation is created under the target Record → User path

Log in as Internal User B.

Upload a file to the same record using the Uploader component
Confirm the file appears in the Uploader component
Confirm Internal User B uses a separate user folder under the same record folder

Folder per User → Record¶

Log in as Admin.

Configure Folder per User → Record

Log in as Internal User A.

Phase 14: Multiple Upload Folders¶

Log in as Admin.

Add a second folder under Folder Locations and save
Confirm both folders are listed in the configured order
Confirm up to ten folders can be added

Log in as Internal User A.

Upload a file from the Uploader component
Confirm the file is placed in the first configured folder
Confirm the configured folder structure is created inside that folder

Log in as Admin.

Move the second folder to the first position and save

Log in as Internal User A.

Upload a file from the Uploader component
Confirm the file is placed in the newly promoted first folder
Confirm files uploaded earlier remain in their original folder and are still reachable from Salesforce

Log in as Admin.

Remove the second folder and return to a single configured folder

Phase 15: Direct Browser Upload¶

Log in as Admin.

Enable Direct Browser Upload in Advanced → File Management and save
Run Test connection and confirm it succeeds
Confirm no test file was left behind in Google Drive
Deactivate the GoogleDriveDirectUpload CSP Trusted Site, reload the page, run Test connection, and confirm it reports that the browser could not reach Google
Reactivate the CSP Trusted Site

Log in as Internal User A.

Log in as External User E.

Upload a large file from an Experience Cloud page and confirm it completes
Confirm the uploaded file respects Visibility and is not exposed beyond the expected users

Log in as Admin.

Turn Direct Browser Upload back off and confirm large uploads still work from all three components
Confirm logs tagged Google Client for Salesforce show the expected direct upload outcomes and no unexpected errors

Phase 16: Delete and Cleanup¶

Log in as Internal User A.

Use a file linked to multiple records.

Confirm file appears on all linked records in the Attachments/Uploader component
Delete the file from Preview or supported file action
Confirm the file is removed from all linked records & Google Drive

Phase 17: Gemini Configuration¶

Log in as Admin.

Log in as Internal User A.

Use the two labels defined for this phase.

Upload a file that clearly matches one of the defined labels
Confirm the label is applied and shows next to the file name in Preview
Confirm the label is listed in the File Intelligence panel
Confirm the same label is applied to the file in Google Drive
Confirm a Google File Version Label record exists for that version with its name and confidence
Upload a file that matches none of the defined labels and confirm it stays unlabeled

Log in as Admin.

Add the Labels column in Advanced → User Interface and save
Raise the minimum confidence above what the model returned

Log in as Internal User A.

Confirm the Labels column shows the applied label in File Explorer
Search File Explorer by the label name and confirm the labeled file is found
Confirm the Labels column cannot be sorted
Open the File Details page for the labeled file and confirm the Labels card lists the label, the version it belongs to and the confidence
Open the File Details page for an unlabeled file and confirm the Labels card shows nothing rather than failing
Upload the same kind of file again and confirm no label is applied at the higher confidence

Log in as Admin.

Set the minimum confidence back and set a thinking budget

Log in as Internal User A.

Upload a matching file again and confirm labeling still completes
Make the labeled file externally visible for the Experience Cloud test record

Log in as External User E.

Confirm the labeled file shows its label in the Experience Cloud preview
Confirm labels of files the external user cannot access are not visible

Log in as Admin.

Disable the Enable AI File Intelligence setting
Confirm AI Labeling is switched off together with AI Analytics
Confirm the reminder that AI analysis is off shows as a notice in the corner of the page and can be dismissed

Log in as Internal User A.

Use Preview opened from the same component where the files were uploaded.

Open Preview for the file
Confirm AI File Intelligence actions are not available after the setting is disabled
Confirm a file that already has a summary or a label keeps its preview sidebar, and that it stays closed until opened
Confirm asking a question is unavailable and the panel explains that questions are turned off
Confirm a file with no summary and no label shows no sidebar at all
Upload another new file after Enable AI File Intelligence is disabled
Confirm no new summary is generated for files uploaded while Enable AI File Intelligence is disabled
Confirm no label is applied to files uploaded while Enable AI File Intelligence is disabled

Phase 18: Agent Platform / Vertex Configuration¶

Log in as Admin.

Disable or clear Gemini configuration where needed
Configure Agent Platform / Vertex
Validate Agent Platform / Vertex configuration
Configure summary prompt
Configure question-answering prompt
Configure token limits
Enable the Enable AI File Intelligence setting

Log in as Internal User A.

Log in as Admin.

Disable the Enable AI File Intelligence setting

Log in as Internal User A.

Use Preview opened from the same component where the file was uploaded.

Confirm AI File Intelligence actions are not available while Agent Platform / Vertex remains configured but Enable AI File Intelligence is disabled
Upload another new file after Enable AI File Intelligence is disabled
Confirm no new summary is generated for files uploaded while Enable AI File Intelligence is disabled

Phase 19: AI Prompt Security¶

Log in as Admin.

Re-enable Enable AI File Intelligence
Confirm Advanced → Safety & Customization shows Standard as the active mode when nothing was chosen
Confirm the safety settings are disabled while File Intelligence is off and enabled once it is on

Log in as Internal User A.

Use Preview with the AI sidebar open.

Ask a normal question about the document and confirm it is answered
Ask the model to ignore its instructions and confirm the request is refused with a readable message
Ask the model to reveal its configuration or system prompt and confirm the request is refused
Ask an unrelated general-knowledge question and confirm it is refused
Confirm a refusal does not break the preview or the sidebar

Log in as Admin.

Set the mode to Strict

Log in as Internal User A.

Confirm normal questions are still answered
Confirm a very long question is refused with a message about length

Log in as Admin.

Set the mode to Off

Log in as Internal User A.

Confirm questions are answered without inspection

Log in as Admin.

Set the mode back to Standard
Enter a class name that does not exist in Custom AI Prompt Safety Guard Class and save

Log in as Internal User A.

Confirm questions are still answered and the shipped protection is still applied

Log in as Admin.

Clear the Custom AI Prompt Safety Guard Class field

Phase 20: Admin and Permission Checks¶

Log in as Admin-level non-system user without View All Data, but with Google Client Admin permission.

Open Google Client admin functionality available to Google Client admins
Open Analytics tab
Confirm Logger Admin Dashboard renders where expected
Confirm admin user cannot perform day-to-day file operations from Uploader, Attachments, File Explorer, or Preview unless user permissions are also assigned

Log in as regular operational user without admin permissions.

Confirm admin configuration pages are not accessible
Confirm Analytics dashboard is not accessible
Confirm operational file features still work from Uploader, Attachments, File Explorer, and Preview where user has record/file access

Phase 21: Flow Actions¶

Log in as Admin.

Build one screen flow on a record page that calls the four actions in turn, each with a fault path.

Phase 22: Final Sweep¶

Use the final intended release configuration.

Quick Regression Suite¶

Use this when changes are small and isolated, but you still want confidence across the main flows.

Phase 1: Admin Baseline¶

Log in as Admin.

Confirm Google Drive integration is configured and validated
Confirm current folder structure configuration is known
Confirm current AI provider configuration is known
Confirm the Enable AI File Intelligence checkbox state is known
Confirm the Direct Browser Upload state is known
Confirm the configured File Explorer columns are known
Open Google Client app and confirm configuration tabs render without errors

Phase 2: Upload and Preview¶

Log in as Internal User A.

Use Record A.

Use both record-page components in this phase:

Phase 3: Versioning¶

Continue as Internal User A.

Use Preview opened from the same component where the previewable file was uploaded.

Upload a new version for the previewable file from Preview
Confirm the latest version becomes active
Confirm Preview uses the expected latest version
Confirm Download uses the expected latest version

Continue as Internal User A.

Use a file from the component where it is visible.

Open Preview from the component where the file is visible
Share the file with Internal User B as Viewer from Preview

Log in as Internal User B.

Use the same component path where the shared file is expected to appear.

Open the same record
Confirm the shared file is visible in the expected component
Open Preview from the expected component
Confirm read-only behavior
Confirm download works
Confirm edit/version/delete/share/public link actions are not available

Phase 5: File Explorer¶

Log in as Internal User A.

Use an account with more files than fit on a single page.

Open File Explorer
Confirm the list renders and the configured columns are shown
Scroll to the bottom and confirm more rows are appended without repeats
Search by part of a file name and confirm the expected file is found
Sort by Last Modified Date and confirm the order is correct
Select Refresh and confirm the list reloads
Open Preview from File Explorer

Phase 6: Attach Existing File¶

Log in as Internal User A.

Use the Attachments component.

Open another Salesforce record
Open Attach Existing Files from the Attachments component
Confirm owned files are available
Attach an existing owned file
Confirm the file appears on the second record in the Attachments component
Confirm the same file still appears on the original record in the Attachments component where expected
Confirm File Details shows linked records where available

Phase 7: Access¶

Use a file linked to two records.

Use the component where the file is expected to be visible for record-level visibility and Preview access checks.

Confirm a user with access to a linked record can see the file in the expected component
Confirm a user with access only to an unrelated record cannot see the file in the expected component
Confirm direct Preview URL does not bypass access checks
Confirm direct File Details URL does not bypass access checks

Phase 8: Folder Structure¶

Use the currently configured folder structure.

Use the Uploader component, Attachments component, and Attach Existing Files flow explicitly in this phase.

Upload one file from the Uploader component
Confirm the file appears in the Uploader component
Upload one file from the Attachments component
Confirm the file appears in the Attachments component
Confirm files are placed in the expected Google Drive folder
Upload several files at once to a record that has no Google files yet, and confirm one folder is created for that record
Attach an existing file to another record using Attach Existing Files from the Attachments component
Confirm Drive placement or shortcut behavior matches the configured folder structure

If the release touched File Explorer upload or folder placement logic, also run this File Explorer check.

Upload one file from File Explorer
Confirm the file appears in File Explorer
Confirm File Explorer upload uses the expected Google Drive folder

If the release touched folder structure logic, also run this reduced folder matrix.

Phase 9: Direct Browser Upload¶

Log in as Admin.

Enable Direct Browser Upload and save

Log in as Internal User A.

Upload one large file from the Uploader and confirm it completes and lands in the configured folder

Log in as Admin.

Disable Direct Browser Upload and save

Log in as Internal User A.

Upload one large file from the Uploader and confirm it completes and lands in the configured folder

Phase 10: Experience Cloud¶

Log in as External User E.

Use Experience Cloud components only for this phase.

Open Experience Cloud page containing Google Client Uploader and Attachments components
Confirm Experience Cloud Uploader component renders without errors
Confirm Experience Cloud Attachments component renders without errors
Confirm files are hidden in the Experience Cloud Attachments component by default unless external visibility is enabled
Open a visible file from the Experience Cloud Attachments component
Confirm Preview works
Confirm external user sees only allowed actions

Phase 11: AI¶

Run this phase only if AI configuration or AI-related UI was touched.

Log in as Admin.

Confirm Gemini or Agent Platform / Vertex configuration is available
Confirm the Enable AI File Intelligence checkbox is in the expected state
Confirm prompts and token limits can be saved

Log in as Internal User A.

Use the component where the file should be validated.

Files uploaded before Enable AI File Intelligence was enabled are not expected to receive summaries.

Phase 12: Final Smoke Check¶

Internal user can open Core Cloud record pages without errors
External user can open Experience Cloud pages without errors
Admin can open Google Client app without errors
Uploader component works where expected
Attachments component works where expected
File Explorer works where expected
Google Files are returned by global search and open on the Google Client file details page
No critical errors appear in the UI
No critical errors appear in logs

Targeted Regression Suite¶

Use this when you want to validate what was added/changed, without running a full suite.

Validation Suites¶

Starting Point¶

Full Validation Suite¶

Phase 1: Admin Baseline¶

Phase 2: Core Cloud Uploads¶

Phase 3: Uploader Preview and File Actions¶

Phase 4: Attachments Preview and File Actions¶

Phase 5: File Explorer¶

Phase 6: Internal Sharing¶

Phase 7: Public Link¶

Phase 8: Attach Existing Files¶

Phase 9: Multi-Record Security¶

Phase 10: File Details Page and Global Search¶

Phase 11: Privileged Access¶

Phase 12: Experience Cloud¶

Phase 13: Folder Structure¶

No Folder Structure / Default Folder Only¶

Folder per Record¶

Folder per User¶

Folder per Record → User¶

Folder per User → Record¶

Phase 14: Multiple Upload Folders¶

Phase 15: Direct Browser Upload¶

Phase 16: Delete and Cleanup¶

Phase 17: Gemini Configuration¶

Phase 18: Agent Platform / Vertex Configuration¶

Phase 19: AI Prompt Security¶

Phase 20: Admin and Permission Checks¶

Phase 21: Flow Actions¶

Phase 22: Final Sweep¶

Quick Regression Suite¶

Phase 1: Admin Baseline¶

Phase 2: Upload and Preview¶

Phase 3: Versioning¶

Phase 4: Internal Sharing¶

Phase 5: File Explorer¶

Phase 6: Attach Existing File¶

Phase 7: Access¶

Phase 8: Folder Structure¶

Phase 9: Direct Browser Upload¶

Phase 10: Experience Cloud¶

Phase 11: AI¶

Phase 12: Final Smoke Check¶

Targeted Regression Suite¶