Overview What is an Organization Admin?

An Organization Admin (Org Admin) is a user who manages a DeadlineFTP organization. As an org admin, you control who can upload images, who can download them, what metadata fields are available, and how your team's workflow is configured.

When you sign up for DeadlineFTP, you automatically become the org admin for your organization. You can also grant admin privileges to other team members.

Admin Dashboard Access

Org admins access the admin dashboard at dashboard.deadlineftp.com. After signing in, you'll see the organization management interface instead of the gallery view.

Roles Understanding User Roles

DeadlineFTP has three user roles within an organization. Each role has different capabilities:

Role Capabilities
Organization Admin Full control over the organization: manage members, configure settings, set up FTP users, customize XMP templates, configure FTP destinations, and access the admin dashboard.
Photographer Upload images via FTP from cameras or computers. Each photographer has unique FTP credentials. Photographers can also access the gallery to view and edit their own uploads.
Editor View the gallery, edit image metadata, and download images via DeadlineFTP Connect. Editors cannot upload via FTP or change organization settings.
Combined Roles

A single user can have multiple roles. For example, someone can be both a photographer (FTP upload access) and an editor (download access). Role checkboxes are independent.

Members Managing Team Members

The Members section of your admin dashboard lets you add, configure, and manage everyone in your organization.

Adding Members

There are two ways to add members to your organization:

Member Settings

For each member, you can configure:

Resending Credentials

If a member loses their login information, you can resend it from their member detail page. Use "Resend Login Info" to email their current credentials, or "Send Password Reset" to let them create a new password.

Photographers Managing Photographers (FTP Users)

Photographers (FTP users) are the accounts that upload images directly from cameras. Each photographer needs unique FTP credentials configured in their camera.

Creating FTP Users

  1. Go to the Members section in your admin dashboard
  2. Click Add Member and enter their name and email
  3. Enable the Photographer checkbox
  4. The system generates a unique FTP username and password automatically
  5. Share the FTP credentials with the photographer for camera configuration

FTP Credentials Format

Each photographer receives:

Camera Setup

For step-by-step camera FTP configuration, see our Camera Setup Guides for Canon, Nikon, and Sony cameras.

FTP Logins Additional FTP Logins (Multiple Cameras)

When you enable the Photographer role, the member gets one primary FTP login. If that photographer shoots with more than one body — an in-hand camera plus a remote, say — you can give the same person additional FTP logins. Each camera is configured with its own FTP username, so each one uploads independently, but everything still belongs to the same person.

What's Separate, What's Shared

Separate per login Shared across the member's logins
The gallery. Each login gets its own sub-gallery. When a photographer has more than one login, a camera selector appears so you can view one body at a time. The XMP templates, Quick Text, and photographer registry entry. All of a photographer's cameras caption from the same setup — you configure it once, not once per body.
The FTP username, which is what you type into the camera, and the optional label that names the camera in the gallery and desktop app. The password, unless you give a login its own. A blank password means the login inherits the member's primary FTP password, so changing the primary password updates every camera that inherits it.
Each Additional Login Counts Against Your User Limit

Additional FTP logins are billed as users. A member's primary login is included in their own user slot, but every extra login uses another slot from your plan's user limit — the same pool your team members draw from. One photographer with a primary login and two extra cameras uses three of your plan's users.

When the pool is full, adding a login fails with "User limit reached. Upgrade your plan to add more FTP logins." Deactivating a login you're not using returns its slot to the pool.

Adding an FTP Login

  1. Go to Members and open the member who needs the extra camera
  2. Find the Additional FTP logins section
  3. Enter a username — letters, numbers, dots, underscores, and hyphens only. It must be unique across all of DeadlineFTP, so prefix it with the photographer or organization name (e.g. jsmith.remote)
  4. Optionally enter a label that describes the camera, such as Remote or High endzone
  5. Leave the password blank to inherit the member's primary FTP password, or type one to give this camera its own
  6. Click + Add login
"+ Add login" Saves on Its Own

The + Add login button saves the new login immediately. The Update user button at the bottom of the member window does not save it — if you fill in the fields and only click Update user, the login is not created.

Managing Existing Logins

Each login in the list shows whether it inherits the primary password or has its own, along with how many files it has uploaded. For each one you can:

The primary login can't be deactivated, deleted, or set to inherit a password — it's the member's own login. To remove it, remove the member from the organization.

Admins Only

Only org admins can add, rename, or deactivate FTP logins. Photographers cannot create additional logins for themselves — ask an admin, since each one affects the organization's user limit.

Label Cameras the Way You Talk About Them

The label is what titles the camera's sub-gallery, so use the name your team already says out loud — In-hand, Remote left, Robo. An editor pulling from a remote body should be able to spot it without checking which FTP username it came from.

Metadata Default XMP Fields

Default XMP Fields controls which metadata fields your team sees when editing an image, the order they appear in, and how they're laid out. Open it from the Configuration menu on your organization page. It applies to everyone in the organization.

Fields, not values

This screen decides which fields exist for your team. It doesn't set what goes in them. To pre-fill captions, credit lines, or copyright notices on upload, use XMP templates with values — see the XMP Templates Guide.

Selecting Fields

Add the IPTC/XMP fields that matter to your workflow from the list on the left, and remove any you don't need with the on each field. Common fields include:

You can't save an empty list. An organization with no fields configured falls back to showing every available field, so clearing the list would give your team more clutter, not less.

Ordering and Layout

Drag fields to arrange them. A blue line shows exactly where the field will land as you drag. The first field sits full-width at the top — usually Caption — and the rest fill the Left and Right columns. Drag a field into either column, or use the arrow button on a field to send it across.

