Create a shared photo process without passing passwords around. Invite the right people, give them the access they need and keep the organisation’s stock photographs together.
Explore showrooms ↗
Owners manage membership and ownership. Administrators manage organisation details, billing, branding and invitations. Members work with projects, generation, review and downloads.
Use individual accounts rather than a generic login shared across a sales desk. When a colleague leaves, an owner can remove their account and sign out its sessions without removing the organisation’s photos.
Saved styles keep showroom and branding decisions available to the team. Private background references belong to the organisation, so a photographer does not need to re-upload the same environment for every vehicle.
Agree who can change the default style and who approves samples. A tool provides access controls; a short written handover tells people when to use them.
A named project holds originals, sample decisions and generated results. Processing status and credit activity help the team understand what is happening before starting duplicate work.
Use notifications for the people who need completion or failure updates. Make the publishing owner explicit, then review the actual website or marketplace listing after uploading the approved files.
Credit purchases are restricted to organisation owners and administrators. Members can use available credits for the photo workflow.
No. Organisation projects and their media stay with the organisation when a member account is removed.
The current owner can transfer ownership to another member with password confirmation. Administrator access is different from organisation ownership.
Original vehicle photographs and working results need an intentional storage model.
Read the guide ↗
Team access should reflect current responsibilities.
Read the guide ↗
Notifications should help the next person act.
Read the guide ↗