Skip to main content

Changelog

Follow new updates and improvements to StackJack.io.

StackJack 0.1.0.15636+cd1197a

StackJack 0.1.0.15636+cd1197a

This release fixes deleting computers and policies through the ThreatLocker connector, adds the ability to delete several of them in one request, and corrects how some ThreatLocker errors are reported.

Improvements

  • The ThreatLocker computer and policy delete tools now accept a list of records, so you can remove several in one request. Deleting a single record by its ID works the same as before.
  • The ThreatLocker delete tools now check your input before sending anything to ThreatLocker. Blank IDs, duplicate IDs, and requests with no records are rejected with a clear message.

Bug fixes

  • Deleting computers or policies through the ThreatLocker connector no longer fails. ThreatLocker had been rejecting these requests as invalid.
  • Some ThreatLocker request errors were wrongly reported as rate-limit errors. They now show the actual error, so you can tell a bad request apart from being throttled.
ImprovedBug Fix

StackJack 0.1.0.15572+6c87d7d

StackJack 0.1.0.15572+6c87d7d

This release makes Microsoft connector setup and consent more reliable, gets SharePoint Admin tools working in customer directories managed through GDAP, and fixes Purview for Canada-region tenants. It also clarifies several AI tool descriptions and improves the message shown when a card is declined during a bundle change.

Improvements

  • Exchange Online and Purview admin consent for customer directories is now a one-click link on the connector cards and in the Set up Microsoft wizard. A short note beside the link explains three things:
  • The consent covers every permission the app lists.
  • A directory that doesn't have one of those services will refuse it.
  • If you use your own app, its registration must include the Exchange management permission.
  • GDAP customers are still directed to Authorize all customers. The setup guides and help text now match this flow.
  • When Microsoft reports a missing consent for Exchange Online or Purview, the guidance now tells you what to check first and points you to the consent link.
  • The Autotask charge-writing tools now tell your AI agent that charges created through the API are recorded under the API user, not the technician who asked.
  • The SharePoint Admin tools for reading and updating SharePoint settings now point your AI agent to the tenant-property tools when working in a customer directory through GDAP. Microsoft doesn't allow the settings tools in that setup.
  • StackJack's support assistant now picks up messages you send in support chat conversations, including conversations with no ticket or a closed ticket.
  • The support assistant can now answer questions about your connectors' own data that use billing-like words, such as Autotask ticket charges or QuickBooks invoices. Previously it declined these questions.

Optimizations

  • SharePoint Admin calls in GDAP-managed customer directories now remember the admin site location between requests. This avoids repeating the lookup on every call.

Bug fixes

  • SharePoint Admin tools that use the SharePoint admin site now work in customer directories accessed through GDAP. Previously they failed in every such directory.
  • When a SharePoint Admin call hits a network problem or throttling, StackJack now reports it as a temporary error you can retry. Previously it showed a misleading sign-in or consent message.
  • Purview connector calls for tenants in the Canada region no longer time out.
  • For connections that use your organization's Microsoft partner app with a certificate, Generate link now produces a consent link for your app instead of StackJack's.
  • While you're adding a new Microsoft connection, the consent link now uses the app details entered in the form instead of the default connection's.
  • While you're adding a Microsoft Graph connection, the card now shows a message if the permission tier isn't known yet, instead of generating a full-permission link.
  • The Autotask stocked-items list tool now names the correct field for filtering by product. Filtering on the wrong field caused errors from Autotask.

UI & UX changes

  • Signing in to a Microsoft connector now always asks you to choose an account. Previously the browser could silently reuse whichever Microsoft account was already signed in.
  • The NinjaOne Region list now shows the host and location for the two US regions, so it's easier to tell them apart. Choosing the wrong one leads to a sign-in error on NinjaOne's side.
  • A passing Test for Exchange Online, SharePoint Admin, Defender, Teams Admin, Purview and Power Platform now says what was actually checked:
  • The sign-in works.
  • The service itself wasn't tested.
  • Each customer directory still needs its own consent and role.
  • If your card is declined during a bundle change, you now see a clear message: nothing was changed, and you should update your payment method and try again. Previously you only saw a generic "please try again".

Fixed customer-reported issues

  • Connecting NinjaOne failed with a region and domain mismatch on NinjaOne's sign-in page (01M7K70QP98HGEASV4RW82V4C2). The Region list now names each US region's host and location, so the correct one is easier to pick.
  • Microsoft consent links failed in customer directories, with unclear results when a directory lacked a required service (01M7DT4XWD0CM9FAGK2VD1FS4P). Exchange Online and Purview now use a one-click consent link, with a note explaining when and why a directory may refuse it.
