The client portal
The client portal (/portal/{engagementId}) gives the client’s own team a
scoped view of the engagement. It’s a separate surface from the full
application — the client never sees the working model directly.
The screens
Section titled “The screens”- Contribute — upload documents in response to the artifact-request checklist, and mark a contribution session complete.
- Capability heat map — the scored capability model as a visual.
- Deliverables — review deliverables shared for their review, and accept them.
- Recommendations — review recommendations and record sign-off on the ones they commit to.
- AI interview — a guided discovery interview (this one runs locally — the raw text is classified on the deployment and discarded before anything reaches the language model).
Client roles
Section titled “Client roles”| Role | Can |
|---|---|
| Client EA lead | View and act — contribute documents, accept framings, record commitment decisions, and provide one half of the closure sign-off. |
| Client executive sponsor | View only, plus the second half of the dual closure sign-off. |
Access is checked per screen: a client user only sees what their role permits, and the portal renders a view-only or full interface based on that.
Where the portal stands
Section titled “Where the portal stands”The portal is the least-developed part of eavantage today. The essentials — contribute, heat map, deliverable and recommendation review, sign-off — work. The surrounding flows (notifications, clarification threads) are lighter than the rest of the product. If a richer client experience is central to how you’d run engagements, raise it early.