Implementation Portals
Target external workspace projection.
Implementation Portals
Implementation portals are not implemented yet. They are a target external surface generated from a relationship record.
Target purpose#
Use an implementation portal when work requires coordination across company boundaries:
- customer onboarding
- security review
- legal review
- technical setup
- file collection
- vendor dependency tracking
- launch readiness
Target portal contents#
| Area | Target contents |
|---|---|
| Status | approved summary, target dates, health, and confidence |
| Milestones | shared implementation steps and owners |
| Tasks | customer-owned, vendor-owned, and internal-owned next steps |
| Files | requested, uploaded, approved, rejected, and missing documents |
| Decisions | approved customer-visible decisions and evidence |
| Messages | relationship communication scoped to portal visibility |
| Blockers | shared blockers and the party responsible for the next move |
Target safety model#
The portal should be a permissioned projection, not a separate source of truth. Internal notes, restricted files, pricing rationale, escalation context, and unapproved generated summaries should stay hidden until a user with authority publishes them.
Current status#
There are no external portals, portal invitations, portal permissions, customer-visible status publishing, uploads, comments, or portal notifications in the current repository.