Folders and collections

Browsing folders uses files.read; creating and organizing them requires folders.manage. Moving existing files also needs files.update. Publishing or revoking a folder link requires folders.share. These grants come from your roles, not from membership in the folder.

Folders give a project or collection its own place while All files keeps your entire library available. Each file belongs to one folder or is unfiled. Tags work across folders when a file belongs to several topics.

Folder and file organization changes can leave names and IDs in the instance audit log, visible to people with audit.read even when the folder is not shared.

Everyone initially includes folder permissions; an administrator can restrict them through roles. Creating a folder does not change file links, storage paths, visibility, or passwords.

Browse a project's direct files while keeping subfolders and sharing controls close by.

Browse a project's direct files while keeping subfolders and sharing controls close by.

Create and browse folders

1. Open Files and choose New folder.
2. Give it a name and save.
3. Open the folder to see its direct files and subfolders.
4. Choose New folder inside it to create a subfolder, or Upload here to add files.

Folder names can be up to 80 characters. Use a plain-text name without / or \; . and .. are reserved. Names must be distinct within the same parent. The same name can be useful in separate projects.

All files includes files from every folder. Unfiled includes files that do not belong to a folder. Opening a specific folder shows its direct files; open a subfolder to see the files inside that subfolder.

Search, tag filters, sorting, dates, and image browsing stay within the folder you are viewing. Its direct files use the same continuous scrolling and date rail as All files; the rail covers only the matching files in that folder. Resetting those filters keeps the folder selected.

Move files

For one file, open its menu and choose Move to folder. For several files, choose Select, select individual files or Select visible files, and choose Move. Pick a destination and confirm.

A selection can include up to 100 files and stays selected as you scroll. Select visible files adds only loaded files currently on screen, not every file in the folder. Changing the folder or filters clears the selection; finish the move first.

Choose Unfiled to remove files from their current folder. Moving a file preserves its share link, tags, password, visibility, and expiration.

Select visible files, scroll to add others, then choose Move to pick a destination for the selection.

Select visible files, scroll to add others, then choose Move to pick a destination for the selection.

Moving changes collection membership

When a folder has a share link, moving a public file into it adds that file to the collection. Moving it out removes it from the collection. Its separate file link continues to follow its own access settings.

Upload into the right place

• Upload here opens the upload page with the current folder selected.
• Save to on the upload page lets you choose a folder when you have folders.
• Dropping files onto the library uploads them into the folder currently open.
• Dropping files elsewhere in the dashboard leaves them unfiled.

The destination is chosen for the upload; it is not saved inside an upload profile. If a folder is removed while an upload is running, finalization can fail instead of quietly putting the file somewhere else. Choose a valid destination and retry.

Archive extraction creates a new wrapper folder inside the chosen destination and preserves the archive's subfolders. It requires files.read, files.upload, and folders.manage. With Private (no profile), extracted files stay private even in a shared destination. Explicitly selecting an upload profile can instead publish them with that profile’s visibility and expiration; check the summary before confirming. Choosing Unfiled in that flow creates a top-level wrapper rather than leaving the extracted files unfiled.

Share a folder

Folders start private. To publish a collection:

1. Open the folder menu and choose Share.
2. Choose Create share link.
3. Copy the generated URL and send it to your recipients.
4. Review the page in a signed-out browser window to check what visitors see.

The shared page uses a link under /s/folders/…. It lists up to 48 files per page and follows changes to the collection: newly added public files appear, and files moved out or made private disappear.

The public collection excludes private files and hides the filename and preview of locked files.

The public collection excludes private files and hides the filename and preview of locked files.

Item in your folder	What a visitor sees
Direct public file without a password	A file tile and access to its viewer.
Direct public file with a password	A locked tile without a filename or preview; opening it asks for the file password.
Private file	Nothing; it is excluded from the listing.
Subfolder and its files	Nothing; sharing does not recursively publish subfolders.
Tags and account details	Not listed.

There is no separate folder password. Protect individual public files with their own passwords, or keep them private. A shared folder is a collection for viewing, not a collaborative upload or editing space.

The protected-file route reached through a folder also checks that the share is still enabled and that the file is still a public member of that folder. Moving the file out or disabling the share stops access through that folder route.

Recipients opening a public archive can browse and download its entries after any file-password check. This does not publish archive members as separate folder items or add them to the recipient's account. The canonical public file URL remains independent of the folder entrypoint: disabling this share or moving the archive does not revoke an already-known public file URL. Change the archive's own visibility, password, or existence to change access through that URL.

Disable a folder link

Choose Share → Disable link. This stops new requests to that folder share. If you enable sharing again, Flare generates a new link; distribute the new URL to recipients.

Disabling the collection does not revoke the individual public file links that people may already have copied. To stop access to a file itself, change it to private or delete it.

Rename or remove a folder

Use the folder menu to rename a folder. Renaming does not rename its files or alter their URLs.

Removing a folder keeps its contents:

• Its files and subfolders move up one level.
• Removing a top-level folder leaves its direct files unfiled and promotes its subfolders to the top level.
• Its folder share link stops working.
• If a promoted subfolder would conflict with a sibling name, rename the conflicting folder first.

Check a shared parent before removing a folder

If the parent folder is shared, public files promoted into it become part of that parent's public collection. Review their visibility before removing the child folder.

Example: hand off a project

Create a Client handoff folder. Put approved public deliverables directly inside it, put work-in-progress into a private subfolder, and keep sensitive files private. Create a share link for Client handoff. Your recipient sees the direct public deliverables, while the subfolder and private files stay out of the listing.

Use tags such as Approved or Needs revision for your own workflow. Those labels stay private even when the file appears in the collection.

Watch real browser recordings of organizing and sharing folders to see this workflow in motion.