> ## Documentation Index
> Fetch the complete documentation index at: https://docs.autype.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Projects

> Projects are the central data structure in Autype — they contain documents, variables, versions, and all associated content.

A **project** is the top-level container for your work in Autype. Think of it as a folder that holds everything related to a specific document or set of documents.

## What a project contains

<CardGroup cols={2}>
  <Card title="Documents" icon="file-text">
    The actual content you write — your Markdown, sections, and styling. Each project has one primary document.
  </Card>

  <Card title="Variables" icon="braces">
    Dynamic placeholders like `{{company}}` or `{{logo}}` that can be set per export or via API. Defined at the project level.
  </Card>

  <Card title="Version history" icon="history">
    Every edit is tracked. Automatic versions on session end, manual snapshots anytime. Full diff view and one-click restore.
  </Card>

  <Card title="Assets" icon="image">
    Images, logos, and other files used in the document. Managed within the project context.
  </Card>
</CardGroup>

## Project structure

```
Project
├── Document (Markdown + JSON)
│   ├── Sections
│   ├── Defaults & Styling
│   ├── Citations & Bibliography
│   └── Abbreviations
├── Variables
│   ├── Text variables
│   ├── Image variables
│   ├── List variables
│   └── Table variables
├── Version History
│   ├── Automatic versions
│   └── Named snapshots
└── Settings
    ├── Export format preferences
    └── Collaboration settings
```

## Projects and organizations

Projects always belong to an organization. This means:

* All team members with the right role can access the project
* API keys scoped to the organization can interact with any project
* Credit costs for rendering are charged to the organization's balance

## Working with projects

### In the editor

You create and manage projects from the Autype workspace. Each project opens in the full editor with all its content, variables, and history.

### Via the API

The Developer API provides endpoints to list projects and use them for rendering:

* **List projects** — `GET /projects` returns all projects in your organization
* **Get variables** — `GET /documents/{id}/variables` returns the variable definitions for a document
* **Render** — `POST /render` generates a document from a project's content with optional variable overrides
* **Bulk render** — `POST /bulk-render` generates multiple documents with different variable sets

<Note>
  For step-by-step instructions on creating and managing projects, see the [Guides](/getting-started/guides/overview). For API details, see the [Developer API](/api-reference/introduction).
</Note>