Seats and purchases
A seat is a paid place for one person in an AI tool: a Microsoft 365 Copilot licence, a Claude, ChatGPT or OpenAI seat, a GitHub Copilot seat or a Google licence. The Seats tab shows who holds each…
Written By Christopher Scaminaci
Last updated 9 days ago
A seat is a paid place for one person in an AI tool: a Microsoft 365 Copilot licence, a Claude, ChatGPT or OpenAI seat, a GitHub Copilot seat or a Google licence. The Seats tab shows who holds each seat at a client, when they last used it and what it costs. It can propose taking back seats nobody uses. The Purchases tab sets the safety stop on automatic buying and links the client's account at a distributor.
At a glance
- What it does: shows seat holders and cost, proposes removing unused seats, and buys seats through a distributor after approval.
- Plan: Pro and above.
- Who: any role with access to the client can look. An Administrator of your whole organization (or a role given Apply changes for seat changes) changes seat groups. Only an Administrator of your whole organization sets the safety stop, resets it, and links distributor accounts.
- Where: AI Governance → Deploy and manage → Seats and Purchases.
- Needs: for seats, a connection for the platform. For purchases, a connection to the distributor and the client's account there.
Seats
Watch a group
A seat group is the group or licence that gives people a seat. Under Watch a group (Watch another group once one is watched), choose the platform, type the group or licence id, and select Watch the group. For GitHub Copilot, Claude and OpenAI organizations the id is filled in for you: leave the box empty.
Within an hour StackJack has the first reading. For each group the page shows the number of holders, the cost, and each holder.
What the page shows
- Holders show by the name your organization's name policy allows you to see: a real name for a person who may see names, a pseudonym for everyone else, and Removed person when the person's record no longer exists. A holder StackJack could not match to a person shows Not matched to a person. Each holder also shows when they last used the seat, or no activity reading, or never used. The page does not show email addresses.
- A seat kept by the standard is protected from cleanup. A group whose membership is set by a rule is shown, and its seats are never proposed for removal.
- Cost. The page adds up what the seats cost a month, in the currency of the prices. When some prices are not known the page says the real total is higher. A price comes from your latest bought order; before there is one it can come from a price set on the group.
Clean up unused seats
For each group, two switches. Both only propose removals. A person approves them on the Changes tab, with the phrase CHANGE SEATS.
- Remove seats nobody has used for a number of days, from 7 to 180.
- Remove the seats of people the directory disabled.
A seat with no activity reading is never proposed for being idle. Select Keep this seat for 30 days to stop a proposal for one person, and Stop keeping to end it.
If a cleanup would remove more than half of a group, StackJack stops it. That usually means the activity readings are wrong. Read the list, then select Resume cleanup.
Stop watching this group stops StackJack watching. It changes no seat.
Purchases
The safety stop
The safety stop sets how much StackJack may buy by itself. With no limit set, every purchase goes to a person.
- Open Deploy and manage → Purchases.
- Under The purchase safety stop, type Most to buy by itself in whole units of the client's currency, and In this many days.
- Select Save the stop.
A limit that lets StackJack buy more needs the phrase ALLOW AUTOMATIC CHANGES and a sign-in with a second factor. Setting the first limit, raising the limit and shortening the period all count as buying more, because the same amount can be spent again sooner. A smaller limit or a longer period needs neither.
The stop also trips. If a purchase that no person approved would take the spend of the period past the limit, the stop trips and that purchase does not run. While it is tripped, only a person approves a purchase. An Administrator of your whole organization selects Reset the stop to start a new window. StackJack never resets it by itself.
An approval rule can also let StackJack approve purchases within limits. See Approvals and automatic changes. A purchase that is inside the rule but above the safety stop still goes to a person.
Distributor accounts
StackJack buys for a client through the client's own account at a distributor. The page lists Pax8, Sherweb, Crayon, Ingram Micro, TD SYNNEX and Dicker Data. For each, type the client's account id at this distributor and select Save. The page says one of:
- Not linked.
- Linked, not checked yet: the first purchase checks it.
- Linked and found.
- Not found at the distributor: fix the account id.
Microsoft seats can also be bought through Partner Center when the Microsoft partner identity has the Admin Agent role in your partner organization.
Make a purchase
A purchase starts in one of three ways: from a plan that needs more seats than the client holds, from the Ask for a price form on the Purchases page, or from your AI tools (aigov_propose_purchase). The form and the tool take the same road. On the form, choose the distributor (only distributors where the client has a linked account are listed), type the offer id from the distributor's catalog, the term in months, how it is billed and the number of seats, then select Ask for the price. For Ingram Micro, also type the vendor name of the offer, because an Ingram Micro Cloud Marketplace offer belongs to one vendor (the tool takes it as vendor). You need the right to request purchases at the client. StackJack asks the distributor for the price and shows the seats, the term, the price per seat and the total, with the currency. Every purchase needs a decision. A person approves it with the phrase BUY SEATS. Approving a change in seats uses CHANGE SEATS.
StackJack checks the price again when it orders. If the price, the seats or the term changed after you approved, nothing is ordered. Plan again and approve the new numbers. StackJack never sends an order twice. If it cannot see the answer to an order, it says so and tells you to look at the distributor's console before you plan again.
Open a purchase run to read its quote. Purchases lists every purchase plan for the client, newest first.
Common messages
- "This client has no account link at the distributor." Add the link on the Purchases tab, then plan again.
- "The distributor does not know the account id saved for this client." Fix the account id and save the link again.
- "The distributor gave no price for this offer." StackJack cannot plan the purchase. Check the offer and the client's market.
- "The purchase safety stop for this client has tripped." An Administrator resets it on the Purchases tab.
- "Purchases are switched off on this platform." Contact StackJack support.
Was this helpful?
More in For MSPs
All clientsClient organizationsClient administrators and auditorsSources for a client organizationStill need help? Ask the team