Skip to main content
Back to Help

Use projects to organize files and workflows

Projects help you group files, context, workflows, and — on Business and Enterprise — people around a real body of work.

Individual plan: projects are personal workspaces. You cannot invite teammates. Use them to keep files and sessions together for a job.

When to use a project​

Use a project when you want to:

  • Keep files for a project or use case together
  • Limit the Nomic agent 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, a standalone conversation may be enough.

Use projects for reusable context​

A standalone session is best for a focused conversation. A project is the better place for context you want to reuse across sessions, teammates, and workflows.

Add drawings, specifications, standards, accepted examples, and other stable references to the project once. Then start new conversations or workflow runs from that project when you want Nomic to work from the same source material again.

Projects do not automatically make every new conversation remember everything a user has ever asked. They provide a shared workspace of files and outputs that you can deliberately include as context for the next task.

What belongs in a project​

A project can include:

  • Synced files from an integration
  • Uploaded files
  • Folders
  • Nomic agent 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​

  1. Create or open the project. New project on the Projects page opens the project wizard; to start from files you already have, select them in Drive and choose Create project from files.
  2. Add your firm's job or project number, if the work is billable.
  3. Add only the files or folders the team needs, from the wizard or later with Add files on the project's Files page.
  4. Confirm the key files have indexed.
  5. Add the right users (Business and Enterprise). See Add users and members.
  6. Start a conversation with the Nomic agent to explore the context.
  7. Create or run workflows once the repeated task is clear.

Keep projects tied to your job numbers​

If your firm accounts for AI usage per job, set the project number on each delivery project. It is optional, so a project used to try something out can go without one, but a project whose usage needs to reach your accounting system should have it from the start.

Project admins set it in Project Settings → General, and organization admins can set or correct it for any project from Admin → Projects. Admin usage exports include it, so project spend can be reconciled against the job.

To give a project its own AI budget from the company pool — and to set project-level member spend limits — see Set and interpret spend caps.

Common patterns​

  • Pilot project: one project for the team's first 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.

Related​