App files vs project files

	App files	Project files
Scope	Shared across every project of the app	One project only
Lifecycle	Included when you export or import the app	Stay with that project
Typical use	Branding, logos, shared assets, custom UI sources	Uploads, exports, product images, client-specific documents
Visibility	Private by default; public only when a link must work without login	`private` (owning end-user + builders) or `project` (any authenticated member of that project)

Project files are a shared workspace with file-level access:

New writes are private by default (form uploads, chat attachments, exports, generated files). To share a file with every authenticated member of the project, a tool must set visibility: "project" explicitly (for example a product image on a Stock page).
Private files stay with the owning end-user. Builders still see them in project Files for support. Each row shows ownership and access as icons (person = end-user file, folder = shared workspace; lock = private, unlocked = shared with the project), with a hover summary. Filters cover All / Shared workspace / End-user files.
End users see their own private files under portal My Files. They can open project-visible files from pages and chat when the app links to them (by file id).

In the UI: App Blueprint → Files for app files, and Files under the selected project for project files.

⌘I

​App files vs project files