Every project ends with a handover question. The customer takes over operations, moves to another agency, or simply wants a record of what they paid for — usually met with a document written from memory on the last day.
The effort is not the real problem — the gaps are: a login that only existed in a chat thread, an environment variable nobody wrote down, a keystore on the laptop of whoever set the project up and has since moved on. None of it surfaces until months later, when everyone has lost the context.
Since 5 August a project can be exported as a PDF, generated from what is configured.
What the export contains
The PDF opens with a title page and a short introduction, giving the recipient more than a list of items — a frame of reference for what the project runs on.
Credentials can be included on request. For documentation while a project is running, the export without them is enough; for a complete handover, you need them. Android upload keystores can also be downloaded — the key needed to keep publishing updates for an app already in the store.
An export with credentials is confidential
A PDF with credentials is a sensitive document, gathering into one file what is otherwise spread across several systems and protected separately.
Treat it accordingly: not over unencrypted email, not in a shared drive everyone can reach, not kept longer than needed. A handover deserves a secure channel, and once responsibility changes hands, rotate the credentials it contained. For documentation only, leave the credentials out.
It works because the project is the source of truth
An export is only as complete as the data behind it. The substance here is not the PDF but that the platform keeps credentials, environment variables and GitOps configuration centrally — one home for those details rather than a scattering of local files, chat messages and verbal knowledge. An audit log records what happened, and roles determine who sees what.
Where this helps day to day
Three situations come up regularly.
End of a project. The customer takes over or hands work to another team, receiving a document that reflects the actual state instead of an improvised summary.
Traceability during operation. Even without a handover, a written record of what belongs to a project helps the person who joins a year in.
Less dependence on individuals. When the knowledge lives in the project, a holiday or departure is not a risk.
For agencies and freelancers running several projects in parallel, this is the difference between a one-hour handover and one that drags on for weeks.
Related topics
At organisation level, the compliance area generates contract documents as PDFs and a ZIP export. The two complement each other: project documentation describes one project, compliance documentation the legal frame around it. See the pages for agencies and for freelancers.
