Browse the account file tree
Open Files within the owning active account. Admin selects an authorized account; Customer remains in its own account. Paths are resolved inside the managed root with ownership, quota, link and concurrent-write checks. Suspended or transitional accounts block file and transfer operations even if a previously loaded table is visible.
The workspace lists file/directory type, size, permissions, modification time and ETag. Search is folder-scoped; pagination loads more authorized entries. Symlinks and special objects are not ordinary mutable selections. Uploaded HTML/SVG are never embedded in the trusted Panel origin; downloads are forced attachments.
Upload, pause and resume
Choose a file and start the upload. The client creates an upload session with account_id, target path, size_bytes, last_modified_ms and content type, then sends chunks against the returned upload ID, ETag and confirmed offset. Progress distinguishes confirmed bytes from bytes currently sent. Pause aborts the active transport; Resume upload continues only matching state. Discard saved upload cancels the session. Completion is a separate request; an uploaded chunk count is not final publication.
Edit and change files
Text editing uses GET /v1/file-text and PUT /v1/file-text with a current If-Match ETag and plain UTF-8 body. On edit conflict, reload and reconcile; never overwrite a concurrent change blindly. Rename, move, copy and chmod send account_id, action, source paths, expected ETags and reviewed destination/mode. Create folders through the dedicated directory endpoint.
Use Move to trash for recoverable deletion and inspect View trash before restoring to the original path. Archive creation and safe extraction support the formats offered by the actual dialog, including ZIP and tar.gz/tgz. Review selected entries and destination containment; do not use archives to bypass link or path validation.
Scoped transfer users
The Files workspace's transfer-user section defines a display name, account-relative root and read-only/read-write access. Use supported SSH public-key enrollment, key revocation, user revocation and reconcile actions. Keep one-time secrets private and check the effective service state. An FTP Accounts label refers to this supported scoped transfer workflow, not a universal FTP server or unrestricted shell. FTP Connections inspection is not implemented. Customer SSH application access has its own reviewed grant and is not Linux root.
Verify and troubleshoot
Re-list the target after each operation and download a harmless test file to verify bytes. For an ETag conflict, refresh; for quota denial, check the actual UID/filesystem scope; for an interrupted upload, inspect the existing session. Large streaming downloads depend on browser capabilities and may use a save-file stream. Directory Privacy and a general browser terminal are not implemented.