Skip to main content
A project is an organization-owned folder for related documents. It helps teams group contracts, reports, or customer material without coupling the individual documents to one shared set of variables or versions.

​
What a project contains

Documents

A project can contain multiple independently maintained documents.

Variables

Dynamic placeholders like {{company}} or {{logo}} are defined per document.

Version history

Snapshots and named versions belong to the document they describe.

Assets

Protected images, source files, and generated media stay associated with their document and organization.

​
Project structure

​
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
  • Plan allowances and automation credits are scoped to the organization

​
Working with projects

​
In the editor

You create and manage projects from the workspace. Search can find documents across projects, while each project view supports server-side filtering and pagination for larger workspaces.

​
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/document/{id} generates a persistent document with optional variable overrides
  • Bulk render — POST /bulk-render generates multiple documents with different variable sets
For step-by-step instructions on creating and managing projects, see the Guides. For API details, see the Developer API.