How to set up a shared drive for your team

A shared drive should be more than a dumping ground for documents. It should be the place where your team's collective knowledge lives, stays organised, and remains easy to find months after someone first uploaded a file. That is the gap most traditional shared drives fail to close. They give you folders and storage quotas, but they do not connect your team's work in any meaningful way.

Fabric approaches the problem differently. Rather than replicating the folder-and-sync model of Google Drive or Dropbox, it gives your team an infinite cloud drive that streams content on demand, requires zero local storage on anyone's machine, and layers collaboration, AI search, and a memory engine on top. Setting one up for a small team takes less than an hour, and this guide walks through each step.

Why traditional shared drives fall short for small teams

Small teams tend to outgrow traditional shared drives quickly, not because they run out of storage but because they run out of structure. Google Drive's shared drives work well enough when a team of three is passing around a handful of documents. Once the team grows to eight or ten people, each working across multiple projects, the cracks appear. Files get duplicated. Naming conventions drift. People stop trusting search and start asking each other where things are stored.

The deeper problem is that conventional drives treat files as isolated objects. A proposal document, the research that informed it, the client brief it responds to, and the internal notes discussing its direction all sit in separate folders with no relationship between them. Finding the proposal is easy. Understanding the full context around it requires opening five tabs and remembering which subfolder someone used three months ago.

Fabric's memory engine solves this by building a persistent context layer across everything your team stores. When you add a document, Fabric connects it to related content automatically. This means a new team member can find not just the proposal but the full thread of thinking behind it, without anyone having to explain the folder structure.

Step one: create your team workspace

Start by setting up a Fabric account and choosing a Teams plan, which starts at $125 per month. Once you are inside Fabric, create a shared space for your team. Think of a space as the equivalent of a shared drive, except that it comes with built-in permissions, AI capabilities, and semantic organisation from the start.

Name your space something functional. "Marketing team" or "Product development" works better than clever names that new members will not recognise. You can create multiple spaces later for different projects or departments, but begin with one shared space that covers your team's primary work.

Step two: set permissions and invite your team

Fabric's collaboration features let you set granular permissions at the space level. Each team member can be given viewer or editor access, so you control who can add and modify content versus who can only read it.

Invite your team members by email. As each person joins, they get access to the shared space through their own Fabric account. Because Fabric's cloud drive uses zero local storage, nobody needs to worry about syncing large folders or filling up their laptop's hard drive. Everything streams on demand when someone opens a file.

For teams that handle sensitive client work, consider which members need access to which areas. Fabric lets you limit team members to specific folders within a space, so a freelance designer can access creative assets without seeing financial documents. This is the kind of granular control that most shared drives either lack entirely or bury behind enterprise pricing.

Step three: organise your content

Resist the temptation to replicate your old folder structure exactly. One of the advantages of moving to Fabric is that you do not need to rely on rigid folder hierarchies, because semantic search and the memory engine let your team find content by meaning rather than by location.

That said, some structure helps. Create top-level folders for your major categories of work. If you manage multiple clients, set up a folder per client, as covered in the guide on organising files across multiple clients. Within those folders, let the content accumulate naturally. Fabric's AI will surface connections between documents regardless of where they sit in your hierarchy.

Upload your existing files from wherever they currently live. If your team already uses Google Drive, Dropbox, or another service, Fabric's connections feature can bring that content in without requiring you to manually download and re-upload everything. This is particularly useful during the transition period when some team members are still working from the old system.

Step four: enable AI features for your team

One of the most significant differences between Fabric and a conventional shared drive is that every team member gets access to an AI assistant that understands your shared content. Once your files are in a shared space, anyone on the team can ask questions about them, summarise documents, or find connections between different pieces of work.

This changes how onboarding works. Instead of a new hire spending their first week reading through old documents and guessing at context, they can ask the AI assistant to explain a project's history, summarise a client relationship, or surface the most relevant files for whatever they are working on.

Fabric also offers self-writing docs that update themselves as new content is added. For a team, this means you can create living documents, such as project status pages or knowledge bases, that stay current without anyone having to remember to update them manually. The AI draws on your team's stored content and keeps the documentation aligned with what is happening in practice.

Step five: set up external sharing and security

Not all of your shared content stays internal. Fabric's publish feature lets you share selected spaces or folders with people outside your team, such as clients, contractors, or partner organisations. Published spaces give external viewers a clean, read-only view of the content you choose to share.

For sensitive material, add password protection to specific areas. This is useful when you need to share financial projections with a board member or send a client a collection of deliverables that should not be publicly accessible.

