Use Cases

These are the situations we had in mind when building Next File Manager. They are our suggestions, not a limit. Your site will run differently, so adapt them to your needs, and you may well find a use for it that we haven't thought of.

Managing files beyond the images folder

• Situation: a template override, a backup archive or another file outside images/ means reaching for an FTP client or a hosting control panel.
• How it can help:
  • Browse the Joomla install from Components → Next File Manager, with no setup for Super Users
  • Edit text and code files in place
  • Pack and unpack ZIP files without shell access

Several drives, one interface

• Situation: your files live on another host, a Nextcloud share or an S3-compatible bucket.
• How it can help:
  • Attach each one as storage
  • Name the folders that matter as places
  • Copy and move between drives, streamed rather than buffered

Giving a contributor one folder

• Situation: someone needs to upload to a single client folder, and nothing else.
• How it can help:
  • Grant one subfolder through a profile root
  • Set a maximum file size and permitted extensions
  • Assign the profile to that Joomla user, with no shared credential

Read-only review

• Situation: someone needs to look through files without being able to change them.
• How it can help:
  • Grant only download, search, info and preview, with write switched off on each root
  • See the worked examples

File access for logged-in site users

• Situation: users should reach their files from the public site, not the Joomla admin.
• How it can help:
  • Publish the app through a Joomla menu item
  • Apply the same profile checks and protection rules as the admin
  • Keep storage, places, profiles and settings admin-only

Knowing who changed what

• Situation: several people work on the same files and you need a record.
• How it can help:
  • Review every change made through Next File Manager in the activity log
  • See the user, action, place and path for each entry

Protecting critical files

• Situation: you want people working on the site without risking Joomla's core files.
• How it can help:
  • Rely on default protected paths for Joomla's entry points and core trees
  • Lock specific paths that matter to your own site
  • Keep secret files such as configuration.php and .env unreadable below Super User