Menu
A folder structure for a shared media library
Organize originals, working projects, generated assets and approved deliveries so humans and agents can find the right files.
Organize around the handoff
A shared cloud filesystem becomes more useful when people can tell what a file is for before opening it. Use a small, consistent structure that distinguishes source material, active work, generated assets and approved deliveries. Suite supplies the shared file access; the folder convention is a team practice you control.
One proposed project layout is Originals, Projects, Derived, Review and Delivery under a stable project identifier. These are example names, not required Suite folders. Choose names that fit your existing production vocabulary and keep them consistent across jobs.
Give each area a clear purpose
Originals holds the approved inputs. Avoid treating it as a scratch area for processors. Projects holds application documents, with ownership rules appropriate to the application. Derived holds proxies, transcripts, thumbnails and other reproducible results. Review holds versions ready for feedback. Delivery holds explicitly approved outputs.
Keep a short project record at the root: project owner, naming convention, active revision and where to find the current delivery. A directory called Delivery does not itself make every file inside approved. Record that decision in a named manifest or the team's production system.
Use structure to narrow agent assignments
An agent can receive a precise instruction such as reading selected originals and writing candidate transcripts into a particular derived-output folder. A folder name is only an organizational cue; permissions must enforce the intended access. Our agent guidance explains the distinction between using files and provisioning accounts.
The benefit is a smaller, clearer task. The agent does not need to scan unrelated customer projects to find a single recording. A human reviewer can inspect candidate results before anything enters the approved-delivery area.
Avoid a disruptive reorganization
Introduce the convention on one new project first. Existing application documents may store references to media paths, so moving an active library can break links. Preserve the relative layout of dependencies and test the application after any planned relocation. Adobe's linked-file guidance for Illustrator illustrates why relationships between files matter.
Have a new collaborator locate one original, open the current project and identify the approved output using only the project record. If that works, the structure is doing useful work. Explore Suite Managed to give the team a shared place for that convention without preparing a full library copy on every workstation.
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.