When building file-upload functionality in Salesforce Communities (Experience Cloud), many developers run into a confusing issue: Partner Community Users cannot upload files using lightning-file-upload , even when they have access to the parent object — such as a Case. This often leads to the common question: “Do Partner Users actually have access to ContentVersion, ContentDocument, and ContentDocumentLink?” Let’s break down the full explanation. Partner Community Users do not have direct access to the objects: ContentVersion ContentDocument ContentDocumentLink These objects are hidden in the profile/permission set UI, meaning you cannot grant CRUD access directly. However… Partner Users can upload files as long as: They have access to the parent record (e.g., Case) The community sharing model allows file visibility The Salesforce system handles ContentDocument & related objects implicitly But certain org settings or sharing restrictions can still...