Overview & nav
How org mode differs from solo — projects, clients, team, reports.
If you run a studio, agency or in-house photo team — several photographers, shared clients, a review-and-approve workflow — SnapFlow has an organization mode built for it. This track covers what's different for org accounts. The core craft (uploading, culling, recognition, metadata, socials) works exactly as in the Photographer (web) track; here we focus on the team, client and workflow layers on top. Web
Who this is for
Org accounts come in corporate and agency flavours. Most of this track applies to both. Where a feature needs a specific tier (e.g. white-label is agency, brand colours are corporate_pro) we say so.
How org mode looks different
A solo photographer works under /dashboard with a personal plan. An organization gets a team workspace with its own navigation, branding and billing. The top bar reads SnapFlow · {your org name}, and the nav is:
- Projects — your jobs, each grouping one or more shoots (events). (org-only)
- Albums — the flat list of every event/album.
- People — the athlete/face registry. Shown when your plan includes recognition — the corporate Pro tier and up, and all agency tiers (the entry-level corporate plan doesn't surface it).
- Clients — your client CRM. (org-only)
- Socials — Instagram posting (shared; accounts are per-user).
- Reports — storage, quota, deliveries and activity analytics. (org-only)
- Team — members, roles and invites. (org-only)
Projects, Clients, Reports and Team live under /admin/…; Albums, People and Socials are shared with the personal surfaces. You don't need to memorise the URLs — the nav links take you there.
People is plan-gated, not org-gated
Recognition (face detection, the athlete registry, team/kit matching) works the same for orgs as for solo photographers — it's just gated by your plan. The corporate Pro tier and up and all agency tiers include it; the entry-level corporate plan doesn't surface the People destination. When it's on, it behaves exactly as in Recognition.
The shape of an org job
A typical organization workflow:
- Create a project for the job (and link the client).
- Add an event (a shoot) under it, with the workflow toggles you need.
- Assign a photographer to the event.
- Photos come in; the event moves through Upload → Review → Proofing → Delivered phases.
- Your team reviews and proofs internally; the client picks favourites.
- You Confirm delivery — the client is emailed their finished gallery.
The next chapters walk each piece: Projects & event phases, Team & roles, Clients, Internal review, proofing & delivery, Reports, Branding & white-label, Marketing consent, and Billing & ownership.