A customer portal, from the customer's point of view.

A customer accepts an invitation tied to an approved relationship. Signing in does not grant access to other organizations, even if they use a similar email domain.

The home view shows project status and documents deliberately shared with that account. Internal estimates and working notes remain outside the customer view.

The customer sends a request with project context. The interface distinguishes receipt from a completed response, and shows a useful reference.

Expired invitations, removed access and unavailable services need clear messages. A real implementation would test these boundaries against the chosen systems.

Use these design decisions to define your own portal. Agree the integrations, access rules and acceptance criteria before development begins.