What users may upload
SAML, OIDC, HAR, metadata, certificates, Windows/AD/Kerberos/LDAP notes, application errors, and mixed access evidence.
Security and evidence handling
Built for sensitive access troubleshooting evidence.
AccessTrace is designed around explicit upload, optional raw-artifact storage, redaction awareness, usage limits, and clear user control.
Core principle
Users choose what to upload.
AccessTrace is not a silent browser or network monitor. Browser traffic analysis starts with an explicit HAR upload.
What users should avoid uploading
Passwords, private keys, full session cookies, unredacted production tokens, and unrelated personal data.
Raw artifact storage
Raw artifact storage is optional. Leave it unchecked unless full evidence retention is deliberately needed.
What AI sees
The AI receives the evidence needed to generate or explain the report. The assistant uses shortened report context and cannot change saved findings.
Cost and abuse controls
Assistant usage is limited by plan and by case. Large analysis submissions can also be capped with environment variables.
Operational guidance
AccessTrace assists troubleshooting and report writing. Teams should confirm findings against authoritative IdP, SP, directory, endpoint, or application logs before making production configuration changes.