Skip to content

Documentation

Approvals and temporary access

This guide explains when an action waits for a second person, how to approve or reject it, and how to ask for a higher role for a few hours.

Before you start

  • Everybody can open Approvals from the left menu to follow their own requests.
  • To approve or reject other people's requests you need the Decide approvals permission (the Operator, Engineer and Administrator roles have it) and the permission the action itself needs, on the same hosts or groups.
  • To change the approval policy you need the Security policy permission (Administrator).
  • Words used here: a channel is the way an action reaches LEA Platform, for example the console, an MCP client or Slack.

What needs approval and why

An approval is a second person's yes before an action runs, so that one stolen token, one AI agent or one chat message cannot change your fleet alone.

LEA Platform decides for every action from two things:

  • the channel it comes from, and
  • the risk of the permission it needs: View, Change, Run on hosts (commands, remedies, rule rollouts) or Administer.

For each channel and risk, the approval policy says Allow (run at once), Needs approval (wait for a second person) or Deny (refuse).

ChannelWhat it isViewChangeRun on hostsAdminister
ConsolePeople signed in to the consoleAllowAllowAllowAllow
AI assistantThe built-in assistant; you already confirm each change in the chatAllowAllowAllowAllow
MCP clientAI tools such as Claude Desktop or Open WebUI that use a tokenAllowNeeds approvalNeeds approvalDeny
Personal token, lea CLI, Application, Service accountScripts, the lea command and integrationsAllowAllowAllowAllow
Slack or TeamsButtons and commands in chatAllowNeeds approvalDenyDeny

The table shows the defaults. Handling notifications from Slack or Teams is allowed by default.

Actions that can wait for approval are the ones that change hosts or what runs on them: ad-hoc commands, host actions (activate, deactivate, delete, re-enroll), removing results, group changes, rule changes, assignments, rollouts and rule sources, functions and remediation. Settings, users and tokens never wait for approval; they need the right role and Confirm it is you instead.

Note: A four-eyes permission always needs a second person, also in the console and also for administrators. None is set by default.

When your action is sent for approval

When the policy says Needs approval, nothing runs yet. Instead:

  1. A message Sent for approval appears at the bottom of the page. Click Open request to see it.
  2. Everybody who may decide gets a notification Approval requested.
  3. The request waits on Approvals → My requests with the status PENDING.
  4. When someone decides, you get a notification. If it was approved, the action has already run, as you.

The page where you started may also show the message as an error: the action did not run yet, so nothing changed there.

To withdraw a request, open My requests and click Cancel.

Approve or reject a request

A request waiting for you lists who asked, what they want to do, and on which hosts, groups or rules.

  1. Open Approvals. The number on Approvals in the left menu is how many requests wait for you.
  2. On Waiting for me, click a row to see the details: the permission, the action, the targets and when it expires.
  3. Click Approve or Reject.
  4. Optionally type a Note. For a rejection, say why, so the person can fix it and ask again.
  5. Click Approve or Reject in the dialog. You may be asked to confirm it is you.

You should see: "Approved. The action ran." or "Rejected." The request moves to History.

ColumnWhat it shows
WhatThe action in plain words, and the permission it needs.
Requested byThe person, application or service account that asked; "for …" when an AI tool asked on someone's behalf.
TargetsThe hosts, groups and rules the action works on. Click one to look at it before you decide.
ChannelWhere the request came from: Console, AI assistant, MCP client, Personal token, lea CLI, Application, Service account, or Slack or Teams.
ExpiresWhen the request expires if nobody decides; it then never runs.

Rules for deciding:

  • You cannot approve your own request. For a four-eyes permission you also cannot approve one an AI tool made on your behalf.
  • You only see and decide requests on hosts and groups you have access to, and only when your role includes the permission the action needs.
  • An approved action runs with the requester's access at that moment. If they lost the permission since they asked, it fails with the status FAILED.

Request statuses

The status of a request tells you whether it is still waiting, and what happened.

