Draft · not indexed. Part of what this page describes is not generally available yet.
For clients & stakeholders
Clients want to know where you stand. Not everything that happens inside.
Stakeholders need a clear status and one place for decisions. Peak One shares only a released snapshot and records approvals with what they refer to.
Try it
Who sees what in the project?
Sample data · nothing is saved- Milestones and dates✓ visible
- What waits for approval✓ visible
- Released snapshot of results✓ visible
- Internal comments✓ visible
- Hours and rates✓ visible
- Other clients' tasks✓ visible
Clients see only a released snapshot. A client account inside the project is still beta in Peak One.
Interactive demo with invented sample data. No account, nothing is saved or sent.
What your week looks like
Released snapshot (beta)
By link or service portal the client sees exactly the snapshot you share. There is no client account inside the project yet.
Approvals on a fixed version
The Approval Engine is available today and records what was approved.
Peak writes nothing to clients
Nothing leaves the workspace unless you release exactly that snapshot.
An example
What does the client see?
Example: Agentur Nordlicht shares the relaunch status with Nordwind Travel Goods. In the demo you switch between team, client and guest and see which fields each can see. Internal notes stay internal.
Honest limits
No client account in the project
Clients see a snapshot; they don't work inside the project themselves yet.
Client view is beta
Released snapshots by link and the service portal are in beta.
Frequently asked questions
Does the client see internal comments?
No. They see only the snapshot you release.
Does the shared view update itself?
What is shared is a released snapshot. You release a new one deliberately.
Does the client need an account?
Not for a released snapshot by link.