All guides
Admin

Files

Screen guide

Before you start

Use an administrator account with permission to manage this feature. The feature also needs to be enabled for this installation and plan.

Open this feature
  1. Open /admin/files on your site.

Steps

Use Save changes

  1. Open /admin/files on your application domain, using the administrator account for this task.
  2. Find the form containing Stogare server, Allowed File Types, File Upload by URL. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Save changes. Check the current record, recipients, amount or destination before confirming when those values apply.
  4. If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.
FieldWhat to enter or choose
Stogare serverEnter the stogare server for this task, using the help or example shown by the form.
Allowed File TypesEnter the allowed file types for this task, using the help or example shown by the form.
File Upload by URLChoose Enable, Disable.
RegionEnter the region for this task, using the help or example shown by the form.
Access KeyEnter the access key for this task, using the help or example shown by the form.
Secret Access KeyEnter the value privately from your account or the service configuration. Do not use sample credentials from a guide.
Bucket NameEnter the bucket name for this task, using the help or example shown by the form.
RegionEnter the region for this task, using the help or example shown by the form.
Access KeyEnter the access key for this task, using the help or example shown by the form.
Secret Access KeyEnter the value privately from your account or the service configuration. Do not use sample credentials from a guide.
Bucket NameEnter the bucket name for this task, using the help or example shown by the form.
EndpointEnter the endpoint for this task, using the help or example shown by the form.
Public URLEnter the complete address required by this field. For a callback or webhook, copy the URL shown by the running application instead of guessing its path.
StatusChoose Enable, Disable.
API KeyEnter the api key for this task, using the help or example shown by the form.
StatusChoose Enable, Disable.
Access KeyEnter the access key for this task, using the help or example shown by the form.
Secret keyEnter the value privately from your account or the service configuration. Do not use sample credentials from a guide.
StatusChoose Enable, Disable.
API KeyEnter the api key for this task, using the help or example shown by the form.
StatusChoose Enable, Disable.
API KeyEnter the api key for this task, using the help or example shown by the form.
StatusChoose Enable, Disable.
API KeyEnter the api key for this task, using the help or example shown by the form.
Client IDEnter the client id for this task, using the help or example shown by the form.
Client SecretEnter the value privately from your account or the service configuration. Do not use sample credentials from a guide.
StatusChoose Enable, Disable.
API KeyEnter the api key for this task, using the help or example shown by the form.
StatusChoose Enable, Disable.
API KeyEnter the api key for this task, using the help or example shown by the form.

Use Save changes

  1. Open /admin/files on your application domain, using the administrator account for this task.
  2. Find the form containing Parent folder, Root Folder. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Save changes. Check the current record, recipients, amount or destination before confirming when those values apply.
  4. If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.
FieldWhat to enter or choose
Parent folderEnter the parent folder for this task, using the help or example shown by the form.
Root FolderEnable or select this option only when you want the behavior named by the field.

Use Upload

  1. Open /admin/files on your application domain, using the administrator account for this task.
  2. Find the form containing File URL. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Upload. Check the current record, recipients, amount or destination before confirming when those values apply.
  4. If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.
FieldWhat to enter or choose
File URLEnter the complete address required by this field. For a callback or webhook, copy the URL shown by the running application instead of guessing its path.

Fields and choices

Field descriptions appear beside each task above so that separate forms are not mixed together.

Check the result

  1. Stay in the same account/workspace and reopen the intended record or result screen.
  2. For saved settings, compare the displayed values with the choices you made. For filters and previews, check the current result scope.
  3. For queued or external work, inspect its status/history and provider result where applicable. A successful save does not by itself prove message delivery, publication, payment completion or provider approval.

Common problems

ProblemWhat to check
The screen or action is missingCheck the correct administrator account, role, enabled app and plan. A hidden action is not fixed by typing an internal endpoint.
A field is rejectedRead its validation message, choose from the offered options and check the relevant format or limit. Do not substitute a database ID for a displayed choice.
A list is emptyCheck the selected workspace, search text, date range and status filters. Clear one filter at a time before concluding that records are missing.
A request is still pendingCheck its status/history before repeating it. For messages, publishing, imports and payments, a submitted request can finish later or fail separately.

Technical reference

Role-scoped source references

Pinned commit: 275481cdd3c8519a24c5ecf5cac3e11ceb1708d8

Source-only route information
MethodSource-default route
RESOURCE/admin/files
POST/admin/files/popup_files
POST/admin/files/list
POST/admin/files/mini_list
POST/admin/files/popup_list
POST/admin/files/upload_files
POST/admin/files/upload_from_url
POST/admin/files/save_file
POST/admin/files/save_files
POST/admin/files/save_file_from_cloud
POST/admin/files/destroy
POST/admin/files/update_folder
POST/admin/files/save_folder
POST/admin/files/popup_search_media
GET/admin/settings/files
Unmapped fields — not user instructions

These fields belong to this role’s source handler, but their screen labels were not confirmed.

Source keyHandler
filemodules/AppFiles/app/Http/Controllers/AppFilesController.php
file_urlmodules/AppFiles/app/Http/Controllers/AppFilesController.php
filesmodules/AppFiles/app/Http/Controllers/AppFilesController.php
files.*modules/AppFiles/app/Http/Controllers/AppFilesController.php
folder_idmodules/AppFiles/app/Http/Controllers/AppFilesController.php
filesmodules/AppFiles/app/Http/Controllers/AppFilesController.php
namemodules/AppFiles/app/Http/Controllers/AppFilesController.php