Skip to content

Document access conflict scope type for campaigns#112

Open
c1-dev-bot[bot] wants to merge 2 commits intomainfrom
docs/gov-380-access-conflict-scope-campaigns
Open

Document access conflict scope type for campaigns#112
c1-dev-bot[bot] wants to merge 2 commits intomainfrom
docs/gov-380-access-conflict-scope-campaigns

Conversation

@c1-dev-bot
Copy link
Contributor

@c1-dev-bot c1-dev-bot bot commented Mar 2, 2026

Summary

Documents the new Access conflicts review type for access review campaigns. Users can now scope campaigns by conflict monitors in addition to the existing entitlements-based scoping.

Changes

product/admin/campaigns.mdx:

  • Added Review type field to the campaign creation form (Step 1) for both single campaigns and templates
  • Reorganized Step 3 ("Choose what to review") with tabs for Entitlements and Access conflicts review types
  • Documented the access conflict scope configuration: choosing between All monitors and Specific monitors
  • Added prerequisite note about needing enabled conflict monitors
  • Added two new FAQ entries about review type immutability and monitor timing
  • Updated page description to mention access conflicts
  • Removed a duplicate step in the template section

product/admin/access-conflicts.mdx:

  • Added a "Review access conflicts in a campaign" section with a cross-reference to the campaigns page

Context

This feature adds a new campaign scope type that lets users create access review campaigns focused on separation of duties (SoD) violations detected by conflict monitors, rather than traditional entitlement-based reviews.


Automated PR Notice

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

This documentation requires:

  • Human review for accuracy and completeness
  • Verification that it matches current product behavior
  • Approval from the appropriate team before merging

Add documentation for the new "By Access Conflicts" campaign review type,
which allows users to scope access review campaigns by conflict monitors
instead of entitlements. Updates include:

- New "Review type" field in campaign and template creation forms
- Tabbed scope configuration (Entitlements vs Access conflicts)
- Access conflict scope options (All monitors vs Specific monitors)
- Cross-reference from access conflicts page to campaign integration
- New FAQ entries about review type and conflict monitor behavior
@linear
Copy link

linear bot commented Mar 2, 2026

@jessstarr-hub jessstarr-hub requested review from mindymo March 5, 2026 22:30
@jessstarr-hub
Copy link

@mindymo - I'd like to merge this by noon Friday.

- Swap Steps 2 and 3 so scope comes before configuration (matches in-app workflow)
- Remove Review type field from Step 1 (not in the setup form UI)
- Replace Entitlements/Access conflicts tabs with flat list of 4 scope types
- Move user/account/grant filtering outside the Steps component
- Simplify template Step 3 to reference single campaign flow instead of duplicating
- Add guidance on when to duplicate a campaign vs create a template
- Update cross-references and FAQ wording
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants