NEEDS REVIEW Add access conflict trigger to automation triggers reference

[c1-dev-bot]

Summary

• Adds the "Access conflict" trigger type to the automation triggers reference page
• Documents all available context fields including new enriched fields (monitor name, user info, violation details)
• Adds the trigger to the subject user summary table

This documentation supports the access conflict trigger feature being GA'd for customers with the Advanced Compliance SKU.

Test plan

• Verify the new section renders correctly in the docs site
• Verify all field names match the implementation
• Verify links to related pages work

Fixes: IGA-1271

---

Automated PR Notice

This PR was automatically created by c1-dev-bot as a potential implementation.

This code requires:

• Human review of the implementation approach
• Manual testing to verify correctness
• Approval from the appropriate team before merging

[linear]

IGA-1271 Native Jira integration for access conflict monitor findings

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
conductorone	🟢 Ready	View Preview	Apr 4, 2026, 1:09 AM

[mindymo]

@rtfc1 I don't know if this is another "the bot wrote the docs for code that doesn't exist yet" ... maybe partly?

[rtfc1]

@mindymo Partly? Maybe this is the work to implement? https://github.com/ductone/c1/pull/15952

But I have a spec to do it here: https://www.notion.so/conductorone/Spec-Automation-Trigger-Conflict-Monitor-3344694ad84681f8a0a7e7503498421c ... Hold until someone can review the actual Eng PR. But the docs seem aligned to the spec. I wonder if it found the Notion spec and wrote it partially based on those details?