Client portal app prompt with project approvals

Build a client portal for [BUSINESS TYPE] serving [CLIENT TYPE]. The portal's main job is to help a client understand project status and approve or request changes to a deliverable without hunting through email.

Define the data model and permissions first: organizations, users, projects, milestones, deliverables, files, comments, and approval events. Use three roles: client, team member, and admin. Describe which records each role can read and change.

Build these flows:
1. Client dashboard showing only that client's projects, next milestone, recent update, and pending decisions.
2. Project detail with a clear timeline, deliverables, files, discussion thread, and named owner.
3. Approval action that records who approved what version and when; a request-changes action must capture actionable feedback.
4. Team workspace to publish updates, upload a new deliverable version, respond to comments, and see unresolved decisions.
5. Account settings with notification preferences and a clear sign-out path.

Security and reliability:
- Enforce tenant and role access at the server or database layer, not only in the UI. Test direct URLs, file links, and API requests with two unrelated client accounts.
- Use private file storage and time-limited access where appropriate. Validate file type and size and never expose storage credentials in client code.
- Preserve an audit history of approval and version changes. Do not rewrite an earlier approval when a new file version is uploaded.
- Send email only if a real notification service is configured; otherwise label notifications as pending integration.
- Show useful empty, loading, permission-denied, and upload-failure states. Use fictional client and project data clearly marked as sample.

Visual direction: [VISUAL DIRECTION]. Keep project status and pending decisions easy to scan on mobile. Finish with a two-client access test, an approval-version test, and a list of integrations required before production use.