01 / The existing evidence
No roles of its own
Peak Command creates no roles and extends no permissions. There is no way around the source.
Path
- Read
- Built in Peak One
- Shown in Command
- Not checked here
Peak Command · permissions and approvals
You see what you may see.
Permissions come from the source product.
Peak Command has no permission system of its own. It takes over the permissions of Peak One: whoever may not see figures in Peak Finance does not see them in Peak Command either.
Sign in to Peak CommandBuilt in Peak One · example with fictional roles
Peak One permissionsPermission in the sourcePeak CommandVisibility in CommandPeak Command · Example path
One mapping in detail
01 / Peak One permissionsFinance: no access
02 / Fictional test valueExample: not visible
03 / Peak Command
Finance scenariosA readable path as an example. Peak Command reads, it does not copy.
View all 5 mappings
| Peak One permissions | Line in Peak Command |
|---|---|
| Finance: no access | Finance scenarios |
| Goals: read | Goals |
| Year: edit | Create initiative |
| Log: write | Record decision |
| Approval required | Status |
Read path
Nothing transferred here
Nothing transferred here
Nothing is connected on this page. In Peak One, Peak Command reads the products you are allowed to see.
One concrete linePeak CommandLine in Peak CommandRead only
Read the source. Show where it came from.
Peak CommandLine in Peak CommandRead onlyThe path shows where a line in Peak Command comes from. The values are fictional. In Peak One you see your own.
02 / How permissions apply
Read. Write. Approve.
Reading follows the source's permissions. Writing goes through the owning product. Approvals exist where the owning product has them.
- 01 / Read
Read
What you may see in Peak Goals, Peak Year or Peak Finance, you also see in Peak Command.
As in the source.GoalsInitiativesFinance - 02 / Write
Write
A decision goes to Peak Log, an initiative to Peak Year, a task to Peak Work, each with the permissions there.
Through the product.Peak LogPeak YearPeak Work - 03 / Approve
Approve
Where the owning product requires approval, it runs through Peak One's approval engine, not through Peak Command.
Where the source wants it.Approval enginePermitted personRecord
Trust needs clarity
What Peak Command does not do.
Path02 / Your check
No approvals of its own
Approvals exist only where the owning product has them. Peak Command invents no extra ones.
- Account
- Peak One sign-in
- Permissions
- From the source product
03 / The clear limit
Example roles
The roles on this page are fictional. Your organisation sets your permissions in Peak One.
- Adapter
- Webhook
- Embed
- Planned
The next step
Check it with your own account.
Sign in to Peak One. Peak Command shows you exactly what your permissions in the source products allow.
Sign in to Peak Command→In Peak One you see which source stands behind every line.
Frequently asked questions
Does Peak Command have roles of its own?
No. It takes over the permissions of Peak One. What you may not see in the source product, you do not see in Peak Command either.
Where do approvals run?
In Peak One's approval engine, and only where the owning product requires approval. Peak Command invents none of its own.
Can a member change more through Command than in the product?
No. Writes go through the owning product, with the permissions there.
Does Peak Command store data of its own?
No. Peak Command owns no data. It reads the Peak products with your permissions and writes only through the owning product, such as decisions in Peak Log.