Frequently asked questions
Plain answers before you apply.
Start here for access, field use, privacy, photographs, and product readiness. If your question is not covered, contact CaptureBeacon support.
Access & readiness
Is CaptureBeacon ready to use?
CaptureBeacon is a working alpha under controlled testing. The public site is ready for learning and applications; product workspaces are opened only for approved trials.
Who can apply?
Solo photographers, students, informal teams, established businesses, organizations, and nonprofit programs can apply. You do not need a registered company or professional license.
What happens after I apply?
You receive a reference number and email acknowledgment. We review whether the current alpha fits your work. If approved, we send a private invitation and acceptance steps to the email you provided.
Does approval happen automatically?
No. The application site never creates a workspace on its own, and applying does not promise acceptance, pricing, or an activation date.
Is pricing active?
No public price or payment flow is active. Pilot, sponsored, nonprofit, and future paid access remain subject to review.
Working with CaptureBeacon
What is the difference between Manager and Field?
Manager is for planning, assignments, oversight, delivery, and closeout. Field is the focused mobile experience for the current event: brief, checklist, timing, Photo Hubs, status, and help.
Can I use it on a phone?
The Field experience is designed for phones and tablets and can be installed. Manager is useful on larger screens but also supports mobile access.
What happens if the connection drops?
Preloaded field work is designed to queue eligible updates and synchronize them in order when service returns. Offline and multi-device behavior remains part of controlled alpha verification.
Can photographers see every event?
No. Photographer access is tied to the exact assigned event and role. Workspace-wide management information is not part of that view.
Can participants see private event operations?
No. Participant-facing pages expose only the specifically approved public information and actions for that event.
Photographs, galleries & trust
Does CaptureBeacon store photographs?
No. CaptureBeacon tracks operational milestones, approved links, counts, dates, permissions, and history. Photograph files and galleries remain in the photographer’s or organization’s chosen outside service.
Which gallery services work?
The workflow can track an approved external destination such as Pixieset, Dropbox, or another selected provider. Specific integrations and automation vary during alpha testing.
Can it handle both small and large events?
The same path can support a small portrait session or a larger staffed event: plan, assign, work, hand off, approve, deliver, and close. The details and team size change, but the operating rhythm does not.
How is support access handled?
Support diagnostics are controlled and owner-approved. Support should not receive broad, permanent access to a private workspace simply because a problem is reported.
What is the relationship to Frames of Service Foundation?
CaptureBeacon is currently a program of Frames of Service Foundation. Its credentials, data boundaries, and operating records are kept structured so the product can remain distinct if its ownership or organizational home changes later.
Still deciding?
Walk through the product surfaces or use the invented guided preview. Neither action creates a workspace.