Loading

Understanding the "Query Non Vetoed Files" Permission and Salesforce File Access Issues

Publiceringsdatum: Aug 26, 2026
Beskrivning

Some Salesforce users run into unexpected trouble accessing their own files. This can show up as an inability to upload files through the user interface (UI), file access failures when using the REST API, errors in Apex code, or a broken "save/preview" step after uploading a branding image in Survey. In every case, the user is unable to find files they uploaded or expect to have access to.

The root cause is almost always the same: the "Query Non Vetoed Files" permission combined with the "Enable Files to be ingested into Data Cloud" org setting. This article explains why that combination breaks file access and how to fix it.

Symptoms

  • Users cannot find their own uploaded files.
  • File access issues occur when using Apex code.
  • File access problems are observed when uploading files through the Salesforce UI.
  • File access problems occur when accessing files through the REST API.
  • Error: "Unable to upload survey branding" after uploading a background image in the Survey builder.
  • Uploading a file within Document AI results in a gray "Done" button that is not clickable in the file upload modal.

Cause

This issue is related to the "Query Non Vetoed Files" user permission and a related organization-level setting. When both the "Query Non Vetoed Files" permission is enabled for a user and the "Enable Files to be ingested into Data Cloud" organization setting is also enabled, Salesforce applies a filter that restricts file search results to only files marked as public.

These settings are intended for specific system integrations, not for regular user accounts. The "Query Non Vetoed Files" permission is designed for machine-to-machine (M2M) integrations that handle data ingestion into Data Cloud - it is not meant for individual users, including administrators.

Key Takeaway

The "Query Non Vetoed Files" permission is intended for machine-to-machine (M2M) integrations system-to-system connections that ingest data into Data Cloud without human user interaction. It should never be assigned to a regular user or admin profile.

Lösning

This section explains how to fix file access problems caused by the "Query Non Vetoed Files" permission, by finding and disabling the permission for any affected user.

Steps to Resolve

  1. Navigate to the affected user's detail page in Setup and click "View Summary."
  2. Go to the "User Permissions" tab and search for "Query Non Vetoed Files."
  3. If the permission is enabled, it appears in the search results. Click the actions button (chevron) next to the permission and select "Access Granted By." This shows the profile or permission set that grants the permission.
  4. Edit the identified profile or permission set and disable the "Query Non Vetoed Files" permission.

Additional Information

The "Enable Files to be ingested into Data Cloud" setting is found under Setup > Salesforce Files > General Settings. This setting, combined with the user permission, triggers the file visibility restriction described above.

For example, when the "Query Non Vetoed Files" permission is assigned to a user and the "Enable Files to be ingested into Data Cloud" setting is enabled, a user who also has "View All Data" and "Query All Files" permissions is still unable to access the file in Lightning Experience. The same record can be opened when switching to Classic. Additionally, queries against the file return no records at all.

Disabling the "Query Non Vetoed Files" permission for regular users restores standard file access behavior.

Knowledge-artikelnummer

004517924

 
Laddar
Salesforce Help | Article