Invite collaborators to a folder without a shared Drive
To invite collaborators to a folder you do not have to add them to Google Drive. Spike People invites put Can edit or Can view on one folder, by email. Clients and buyers still open the public page. The archive stays yours.
People search how to invite collaborators to a folder when the work is no longer a solo drop. An assistant is culling. A junior is packing fonts. A producer needs to see the set before the client does. The usual fix is a shared Drive. That works when the team already lives in Google. It is a costly habit when the recipient is a client who only needed a page, or a freelancer who should not see last year's jobs.
This page is the leftover job: share a folder with collaborators without handing them the archive. Spike keeps two doors. The public link is for clients and buyers. People invites are for the people who help you build the folder. How to share files with clients is the client door. This note is the studio door.
- Email invite, Can edit or Can view
- People
- Clients open the page, not Shared with me
- Link
- One unique email across your folders
- Seat
A public link is not a teammate
A spike.zip/f/… URL is a door you can password, treat, expire, or price. Guests look. They download if you allow it. They pay if you turned selling on. They do not sit in your library. That is the right tool for a couple, a brand, a buyer who found you on Instagram.
A People invite is a different object. You type an email on the share panel. You pick Can edit or Can view. They get a mail, they sign in, the folder appears under Shared with me. Nested folders inherit that invite. A closer invite on a child folder wins if you add one later. This is how you share a folder with a team that should live in the work, not only open a tab.
How a shared Drive usually works
Google Drive is excellent at collaboration when that is the job. Comments on a Doc. Versions. People who already have Google accounts. A shared tree the colourist and the producer already live in. Google Drive vs Spike does not argue that Drive is worse. It argues that a delivery should not be a room in your house.
The Drive habit for client work is: add them as a viewer, or turn on anyone with the link, and hope the folder was the right folder. Last year's jobs sit next to this week's finals. "Make a copy" on a master is a download. Permissions linger. None of that makes Drive a bad workbench. It makes it a weak client door, and a heavy way to invite one assistant onto one pack.
Where a shared Drive becomes limiting
- The assistant only needed this wedding, not the studio tree.
- The client will not sign in to Google to fetch a ZIP.
- A full-resolution still in Drive is already the delivery.
- You want a treated preview and a public page for the brand, and a signed-in editor for the cull.
- Selling should stay on the owner's till, not on a shared drive permission.
Those are five different leftovers. If the team already lives in Workspace and the file is an internal draft, stay in Drive. If the leftover job is a client page plus a small crew on that folder, invite collaborators to a folder on Spike and keep Drive as the workbench.
How to invite collaborators to a folder
The buying checklist is short because the product is short. You are not standing up a second Drive. You are putting names on a folder you already own. The clicks live in People & invites.
Open a folder you own
People lives on the share panel, under Copy link. Only the owner can invite, change a role, or remove someone. Editors and viewers see the list and can leave.
Type emails and pick a role
Can edit or Can view. You can paste several addresses at once. The invite is on that folder. Nested folders inherit it.
They accept with that inbox
The mail has Accept invitation. Invites expire after 14 days. Resend from the pending row. After they join, the folder is under Shared with me. You get a mail that they accepted.
Keep the public link for the client
Password it, treat the unpaid view, or put a price on it. That URL is still the client door. People invites are not a second public link.
What Can edit actually does
Can edit means they can upload, rename, nest folders, and organise files. Uploads they add belong to the owner. Their own storage meter does not move. That is the point: a junior can drop selects into your library without you forwarding a ZIP, and without their Free plan eating the wedding.
What Can view actually does
Can view means they open the folder in Shared with me and can download. They cannot add or rearrange files. A producer who should see the cut, not restack it, is a viewer. Viewers are signed in. They are not anonymous visitors on the public page.
Seats: one person, many folders
Free allows up to 3 collaborators. Pro allows up to 15. Business is unlimited. A seat is a unique email that is pending or active anywhere in your library. Inviting Alex to a second folder does not take a second seat. Pending invites count. Revoked or declined addresses free the seat. If you downgrade under your current headcount, existing people stay. New unique emails wait until you upgrade or remove someone.
When should you invite collaborators?
Invite collaborators to a folder when at least one of these is true. Send a public link when none of them are.
- Someone on your side must upload or tidy files in the same library.
- A producer or art director should review inside Shared with me, not only on a guest page.
- You do not want that person in the rest of your Drive.
- The client should still get a treated page they can forward inside their company.
- Selling, privacy, and delete must stay on one owner.
Replace a shared Drive link with a Spike workflow
A photographer finishes a wedding. The old sequence is: a Drive folder the assistant also has, a second link for the couple, a hope that "anyone with the link" was only on selects. The Spike sequence is one folder and two doors.
Put the job in one folder
Selects, a licence note, a size guide. This is the pack you would have shared from Drive.
Invite the assistant as Can edit
They upload from Shared with me. Bytes count on your plan. They cannot flip privacy or the price.
Treat the unpaid view for the couple
Blur or watermark stills if they should look before they take. Password the public page if the couple is named.
Send the public URL, not a Drive seat
Email, WhatsApp, a highlight. When they ask in November, you point at the same page. The assistant is not in that story.
Why the client still gets a page, not a seat
A standing creator link is useful compared with a shared Drive because the address does not pull the recipient into your tree. Instagram, invoice, portfolio: the same folder. The assistant has a seat. The client has a URL. When you add a missing file, both doors update. When you remove the assistant, the couple's page does not vanish.
Use cases: photographers, designers, video, music, agencies
Photographers
A second shooter dumps cards into your folder. You keep the couple's gallery as a public, passworded page. Photographers and how to share files with clients are that week. The invite is for the shooter. The link is for the couple.
Designers
A junior packs the brand kit. You invite them as Can edit. The client gets flattened mockups on the unpaid view and sources when they are meant to have them. Designers.
Videographers
An editor with Can edit drops proxies. A producer with Can view checks the cut in the library. The client still gets a review clip on the public page, not a Drive tree of every take. Filmmakers.
Musicians
A mix engineer uploads stems into your pack. The buyer still pays on the public URL if the kit is a product. Musicians.
Agencies and freelancers
Agencies keep Drive for the team corpus and a Spike door for the brand. Invite the people on this job. Send the client one URL they can forward inside the company. How agencies deliver files and how freelancers sell and deliver files.
Shared Drive vs Spike People plus a public link
This table is about workflow, not a screenshot of someone else's admin console. Drive still wins at Docs. Spike wins at a folder with two doors.
Keep Drive for the workbench. Invite Spike people for the pack. Send clients the public page.
Drive answers how the studio works together. Inviting collaborators to a folder answers who may fill this pack, while the client still gets a page.
Invite collaborators to a folder when the leftover job is a small crew on a pack you own. Keep Drive for drafts and Docs. Keep the public Spike link for the people who should look, pay, or download without joining the library. What Spike is is that split: a shelf you own, People for the team, a door for everyone else.
Questions
Good to know
Usually no. Clients and buyers open the public spike.zip/f/… page. Invite the people who help you build the folder: an assistant who uploads, a producer who reviews. The sharing guide has the clicks under People & invites.
Keep reading
Related articles
Try the workflow in the article.
Upload a folder, protect the preview, share or sell from one link.