File and folder organization
Create a file structure your team can actually use.
Create folders, find files by name and organize private, selected-person and company material while keeping folder access part of every move.
Organization is also an access decision.
A useful folder structure helps colleagues find the right file without making every file public. Drive separates file organization from visibility. You can create folders and rename or move material, but the destination's access still matters. Plan a small structure around the work your team actually shares rather than importing an unexplained archive into company-wide visibility.
Give everyday files recognizable names.
Use file names that explain the document's purpose and search by name when the folder is not obvious. Rename material when the working meaning changes, without assuming the name itself certifies status. A filename such as final does not replace the team's review or establish that the client received that version.
- Folder creation, rename and name search
Check the destination before moving a file.
Folder access continues to apply to contained files. The move is not simply cosmetic: people need the relevant access through the folder hierarchy. Review the intended audience before reorganizing shared material, particularly when a private working document is being placed near company material. An administrator role does not bypass private file boundaries.
- Folder-aware access throughout the hierarchy
Separate archive maintenance from external delivery.
Moving or renaming a file does not mean a recipient should automatically receive a different deliverable. External links remain tied to the shared version. When deleting and restoring folders, review sharing separately: deleted folders revoke underlying external links, and restoration does not silently reactivate them. Check the intended handover before creating another link.
- Version-bound sharing independent of file names
A concrete workflow
Choose a structure
Start with one customer's working folder and a clear naming convention.
Add material
Upload eligible files and wait for processing before organization is complete.
Check access
Confirm who should reach the file through its destination folder.
Maintain
Review names, moves and external links when archiving the engagement.
An illustrative working example
Illustrative scenario: reorganizing client work
A team separates a client's working material from reviewed handover files. The owner creates a small folder structure, names files for their purpose and checks access before moving them. A colleague tests the name search and confirms the destination is usable. The team then reviews external links independently. This pilot establishes whether the proposed structure explains current work, not whether every historical file has been migrated.
Questions about this topic
Can I rename and move files?
Yes, subject to the relevant file and folder authority. Check the destination audience rather than treating a move as permission-neutral.
Does an association determine the folder's access?
No. Customer, contact and employee associations organize context, while file and folder sharing remain separate decisions.
Do restored folders reactivate external links?
No. Folder deletion revokes underlying external links. Restoration does not make them active again; review the intended sharing separately.
Is the folder structure a backup system?
No backup or disaster-recovery capability is claimed by this page. File organization should not replace your data retention and continuity planning.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Google Drive
Application concept: Compare a customer's Google Drive folder names with the proposed Tsumira structure before moving selected material.
Dropbox
Application concept: Identify active Dropbox working files separately from obsolete archive material before organizing the new folders.
SharePoint Online (v2)
Application concept: Review SharePoint library ownership and intended audiences before designing equivalent Tsumira folder responsibilities.