The phone stays in the van, and so does the session
A shared phone can be convenient. A permanently signed-in owner account can also give the next user administrative access unintentionally. Decide who signs in, which role they need and when they sign out. An unlocked device with an active session is not a neutral filing cabinet: it enables actions under the currently authenticated account.
Give each person a clear account
Owners can issue controlled manual invitations and manage worker accounts. A valid invitation or recovery link is sensitive and should not be placed in an open group chat or photograph. The current workflow does not independently verify mailbox ownership or deliver invitations automatically by email. The business needs a deliberate procedure for checking the intended recipient and transferring access safely.
Understand the project boundary
The product separates businesses and restricts workers to explicitly granted projects. New workers and projects start without grants. Historical access was retained through an explicit compatibility migration and requires owner review. Owners retain administrative authority. These project grants are not a special customer portal, guest role or per-photo permission model; do not share an internal team account as a shortcut.
Close the handover consciously
Wait for confirmed uploads before signing out. The online queue exists only in page memory; logout discards pending files. Keep device originals until upload confirmation. Sessions can be revoked and accounts disabled, but downloaded copies cannot be remotely recalled. Device locks, loss procedures and careful account choice remain necessary; multifactor authentication and comprehensive device management are not implemented.
Test the complete account switch
With invented data, switch between two accounts and check which project information remains visible, what happens to pending uploads and whether the second user must authenticate again. Automated checks cover parts of this workflow, not every phone’s autofill or operating-system behavior. Real shared iPhone and Android devices still need supervised testing before use with customer data.
WHERE FOTONACHWERK STANDS TODAY
Personal accounts, explicit grants and manual invitations
Implemented locally; no MFA, guest portal or device management.
View the product and current status ↗About this article
External sources may change. Examples describe typical workflows, not documented customer cases. This article does not replace an assessment of your specific project. General information, not individual legal advice.