Shared folders for teams: how to set them up
In short
- Before creating a shared folder, write down its purpose, its audience, and who is responsible for maintaining the structure and approving access.
- A simple project structure can use numbered folders such as Start Here, Brief and Planning, Working Files, Review, Approved Deliverables, and Archive.
- Give each person only the access their task requires, and test permissions on the real location, since a folder named Internal is no access control.
- Test the setup with a small sample and representative users first, then review membership and external access regularly as roles and projects change.
Shared folders give a team a common place to store, find, and work on documents. To set them up, choose an approved workspace, create a clear folder structure, assign access, and test it before moving everyday work into it. This guide covers those decisions, plus the habits that keep team document sharing organized as people and projects change.
How do you set up shared folders for a team?
Set up shared folders by creating a team-managed location, organizing it around the work, and inviting people with appropriate permissions. Add a small set of current documents, test access with representative users, and explain where future files belong. Treat the launch as a working agreement, not just a storage task.
Before creating anything, write down three decisions:
- Purpose: Which project, department, or ongoing process will this space support?
- Audience: Who needs to contribute, review, or simply read the files?
- Responsibility: Who will maintain the structure, approve access, and handle questions?
For example, a campaign workspace might serve internal writers, a project lead, and an external designer. Plan separate areas for internal planning and material approved for the designer. Keep the initial scope narrow enough that everyone understands what belongs there.
Choose a workspace that fits your existing workflow
Start by evaluating your organization's approved team collaboration tools. Before introducing another service, ask your administrator whether the current platform supports the ownership and access model you need. Make the decision around practical requirements rather than a feature list.
Use these questions to compare shared workspace solutions:
- Can the organization retain team files when an employee leaves?
- Can you control who edits, invites others, or shares externally?
- Does the workspace support your document types and review process?
- What recovery, version-history, and administrative options are available under your plan?
Ownership deserves particular attention. Google states that files in its shared drives belong to the organization rather than an individual and remain when their creator leaves. If you use Google Workspace, confirm that shared drives are available to your account before designing the setup around them. (knowledge.workspace.google.com)
Name a primary coordinator and a backup contact. Their job should include answering filing questions and arranging access reviews, not merely creating the original folder. Document who can take over if either person changes roles.
Build a folder structure people can understand
Organize around the way your team looks for work. For a project, that might mean briefs, working files, approvals, and deliverables. For an ongoing department, categories such as procedures, templates, and active initiatives may be more useful.
Dropbox's organizational guidance recommends a familiar, predictable structure with someone responsible for maintaining it. Its project example separates working files, reviews, final deliverables, and archives. Use that principle as a starting point, then adapt the labels to your team's vocabulary. (dropbox.com)
A practical project structure could look like this:
- 00 Start Here: Purpose, contacts, filing rules, and useful links.
- 01 Brief and Planning: Requirements, schedules, and project decisions.
- 02 Working Files: Drafts and material still being developed.
- 03 Review: Items awaiting feedback or approval.
- 04 Approved Deliverables: Material cleared for its intended use.
- 05 Archive: Superseded work retained under your organization's rules.
Keep the first version simple. Add a subfolder when it serves a clear distinction, not because the structure looks incomplete without it. Ask a teammate to place three example documents into the structure; use their hesitation to identify labels that need clarification.
Agree on a naming pattern such as Project_Document_Status. For meeting notes or dated reports, consider YYYY-MM-DD_Topic. Avoid putting a date into every filename when it adds no useful meaning, and define what labels such as “approved” actually mean.
Which permissions should team members have?
Give each person the access required for their task, then check what that role actually allows in your platform. Use editing access for contributors, review-oriented access where available for reviewers, and reading access for people who only need reference material. Reserve membership management for designated people rather than granting it automatically to every contributor.
Permission names are not interchangeable across products. Google shared drives distinguish roles including Manager, Content manager, Contributor, Commenter, and Viewer. Dropbox's shared-folder permissions work differently: its “Can view” permission can include downloading, sharing, and commenting, while “Can edit” includes deleting files. Review the documented capabilities before inviting people. (support.google.com)
Use this access plan as a starting point:
| Participant | Access to consider | Check before launch |
|---|---|---|
| Folder coordinator | Manage membership and structure | Who provides backup coverage? |
| Active contributor | Create and edit working material | Can this role also delete or reshare? |
| Reviewer | Comment or view, where supported | Does feedback require editing? |
| External partner | Access to selected material | Can they see anything beyond their assignment? |
Be deliberate about links. Microsoft distinguishes links for specific people from organization-wide and anyone links; anyone links can work without sign-in. For nonpublic material, choose an appropriately restricted option and verify the recipient list. (learn.microsoft.com)
Do not treat a folder name such as “Internal” as an access control. Test the permissions on that location before storing restricted material there.
Create the folders and test the real experience
With the plan agreed, move into your platform's approved team location. Interface labels vary, so use its current instructions for creating folders and managing members. Follow this sequence rather than uploading everything immediately:
- Create the main location. Give it a recognizable team or project name and record its purpose in the Start Here document.
- Add the core folders. Build the agreed structure, including any separately controlled area for external collaboration.
- Configure access. Invite the intended users or approved groups, inspect their roles, and check sharing-link settings.
- Upload a sample. Include a working document, a review item, and an approved example rather than the entire historical collection.
- Test representative roles. Ask a contributor, reviewer, and external participant, if relevant, to try their expected tasks.
- Resolve problems before launch. Check that people can find and use what they need without seeing unrelated material.
For Google shared drives, also review access after moving existing content. Google notes that moved files retain sharing permissions, but access can change when the destination's sharing settings are more restrictive. Do not assume the original audience will retain exactly the same experience. (support.google.com)
Record the test results and the person responsible for each fix. A successful test means the intended work is possible, not simply that the folder opens.
Make collaborative file sharing an everyday habit
Agree on a single working location for each active document. Ask teammates to share that location in project messages rather than routinely circulating new attachments. If a separate copy is necessary, label its purpose and explain whether changes should return to the working document.
Add brief operating rules to Start Here:
- Drafting: State where new work begins and how contributors request feedback.
- Review: Identify who gathers comments and decides when an item is ready.
- Approval: Name the person responsible for marking material as approved.
- Completion: Explain who archives finished work and which retention rules to follow.
Walk through one realistic task during onboarding: find the brief, open a draft, leave feedback, and locate the approved output. Ask the teammate to repeat the process without guidance. Revise confusing instructions before expanding the rollout.
Before a large migration, sort existing material into current work, useful reference, and content needing a retention decision. Ask document owners to resolve uncertain duplicates rather than guessing which copy matters. Keep the old location's transition status clear so people know where to continue working.
Set a recurring review appropriate to the team's pace. Check membership after role changes, examine external access when projects end, and resolve unowned folders. Ask your administrator to explain recovery options before you need them.
Start small and make ownership clear
A useful shared folder setup combines a recognizable structure, deliberate permissions, and clear working rules. Start with one project, test it with the people doing the work, and adjust before copying the approach elsewhere. Keep responsibility visible: everyone should know where files belong, which version to use, and whom to contact when access or organization needs attention.
Related guides
Sources
- Set up shared drives for your organization | Drive & Docs | Google Workspace Help
- How to Improve Cross-Functional Collaboration - Dropbox
- Store & share files or folders with shared drives - Computer - Google Drive Help
- Plan sharing and collaboration options in SharePoint and OneDrive - SharePoint in Microsoft 365 | Microsoft Learn
- How file access works in shared drives - Google Workspace Learning Center