docs: Document Form-mode Policies notification channel dropdowns (Inherit / Disabled / channel)#747
Open
promptless[bot] wants to merge 1 commit into
Open
Conversation
… Disabled / channel)
![promptless[bot]](https://avatars.githubusercontent.com/in/979718?s=60&v=4){kind=small}
| ### Set notification channels in Form mode | ||
|
|
||
| On the **Policies** tab, both the default policy and each rule expose a dropdown per notification channel—Slack and Microsoft Teams—rather than a free-text field. On a rule, the option you pick maps directly to the tri-state resolution described under [Policy fields](#policy-fields): | ||
|
|
Contributor
Author
There was a problem hiding this comment.
PR #3773 made each Form-mode notification channel a single NotificationChannelSelect in PoliciesSection.tsx with Inherit (omit the field), Disabled (→ null), or a channel; the default overlay shows "No notifications". The option labels documented here (channelInheritLabel, channelDisabledLabel, channelNoneLabel, msteamsNoneLabel) come from policyValidation.ts's POLICY_COPY, and the Teams paste-fallback supporting inherit/route but not disable is called out in the PR's dashboard-mirror notes.
Source: https://github.com/Promptless/promptless/pull/3773
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
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.
Open this suggestion in Promptless to view citations and reasoning process
Documents how notification channels behave in the dashboard's Form-mode Policies editor, mirroring the YAML tri-state contract. Adds a "Set notification channels in Form mode" subsection to the Configuration Reference explaining the per-channel dropdown options (Inherit from default, Disabled — no Slack/Teams notifications, or a channel), the default policy's "No Slack/Teams notifications" option, and the Teams paste-fallback limitation (inherit/route but not disable → use YAML
msteams_channel: null).Closes a gap left by merged docs PR #648, which documented the YAML
nulltri-state but not the dashboard editor a Form-mode user would reach. Grounded against the live dashboard Policies editor.Trigger Events
Tip: Use Vale? Point your collection at your vale.ini in Configuration.