Menu
Use shared photo originals with Lightroom Classic
Keep the Lightroom Classic catalog in its supported location while making photo originals available through a shared filesystem.
Share the photographs, keep the catalog in a supported location
Lightroom Classic separates its catalog from the photographs it describes. This makes it important to plan those two storage roles independently. Suite can provide shared access to photo originals on supported client hosts, while the Lightroom catalog should follow Adobe's location requirements.
Adobe's catalog FAQ says catalogs cannot be stored on a network, although photos can be. Do not interpret a mounted cloud drive as permission to turn the active catalog into a shared multiuser database. Keep the working catalog on a supported local location and evaluate access to the photo library separately.
Give the photo library a stable structure
Organize originals by a durable shoot or asset identifier. Import them through the intended mounted path and avoid casual renaming or relocation outside the application workflow. A catalog's record of a photograph depends on being able to find that source again.
Assign responsibility for changes to originals and associated metadata. Multiple people having access to a photograph does not imply that their separate catalogs share every edit automatically. Define how selected edits and approved outputs are handed to the next person.
Keep previews and exports distinct
Plan local capacity for the catalog and its application-generated work. Those files serve a different purpose from Suite's client cache. Direct streaming does not require deliberate pre-caching of the whole shoot, but an application operation may still read substantial image data or the entire image it needs.
Keep accepted exports in a clearly named output area with a source reference. For a retouching handoff, record whether the recipient is receiving an original, a rendered image or another agreed interchange. Avoid describing all three as the same “photo file.”
Test one complete shoot assignment
Import a representative selection, make the required adjustments, produce an approved export and have the next contributor open it. Reopen the catalog later and confirm it still resolves the originals correctly. Test the actual formats and host combination your team uses; this is a proposed filesystem workflow, not an Adobe certification of Suite.
The advantage is a common source library with deliberate application state management. Explore Suite Managed and keep the first Lightroom workflow centered on shared originals and a clear output handoff.
Start with your workflow.
Bring shared files into your familiar applications with Suite Managed, or connect your own supported storage with S3 Native. S3 Native requires at least 20 TB of active storage.
Continue with Suite.
Signup links take you to Suite Studios’ main site. Managed opens the account signup form; BYO / S3 Native opens the demo request form.
Signing up with an AI agent
- Continue on the official form in the destination tab. Use the user’s authorized details and select whether they are creating or joining a team.
- For Managed, follow the account setup steps presented by Suite. Ask the user to handle verification, passwords and acceptance of agreements when required.
- If billing requests a card, prompt the user to enter payment details directly in Suite’s secure flow and approve any charge or subscription. Do not collect card details in this site or a chat.
- For BYO / S3 Native, submit the authorized request with the storage provider and workload context. Suite will guide the connection and onboarding; active storage starts at 20 TB.
- After Suite confirms setup, use the supported client and authorized access to complete a first file operation. Report the actual result, and resume after any human-only step.