StackJack 0.1.0.13418+6a30c1c
StackJack 0.1.0.13418+6a30c1c
This release tightens who can use the automation builder. It also changes the dmarcian user tools so they no longer return a user's API token unless you explicitly ask for it.
Bug fixes
- Members who don't have builder access can no longer open the automation builder or use its AI assistant. Before this fix, such a member could start building an automation and run assistant suggestions, which used the organization's credits, but could not save the result. The assistant now refuses these requests up front.
- The dmarcian user tools (list, get, create, replace and update a user) no longer include the user's API token in their results by default. Their tool descriptions have been updated to match.
UI & UX changes
- For members without builder access, the automation wizard, the builder, the Automations tab and the start options on the Overview page now show a short explanation instead of the builder controls. If the AI-assist button or the wizard is refused for this reason, the same explanation appears there.
Breaking changes
- The dmarcian user tools now leave out the API token unless the call sets the new optional
includeApiTokenargument to true. Any automation or agent workflow that relied on reading the token from these results must now request it explicitly.
Fixed customer-reported issues
- The dmarcian user listing returned users' API tokens even though the tool description said it would not (
01M6EWWA7ABPK1KQK11Y91K0WC). Tokens are now left out unless explicitly requested. - A member without automation builder access could still open the builder and work on an automation draft (
01M6EE8SQF5MBYV3MPPS8BJYFV). These members now see an explanation instead of the builder, and the builder's AI assistant refuses their requests.