Project Detail - Shares / Project Share (files→share link)¶
| Stage | Estimated |
|---|---|
| Status | Deferred |
| Design status | Missing |
| Estimate | 1w (M) |
| Confidence | Low |
| Linear | PIN-520 ↗ PIN-195 ↗ |
| Linear status | Done · +1 backlog |
| Design | |
| Linear epic | Project Management & Controls |
| Module | Projects ↗ |
Status check: deferred, but shipped work exists
This surface is marked deferred, yet Linear shows PIN-195 as Done. Confirm whether it actually shipped (move the status off deferred) or only the remaining scope is deferred. Flagged for reconciliation.
Priority: High · Route: /projects/:id/detail?tab=shares
Scope¶
Share tab within Project Detail documents: a PM multi-selects project files/drawings and generates a read-only, expiring, login-free link to send to outside vendors, reusing the existing bid-acceptance share-link mechanism. September rollout, not part of the July pilot. (Source: PIN-520, PIN-195.)
Acceptance criteria¶
- Multi-select files/drawings from the project document tree, with select-all per folder
- "Generate share link" produces a read-only, expiring, no-login link for the selected set
- Preview selected files before generating the link
- Copy-link / send-to-vendor action
- Reuses the bid-acceptance share-link service (secure, expiring, public read-only)
- Targeted for the September rollout, outside the July pilot scope
Conor's comments¶
re-model - area-scoped grants, not a bid-style share link. All links tie into main external shares module
Notes¶
Reuse PIN-195 share link
Open question for Conor¶
- Design canon MISSING — no
.dc.htmlmaps to this page. Confirm the design source: reuse an existing module export, or schedule a dedicated design pass? (F2) Confirm which project files/drawings vendors should and should not see (reuse PIN-195 share link)