Deliverables

The Deliverables tab is where you manage packages — bundles of Vault files shared with clients, vendors, or anyone outside the firm. Vault remains the filesystem; Deliverables is the workspace for packaging and link lifecycle.

Deliverables vs packages

• Deliverables — the project tab that lists every package.
• Package — one titled bundle of Vault files, with an optional share link, expiry, and password.

Create a package from Deliverables

On the Deliverables tab, project members (Admins, Managers, and Contributors) can choose Create package. Pick From linked files to start from Vault files linked on Work — drawings grouped by section, plus general tasks and vendor requests that have linked files. Checking a section selects every drawing in it; uncheck (or check) individual items, then continue to the same package wizard for title, description, expiry, password, and sharing.

Or pick From tags. In Vault, tag files or folders in the details pane (project tags are unique to that project). Tagging a folder includes all files in it and nested folders. From Deliverables, choose the tag, trim the file list, then finish in the wizard.

Create a package from Vault

On the Vault tab, select one or more files. In the selection bar next to Delete, choose Create package. A wizard asks for title, optional description, and the file list. Choose Save as draft (no public link yet) or Share now (optional expiry and password). When you share, the link is copied to the clipboard.

To grow a draft, select more files in Vault and use Add to package — pick an existing draft. Adding from Vault only works for drafts.

Package status

Manage packages on Deliverables

Open a package row to edit details, remove files, share or reshare, copy the link, set or clear a password, change expiry, revoke, or permanently delete the package. View and download activity (when available) appears in the detail panel.

• Share / Reshare — create a public link with optional expiry and password
• Copy link — for Active (and Expired, until extended) packages
• Revoke — immediately stops access
• Extend / set expiry — none, 7 days, 30 days, or a custom date
• Delete — removes the package and revokes any link; Vault files stay

What recipients see

Opening a package share link lists every file with an individual download. When the package has two or more files, recipients also get Download all as ZIP to fetch everything in one archive. Password-protected links still require the password before files or the zip are available.

Who can manage packages

• Admins, Managers, and Contributors — create packages, add files, share, revoke, and delete on projects they can access (unless the firm restricts external shares to Admins and Managers).
• Firm Library — packages are project-scoped; Library file management stays Admin-only.

Before you start

• Project files are already organized in Vault and final/approved files are clearly identified.
• You know whether your firm restricts external sharing to Admins and Managers only.

Workflow checks and quality guardrails

• ✓

  Checklist item 1: Use clear package titles that include issue purpose and date so recipients can identify the right release immediately.

• ✓

  Checklist item 2: Set expiry and optional password by default for external recipients, then extend only when business context requires.

Common mistakes to avoid

• Publishing packages before confirming file completeness and latest revision state.
• Leaving old links active after superseded issue releases.

Troubleshooting

1. 1
   Troubleshooting step 1

   If recipients cannot open links, confirm link status is Active and the password was shared correctly.

2. 2
   Troubleshooting step 2

   If Download ZIP is missing, check package file count because ZIP appears only for multi-file packages.

What to do next

1. Open /docs/vault and continue with the next workflow.
2. Open /docs/security and continue with the next workflow.
3. Open /docs/activity and continue with the next workflow.