USE AVERIL

Working with cases

Every case lives in one Slack thread. This page covers the buttons, who can press them, and how a case ends.

One thread per case

Averil posts each case once, in your case channel. The top message says what happened, how severe it is, how confident Averil is, and the evidence behind each claim. As the case moves, Averil updates that message and replies in the thread, so the channel stays readable.

ButtonWhat it does
Approve planApproves the exact steps shown. Only people on your approver list.
RejectRejects the plan. Nothing runs.
AssignMakes you the owner of the case.
It was intendedCloses the case as a deliberate change.
Accept riskOpens the Averil console, where you give a reason and an end date.
Open caseOpens the case in the Averil console.

Approving the exact action

A plan lists each step, its target and the outcome Averil expects. It also shows a short action hash. Your approval is bound to exactly those steps. If anything changes, the plan needs a new approval.

  • Low and medium-risk plans can be approved from Slack by one person on your approver list.
  • High-risk plans show no buttons. An admin approves them in the Averil console with a passkey. A change that can't be undone needs two different people, each with a passkey. Nobody can approve their own request.
  • Right before each step, the executor checks your policy again and confirms the hash. Then it runs the step and reads back the result.
Fixes can be pausedYou can pause all fixes, turn off an action, or protect a target such as a production repository. A refused plan stays on the case with the reason, and the approval is not used up.

Answering Averil's questions

When an investigation needs something only a person knows, the question appears in the case thread. Reply in the thread and mention @Averil. Without the mention, Slack does not send your reply to Averil. Your answer goes on the case, and the investigation picks up again with it.

Accepting a risk

Sometimes the right call is to live with a problem for now. Accepting a risk needs a person (never a model), a reason, and an end date in the future, at most one year away. When the date comes, the case is due for another look.

Dismissing and reopening

  • It was intended closes the case as confirmed intended. If the same thing happens again within 30 days, Averil attaches it to this case without posting, unless it is more serious.
  • Any other dismissal needs a reason, which stays on the case.
  • A closed case can reopen with a reason. It starts a new version, and the earlier outcome stays in the history. Reopens count toward the 30-day reopen rate.
Early accessAccepting risk, dismissing and reopening from the console are being rolled out to design partners. Until they are on for you, the founders do them with you.

Who can do what

RoleCan
ViewerRead cases, dashboards and the action log
MemberComment, confirm ownership, ask Averil, approve low-risk actions on resources they own
ResponderAssign, dismiss, accept risk, reopen, export cases, approve low and medium-risk actions
AdminManage integrations, policies and playbooks, approve high and critical-risk actions
OwnerBilling, autonomy levels, members and deleting the account

Stuck? Email averil@averil.ai or ask me in Slack.

Start with a free
security check

Connect GitHub and your cloud, and I'll send you a short list of what to fix, in Slack.

Get a free security checkSee pricing