Evidence should be attached to the decision.
Atomation keeps the source objects, screenshots, affected scope, finding text, and report output connected so teams do not rebuild the story from raw exports.
The trail is the product, not a screenshot gallery.
Okta objects, policy records, group paths, app assignments, logs, and supplied review evidence.
Severity, affected scope, owner context, recommendation, screenshot, and traceable reference.
Executive summary, operator detail, framework lens, evidence appendix, PDF or Markdown report, and supported inventory CSV path.
Use screenshots when they prove the product state.
Real screenshots are useful for showing dashboard shape and evidence context. The marketing story now uses HTML/CSS mockups for concepts and keeps screenshots as proof.
Evidence feeds multiple audiences.
The same source trail can support leadership summaries, operator detail, framework mapping, PDF or Markdown report output, and supported inventory CSV views.
PDF and Markdown outputs for leadership, audit packets, operator review, and internal remediation planning.
CSV export is available on supported filtered inventory views. The active portal does not expose DOCX, raw JSON, or raw snapshot downloads.
Keep screenshots where they add confidence.
Sanitized product screenshots support the evidence trail without overloading every section.
Group-rule dependencies
Visual evidence helps IAM teams review relationships that are easy to miss in exports.
- Cascading rules
- Duplicate conditions
- Assignment paths that need owner review
Licensing signals
When scope includes licensing review, usage signals become evidence for renewal planning.
- Licensed users with no sign-in history
- Usage and assignment signals
- Finance, procurement, IAM, and leadership review
Ask for evidence that survives review.
The finding should include the proof, the reviewer context, and the next practical step.