The layout you build here is what your team actually sees: the same arrangement applies in the desktop gallery, the mobile gallery, and the image edit window. Put frequently-edited fields first to minimize scrolling.

Starting From an Existing XMP File

Click Upload XMP File and pick a representative sidecar. Every field that carries a value in that file is added to your list, which is a fast way to seed the layout from a shoot you've already captioned the way you like.

Keep It Simple

Only enable fields your team actually uses. Fewer fields means faster captioning and less visual clutter for photographers and editors.

Delivery Configuring FTP Destinations

FTP destinations are external servers where your team can send edited images. This is typically used for wire services (AP, Reuters, Getty) or publication FTP servers.

Adding a Destination

  1. Go to FTP Accounts in the gallery toolbar
  2. Click Add Destination
  3. Enter the server details: hostname, port, username, password
  4. Choose the protocol: FTP, FTPS (FTP over TLS), or SFTP
  5. Optionally specify a remote directory path
  6. Click Test Connection to verify the settings
  7. Save the destination

Using Destinations

Once configured, destinations appear in the image edit window under "Send to FTP". Select a destination and click Send to export the image with its embedded metadata.

Credentials Security

FTP destination passwords are encrypted and stored securely. However, anyone with editor access to your organization can send images to configured destinations. Only add destinations you want your entire team to access.

Renaming File Renaming Recipes

A rename recipe is a saved, pattern-based rule that builds output filenames from template variables — date, a running sequence number, the original filename, metadata fields, and more. Instead of shipping cameras' raw IMG_1234.jpg names, your delivered files follow a consistent, wire-ready naming scheme.

Recipes use the same $variable / $$variable syntax as XMP templates, so anything you can drop into a template value you can build into a filename. See the XMP Templates Guide for the full variable list.

Pattern Result
$$year4$$month02$$day02_$$filenamebase 20260115_IMG_1234
AP_$$year4$$month02$$day02_$$filenamebase AP_20260115_IMG_1234
$$filenamebase_$$hour24$$minute IMG_1234_1435
Keep the Original Recognizable

Include $$filenamebase somewhere in the pattern so photographers can still trace a delivered file back to the frame on their card. Leading the name with the capture date keeps a shoot sorted chronologically at the destination.

Delivery Delivery Preset Options

A delivery preset does more than point at a destination — it can describe the entire way a gallery goes out the door. Beyond the FTP destination itself, a saved preset can bundle:

Bundling these into one preset means a single choice fully describes how a gallery is delivered — pick the preset and the format, size, filename, and destination are all handled together.

Settings Gallery and Workflow Settings

Several settings control how your gallery behaves and how images flow through your workflow.

Auto-Push to Subscribers

When enabled, images with completed audio transcriptions are automatically pushed to all connected DeadlineFTP Connect users. This is useful for voice-captioning workflows where transcribed images should reach editors immediately.

Gallery Generation

Controls whether thumbnail galleries are generated for uploaded images. In most cases, leave this enabled. Disable only if you're using DeadlineFTP purely for FTP relay without the web gallery.

Per-Member Settings

These settings can be configured at the organization level (applies to everyone) or overridden for specific members. Member settings can:

FTP Your Organization's FTP Server

Click FTP Info in the gallery toolbar to view your organization's FTP server details. This information is needed to configure cameras and FTP clients.

Server Details

Each photographer uses these server details combined with their personal username and password to upload images.

Captioning Quick Text for Your Team

Quick Text files speed up captioning by expanding short codes into full text. As an org admin, you can prepare Quick Text files for your photographers.

Creating Quick Text Files

Create CSV or TSV files with player rosters, staff directories, or common captions. Each row contains a trigger code and up to three replacement options.

Sharing with Your Team

Quick Text is stored at the organization level. A Quick Text source added for the whole organization is visible to every member immediately — there's nothing to copy, redistribute, or re-import, and new members see it the moment they join. Deleting a source removes it for everyone.

You can also scope a source to a single photographer, so a roster only shows up for the person shooting that beat. See Sharing Across Your Organization for how org-wide and per-photographer entries fit together.

See the Quick Text Guide for file format details and examples.

Storage Storage and File Management

Your organization has a storage quota based on your subscription plan. Monitor usage and manage files to stay within your limits.

Checking Storage Usage

A storage banner appears in the gallery when you're approaching your quota. It shows current usage and total available storage.

Freeing Up Space

To free storage space:

Permanent Deletion

Deleted files cannot be recovered. Make sure images have been downloaded or exported before deleting them from the gallery.

Checklist Getting Started Checklist

Use this checklist when setting up your organization:

  1. Set your Default XMP Fields - Select, order, and lay out the metadata fields your team needs
  2. Set default values - Add credit lines, copyright notices, and other defaults
  3. Add photographers - Create FTP accounts for everyone who will upload images
  4. Add extra camera logins - Give photographers who shoot a second or remote body an additional FTP login (each counts as a user)
  5. Share FTP credentials - Send camera configuration details to photographers
  6. Add editors - Create accounts for people who need download access
  7. Configure FTP destinations - Set up wire service or publication servers
  8. Prepare Quick Text files - Create rosters or caption shortcuts if needed
  9. Test the workflow - Upload a test image and verify it appears in the gallery
Reference Admin Quick Reference

Members

Add users, set roles (admin/photographer/editor), manage FTP credentials, control access.

Additional FTP Logins

Give one photographer a login per camera. Separate galleries, shared templates. Each login counts as a user.

Default XMP Fields

Choose which metadata fields your team sees, their order, and their two-column layout.

FTP Destinations

Add external FTP servers for image delivery to wire services and publications.

FTP Info

View your organization's FTP server details for camera configuration.

Quick Text

Load text expansion files for faster captioning with trigger codes.

Gallery Settings

Configure auto-push, gallery generation, and per-member overrides.