Docs · ProjectSend

Documentation

Guides that ship with the release

Every guide travels with the code and is published here from the release you download. This is the documentation for ProjectSend 2.3.0.

Install & run

Run with Docker

The recommended path: the production compose file, where your database and uploads actually live, surviving reboots, reverse proxies, backups and upgrades.

Install from the zip

The manual route: nginx, PHP-FPM and MySQL, seven steps from the release zip to your administrator account, plus the background worker and scheduled tasks.

Update

Moving a 2.x installation to a new release — what to back up first, the Docker path, the update.sh path, and what to do when it goes wrong.

Email through Microsoft 365 or Gmail

Send ProjectSend's email through your own Microsoft 365 or Google account with OAuth, instead of SMTP passwords.

Moving from Legacy

Move from Legacy

ProjectSend 2 installs fresh and imports your data: what comes across, the direct and bundle routes, and the preflight report — nothing is written to your old site.

The API

API guide

The narrative guide to the REST API: authentication, abilities, pagination, polling for changes, uploads and versioning.

Zapier, Make & n8n

Connect ProjectSend to automation tools with the API and Webhooks by Zapier — triggers, actions, three complete examples, and the honest limits.

Looking for a quick overview of the API first? Start at projectsend.org/api. Running the previous generation? The Legacy documentation remains available at docs.projectsend.org.