External Users (subconsultant/architect project access)¶
| Stage | Backlog |
|---|---|
| Status | Deferred |
| Design status | In progress |
| Estimate | L |
| Confidence | Medium |
| Linear | PIN-263 ↗ PIN-364 ↗ |
| Linear status | Backlog |
| Design | Design ↗ |
| Linear epic | Platform Foundation |
| Module | External Access & Shares ↗ |
Status: Not built · Route: /external/* (planned)
A Procore-style external-user system: a PM invites an architect, subconsultant, or engineer to one specific project with scoped, per-tab access (e.g. Drawings, Submittals, RFIs). External users live in a separate external-directory namespace, never see projects they aren't assigned to, and can be removed at any time.
Scope¶
Procore-style external-user access: a PM invites an architect, subconsultant, or engineer to one specific project with scoped, per-tab permissions; external users sit in a separate external directory, see only their assigned project(s), and can be removed at any time. The MVP slice ships a single read-only "External Subconsultant" role scoped to Drawings, RFIs, and Submittals. (Source: PIN-263, PIN-364.)
Acceptance criteria¶
- PM invites an external user by email from Project Detail → Team, choosing a role (Architect / Engineer / Subconsultant / Owner Rep in the full epic; "External Subconsultant" only in the MVP slice)
- Invitee accepts and lands on a scoped external login, seeing only the project(s) they're assigned to — zero visibility into other projects
- MVP role: read-only access to Drawings, RFIs, and Submittals
- Full epic: per-project role and per-tab visibility independently configurable (e.g. read-only Architect vs. upload-allowed Engineer)
- PM can remove an external user at any time; removal immediately revokes access and invalidates the session
- All external-user actions are audit-logged
- Owner role sees the full external directory; PMs see only external users on their own projects
Notes¶
Entirely unbuilt — Backlog epic with no started child tickets as of 2026-08-25. Distinct from the sibling "portfolio register" page (PIN-520): that mechanism is anonymous, expiring file-share links sent to outside vendors; this is authenticated, ongoing per-project access for named external collaborators. Planned approach reuses the permission-matrix work (PIN-262) for per-project, per-tab permission overrides. PIN-364 (Roles/ Permissions hardening + external-user basics) is the nearest scoped near-term slice toward this.