ImprovedBug Fix

StackJack 0.1.0.15482+639f4bf

StackJack 0.1.0.15482+639f4bf

This release lets each person use their own ConnectWise PSA API keys, adds a way to paste tool names into custom tool roles, and accepts NinjaOne's US2 branded addresses. It also speeds up several pages and fixes a number of smaller issues.

New features

  • Personal ConnectWise PSA API keys. People in your organization can now connect ConnectWise PSA with their own API key pair instead of the organization's shared key. Calls then run with that person's own ConnectWise security role.
  • Under Connectors → Your personal sign-ins, each shared ConnectWise connection has its own card. The card shows whether you are on the shared key, your own keys, or keys that were switched off, and why. You can add, replace, test, or remove your keys there.
  • You only enter the key pair. The site, company, and client ID come from the organization's connection.
  • Keys that ConnectWise rejects are removed right after you save them.
  • Owners and administrators can manage ConnectWise keys for team members. On the Team page, a new ConnectWise API Keys action lets an owner or administrator set keys on a member's behalf for each connection. The primary owner's row does not have this action, because the primary owner uses the organization's connection.
  • Require each person's own ConnectWise API keys. A new organization setting on the Team page blocks ConnectWise changes (writes) that would otherwise go out on the shared key for a person who has no keys of their own. Reads still use the shared key. The refusal message tells the person how to fix it.
  • Experimental ConnectWise member ID option. A new per-connection checkbox on the ConnectWise connection form turns this on. An owner or administrator can then set a person's ConnectWise member ID, so StackJack acts with that member's own security role. Only active owners and administrators can set or clear a member ID.
  • Paste tool names in the custom tool role editor. When choosing specific tools or extra tools for a custom role, you can paste a list of tool names, for example a column copied from a spreadsheet. Names are matched regardless of capitalization and ticked. Names that aren't found are listed. Tools above your plan or not in your catalog are never ticked.

Improvements

  • Changes to the shared ConnectWise connection now carry over to personal keys.
  • If an administrator changes the client ID or the connection's address spelling, the change is applied to everyone's personal keys on that connection.
  • If the connection moves to a different ConnectWise site or company, personal keys are switched off. Each person sees a reason telling them to save their keys again.
  • After saving, the administrator is shown how many people need to save their own keys again.
  • Clearer ConnectWise messages.
  • If your personal key save overlaps with an administrator saving the shared connection, you get a short message asking you to save again in a few seconds.
  • Saving a member ID on a connection that is switched off now shows an error explaining that the connection must be turned on first. Previously it appeared to save but never took effect.
  • Support tickets opened by an AI through a shared key now name the key. A ticket opened through a shared key or an automation with no run-as person is labeled with that key's or automation's name, and says that no person opened it. Previously these tickets named the account owner.
  • AI Governance archiving to your main store. Original raw records are now copied to your organization's main archive store and trimmed like other stored text. They are counted in "Older text still to copy." Extra copies continue not to receive raw records.
  • Sign-in sessions cover the last 90 days. The sign-in sessions list on the connections view and the Team page is now based on the last 90 days of activity. The Team row's call count is labeled accordingly.
  • Activity log connector filter. The filter now offers connectors used in the last 90 days. Enterprise plans also see every subscribed connector. A connector whose only calls are older than 90 days, with no subscription, no longer appears in the filter, though its rows still show when browsing.

Optimizations

  • The Dashboard analytics and the billing page's usage stats now load from a single summarized read, so they load faster for organizations with heavy usage.
  • Reduced the processing and memory overhead of each request to the MCP endpoint.
  • Diagnostics bundles for support are gathered faster.

Bug fixes

  • Deleting an automation with a long run history could time out and leave the automation in place. It now completes.
  • When a tool's guidance was withdrawn, the old guidance text could stay in that tool's description until a restart. It now disappears from the next tool list.
  • During a connector trial, buying the connector on the website or adding it to your bundle in the Portal could be blocked. Purchases during a trial now apply normally, and you keep the paid tier.

Fixed customer-reported issues

  • The NinjaOne connector would not accept a branded address in the US2 region. 01M73SG8N5CWEK071H134T4HAX — The connection form now accepts addresses ending in .rmmservices.net, and its help text lists which ending belongs to which region.

Earlier updates