Shipped. Autotask keys this on the resource id rather than a UPN, so that's the value to store. Each person sets their own Autotask resource id on Connectors (the My Autotask identity card once Autotask is connected), or an administrator sets it for them from Team, and StackJack records tickets, notes and time entries as that person instead of the API user. A client-ID connection isn't a person, so on that path the AI passes impersonationResourceId on the call. The Autotask-side setup (the API user's security level must allow impersonation, and the resources must allow being impersonated) is in the docs: https://docs.stackjack.io/docs/connectors/autotask
Log in to comment and vote
Comments2
Christopher Scaminaci
Sep 8
Shipped. Autotask keys this on the resource id rather than a UPN, so that's the value to store. Each person sets their own Autotask resource id on Connectors (the My Autotask identity card once Autotask is connected), or an administrator sets it for them from Team, and StackJack records tickets, notes and time entries as that person instead of the API user. A client-ID connection isn't a person, so on that path the AI passes impersonationResourceId on the call. The Autotask-side setup (the API user's security level must allow impersonation, and the resources must allow being impersonated) is in the docs: https://docs.stackjack.io/docs/connectors/autotask
Gold ZeroG
Aug 23
ImpersonationResourceId is the key.