# Projects

Projects are the primary containers for work, integrations, products, experiments, and ecosystem deliverables.

<div class="docs-section-heading">
  <h2>Project model</h2>
  <p>Use projects to group resources, collaborators, settings, and operational history.</p>
</div>

A project may be a game, app, API integration, research effort, studio build, community tool, or internal system. Projects usually live inside [[Organizations]] and use [[Teams]] and [[Permissions]] to manage access.

## Project contents

- Name, description, and ownership.
- Members, teams, and roles.
- API credentials or integration settings.
- Environments such as development, staging, and production.
- Links to docs, repos, support channels, or dashboards.

## Project lifecycle

1. Create project and assign ownership.
2. Add teams or collaborators.
3. Configure integrations and environments.
4. Document security and operational notes.
5. Archive or transfer when work ends.

<div class="docs-grid">
<a class="docs-card" href="/Organizations">Organizations</a>
<a class="docs-card" href="/Teams">Teams</a>
<a class="docs-card" href="/Permissions">Permissions</a>
<a class="docs-card" href="/Studio">Studio</a>
</div>