Skip to content
Peak Atlas

Peak Automations · Security and permissions

An automation may never do more than you.
Risky steps wait for approval.

Every automation runs with the workspace's rights and only through connections a person made there. Before every step Peak checks workspace and role. Risky steps, such as an email going out, wait for a confirmation or an owner or admin approval in the Inbox.

Set up automations with approvals

Illustrative example · sample data · nothing is run

EXAMPLE / LIVE PREVIEW

One check.
The fitting step.

Peak Automations / Sample flowLOCAL EXAMPLE

01 / Example value

How risky is this step?

02 / What Peak Automations showsSend an email through Gmail to a customer.

Waits for approval in the Inbox · only then sent

Change the example value. The next step follows the check.
Sample data · nothing runs

One example. Two paths.
The check
decides the next step.Compare both paths below ↓

Two example steps

How risky is this step?

Schematic scale from 0 to 10 for illustration. In the product the automation sets per step whether it needs approval.

8/ 10Outbound
Waits for approvalEXAMPLE PATH
Send an email through Gmail to a customer.
Then

Add a note to the team's Peak Inbox.

Waits for approval in the Inbox · only then sent

2/ 10Internal
Runs straight awayEXAMPLE PATH
Add a note to the team's Peak Inbox.

Runs without approval · shows in the history

Trust needs clarity

What the protection does, and what it does not.

01 / The existing evidence

An example, not proof

The steps on this page are made up. This page names no certification.

Peak Automations / Example pathsEXAMPLE
  1. 8/10
    Send an email through Gmail to a customer.Waits for approval in the Inbox · only then sent
  2. 2/10
    Add a note to the team's Peak Inbox.Runs without approval · shows in the history

02 / Your check

No silent connections

Peak connects no account on its own. An automation only uses your workspace's connections.

4 / 1010 / 10

Compare both paths and their reasons.

03 / The clear limit

Live only after a test

Without a passed test of the current version no automation goes live, not even with admin rights.

ExampleNothing runs

The next step

Automate within clear limits.

Start Peak Automations and see which steps of your first automation need approval.

Set up automations with approvals
Peak Automations · Security and permissionsWhose account?

Illustrative example · sample data · nothing is run

Frequently asked questions

Does Peak connect accounts on its own?

No. A person connects accounts in Settings › Integrations. Automations only use those connections.

Which steps need approval?

Risky steps, such as an outbound email, wait for a confirmation or an owner or admin approval in the Inbox.

Can an automation go live without a test?

No. Only the current version goes live, after a passed test.

More in Peak Automations