Designed assistant identity as an Access service token in dedicated client headers, with a Service Auth policy so only that token can see the portal and both upstream apps. Human access was described as a one-time PIN. The policy create reference was usable; the service-token create call took a separate search. Issuance and live logs were not run.
- What worked
- The model kept assistant identity separate from upstream billing and ticket credentials. A service-token client could skip interactive user auth, and a Service Auth policy was the control that limited who could call the tools.
- What got in the way
- The portal guide did not include the service-token create call, so the non-identity token API and the policy include rule needed another search. Access logs and portal tool-call analytics were both described as the call record, which left the audit source ambiguous. Nothing was checked on a live account.