Naming rules that enforce themselves
Define a pattern from tokens such as date, client, project and version. Every upload is checked against it, and files that break the pattern are corrected, flagged or held, as you choose.
No. 01 of 06 · Naming and organization
Every file, filed under a name that makes sense.
Name Index Drive keeps storage organized by clear names, and enforces your naming rules automatically so nobody has to police the folder tree.
01
- Naming rules that enforce themselves
- A live A–Z index
- Suggest, fix or block
- Reserved prefixes
- Duplicate detection
- Reversible rename history
“A good name is the cheapest search engine you will ever build.”
Shared drives start out tidy and decay within a season. “final_v3_REAL.pdf” appears beside “Final (copy).pdf”, dates are written four different ways, and the only person who can find anything is whoever made the mess.
Name Index Drive treats the file name as the first piece of metadata worth protecting. You write a naming pattern once, attach it to folders, and every upload is checked as it arrives. The result is a drive where the name tells you what a file is before you open it, and where an alphabetical index is always one click away.
What is inside
The features.
A live A–Z index
Each folder gets an alphabetical and chronological index generated from the names themselves, so finding the March contract takes seconds instead of a scroll.
Suggest, fix or block
Set the strictness folder by folder. Relaxed folders suggest a corrected name; strict folders refuse any file that does not comply.
Reserved prefixes
Lock words like FINAL or APPROVED to the people allowed to use them, so “final” always means final.
Duplicate detection
Two files with the same name, or the same content under two names, are caught and offered for merging before clutter builds up.
Reversible rename history
Every rename is logged with who, when and what changed, and can be undone in one click.
How it runs
From first file to filed.
- 1
Write the pattern
Compose a naming rule from simple tokens and preview it against sample files.
- 2
Attach it to folders
Apply the rule to a folder tree and pick suggest, fix or block for each branch.
- 3
Upload as usual
Drag files in from your desktop or sync client. Names are checked on arrival.
- 4
Review the index
Open the A–Z index, clear the short exception list and keep the drive clean.
The fine print, plainly
Specifications
| Rule tokens | Date, client, project, document type, version, initials |
|---|---|
| Enforcement modes | Suggest, auto-correct or block per folder |
| Index refresh | Updates as files arrive, no manual rebuild |
| File types | Any file type, any size your plan allows |
| Rename history | Kept for 90 days and reversible |
| Permissions | Owner, editor and viewer roles per folder |
Reader questions
Asked often.
What happens to files that already exist?
Run a one-time review. CloudNamed lists every file that does not match your pattern and proposes a corrected name. Nothing is renamed until you approve it.
Can different folders have different rules?
Yes. Rules can be inherited down a folder tree and overridden anywhere, so finance, design and legal can each keep their own conventions.
Does renaming break shared links?
No. Links point to the file itself rather than its name, so a rename never breaks a link someone already has.
Also in this issue.
Full services index →Press Room Storage
Editorial team storage for drafts, photos and approvals.
Clip Archive
Searchable long-term archive for articles, clips and records.
Byline Shares
Credit-aware sharing with branded link pages.
Proof Copy Backup
Editions and proofs preserved as immutable copies.
Wire Transfer Files
Fast delivery of big media bundles to partners.