Projects
Grouping related artifacts under one project and sharing a single project link for a multi-part handoff.
In short
A project groups artifacts that belong together. A project link is one URL that indexes the group, which is the right shape for a release packet, a multi-part deliverable, or a recurring report series.
When a project is the right unit
Use a project when the recipient needs more than one document and would otherwise get several links in one message. A release packet with a change summary, a risk note, and test evidence is one project, not three unrelated artifacts.
Use a project for recurring work too. Publishing every weekly run into one project means a stakeholder can see the series rather than only the newest run.
How publishing into a project works
Pass a project name when you publish. If the project does not exist it is created; if it does, the artifact joins it. Using a stable project name across runs is what keeps a series together.
Creating the share link is a separate call, so a project can exist and accumulate artifacts before anyone outside sees it.
What a project link is not
It is not a website with navigation you control. The project page is a BinHTML-rendered index of the artifacts in the project; you cannot inject your own HTML into it.
There is one share link per project. Revoking it revokes access to the index for everyone.
- Projects on Builder
- 50
- Projects on Pro
- 500
- Active project links on Builder
- 10 active
- Active project links on Pro
- 500 active
- Artifacts per project link on Builder
- 25
- Artifacts per project link on Pro
- 250