How to Build a File Management System for Your Clients and Team

A client emails on Friday afternoon: “Can you resend the signed scope? And which version of the site drawings is the latest?” Someone on your team digs through their inbox, finds two attachments with the same name, and sends the wrong one.

Earlier this year we launched our Agency OS for professional services teams that run client work through projects and tasks. Lots of teams adopted it and made it their own. But one piece of feedback kept coming back: the work still revolves around files, and people wanted a proper place for them at the project level, and sometimes at the task level.

We could always support files in Noloco, but it never felt like the file browsers people already know, like Google Drive, Dropbox, or Finder on their laptop. With Canvas, that has changed. In this guide I’ll show you how I built a file browser inside each project in a few minutes, shared safely with both our team and our clients.

Ready? Let’s get started!

Why do client files end up scattered across email, drives, and chat?

Because files arrive from everywhere. A client sends a contract by email, a site engineer drops photos in a chat thread, and someone saves the final report to a shared drive folder that only half the team knows about. Nobody planned it that way. It happens one attachment at a time.

The cost is real time. In Ricoh Europe’s research of 6,000 office workers across six European countries, 32% said they spend time searching for files across multiple systems or shared drives (Ricoh Europe via IT Brief, 2026). Atlassian’s survey of 12,000 knowledge workers found that teams lose 25% of their time just searching for answers (Atlassian State of Teams, 2025).

For a firm working with clients, there’s a second cost: the file lives in one place and the project lives in another. Your team can see the project status in one tool, but has to open a separate drive to find the drawings it refers to. Your client can’t see either, so they email you instead.

What should a file management system for clients and your team include?

Before you build anything, write down what “good” looks like for your firm. For most teams I speak to, it comes down to six things:

• Files live inside the project. Open the project, click Files, and everything for that job is there.
• Folders, including folders inside folders. For example “Drawings”, then “Revision B” inside it.
• Drag and drop. If it’s harder than dropping a file into Dropbox, people will go back to email.
• Preview without downloading. Click a PDF or image and see it straight away.
• Who uploaded it, and when. So “which version is the latest?” has a clear answer.
• The right people see the right files. Your team sees every project they work on. Each client sees only their own projects. You can read more about this in our guide to client portal permissions.

Here’s how the usual ways of sharing client files stack up against that list.

What you need	Email attachments	Shared drive folders (Google Drive, Dropbox)	Files browser in Noloco
Files sit inside the project	❌ No: files sit in individual inboxes	⚠️ Partial: a folder can be named after the project, but it lives outside the tool where you manage the work	✅ Yes: every file is linked to the project record it was uploaded to
Folders inside folders	❌ No	✅ Yes	✅ Yes: each folder can have a parent folder
Drag and drop uploads	⚠️ Into an email, not into a shared place	✅ Yes	✅ Yes: into a folder or the main area
Preview without downloading	⚠️ Depends on the email app	✅ Yes	✅ Yes
Who uploaded it, and when	⚠️ Only by searching old emails	✅ Yes, in file details and activity	✅ Yes: Uploaded by and Uploaded at on every file
Each client sees only their own files	⚠️ Only if every email goes to the right person	⚠️ Only if every folder is shared correctly, one by one	✅ Yes: set once by role with permissions
Team and clients use the same place	❌ No	⚠️ Yes, but separate from tasks, approvals, and project updates	✅ Yes: files sit next to the rest of the client portal

Shared drives are good at storing files. Where they struggle is everything around the file: which project it belongs to, which client should see it, and keeping those sharing settings right as people join and leave projects.

How do you set up the data behind a file managemnt system?

Noloco already supports file upload fields on any record. For a real file browser, though, a file needs to be its own record, so it can have a name, an owner, a date, and a place in a folder. So the setup is your existing Projects table plus two new tables:

• Project files: one record per file, linked to a project and, optionally, a folder.
• Folders: one record per folder, linked to a project. A folder can have a parent folder, which is how you get folders inside folders.

These are the fields Nola created for me:

Table	Field	What it stores
Project files	Title	The file name people see in the browser
Project files	File	The uploaded file itself
Project files	Project	The project the file was uploaded to, filled in automatically
Project files	Folder	The folder it sits in, or empty if it’s in the main area
Project files	Uploaded by	The person who uploaded it, filled in automatically
Project files	Uploaded at	The date and time it was uploaded
Project files	Client	The client, looked up through the project, so permissions can use it
Folders	Name	The folder name, for example “Drawings”
Folders	Project	The project the folder belongs to
Folders	Created by	The person who created the folder
Folders	Parent folder	The folder it sits inside, or empty if it’s a top-level folder

The Client field is worth calling out. I didn’t ask for it, but Nola added it as a lookup through the project, so every file knows which client it belongs to. That one field is what makes client permissions simple later.