StatusMeaning
PENDINGWaiting for a second person to approve or reject it.
APPROVEDApproved and starting to run; it changes to DONE or FAILED within seconds.
DONEApproved, and the action ran. The Result in the details shows the answer.
REJECTEDSomeone rejected it; it did not run. Their note says why.
FAILEDApproved, but the action failed, for example because the requester no longer has the permission.
EXPIREDNobody decided in time; it did not run.
CANCELLEDThe requester withdrew it; it did not run.

AI assistant, MCP clients and chat

  • MCP clients: when a write tool needs approval, the tool answers "waiting for approval" with a link to the request in the console. The AI tool can tell you the link; the change runs when someone approves it. Tools the policy denies are not offered to the client at all. Allow write tools in Settings → AI Assistant still turns every write tool off.
  • AI assistant in the console: you keep confirming changes in the chat. If the policy says Needs approval for the AI assistant, your confirmation creates a request for another person instead of running the change.
  • Slack and Teams: an action that needs approval answers with a link to the request. Chat requests expire after 15 minutes.
  • Deciding from Slack and Teams: the Approval requested message in your Slack direct messages or personal Teams chat has Approve and Reject buttons when you may decide the request. The decision is the same as in the console and is recorded in the audit log as made from chat; the message then shows who decided and when. Requests for privileged permissions, requests for temporary access, and every request while the Approvals re-authentication setting is on show Open in LEA instead, because chat cannot confirm your identity. See Approve requests from Slack and Teams.
  • The API (/api): from a channel that needs approval, direct database changes that would skip the approval are refused with "The approval policy requires a second person for this change; use the console or the custom API, which create an approval request".

Request temporary access

Temporary access is a higher role for a few hours, approved by an administrator, that ends by itself.

  1. Open My account → Tokens and access, or click Request temporary access on the Approvals page.
  2. Click Request temporary access.
  3. Pick the Role and, if you only need some host groups, the Scope.
  4. Type the Hours (1 to 24, or less if your administrator set a lower maximum) and a Reason, for example the incident number.
  5. Click Send request.

You should see: "Sent for approval" and the request in the Temporary access table with the status PENDING.

People who manage users and access (the Users and sign-in permission on all hosts, and every permission of the role you ask for) get the request. When one of them approves, you get the role at once; Access ends shows when it stops. Sign out and in again if a page still shows your old access.

Note: Temporary access needs a single sign-on identity. Local accounts and API accounts cannot ask for it.

Set the approval policy

The approval policy decides, per channel and risk, whether actions run at once, wait for approval or are refused.

  1. Open Settings → Security and scroll to Approval policy.
  2. In the table, pick Allow, Needs approval or Deny for each channel and risk.
  3. Under Per-permission overrides, pick a Permission and click Add override to choose a different decision for one permission. Default keeps the decision from the table.
  4. Under Four-eyes permissions, pick permissions that always need a second person, even in the console.
  5. Under Time limits, set Requests expire after (hours) and Temporary access maximum (hours).
  6. Click Save approval policy and confirm it is you.

You should see: "Approval policy saved."

Tip: Set every cell to Allow and remove the overrides and four-eyes permissions to turn approvals off completely.

If something goes wrong

  • "Sent for approval" after an action: the policy requires a second person. Follow the request on My requests.
  • "The approval policy does not allow this action from this channel": the policy says Deny for this channel. Use the console, or ask an administrator to change the policy.
  • "The approval policy requires a second person for this change…": an API call tried to change data directly through /api from a channel that needs approval. Use the console or the matching /lea/… API action, which creates a request.
  • You see no Approve button: it is your own request, the targets are outside your host groups, or your role does not include the permission the action needs.
  • Approved, but FAILED: open the request and read Result. Often the requester lost the permission, or the host or rule changed in the meantime. They can ask again.
  • The request EXPIRED: nobody decided in time. Ask again, and tell an approver.
  • Temporary access ends too early or is refused: the hours are above the maximum in the policy, or you asked for a role you already have everywhere.