Approvals: nothing risky goes out without a yes
Every tool call an agent makes is checked against its charter and your approval rules before it runs. Risky calls wait for the right people to approve the exact details: in the app, through the link in every approval email, or in Slack.
Risk tiers decide the default
Every tool carries a risk tier. When an agent's charter grants a tool, the tier sets how it starts: Auto for tiers 0 to 2, Ask first for tiers 3 and 4. You can switch a tool between Auto and Ask first in the charter, except that tier 4 is never Auto, and set any tool to Never.
- Tier 0ReadLook things up. No side effects.
- Tier 1InternalWrite to Everdeck's own records or notify your people.
- Tier 2ReversibleChange something outside that one step can undo.
- Tier 3ExternalAnything a customer or the public sees.
- Tier 4Money or irreversiblePayments, deletions, permission changes. Always a person.
Approval rules
On the Policies page, a company admin writes rules that say which calls need approval and who approves them. The first enabled rule that matches decides. Start from the Strict or Balanced preset, or write your own.
- Match on the tool, the app, a minimum risk tier, the agent asking, and conditions on the details, such as an amount over a limit, a recipient at a particular domain, or a recipient not on a list.
- Chains of up to 5 steps. Each step asks a specific person, people with a role, a specific agent, the requester's manager or whoever asked for the task.
- A step can need any one of its approvers, all of them or a number of them.
- Each step waits from 5 minutes to 30 days, then moves to the next step or denies the request. The last step always denies: a timeout never approves anything.
Safeguards no rule can switch off
Some protections sit underneath every charter and rule.
- Tier 4 actions, such as payments, deletions and permission changes, always need a person's approval. People decide them only in the web app, after confirming it's them with their second factor.
- Once an agent has read outside content, such as a customer's email, its tier 3 and 4 actions need a person by default for the rest of that session. Only an account owner or admin can let a reviewer agent approve tier 3 instead.
- Nobody approves their own request, person or agent.
- An approval covers the exact details shown. If someone edits them, the approval starts again so every step approves exactly what runs.
Deciding
Requests wait on the Approvals page under Waiting for me, All pending and History. Approve, Edit and approve, Request changes or Reject. Every decision goes in the audit log.
- Every approval request also comes by email, with a link to the exact details.
- In Slack, linked approvers can approve or reject agents' requests with buttons, up to the tier you choose on the Chat approvals page (tier 3 unless you change it). Tier 4 requests are never decided in Slack.
- In Microsoft Teams, a channel gets a notice for each request, with a link to decide in Everdeck.
See the tiers on every integration
Each integration's page lists its actions by how they run: on their own, asking first or always asking a person.
Your company, always on deck.
Start a 14-day trial. Card first, nothing charged until day 14.