All content in Fabric is protected with AES-256 encryption and the platform holds CASA Tier 2 certification, so your team's data meets a high bar for security without any additional configuration on your part.

Step six: integrate with your existing tools

A shared drive is only useful if it fits into the way your team already works. Fabric connects with external services so that your cloud drive does not become yet another silo. If team members are communicating in Slack, Fabric Tag lets them save and reference content from Fabric directly within Slack conversations, reducing the context-switching that slows teams down.

For teams that use tasks and reminders, Fabric can track deadlines alongside the content they relate to. A project brief, its associated tasks, and the files needed to complete those tasks all live in the same system, which is a small improvement that compounds over months of work.

Perhaps the most distinctive integration is Fabric's MCP support, which lets AI agents like ChatGPT and Claude access your Fabric workspace directly. This means you can query your team's shared knowledge from within the AI tools you already use, rather than switching to Fabric every time you need to look something up. Agent access is scoped and time-limited, so you control precisely what external tools can see and for how long.

Making the transition from Google Drive or Dropbox

Moving a team from one system to another is never instant, and pretending otherwise leads to frustration. The most practical approach is to run both systems in parallel for a few weeks. Use Fabric's connections feature to mirror your existing Google Drive or Dropbox content, and encourage the team to start new work in Fabric while keeping old projects accessible in their original location.

Set a date, perhaps a month out, after which all new files go into Fabric exclusively. By that point, most team members will have adjusted their habits, and you can archive the old shared drive rather than maintaining two systems indefinitely.

The key selling point for your team is likely the AI layer. Once people experience being able to search for a document by describing what it contains rather than remembering its filename, the switch tends to feel less like a disruption and more like an upgrade.

Frequently asked questions

How much storage does each team member get?

Fabric's cloud drive offers infinite storage with zero local footprint. Files stream on demand rather than syncing to each person's device, so there is no per-user storage cap to worry about. This is a meaningful difference from Google Drive's 15 GB free tier or even its business plans, which allocate storage per seat.

Can I control who sees what within a shared space?

Yes. Fabric supports granular permissions at the folder and file level. You can give team members viewer or editor access, and you can restrict certain members to specific folders. This is covered in detail in the guide on limiting team members to specific client folders.

How does Fabric's search differ from Google Drive's?

Fabric uses semantic search, which means it finds content based on meaning rather than exact keyword matches. If you search for "Q3 revenue projections," Fabric will surface relevant financial documents even if they never use that exact phrase. Google Drive's search is keyword-based and relies more heavily on exact matches and file metadata.

Can external people access our shared drive?

You can publish specific spaces or folders for external access. Published content is read-only for viewers, and you can add password protection for sensitive areas. External viewers do not need a Fabric account to view published content.

What happens to our existing files in Google Drive or Dropbox?

Fabric's connections feature lets you bring in content from Google Drive, Dropbox, and other services. You do not need to abandon your existing storage immediately. Many teams run both systems during a transition period and gradually move their primary workflow to Fabric.

How does the AI assistant work with shared content?

Every team member with access to a shared space can query the AI assistant about that space's content. The assistant can summarise documents, answer questions about stored files, and find connections between different pieces of content. It respects the permissions you have set, so a team member who cannot access a folder will not get AI responses that draw on that folder's contents.

Is Fabric secure enough for sensitive business documents?

Fabric uses AES-256 encryption and holds CASA Tier 2 certification. All data is encrypted in transit and at rest. For additional control, you can password-protect specific spaces and set granular access permissions to limit who can view or edit sensitive content.

What does the Teams plan cost?

Teams plans start at $125 per month. This includes the infinite cloud drive, AI assistant access for all team members, collaboration features, and the full suite of organisational tools including the memory engine and semantic search.

Can AI agents access our shared drive?

Yes, through Fabric's MCP support. You can give AI agents like ChatGPT or Claude scoped, time-limited access to your Fabric workspace. This means your team can query shared knowledge from within the AI tools they use daily, without granting permanent or unrestricted access to your content.

How long does it take to set up a shared drive for a team of ten?

The initial setup, creating a workspace, setting permissions, and inviting members, takes under an hour. Migrating existing content depends on volume, but Fabric's connections feature handles most of the heavy lifting. Most teams are fully operational within a day, with the broader transition from an old system taking two to four weeks.

Related pages

• Your cloud

• Collaboration

• AI assistant

• Search

• Memory engine

• Self-writing docs

• Connections

• Tasks and reminders

• Publish

• Password protection

• Fabric Tag

• Private and secure

• MCP

• How to organise files across multiple clients

• How to limit team members to specific client folders