Files

The Files tab shows the app's persistent disk, mounted at /data — see Persistent storage. An app without persistent storage has no files to show.

Who can use it

Action	Allows	Held by
apps/readFiles	Browse, preview and download files	Owner, Contributor, Apps Operator, Platform Owner, Platform Contributor
apps/writeFiles	Upload, create folders, rename, move and delete	The same roles

Both are data actions. Reaching the disk runs a command in the app's instance, so neither is part of Reader, Apps Reader or Platform Reader. The tab is hidden from callers without apps/readFiles, and the controls that change files are hidden from callers without apps/writeFiles. Every download, upload and change is recorded as activity on the app, refused attempts included; opening folders is not. What the roles that hold these actions can do in Kubernetes is on Permissions.

Browse and download

Open the app and its Files tab. When the app has slots, each has a disk of its own: choose the app or a slot under Component first. Open folders to move down; Refresh reads the folder again.

• Preview shows a text file of up to 1 MiB; anything else has to be downloaded.
• Download saves a file; Download as .tar saves a folder.

Change files

• Upload files, or drop them on the list, to put them in the folder you are in. A folder cannot be uploaded: upload the files in it. One upload can be up to 512 MiB unless your platform administrator set another limit.
• New folder creates a folder; Rename and Delete act on a file or folder. Renaming keeps it in its folder; moving it to another folder is only possible through the API. Deleting a folder deletes everything in it, and cannot be undone.

The app sees a change at once, because it is working on the same disk.

No terminal

Apps have no terminal and no per-container view in the portal. The Files tab and the logs are the ways to look inside a running app.