NobleCloak
Use cases

Super Admin grants need approval

Author

Audrey

NobleCloak's AI Correspondent · AI-drafted, fact-checked against our sourced evidence before publishing.

Date Published

The IT help desk is one of the most natural places to put an AI agent. The requests are frequent, repetitive, and well understood: a locked account, a lost phone, an MFA factor that needs resetting. An agent connected to the identity provider can handle many of them without a person touching the ticket.

The same connection can also reach tools that are nothing like a password reset. Adding someone to the Super Admin group in the identity provider is a different order of action. It hands over the keys to everything behind single sign-on.

The problem in IT's terms

The IT lead wants the help desk agent to be fast on the routine work and careful on the work that changes who holds authority. Two failure modes worry them.

  • A user, or an email the agent reads, persuades it that a Super Admin grant is a reasonable request.
  • A well-meaning agent with a broad tool set simply has the grant tool available and uses it.

An instruction in the agent's prompt is not a control for either. The control needs to sit on the tool.

The policy

Policy is written per tool: the action, who it applies to, and one of three decisions (allowed, needs approval, denied). Role-scoped policy decides who gets each tool at all.

Action

Who

Decision

Reset an MFA factor in the identity provider

Help desk agent

Allowed

Add a user to the Super Admin group

IT Ops role

Needs approval

Add a user to the Super Admin group

Everyone else

Denied

The first line keeps the help desk quick. The second and third together are the scenario. Only the IT Ops role can see the grant tool at all; assistants for other roles never have it listed. And even for IT Ops, a grant does not simply happen. It waits for a decision.

Who approves, and where

The approval request is routed to a named approver or role, such as a security lead or the IT Ops group. They answer in Slack or the web inbox. The call waits for the answer and then proceeds or stops.

Teams choose the approver deliberately. The person who holds authority over administrator membership is the person to ask, and naming that role in policy means the request does not depend on someone remembering whom to message. The web inbox is there for the case where the approver is not in chat.

What the Record of Decisions shows

Every decision is written to the Record of Decisions: who asked, which agent, which tool, the decision, who approved, and when. For administrator grants that produces the view an access review needs.

  • Every Super Admin grant an agent proposed, and who approved or denied it.
  • The grant tool is listed only for IT Ops, so its entries come from IT Ops sessions.
  • The routine resets alongside, so the team can see that the agent's volume sits on the allowed side.

Teams that run periodic access reviews often rebuild this from screenshots and ticket comments. Here the entries were written as each decision was made, so the review starts from the record instead of from a reconstruction.

Treat it as the working record of what policy decided. The identity provider's own system log remains the record of what the identity provider did.

What this does not do. It does not decide whether a particular person should be an administrator. The approver does. NobleCloak routes the question to the right role, waits for the answer, and keeps the result.

Related scenarios

Get started and set role and approval lines on your identity tools.