How do you build the file management system with Nola and Canvas?

The whole build is two pastes and one answer. Here’s how I did it.

1. Write a short prompt

Open Nola in your app and say what you want in one or two sentences. Mine was close to this: I want to add file management to projects, nested folders and files with a file-brwoser tab on the Project record. I’ve attached a full spec covering the data model and the Canvas component. Please follow it closely and ask me if anything’s unclear.

2. Paste a spec with the data and what you want it to look like

The spec covers two things: the data model and how the file browser should look and behave. Here’s an example structure you can copy and adapt:

- Data model. Keep the existing Projects table. Add a Project files table with: Title, File, Project (link), Folder (link, optional), Uploaded by (set automatically), Uploaded at (set automatically). Add a Folders table with: Name, Project (link), Created by, Parent folder (link to Folders, optional).

- File browser (Canvas component). Show it in a new Files tab on the project record. It should look like a normal file browser, with folders and files. Users can create folders and drag files into a folder or into the main area. Every upload is linked to the project being viewed and to the person who uploaded it. Clicking a file shows a preview, a download button, who uploaded it, and when.

You don’t need to know how to code to write this. If you can describe how your team files things today, you can write the spec.

3. Answer Nola’s questions

Nola makes a plan, creates the tables and fields, and builds the Canvas component. If something in the brief is unclear, it asks. In my case it asked one question I hadn’t covered: who should be able to see and use the new Files tab? More on that in the next section.

4. Try it on a real project

A few minutes later, each project had a Files tab that looks and feels like the rest of the app. To test it, I created a folder called “Signed contracts”, dragged a file into it, and dropped another file into the main area. Clicking a file showed a preview, a download option, and who uploaded it and when.

Learn how to build a file management system with Noloco in minutes, including folders, file uploads, and permissions for your team and clients. Hit play 👀

Play video: How to Build a File Management System for your Clients and Team

Close video

Who should see which files: your team, your clients, or both?

This is the question Nola asked me, and it’s the one most worth thinking about before you build. Nola suggested internal team only as the safe default. I chose team and clients, because we want clients to be able to view, download, and upload files on their own projects.

What impressed me most was what Nola did next without being asked. It looked at the rest of the app, saw that we already had a client role, a user role, and a manager role, and set up permissions on both new tables for each of them. Every file and folder came with the right access from the start, so a client logging in only sees files from their own projects.

Two practical tips from setting this up:

• Start with the simplest rule that’s true. “Clients see everything on their own projects” is easy to explain to clients and to your team.
• Add team-only files later if you need them. A single yes/no field on the file, like “Team only”, is enough to hide internal notes or draft versions from clients. You can ask Nola to add it when the need comes up.

If clients will log in to more than just files, our guide to client portals covers what else they usually need to see.

What does this look like in a real firm?

Take a 40-person engineering consultancy running site surveys for property developers. Each survey is a project with tasks for the site visit, the drawings, and the final report.

• The client uploads the site plans and access instructions into a “Client documents” folder before the visit.
• The field engineer uploads site photos from the visit into “Site photos”.
• The design team adds drawings into “Drawings”, with one folder per revision.
• The project manager uploads the final report, and the client downloads it from the same Files tab.

Nobody emails attachments, and nobody asks which version is the latest, because every file shows who uploaded it and when. An accounting firm could use the same setup for year-end: a folder per tax year, the client uploads bank statements and receipts, and the team uploads the finished accounts for sign-off.

If your team still runs client work across email, drives, and spreadsheets, our guide on how to run client delivery shows how files fit alongside tasks, approvals, and updates.

When should you keep using Google Drive or Dropbox instead?

Not every file needs to live in a project. If a file is only used inside your team, isn’t tied to one client project, and nobody needs to know who uploaded it, a shared drive is fine. Company policies, templates, and brand guidelines are good examples. Our guide to document management software for small businesses covers that internal side.

A project file browser makes sense when the file belongs to a specific client job, when clients need to upload or download it, and when you need a record of who added what. That covers most of the files professional services and field teams handle every week.

If your projects already live in Airtable, you don’t have to move them to get started. You can keep Airtable as your data and build on top of it with Noloco, adding client logins and permissions that Airtable alone makes hard. Our guide to building an Airtable client portal securely walks through it.

Final thoughts

Files are where most client work actually happens: contracts, drawings, reports, photos, and statements. If those files live in inboxes and loose shared folders, your team spends its time finding them instead of using them.

A file browser inside each project fixes the basics. Files sit next to the work they belong to, clients can upload and download without emailing you, and everyone can see who added what and when. With Canvas, you describe it once and Nola builds it inside your own app, with your roles and permissions already in place.

Want a Files tab on your own projects, shared safely with your clients? Get started now!