Skip to main content
For MSPs

Approvals and automatic changes

Every change that deploy and manage makes at a client is approved first. By default, a person approves everything. This page shows the inbox where those decisions wait, and how an Administrator can…

Written By Christopher Scaminaci

Last updated 7 days ago

Every change that deploy and manage makes at a client is approved first. By default, a person approves everything. This page shows the inbox where those decisions wait, and how an Administrator can let StackJack approve small changes, or hand a decision to one of your own automations, while a person stays in charge of the rest.

At a glance

  • What it does: shows the changes that wait for a decision, and sets who decides each kind of change.
  • Plan: Pro and above.
  • Who: a person with access to the client decides in the Changes tab. Only an Administrator of your whole organization writes approval rules and client access.
  • Where: AI Governance → Deploy and manage → Changes and Approval rules.
  • Needs: a sign-in that used a second factor, to approve or to widen a rule.

The Changes tab

Changes lists every step that waits for a decision, across the clients you can see, grouped by run. Each group shows the client, the kind of change, and each step with what the client holds now and what it will be, in words, who decides it now, and the cost of a purchase with its currency. In the menu, Changes carries the number of runs that wait for a decision you may see.

  • To approve the group, type the run's phrase and select Approve these and the number of steps. The phrases are in Deploy a standard to a client.
  • To refuse the group, select Reject them. Nothing is changed.
  • To skip one step with a reason, or to read the whole plan first, select Open the run to skip one step. On the run, the skip is in the menu at the end of the step's row. See Deploy a standard to a client.

You only see the steps your role may decide. A step of another client is not listed.

Who may approve a step

A person approves a step when they hold Approve changes up to a limit at the client, or Apply changes on a run they planned themselves. The size of the change must fit inside the limits of their access. An Administrator of your whole organization has no limit.

A person's approval always needs the run's phrase and a sign-in with a second factor.

Approval rules

On Deploy and manage → Approval rules, an Administrator sets how each kind of change is approved. The kinds are Applying a standard, Settings changes, Drift fixes, Seat changes, Purchases and Turning enforcement on or off.

For each kind, choose how it is approved:

ChoiceWhat happens
A person approvesThe step waits for a person. This is the default when there is no rule.
StackJack approves within the limits you setStackJack approves a step that fits every limit. A step above a limit waits for a person.
An automation decidesStackJack hands the step to the automation you name. If it does not decide in time, a person decides.

A rule applies to Every client, to Only the client you picked, or to One standard. Choose One standard, then pick the standard from the list: the rule then covers every client that runs that standard. A rule for one client wins over a rule for a standard, and a rule for a standard wins over the rule for every client. With none of them, a person approves. A rule for a standard needs the same phrase and the same second factor as any other rule that widens what happens without a person.

The limits

Limits only apply when StackJack or an automation decides. Leave a box empty for no limit on that.

  • Most seats in one change.
  • Most money in one change and Most money in a month. Money counts the whole commitment: seats times price times the months of the term. The amount is in whole units of the client's currency.
  • Terms allowed, in months, for example 1,12. A purchase on another term waits for a person.

Widening a rule needs a phrase

Turning on an automatic choice, raising a limit, naming another automation, or removing a rule so that a wider automatic rule applies, are widening changes. Each needs two things:

  1. The phrase ALLOW AUTOMATIC CHANGES, typed exactly.
  2. A sign-in that used a second factor.

Narrowing a rule needs neither. Only an Administrator of your whole organization can write rules. A role limited to one client never can.

Every automatic approval is recorded

When StackJack or an automation approves a step, StackJack writes one entry in the audit trail that names the rule or the automation, and raises a notice. The run page says Approved by the approval policy or Approved by an automation next to the step.

Hand a decision to an automation

You can let one of your own automations decide the steps of a kind of change. For example, an automation can check a change against your ticket system and approve it when a ticket exists.

For this to work:

  • The automation has a webhook trigger, is switched on, and is set to receive the data its trigger sends. The Approval rules page tells you when it is not.
  • Your organization is enrolled in automations. If not, enroll on the Automations page first.
  • An Administrator names the automation in an approval rule, with the number of minutes before a person decides. The time is from 5 minutes to 24 hours. A new rule starts at 60.

What happens:

  1. When a step reaches the automation, StackJack sends the automation one event. It names the run, the step and the client, the kind of change, the seats and the cost with its currency, and the deadline. It sends the event at most one time.
  2. The automation reads the waiting changes and decides. It decides with aigov_decide_pending_change. It can use only three AI Governance tools: aigov_list_pending_changes, aigov_get_deploy_run and aigov_decide_pending_change.
  3. The automation can decide only the steps handed to it, in the clients the rule covers, and only while the rule still names it. It types no phrase. A change to the rule takes effect on the next request.
    • To decide well, the automation can read facts about the change. When it reads the run with aigov_get_deploy_run, the answer also holds a context: the standard the run comes from (its name, version and settings), the client's seat usage and cost (counts and money, never a person), and the client's earlier runs of the kinds of change the rule names. The context is limited to that client and to those kinds of change, and it exists only while a step waits for the automation. The answer lists only the steps handed to the automation, in a read and in the answer to its own decision, and it never includes the proof of the run. Every other AI Governance read still refuses an automation.
  4. If the automation does not decide before the deadline, or the event could not be delivered, a person decides. The Changes tab shows the deadline, and the step shows Waiting for the automation to decide until the time.

An automation can never widen a rule, and it cannot decide a step in a client the rule does not cover.

What each client role may do

A role limited to one client can do nothing in deploy and manage until an Administrator gives it access. Open Approval rules, and under What each person may do choose the person, the kind of change and what they may do:

ChoiceWhat the person can do
View onlyRead the plans, runs and results.
Request changesPlan, and send a plan for approval.
Apply changesRequest, and approve a run they planned themselves.
Approve changes up to a limitApprove steps that fit the limits of the access.

For Turning enforcement on or off, the choices are View only and Apply changes. Select Give access. Select Take access away to remove it.

A client role can never raise its own limit, change an approval rule, or reach another client. An Administrator of your whole organization holds every right at every client, and a Reviewer, Reveal approver or Auditor of the whole organization can only look.

Messages you may see

  • "You do not have permission to do this for this client." Ask an Administrator to give your role access, or ask one to do it.
  • "This change is bigger than the limit set for your role." Ask an Administrator to approve it, or make a smaller change.
  • "The words you typed do not match." Type the phrase exactly as shown, in capital letters.
  • "This change needs a sign-in that used a second factor." Sign in again with your second factor.
  • "Someone else decided this change first." Reload to see the result.