> ## Documentation Index
> Fetch the complete documentation index at: https://resources.athenaintel.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Work as a team in a Project
> A shared Project where a teammate can pick up the work with its files and instructions.
In this lesson, you'll set up a project with your team's files and standing instructions. Then you'll ask from it, and hand it to a teammate.
A project holds everything for one piece of work: the files, the standing instructions, and every conversation about it. Open Projects, and click New project. Name it Northwind freight exceptions, and add a short description. The dispute SOP and the tracker are open, so they're listed under Link to Project. Tick both, then click Create Project.
Next, link the rest of the files this work depends on. Click Add assets, then Link existing assets. Pick the carrier files and the team's template, and click Link to project. Now write the standing instructions, the things you'd otherwise repeat in every chat. On the Instructions card, click Add. Cite every figure, keep the template and the dispute IDs, and mark what's unresolved. Then click Save instructions. They're starting context, not hard rules, so keep them short and specific.
Ask from the project's own box, and the answer already knows the files and the rules. Ask for this week's exceptions checklist. The prompt can stay short. Athena starts with the linked files, and your instructions are already in place. Each item links to its source, and the list ends with what's still open, as the instructions asked.
Share the project, and Sam gets the same sources and instructions you used. Click Share, and add Sam. Projects share with edit access. Keep Share 4 linked assets you own ticked, so the files go along with it. Click Share. The green note confirms Sam can edit. For view-only access, share a single document instead.
When Sam opens the project, everything is already in place. The same instructions, the linked files, and Jordan's checklist under Recent runs. Sam asks for the carrier email. It starts from the same context, so the draft follows the same rules. Nobody re-explains the work.
Quick check. Where do you put guidance every run in this project should follow? In the project's instructions.
An audit team keeps one project per engagement. Its instructions say to cite every balance to a work paper, and flag unresolved items. When a new teammate joins, they open the project and start from the same context.
Try it in your own workspace with this prompt. When it works, the Instructions card is filled in, and the first answer links each point to a file.
## Before you start
Upload these files from the [Northwind starter kit](/docs/athena-101/starter-kit): **Northwind dispute SOP.pdf**, **Northwind exceptions template.xlsx**, **Northwind carrier files/wk 41**, and all files in **Lesson 04**: the tracker, both invoices, and **Carrier rate sheet (wk 41).pdf**.
Create a Project and link the uploaded files. To practice handoff, you need a teammate with access to the Project and its files; ask your admin for help if needed. If the teammate cannot open the earlier chat, save the checklist as a linked document. Without a teammate, reopen it yourself.
## Steps
Open **Projects**, click **New project**, and name the work. Select the procedure and tracker under **Link to Project**, then click **Create Project**.
Use **Add assets** and **Link existing assets** for the remaining files. Add short instructions to cite figures, keep the template, and flag open items; these guide the work, so review the results.
Ask for an exceptions checklist from the Project. Check that it uses the linked files and cites each item.
Click **Share** and add your teammate, including the linked files you own. Projects give edit access; share a single document when someone only needs to view it.
Have your teammate open the Project and continue from the checklist. If the earlier chat is unavailable, save the checklist as a linked document for the handoff.
[1-minute version: share a Project](/docs/athena-101/quick-how-tos#share-project).
## Try it
> Create a project for \[piece of work], link its key files, and add instructions: cite every figure, keep our template, flag open items.
Look for saved Project instructions and source links in the first answer.
## Next
[Turn scattered files into the team's report](/docs/athena-101/05-team-report)
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.