Lumara for photographers
Managing photo visibility inside a client gallery
Use per-photo visibility when selected images should stay out of an otherwise accessible gallery. Use gallery privacy or password protection for access to the collection as a whole, and always test the signed-out result.
What this workflow needs
Hiding one photograph is not the same as making the gallery private. Photographers may need to hold back a sensitive frame, an alternate edit or an image awaiting permission while leaving the rest of the delivery available. The final state should be intentional and documented.
A useful workflow should reduce uncertainty for the photographer and the client. Keep the record specific, make the next action obvious and avoid collecting information that nobody will use. The aim is a calmer handover, not a larger collection of fields.
Set it up step by step
- Choose the access levelDecide whether the whole gallery is public, private or password protected.
- Identify exceptionsMark individual photographs that should not appear in the client-facing collection.
- Use bulk visibility carefullyApply one change to a verified selection rather than an uncertain large batch.
- Test signed outConfirm both the gallery access and the individual visible image set.
How this maps to Lumara
Lumara separates gallery access settings from per-photo visibility. The Manage photos area can update visibility for selected photographs, while gallery details control public, private and password-protected delivery.
Use the dashboard as the working record, then confirm the client-facing result separately. A saved setting or status is useful evidence of progress, but it does not replace checking the public gallery, request link or portfolio preview as the client will receive it.
- Treat gallery access and photo visibility separately.
- Confirm every bulk selection before saving.
- Use client permissions when considering public use.
- Test the result without the photographer session.
Public, private and password-protected galleries explained
Access should follow the people and purpose of the gallery, not a single default used for every shoot.
Client gallery privacy checklist
Privacy is a sequence of decisions about people, access, search, sharing and retention—not a single password switch.
Organising client gallery photos with order and tags
Ordering and tags should make a large shoot easier to manage without turning the client gallery into an internal filing system.
A practical status workflow for photography galleries
Gallery status is most useful when every label corresponds to a real next action and owner.
Linking a client gallery to the right client and job
A connected gallery carries useful context beyond the delivery link and reduces duplicated client records.
Using client favourites and gallery engagement
Favourites provide useful client context when the photographer is clear about what a favourite means—and what it does not.