Skip to content
Olympusx AIOlympusx AIOlympusx AI documentation

Actions and approvals

Security recommends and an admin acts. When an investigation of the audit log finds an Olympusx AI account being misused, its verdict may propose an action: disable that account. The proposal waits on the investigation’s page until an admin approves or rejects it. Approving disables the account exactly as Govern › Users does. Code findings are for people to read, dismiss or export; your developers make any change in the repository.

Who can do what

Section titled “Who can do what”
Role What they can do
Admin Approve (this needs the right to manage people) or reject a proposed action.
Auditor See proposed actions and their decisions.
Builder, End user, Reviewer Cannot open the Investigations tab.

When an action is proposed

Section titled “When an action is proposed”
  • Only an investigation of the Olympusx AI audit log proposes actions, because they act on Olympusx AI accounts. Investigations of your own log stores do not.
  • The action a verdict can propose is disable an account, which an admin runs after approving it.
  • A verdict proposes at most 3. The model is told to propose one only when the events show the account being misused.
  • Olympusx AI keeps a proposal only when the account is an email address and at least one cited event, shown to the model, was performed by that account. Other proposals are dropped.

Decide on a proposal

Section titled “Decide on a proposal”
  1. Open Use cases › Security, select the Investigations tab, and open the investigation.
  2. Under What it proposes a person do, read the proposal: Disable the account email, the reason, and Events ids it rests on. Check those events in the investigation’s rounds or on Audit.
  3. Select Approve and disable, or Reject.
Status Meaning
Waiting for a decision Nobody has decided yet.
Approved by who**: the account is disabled** The account was disabled in the tenant.
Rejected by who Nothing was done.
Not done: why The approval could not be carried out; the reason says why.

A proposal is decided once. Approving refuses an account that is your own, and fails with no account with that email in this tenant when the account no longer exists. Disabling an account stops it signing in. It does not revoke keys: revoke the account’s developer keys, and any application key it may have handled, on Keys and budgets.

Every decision is recorded in the audit log: the approval or rejection, and, for an approval, the account’s disabling, with the action that caused it. To enable the account again, use Users and roles.

Section titled “Related”