Control access to content files and objects via API queries with the Query All Files
and Query All Non Vetoed Files user permissions. To grant users access to content files and
objects, create a permission set with user permissions and assign it to users.
Required Editions
Available in: Salesforce Classic and Lightning
Experience
Available in: Group, Professional, Enterprise,
Performance, Unlimited, Contact Manager, and Developer
Editions
User Permissions Needed
To create permission sets:
Manage Profiles and Permission Sets
To assign permission sets:
Assign Permission Sets
The Query All Files user permission requires the View All Data and View All Records
permissions. Users with the Query All Files permission can query all files in the org with SOQL,
including files in nonmember libraries and unlisted groups. Users can’t edit, upload new
versions, or delete files that they don’t have access to.
Users can query the APIs for
ContentDocument
and ContentVersion, and retrieve all files in the org, including files in nonmember libraries
and files in unlisted groups. Users can query ContentDocumentLink without a filter on
Id, LinkedEntityId, and
DocumentId.
On its own, the View All Data permission allows you to query only files that you own or have
access to.
The Query
Non
Vetoed Files user permission allows users to query
all public, non-vetoed files in a Data Cloud org with SOQL. This permission determines which
files can be ingested into Data Cloud. For all
files
that are enabled, the related records in the APIs for ContentDocument,
ContentVersion, and ContentDocumentLink become accessible for ingestion.
After
you turn on the Query Non Vetoed Files user permission,
enable
the setting
Enable Files to be ingested into Data
Cloud.
To assign these permissions to users,
From Setup, in the Quick Find box, enter Permission Sets, and then
select Permission Sets.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.