Use projects to organize files and workflows
Projects help your team group files, context, workflows, and people around a real body of work. They are useful for project delivery work, pilots, and focused workflow development.
When to use a project
Use a project when you want to:
- Keep files for a project or use case together
- Limit Assistant to a known set of files
- Give a team access to shared context
- Build workflows against the same standards or references
- Track usage and outputs around a specific effort
If you only need one quick question against one file, an Assistant session may be enough.
What belongs in a project
A project can include:
- Synced files from an integration
- Uploaded files
- Folders or tags
- Assistant sessions
- Workflow runs
- Team members with project-level access
Use project context for stable material, such as drawings, specifications, standards, and shared references. Use requested files in workflows for inputs that change every run.
Suggested setup
- Create or open the project.
- Add only the files or folders the team needs.
- Confirm the key files have indexed.
- Add the right users.
- Start with Assistant to explore the context.
- Create or run workflows once the repeated task is clear.
Common patterns
- Pilot project: one project for the first cohort's sample files and test workflows.
- Client context: one project per client or standard set.
- Workflow working group: one project where power users test workflows before sharing them broadly.
- Project delivery: one project connected to the external project folder or Autodesk Forma project.