You review your pending documents before Filently files them. Some of them you never want to keep, so you remove each one on its own. Only failed documents can go in one step today. Filently will let you select pending documents and remove them together, so you clear the list in one action. Filed documents stay untouched.

When you file a document, you pick its folder in the folder browser. Filently will let you search for a folder there as you type. It will show matching folders live, so you can find the right one fast. Before, you could only move down through folders one level at a time.

You forward an email and the attachment waits in Filently for your approval. Today it is only available for 28 days. If you do not get to it in time, it expires and you have to forward the email again. Filently will keep the attachment as soon as your email arrives, so it waits for you as long as you need.

File only the documents you choose. Tick single documents, or select all documents that match your current filters. Filently files each one into the folder it suggested for that document. Before, you could only file everything at once.

When Filently files a document, it already understands a fair amount about it: who it involves, where it belongs, what period it covers. Today that understanding goes into the filename and the folder — which is exactly what it was built for, and for most archives it's enough. It reaches its limit when an archive doesn't split cleanly into folders. A genealogy archive is the clearest example: one document can belong to a family line, a place and a date range at the same time, and a folder tree forces you to pick one. What you actually want to ask is "everything about this family in this location." Requested capability: Extract entities from documents during filing (people, organisations, places, dates, document type) Store them as tags on the document Let users search and filter by combining several tags Files stay where they are in Drive — tags are an additional layer, not a replacement for the folder structure

When Filently rejects a document it is left in the Inbox. When I look at my Inbox I could have 100 documents and no indication which ones were rejected. Request that rejected files go into a separate folder, this will give better management of rejected and also see how many documents in inbox are waiting for progress. I tried to this with a rule but that didn't work. Similarly it's needed that duplicates also are put in a separate folder for the same reason

When I'm looking at changelog or features and roadmap I can't find a link back to the dashboard. Request a link back to dashboard on these webpages

You set up email forwarding in Gmail. Gmail then sends a confirmation mail before it forwards anything. That mail goes to your Filently address, so you never see it, and forwarding stays inactive. Filently will show the confirmation in your email forwarding settings, so you can finish the setup in one place.

Filently gets much better at recognizing when a file is a copy of one you already have, so the same document does not end up filed twice. Duplicates wait for you instead of being filed or turned away. You decide what to keep and what to send to the trash.

Can we have some more rules in Settings that could be checked on or off, instead of having to type them in settings, for example; Import only files and not subfolder branches – yes/no Ensure all file names are unique – yes/no Restrict Levels of subfolders – 1,2,3,4… File types to ignore - .ini .lnk .tmp .sys etc Ignore filenames that contain – crdownload etc

Can you make it so the folder choices displays only root folders first and only when choosing root folder are you presented with next level of sub folders, like file explorer. Plus sorts them in order.

Choose one folder for a whole selection. Filently shows you the folders that most of your selected documents point at, so you can pick with one click. You can also browse for any other folder, or create a new one. A confirm step tells you how many documents move and which ones keep their original name. This also works for documents that are already filed and for documents that failed to process.

Currently you need to approve or reject incoming files purely on their filename. We’ll add a preview so you can check the contents of the document first.

See everything Filently does to your documents, and undo anything you didn't want. The new Activity page gives every document a complete history: When it arrived, when it was filed, and every rename or move since Whether you or auto-filing made each change A clear before and after for every change Revert puts things back. Pick any point in a document's history and Filently restores it to exactly how it looked just before, recreating any folders that were removed in the meantime. You always see a preview first, so there are no surprises. Need to fix more than one? Filter the timeline and revert in bulk. Reverting never deletes your files.

Within the filing location Filently should detect all manually added files and validates its name and location. If it looks not well named or it seems to be in the wrong location Filently will correct that.

Forwarded emails carry more than the document you want to file. Signature logos, tracking pixels and other embedded images arrive as ordinary attachments and become documents. That is enough friction to make users turn auto-processing off, which defeats the point of email forwarding. So junk attachments will be ignored completely and we give more control which file types should be processed, giving you more control and peace.

Customers receive document bundles as ZIP archives (e.g. bank exports, client deliverables) and currently have to unzip manually before Filently can process the contents. Requested capability: detect a ZIP dropped into the Filently Inbox folder, extract its contents automatically, then run the normal identify → rename → file pipeline on each extracted file. Open questions to scope: opt-in vs. always-extract, handling of the original archive after extraction (keep/delete/move), and edge cases like nested or password-protected ZIPs.

Users want to exclude specific subfolders from being processed by Filently, while still using a broader root folder. Current behavior: all subfolders inside the selected root folder are in scope. Use case: shared folders with colleagues that must remain untouched, while other folders in the same root are processed normally. Proposed solution: A dedicated exclusion list in settings where users can select folders to skip.

I want to be able to organize both my personal (My Drive) and Shared Drives at the same time within a single Filently account. Currently, I can only select one filing location, but I need to manage both simultaneously.

I want a feature that summarizes files and stores those summaries in a "Brain" memory within the folder. This way, if I ask the AI about the folder, it can answer immediately based on that "Brain" memory. I have many more ideas to share and would like a free subscription in exchange for my feedback.