Skip to main content
Control and respond

Making changes in your AI vendor accounts

AI Governance can do more than read your Anthropic, OpenAI and GitHub Copilot accounts: with your approval, it can make a change in them. Remove a person who has left, turn off a key that leaked, set…

Written By Christopher Scaminaci

Last updated 16 days ago

AI Governance can do more than read your Anthropic, OpenAI and GitHub Copilot accounts: with your approval, it can make a change in them. Remove a person who has left, turn off a key that leaked, set a spend limit, cancel a Copilot seat. It is the same set of vendor connections you already added on the Connectors page, and StackJack's own tools on those connections still only read.

At a glance

  • What it does: lets you propose a change in an AI vendor account and approve it in StackJack.
  • Plan: Business and above.
  • Who: an Administrator.
  • Where: AI Governance → AI inventory → Vendor changes. You turn the feature on for each connection.

Nothing happens by itself. An administrator turns the ability on for one connection, then approves each change by typing a phrase. StackJack makes the change within a minute and records it.

This needs the Business plan or higher.

What can be changed

VendorChangePhrase to typeWhat happens
AnthropicRemove a userREMOVE USERThe person loses access to your Anthropic organization right away. Anthropic archives their personal API keys.
AnthropicTurn off an API keyDEACTIVATE KEYEverything that uses the key stops working until someone turns it on again in the vendor console. Anthropic has no delete for a key, so StackJack turns it off. Not for a Claude Enterprise connection.
AnthropicSet a person's spend limitSET LIMITOnce the limit is reached, Anthropic blocks further use by that person for the rest of the period. Claude Enterprise only.
AnthropicClear a person's spend limitCLEAR LIMITAnthropic no longer stops that person at a limit. Claude Enterprise only.
OpenAIRemove a userREMOVE USERThe person loses access to your OpenAI organization right away.
OpenAIRemove a user from a projectREMOVE USERThe person loses access to one project (you give the project id).
OpenAIDelete a project API keyDELETE KEYEverything that uses the key stops working, and a deleted key cannot be brought back. The service account it belongs to stays.
OpenAISet the organization's spend limitSET LIMITOnce the monthly limit is reached, OpenAI blocks further use for the rest of the period.
OpenAIClear the organization's spend limitCLEAR LIMITOpenAI no longer stops use at a limit.
OpenAIChange data retentionCHANGE RETENTIONOpenAI changes how long it keeps your data. You choose one of the four retention types OpenAI offers. Check what your agreement with OpenAI allows first.
GitHub CopilotCancel a Copilot seatCANCEL SEATThe person loses their Copilot seat (you give their GitHub login). GitHub bills seats.

A person is found in the vendor account by the email addresses StackJack holds for that staff member. The page says "The account whose email matches" and the person's label, and never shows the email. If no account matches, nothing is changed.

Block a domain in your security product

Three more changes block a web app's domain in the product you use to filter DNS or web traffic: Block a domain in DNSFilter (a policy), Cloudflare (a Gateway list) or Cisco Umbrella (a destination list), each with a matching Unblock a domain. The phrases are BLOCK DOMAIN and UNBLOCK DOMAIN, and they need the Business plan. They do not appear in the Make a change dialog: you start them with Apply fix on an AI tool, and the place the block goes is the one you chose on Fix settings. An undo always uses the list the block used. See From finding to ticket, decision and fix.

The four changes that are not offered

The Vendor changes page lists these so you do not look for them:

  • Anthropic workspace spend limit. Anthropic offers no way to do it through its API. Set it in the Claude Console.
  • Anthropic key delete. Anthropic offers no delete for a key. StackJack turns the key off instead.
  • OpenAI project spend limit. OpenAI's published reference does not document it. Set it in the OpenAI platform.
  • GitHub enterprise seats. GitHub offers no seat removal for an enterprise account. Remove the seat in the organization that assigned it.

What the key StackJack holds must be allowed to do

StackJack makes the change with the key you gave it on the Connectors page. The vendor must allow that key to make the change:

  • Anthropic. A Console Admin key can remove users and turn off keys. A Claude Enterprise scoped key needs the write:spend_limits permission to set or clear a spend limit.
  • OpenAI. The organization Admin key needs the matching write permission in the OpenAI platform for each kind of change. A ChatGPT workspace key cannot make any of these changes.
  • GitHub. The token needs the manage_billing:copilot or admin:org permission. An enterprise connection cannot cancel a seat; cancel it in the organization that assigned it.

