The Agency Workflow: Managing Multiple Photographers

You've got five photographers on the ground at a major event. They're all firing high-res files over spotty 4G/5G connections back to home base.

You probably have tried one or few of the following already:

1. The "Shared Login" Hack: Giving everyone the same ftp_upload generic credential.
   • The Reality: Total chaos. File collisions and untraceable uploads. DSC0001.jpg from Camera A instantly overwrites DSC0001.jpg from Camera B. Your remote editors are screaming. The metadata is a mess, and you have zero clue who actually shot what.
2. The Hardware Route: Handing out physical ethernet cables, or literally running memory cards across the venue.
   • The Reality: Way too slow. The news cycle moves in seconds, not the 15 minutes it takes to jog a card to the editing desk.
3. The "Enterprise" Roll-Your-Own: Standing up custom Linux servers and wrestling with complex user permissions.
   • The Reality: It's an expensive nightmare to maintain, especially when you need it working perfectly at 2 AM on a Saturday.

A Better Pattern: Decoupling Data Store from Identity

The architectural fix we propose you is to separate the Data Store (where the files actually land) from the Identity (the human or camera sending them).

Instead of tying a data store folder directly to an FTP user, you build an "Event Pipe."

• The Pipe: The channel that carries your photos securely from the field to the desk. Let's call it pipe_oscars_2025. It accepts photos from multiple photographers and send them simultaneously to one or many data stores.
• The Senders: Individual credentials mapped to specific humans or devices. Jim, Sarah, or Remote_Cam_1.
• The Data Stores: One or many storage locations accessible by editors, news agencies, or just the backup storage.

How We Actually Set This Up

Here's the exact workflow we use to keep five photographers organized without them stepping on each other's toes.

Phase 1: The Desk (Director Setup)

1. Spin up the Event Pipe:
   • Map a new Pipe to your S3 buckets. Name it something painfully obvious like pipe_oscars_2025.
   • The Gotcha: You must enable the Place files inside a folder named after the sender setting. If you miss this, you're back to dumping everything in the root directory. This forces incoming files into sender-specific subfolders.
2. Issue Identities:
   • Generate distinct sender credentials: Jim, Sarah, Mike.
3. Hand Out Credentials:
   • Jim gets jim@pipe_oscars_2025.
   • Sarah gets sarah@pipe_oscars_2025.

Phase 2: The Field (Photographer Config)

The photographers don't need to manually type folder paths in their camera menus. The Pipe handles the routing logic server-side.

• Jim's Camera:
  • Host: ftp.rilavek.com
  • User: jim@pipe_oscars_2025
  • Directory: / (Leave this alone)
• Sarah's Camera:
  • User: sarah@pipe_oscars_2025
  • Directory: /

What Actually Hits S3

The second they press the shutter, your S3 bucket organizes itself.

s3://my-agency-bucket/2025/oscars/
├── jim/
│   ├── DSC0492.jpg
│   ├── DSC0493.jpg
├── sarah/
│   ├── IMG_9921.jpg
│   ├── IMG_9922.jpg

Editors can now sync specific prefixes. They know exactly whose memory card a file came from.

The "Rule of Two" for Redundancy

For high-stakes stuff, one copy is zero copies. You can configure the pipe to push every upload to a second data store automatically.

• Primary: s3://fast-editing-bucket/ (AWS S3 for the editors)
• Backup: s3://cheap-archive-bucket/ (B2 or Wasabi for disaster recovery)

The camera only makes one upload trip. The backend splits the stream to both buckets simultaneously. This gets you off-site backup without chewing through the photographer's mobile data cap.

Accountability When Things Go Wrong

Because we decoupled identity, you never lose the audit trail. Every single byte transferred is tagged with the Sender ID in the logs. You can filter the dashboard and instantly find out exactly who uploaded what.

Field-Tested Best Practices

• Force Custom Prefixes: Make photographers set a custom file prefix in-camera (e.g., JM_ or SR_). It's a necessary fail-safe against the inevitable overwrite.
• Kill the "Auto-Transfer All" Button: Instruct your team to only send selects using the "Protect" or "Transfer" button. It saves massive amounts of bandwidth and editor sanity.
• Instant Revocation: If a freelancer bails mid-event, disable their specific Sender profile. You don't have to rotate the password for the entire team.

Managing multi-user uploads doesn't have to be a fragile mess of shared passwords. Rilavek handles all this routing and identity isolation out of the box, so you can stop wrestling with FTP servers and just get the shots to the desk.