The file manager is the main day-to-day workspace for normal users. It is where they upload, organize, search, share, move, trash, and restore files and folders.

For admins, it is also one of the most important user-facing surfaces to understand, because many support questions start there.

The current account area is more unified than older releases. The main file manager shell now closely matches the surrounding account pages such as:

• Settings
• Rewards
• Affiliate
• Notifications

Use the file manager to:

• upload files and folders
• create folders
• move or copy items
• search and filter content
• switch between list and grid views
• send items to trash or restore them
• review storage usage and package bandwidth indicators

The sidebar is the navigation layer. Depending on configuration and account state, it can include:

• all files
• recent
• shared
• trash
• rewards and affiliate areas
• account and settings shortcuts
• a logged-in View Plans upgrade path for free users when paid packages exist

It can also show:

• package information
• daily download allowance
• storage quota progress or warning state

If paid packages are configured, View Plans now takes the user to a dedicated logged-in plans page instead of dumping them into the first paid package by guesswork.

The toolbar gives fast control over the current view, including:

• search
• select-all shortcuts
• file-only or folder-only selection helpers
• grid/list toggle
• up-one-level navigation when inside folders

The drop zone is the main upload entry point. Users can drag and drop files, browse from disk, and sometimes use remote URL upload.

The filter bar narrows large libraries by:

• item type
• visibility
• status
• extension
• size
• date
• sort order
• folders-first preference

This is the actual content view. Items can appear in grid view for visual scanning or list view for denser reading.

Grid view is best when:

• users want a more visual layout
• thumbnails or icons matter
• the library is not too dense

List view is best when:

• users want denser scanning
• filenames are long
• users are comparing metadata more than visuals

If one layout feels wrong, make sure the user knows the toggle is there before treating it as a deeper bug.

Fyuhls can support:

• normal browser uploads
• multipart direct-to-storage uploads
• remote URL imports

What the user actually experiences depends on:

• package limits
• upload settings
• configured storage provider
• browser and network behavior

If uploads stall or error:

• check package limits
• check storage health
• check CORS for object storage
• check System Status and background jobs

If the user is on Local Storage, remember that the likely failure domain is different from object storage:

• local permissions
• route availability
• request size limits
• multipart temp staging

Important filters:

• Search for one file or folder by name
• Type for mixed folders
• Visibility for public vs private review
• Status for active vs processing items
• Sort for newest-first and largest-first review

Saved filters help users who repeatedly rebuild the same view.

Users can typically:

• create folders
• open folders
• move files into folders
• move folders into other folders
• rename folders
• send folders to trash

If a folder does not appear where expected, first determine whether the user moved it, copied into another location, sent it to trash, or is looking at a filtered view.

Trash is a soft-delete layer, not immediate destruction.

That means:

• items moved to trash should appear in the Trash view
• items can usually be restored from trash
• permanent delete is separate and more destructive

If a user says something disappeared, check Trash before assuming it is gone.

Items restored from trash return to active state. Depending on workflow, they may need to be moved again afterward if the user expected a different destination.

The move dialog helps users choose a destination safely. Common destinations include:

• root
• current folder
• parent folder
• recent destinations

Copy is for duplication. Move is for organization.

Depending on site rules and package permissions, users may be able to:

• copy share links
• save a public file into their own account from the download page without re-uploading it
• switch between public and private
• use share-field formats from the share/download UI

The public Link Checker can also matter here now, because users may validate batches of file links and optionally copy eligible public files into their own account when that feature is enabled by the admin.

If sharing does not behave as expected, check:

• package entitlements
• file visibility state
• whether the item is still processing

The file manager can surface:

• storage quota usage
• daily download bandwidth remaining
• near-capacity warning colors

If users report failed uploads or missing upload options, check package storage limits, site storage capacity, and whether the user is over quota.

Check:

• current folder
• search
• filters
• trash
• whether it was copied rather than moved

Check:

• package limits
• quota
• storage-node health
• object-storage CORS
• multipart session health and cron

Check:

• whether the item is really in Trash
• whether the action is restore vs move
• whether the view is filtered in a way that hides the item afterward

Check:

• very large folders
• browser or device constraints
• current filters and sort order
• storage or server health

• learn the file manager well before troubleshooting user upload complaints
• treat Trash as the first stop for missing-file reports
• teach users search and filters before escalating navigation complaints
• separate file-manager UI issues from storage, package, or cron issues

The file manager is the user workspace. If you understand search, filters, trash, move/copy behavior, upload state, and quota warnings, you can solve a large percentage of user-facing support questions quickly.