If the vendor refuses, the change ends as failed with: "The key StackJack holds for this connection may not make this change. Give it write permission in the vendor console and try again."

Turn it on for a connection

  1. Open AI Governance → AI inventory → Vendor changes. You need the governance administrator role.
  2. Under the connections, find the vendor connection. The page tells you which changes work on it. A connection that is switched off on the Connectors page, or whose key StackJack cannot read, shows none.
  3. Type ALLOW CHANGES and select Turn changes on. The row now reads "Changes are on".
  4. To stop, select Turn changes off (nothing to type). A change that was approved and had not yet run then ends as failed with "Vendor changes were turned off for this connection before the change ran."

Each connection has its own switch. An organization with two Anthropic connections turns them on one by one.

Make a change

  1. On Vendor changes, select Make a change. You can also start from an item on the inventory page ("Act in the vendor account") or from a person on the Staff page ("Change vendor accounts...").
  2. Choose the connection and the change, then fill in what the change needs: a person, a key id (the id the vendor shows, never the key itself), a project id, a GitHub login, an amount, or a retention type.
  3. Write a reason of 10 to 500 characters. It is shown to the administrators who approve the change, so do not write a person's name in it.
  4. Read the sentence that says what the change does. Type the phrase from the table, in capital letters.
  5. Select Make this change. The change is approved by your typing the phrase, and StackJack runs it within a minute.

An administrator is the only one who can approve. Any administrator can approve a waiting change, including the one who proposed it.

An assistant can propose a change, never approve one. An AI assistant that is connected to StackJack's tools can propose a change for you. It is then Waiting for approval. Open it on the Vendor changes page, read it, and either type the phrase to approve it or reject it. A change nobody approves lapses after seven days: "Nobody approved it in time, so it lapsed."

Why a change can be refused

A change is refused before anything is written. The page says which of these it was:

  • Vendor changes are switched off by StackJack: "StackJack has switched vendor changes off. Nothing will run."
  • Your plan is below Business.
  • The connection is not found, or it is switched off.
  • Changes are not turned on for that connection.
  • The change does not work on that kind of connection (for example a spend limit on a Console key, or any change on a ChatGPT workspace key).
  • Something in the change is missing or not valid.
  • The reason is shorter than 10 or longer than 500 characters.
  • The connection now reaches a different vendor organization than before. A key can be replaced with one for another organization. StackJack stops and asks an administrator to confirm the new organization on the Identities page first.
  • The phrase is wrong: "Type the phrase exactly as shown, in capital letters."
  • The change was already decided.

StackJack also never changes the key it is using to reach the account: a turn-off or delete of that key ends with "This is the key StackJack uses to reach the account, so it was not changed."

What happens next, and what the result says

The status reads Waiting for approval, Approved, waiting to run, Running, Done, Failed or Rejected. A change that is Done says "Done in the vendor account." or, when the vendor was already in that state, "It was already done." Clearing a limit that was never set says "There was no limit set for this person, so there was nothing to clear."

If the vendor is busy or does not answer, StackJack tries again after 1, 5 and 15 minutes, four tries in all, and then ends with "The vendor did not answer after several tries. Nothing was changed. Make the same change again later." A change that ends Failed raises an alert for your administrators, and the Overview shows how many changes are waiting and how many failed in the last seven days. A failed change says why (the vendor refused it, the person was not found, the key may not make the change). It never changes the vendor account when it fails, and you can make the same change again from the page.

What is recorded

Each step is in the audit trail: who proposed the change, who approved it, when it ran and how it ended. The trail never holds a key, an email address or the reason you wrote. In the vendor's own audit log the request is made with the key you gave StackJack, and StackJack's requests name themselves with the product name "StackJack-AiGovernance" in the user agent, so the vendor's trail can tell them from a person.

Related: Get started with AI Governance, Erasing a person. The connection setup pages are on the Connectors page for Anthropic Admin, OpenAI Admin and GitHub Copilot.