Video chapters
- 0:00 Welcome
- 0:08 Overview: one library, public and private, reuse
- 0:41 Part 1 · Organise and upload — Folders and location: explained
- 0:58 A folder for your media
- 1:26 Uploading, with access: explained
- 1:45 Upload from device and web, views and search
- 2:34 Part 2 · Work with files — Selection and renaming: explained
- 2:52 Rename, thumbnails and delete
- 3:26 Part 3 · Who can open a file — Who can open a file: explained
- 3:45 Lock and globe on the card
- 4:01 Part 4 · Reuse in a product — One file, many places: explained
- 4:15 A library photo in a product and the shop
- 5:03 Wrap-up
Earlier tutorials and recordings (3)
These recordings may show an earlier interface or an older cut. Follow the current written instructions below.
Written guide
Overview
Appmint File Manager is the shared library behind images, documents and other uploads. We will organize a small collection, choose whether its files are public, and reuse an image inside content. The important result is not simply an uploaded file: it is the right file, in the right folder, with access that matches its purpose.
The illustration explains the relationship; it is not an app screenshot. A file can be stored once and referenced from several places. Renaming or deleting that file may break those references. Private means access is restricted; an authorized session or a signed link can still retrieve it.
1. Create a folder and understand the current location
Why this matters
The folder tree and breadcrumb identify where the next upload goes. A folder is organization within the file library; it does not create a new website or a separate business.
Follow these steps
- Open DAM in Studio Manager's left menu, then Document. This opens the window titled File Manager; its main heading is Files. It is the same library used by media pickers in other editors.
- Select the intended parent folder in the left tree. The breadcrumb above the file cards and the path below them identify the destination.
- In the toolbar, hover the plus icon to confirm Add folder or file, then click it. Leave What to add as Folder.
- Enter
course-media-20261004as Name for this controlled example. Use your own meaningful folder name; the app normalizes it as you type.
- Select Add once. Wait for the folder to appear in the tree.
- Click its name in the tree. Wait until the breadcrumb includes
course-media-20261004before choosing Upload. The folder request is asynchronous: immediately clicking Upload can show the old breadcrumb while the request is still loading.
Why this matters: A selected folder checkbox is a selection; an opened folder and its breadcrumb determine the upload destination. Read the path rather than relying on the last place you clicked.
Check the result:
The new folder appears after Refresh, and opening it changes the displayed location.
2. Upload with a deliberate privacy setting
Why this matters
Public files can support images on a public website. Private documents need authorized retrieval; making a file private is not the same operation as hiding a content page. The upload switch starts public in this implementation.
Follow these steps
- Hover the upload-arrow toolbar icon to confirm Upload, then click it.
- Keep Upload from File selected. Check Private before selecting your file. The accompanying sentence changes from Files will be publicly accessible to Files will be private. The checkbox is labelled Private even when it is unchecked; read its checked state and explanatory sentence together.
- Select Select files, choose a harmless text file or image from your computer, and wait for the file card. The local rehearsal used a short course text file and the Appmint logo, both uploaded privately.
- Close the upload panel by clicking Upload again. Select Refresh and verify the same names, sizes and folder path remain.
Observed result: The real local library retained course-file-20261004.txt (89bytes) and appmint-logo-black.png (20kB) inside the course folder after refresh. A private badge confirms the displayed access setting; it does not alone prove anonymous access is denied.
Alternative — URL import: Select Upload from URL only when you have the direct file URL, not a webpage that happens to display an image. Set Private deliberately before starting. This alternative still requires its own import/result check; it was not executed in the local file-upload rehearsal.
Check the result:
A stored image is visible in the selected folder. The URL-import example has its own stored result, rather than just an untested external link.
3. Browse, select and reuse the stored image
Why this matters
Grid view makes visual selection easier; List view is useful when similar images have different names. The File Manager can be opened as a picker by another editor, and the selection must be returned to that editor.
Follow these steps
In a saved Content Studio document, select the page and choose Visual → Insert → Image / gallery → Choose from File Manager. Open the course folder, check the image card, and confirm the selection count is 1. Click Use selected files (the checkmark) at the top of File Manager to return it to the editor. The adjacent Clear selection X clears a mistaken selection; Delete is a separate operation.
The image inserts immediately. Save the document with Save Draft. Open the document’s site Preview, then Start on its cover. Verify the selected image loads with the page text.
Actual outcome: The existing private PNG loaded in the editor and site reader on 4 October 2026. Its inserted source was a signed URL; do not mistake this current success for proof that an expiring URL is suitable for permanent public content. Reader preview bypasses page gates and records no learner activity. Grid/List switching and search remain separate pending checks.
Check the result:
The consuming editor contains the selected image. Merely checking an item in the library is not presented as a saved content change.
4. Download, check access and generate thumbnails
Why this matters
File operations apply to the selected files. A visually selected folder or a previous selection can otherwise make a batch operation surprising.
Follow these steps
Select only the intended image. Choose Download and open the downloaded result. Choose Check Privacy to inspect the access indicators. For a disposable file, use Make Private, refresh, then check access again; use Make Public only for content intended to be public. Select a suitable image and choose Create Thumbnail, then refresh and inspect the resulting library state.
Check the result:
The downloaded file opens. Privacy is checked after refresh, and thumbnail creation is not declared successful until its result is visible.
5. Create an empty file and remove a disposable upload
Why this matters
Add folder or file can create an empty file; it does not turn File Manager into a document editor. Deletion can break existing content that still points to the file.
Follow these steps
Choose Add folder or file, set the type to file and enter rehearsal.txt. Submit and inspect its name including the extension. Select only that disposable file, choose Delete, read the confirmation and confirm. Refresh. Keep the image used by the content page. Use Show new files when checking newly uploaded items, then return to the normal folder view.
Check the result:
The disposable entry disappears after refresh while the referenced image remains available.
6. Inspect, rename and copy a file link
Why this matters
The file card has its own actions as well as the top toolbar. Use View to inspect a file and its editable filename to rename it. A copied link is not necessarily a permanent public URL: the current card copies its signed URL.
Follow these steps
Move the pointer over a file card to reveal its bottom actions, then select View. Those buttons are hidden until hover in the current grid layout. Inspect an image, play a video or audio file with its controls, and inspect a text/code file. The Preview dialog opens over the library. Select Close preview, or press Escape, before selecting another file. Text is read-only in this preview; edit the original file and upload a revised copy when you need different content.
Observed checks: The text preview displayed the uploaded content, and the image loaded successfully. Close and Escape both dismissed the preview. Tab remained inside the dialog. Hovering the text card and selecting Download produced the same filename and exact 89-byte contents as the original upload. These are actual local server results, not mocked file responses.
Use the editable filename on a disposable upload. Enter a descriptive lowercase name with hyphens and retain the file extension. Commit the edit, wait for File moved successfully, then Refresh. Select only the renamed file. Choose Copy Link, paste it into a temporary address field and test it. For private material, test access in an appropriate authorized session rather than publishing that copied link. Finally revisit any content that referenced the old path: renaming is a move and the inspected handler does not update downstream references for you.
Check the result: The renamed file is present after refresh and usable at its new location. The original path and existing embedded content are checked explicitly.
Gotcha: Main-toolbar Clone/Edit/Preview are commented out, but that does not mean per-card View and inline rename are unavailable. Copy Link uses file.signedUrl; its lifetime must be verified before using it as a durable published asset. The current card’s rename builds the destination from the original folder and new basename, so rehearse root-folder and nested-folder renaming separately. Unsupported preview types show an instruction to close the preview and use Download. A failed text read shows an error rather than an editable or empty-looking document.
Source references: file-manager/views/card-view.tsx, file-manager/fm-view-content.tsx.
Troubleshooting, recovery and alternatives
If the operation fails, keep the error text and inspect the saved state before retrying. A confirmation message is not enough: reopen the item or reader/output destination. Do not repeat a create action while the original request is pending. Use the smallest disposable example to distinguish a missing permission, unavailable backend or incomplete implementation from a content mistake. Keep explanations of prerequisites separate from the continuous task demonstration.
Next steps
You now have the module’s main path and the checks that tell you whether the result is ready to use. Keep the editable source, verify the output where your audience will see it, and return to the relevant chapter when you need an alternative.
Limitations and checks
Live checks on 4 October 2026 covered folder creation/opening, private text and image uploads, persistence after Refresh, text/image previews, Close/Escape/focus containment and a byte-identical text download. A non-opening View action was repaired locally during this walkthrough. This is a bounded verified path, not a claim that every chapter has passed.
Still required before full-course sign-off: URL import; public/private access transitions including independent anonymous retrieval; list/search; empty-file creation and deletion; thumbnail generation; rename and copied-link lifetime; audio/video previews. Consuming-editor image selection, save and actual site preview now passed. Empty-file creation currently uploads text/plain and defaults public. Clone, Edit and Preview toolbar buttons are commented out; the working View action belongs to each hovered file card.
BusinessMade Files — supporting guide
BusinessMade entry: Content → Files (/content/files).
BusinessMade opens its inline Files page. It does not require opening Studio Manager or spawning the floating picker. Use a product image or another supported editor to prove reuse; keep employee documents private.
Scope: This BusinessMade route uses the shared component whose complete procedures follow. Use the BusinessMade menu and organization throughout. Shared references are implementation evidence, not instructions to switch products. These written steps have not been replayed as a new BusinessMade live walkthrough.
Reader update: Current mounted source and retained application images inspected 5 October 2026. No new BusinessMade save or external outcome is claimed.
Prepare one reusable business asset
Use a non-sensitive image and a disposable product or content record to check reuse. Open Content → Files in BusinessMade. The current page embeds File Manager inline; you do not need Studio Manager or a second floating window. Read the folder breadcrumb before upload so the saved file is easy to find again.
The retained capture below shows the earlier floating wrapper, which has been replaced in this route. Its upload controls illustrate Public, Select files and Upload from URL, not the current page layout. The pictured Public switch is unchecked; read the actual current switch before selecting any file instead of assuming its default matches a screenshot.
Personally inspected retained application view; current action/result captures remain pending.
Overview
BusinessMade Files is the shared library behind images, documents and other uploads. We will organize a small collection, choose whether its files are public, and reuse an image inside content. The important result is not simply an uploaded file: it is the right file, in the right folder, with access that matches its purpose.
1. Create a folder and understand the current location
Context
The folder tree and breadcrumb identify where the next upload goes. A folder is organization within the file library; it does not create a new website or a separate business.
Follow the steps
Open Content → Files. Select the destination in the folder tree and read the breadcrumb. Choose Add folder or file. Choose the folder type, enter course-media, and submit the dialog. Open the new folder before uploading. Names are normalized as you type, so inspect the final value rather than assuming punctuation is preserved.
Check the result:
The new folder appears after Refresh, and opening it changes the displayed location.
2. Upload with a deliberate privacy setting
Context
Public files can support images on a public website. Private documents need authorized retrieval; making a file private is not the same operation as hiding a content page. The upload switch starts public in this implementation.
Follow the steps
Choose Upload. Before selecting a file, inspect Public or Private and change it to the intended state. Upload a non-sensitive image for the public example. Wait for the row or thumbnail to appear. Use Upload from URL for a second file only when you have its direct accessible URL; switch back using Upload from File. Choose Refresh to confirm the result remains listed.
Check the result:
A stored image is visible in the selected folder. The URL-import example has its own stored result, rather than just an untested external link.
3. Browse, select and reuse the stored image
Context
Grid view makes visual selection easier; List view is useful when similar images have different names. The File Manager can be opened as a picker by another editor, and the selection must be returned to that editor.
Follow the steps
Switch Grid view and List view. Select an image and inspect the selection count; clear accidental selections with the selection clear control. In Storefront → Products, open the controlled product, expand Media and choose Choose from File Manager. Select this image and confirm with the picker's checkmark control. Return to the product editor and inspect the added thumbnail. Use Set as default image when this should be the main image, then Save Changes. Reopen the product and verify its gallery and default image.
Check the result:
The product editor contains the selected image. Merely checking an item in the library is not presented as a saved content change.
4. Download, check access and generate thumbnails
Context
File operations apply to the selected files. A visually selected folder or a previous selection can otherwise make a batch operation surprising.
Follow the steps
Select only the intended image. Choose Download and open the downloaded result. Choose Check Privacy to inspect the access indicators. For a disposable file, use Make Private, refresh, then check access again; use Make Public only for content intended to be public. Select a suitable image and choose Create Thumbnail, then refresh and inspect the resulting library state.
Check the result:
The downloaded file opens. Privacy is checked after refresh, and thumbnail creation is not declared successful until its result is visible.
5. Create an empty file and remove a disposable upload
Context
Add folder or file can create an empty file; it does not turn File Manager into a document editor. Deletion can break existing content that still points to the file.
Follow the steps
Choose Add folder or file, set the type to file and enter rehearsal.txt. Submit and inspect its name including the extension. Select only that disposable file, choose Delete, read the confirmation and confirm. Refresh. Keep the image used by the content page. Use Show new files when checking newly uploaded items, then return to the normal folder view.
Check the result:
The disposable entry disappears after refresh while the referenced image remains available.
6. Inspect, rename and copy a file link
Context
The file card has its own actions as well as the top toolbar. Use View to inspect a file and its editable filename to rename it. A copied link is not necessarily a permanent public URL: the current card copies its signed URL.
Follow the steps
Open a file card’s View action. Inspect an image, play a video or audio file with its controls, and inspect a text/code file. Close the popover before selecting another file. The text/code preview does not have a file-save operation here; do not teach it as a storage editor.
Use the editable filename on a disposable upload. Enter a descriptive lowercase name with hyphens and retain the file extension. Commit the edit, wait for File moved successfully, then Refresh. Select only the renamed file. Choose Copy Link, paste it into a temporary address field and test it. For private material, test access in an appropriate authorized session rather than publishing that copied link. Finally revisit any content that referenced the old path: renaming is a move and the inspected handler does not update downstream references for you.
Check the result: The renamed file is present after refresh and usable at its new location. The original path and existing embedded content are checked explicitly.
Gotcha: Main-toolbar Clone/Edit/Preview are commented out, but that does not mean per-card View and inline rename are unavailable. Copy Link uses file.signedUrl; its lifetime must be verified before using it as a durable published asset. The current card’s rename builds the destination from the original folder and new basename, so rehearse root-folder and nested-folder renaming separately. PDF has no dedicated branch in the inspected preview component; download it if the preview is empty.
Source references: file-manager/views/card-view.tsx, file-manager/fm-view-content.tsx.
Troubleshooting, recovery and alternatives
If the operation fails, keep the error text and inspect the saved state before retrying. A confirmation message is not enough: reopen the item or reader/output destination. Do not repeat a create action while the original request is pending. Use the smallest disposable example to distinguish a missing permission, unavailable backend or incomplete implementation from a content mistake. Keep explanations of prerequisites separate from the continuous task demonstration.
Next steps
You now have the module’s main path and the checks that tell you whether the result is ready to use. Keep the editable source, verify the output where your audience will see it, and return to the relevant chapter when you need an alternative.
Limitations and checks
Check Privacy and access changes require an anonymous and an authorized retrieval test before publication. A privacy icon alone is not proof of access enforcement. Clone, Edit and Preview are not available in this toolbar. Empty-file creation currently uploads text/plain and defaults public. URL import, thumbnail generation and downloading need live backend checks.
BusinessMade routing and outcome check
The menu and route were checked in packages/ui/src/ui/sidebars/business-made-links.ts and apps/business-made/src/shell/route-registry.ts. Open the module through the route stated at the start, perform the controlled procedure, save, reopen and inspect its actual BusinessMade consumer. Do not infer branch isolation from a header location selection when this shared screen reads organization-wide records. Record any access refusal or consumer mismatch with the exact record identity. No new provider, payment, physical-device or live-tenant action was performed for this adaptation.
Verify both the file and its consumer
After upload, refresh the folder and match the filename and privacy state. Then open the intended product’s Media picker, select that same stored image and confirm the selection. The picker returning a thumbnail is only the product’s unsaved change: save the product, reopen it and verify the gallery/default image before declaring reuse complete.
For a private document, use an authorised retrieval path and keep it separate from public product artwork. Do not fix a private-preview error by making a confidential file public. No new upload, privacy change or product mutation was performed here.