How to store and share your team's new AI headshots
You just got 100 new headshots. Now what? Here's the simple, secure system we use with clients to organize, share, and update photos without the chaos of endless email chains.
Create a single, master folder in Google Drive
Start here. Name this folder something you can find in two seconds, like "Company_Headshots_2024" or "Team_Photos_Q3". Put it right in the main "My Drive" area, not buried in some other project folder from 2019. I've seen teams waste fifteen minutes of a meeting just trying to locate where someone *thought* they saved the files. One folder. One truth. This is your photo library's foundation, and everything else builds from it. Think of it as the central filing cabinet for everyone's professional face.
Set up three subfolders: Raw, Final, Social Crop
Inside that master folder, make these three. The "Raw" folder is for the untouched, high-resolution files straight from the photographer or the generation tool. They're your digital negatives. The "Final" folder holds the polished, retouched versions everyone will use for LinkedIn, the company website, and email signatures. The "Social Crop" folder is a lifesaver. Take those final headshots and save a separate, square-cropped version (think 1080x1080 pixels) optimized for Instagram, Twitter, or internal social platforms. This simple system prevents the classic nightmare: someone using a blurry, poorly cropped version from a Slack message on the official "About Us" page.
Share the folder with a 'view only' link
Right-click your master folder, hit "Share," and change the general access to "Anyone with the link" as a "Viewer." Copy that link. This is the only link you need to distribute. When you paste it into your team's Slack channel or email, people can see and download their photos, but they cannot accidentally delete a folder, rename your files, or upload their vacation selfies into the system. It gives everyone access without handing them the keys to rearrange the entire library. I once had a client where a well-meaning employee decided to "organize" by adding subfolders for "Blondes" and "Brunettes." We don't do that anymore.
Avoid the chaos of emailing files individually
Picture this: Sarah in Marketing emails you for her headshot. You attach it. Then David in Sales asks. You attach it again. A week later, Sarah needs the square crop for an event. You dig through your Sent Mail. This creates at least five problems instantly. Your inbox becomes a search engine. You have no control over which version people are using. New hires never get added to the chain. You become the bottleneck. If someone leaves, their outdated photo might still be circulating in a hundred old emails. That single shared folder link stops all of it. You tell the team, "Your photos are here. All versions. Forever."
Update one photo, and it updates everywhere
This is the magic. Let's say someone gets a new haircut or a promotion, and you need a fresh headshot. You take the new final image, drag it into the "Final" folder, and name it *exactly* the same as the old file (e.g., "Jane_Doe_Final.jpg"). Overwrite it. Because everyone's links and email signatures are pointing to that file in the shared folder, their picture updates automatically. No more sending a company-wide email begging people to delete the old one from their desktop. The link is the source. I helped a 50-person tech company do this; it saved their communications director roughly eight hours of frantic update requests every quarter.
Stick to this structure, and you’ll never have to hunt for a headshot again. Your team gets a reliable resource, and you get your time back. The goal isn't just storage—it's creating a system that works quietly in the background, so the photos themselves can do their job.