Menu
Share Maya projects with their dependencies
Use Maya project roots and relative resources to make scene handoffs reproducible across authorized workstations.
Make the project the unit of the handoff
A Maya scene can depend on textures, references, scripts and other resources outside the scene file. Suite provides shared filesystem access to those resources on supported hosts. A dependable handoff keeps the scene's project structure and dependencies understandable to the next artist or authorized worker.
Autodesk's Maya project guide explains setting a project and using its resource folders and path rules. Set the intended project when beginning work rather than assuming that opening a scene also establishes every correct resource location.
Keep shared dependencies deliberate
Use project-relative resources where they fit the pipeline. Record dependencies intentionally stored outside the project, such as a controlled studio asset library. Avoid unnoticed references to one artist's desktop or temporary folder, which the next workstation cannot reproduce.
Keep source scenes and approved dependencies separate from temporary simulation or render output. Assign named output revisions so a new render does not replace the only evidence behind an earlier review. Application caches and Suite's client cache have different roles and should be planned separately.
Record the non-file requirements
A common filesystem does not install a renderer, provide a plug-in license or standardize application versions. Include the Maya version, required renderer and relevant plug-in assumptions in the handoff record. Follow the responsible pipeline team's approved setup on each host.
For an agent-driven task, specify the permitted scene, operation and destination. A supported Suite client route does not establish that an arbitrary container or render service can authenticate or mount the library. Choose a validated host and keep provisioning separate from file processing.
Verify a second workstation
Open the scene from its intended project root, inspect missing-resource messages and produce a small agreed test render. Compare the output with the expected result. Then save a new scene revision and have the original artist confirm that its dependencies still resolve.
This is a proposed Maya filesystem workflow rather than a certified Suite integration. The opportunity is broad tool compatibility through familiar paths, with less manual packaging of the entire shared library. Explore Suite Managed and bring one dependency-rich scene to the first handoff test.
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.