> ## Documentation index
> Fetch the complete documentation index at: [llms.txt](../llms.txt)
> Use this file to discover all available pages before exploring further.

# Projects, initiatives, and sharing

How projects are organized, who can see them, and how to get work to people outside Sleuth.

[Open Sleuth Studio](https://app.sleuth.studio)

## Projects

Every question, workflow run, or Explore dataset lives in a project, with its chat, datasets, files, alerts, and outputs. Projects you start from Claude, ChatGPT, or Copilot are saved to your account the same way, so you can open them in Studio later.

## Initiatives

An initiative is a folder for related projects and their datasets, like everything for one asset or one deal. Use initiatives to keep a Team workspace tidy.

## Who can see a project

Each project belongs to the person who made it, on every plan. On a Team plan, everyone draws on the same credits, and you choose which projects to share.

## Work on a project together

| To | Use | What happens |
| --- | --- | --- |
| Give a colleague a copy to build on | **Clone project** | Your colleague gets their own copy, and you keep yours. |
| Hand a project over | **Transfer project** | Your colleague owns it, and it leaves your projects. |

## Share with people outside Sleuth

Download the deck, the report, the charts, or the dataset and send them on. To hand over everything, export the project as one ZIP, which lists every cell's sources. [Outputs and exports](outputs.md)

## Related

- [Outputs and exports](outputs.md): What Sleuth hands back, and how to get each one out of Sleuth.
- [Invite your team](invite-team.md): Bring colleagues into a Team workspace so everyone draws on one pool of credits, fix an invite that didn't arrive, and remove someone who left.
- [How your data is used](data-use.md): Who can see your questions, uploads, and results, and how to delete them.

*Updated November 9, 2026.*
