Document access conflict scope type for campaigns#111
Closed
c1-dev-bot[bot] wants to merge 1 commit intomainfrom
Closed
Document access conflict scope type for campaigns#111c1-dev-bot[bot] wants to merge 1 commit intomainfrom
c1-dev-bot[bot] wants to merge 1 commit intomainfrom
Conversation
Add documentation for the new "By Access Conflicts" review type that allows campaigns to be scoped by conflict monitors instead of entitlements. - Update campaigns.mdx with Review type field and tabbed scope instructions - Add campaign cross-reference to access-conflicts.mdx - Add release notes entry for the feature
|
Closing — this was auto-generated against the release notes ticket (GOV-379) by mistake. The correct docs PR is #112 (linked to GOV-380). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
campaigns.mdx) to document the new Review type field in campaign setup for both single-instance campaigns and templatesaccess-conflicts.mdx) linking to the campaign scope featureFiles changed
product/admin/campaigns.mdx— Added Review type field to Step 1, added tabbed scope instructions in Step 3 for both single campaigns and templatesproduct/admin/access-conflicts.mdx— Added "Review access conflicts in a campaign" section with cross-referenceproduct/release-notes.mdx— Added release notes entry for the access conflict scope type featureAutomated PR Notice
This PR was automatically created by c1-dev-bot as a potential documentation update.
This documentation requires: