crewship notifychannel
Manage outbound notification channels for email, signed webhooks, and chat or push providers.notify-channel. All commands require an
authenticated CLI session and a selected workspace. Workspace-channel writes
require ADMIN or OWNER; --personal makes an added channel personal and
available to its owner in that user’s preference matrix.
Subcommands
crewship notifychannel add
For chat channels,
--provider and either one or more --field arguments or
an advanced pre-composed --url are required. A created webhook secret or
chat service URL is shown once, so save it when the command prints it.
crewship notifychannel providers
List the providers enabled or disabled on the instance:
--provider <name> prints that provider’s category and form fields. Pass those
field keys to add or test-draft as repeated --field key=value arguments.
Administrators can change the instance allowlist:
ADMIN or
OWNER.
Testing and diagnostics
Send a test through an existing channel, or verify settings before saving:test-draft accepts --type, --url, --to, --provider, repeated
--field, and optional --secret. It sends one test and stores nothing.
Inspect delivery outcomes with optional filters:
Agent access
Agents have no channel access by default. Pair an agent with a channel before allowing it to send notifications itself:allow and deny require the --agent flag. Pairing follows the channel’s
authority: ADMIN or OWNER for workspace channels, and the channel owner for
a personal channel.
Delete a channel
Deletion prompts for confirmation unless--yes is supplied. This is useful
for scripts and non-interactive jobs:
Related commands
crewship notify prefs— choose which categories reach which channels.- Outbound notifications — delivery categories and preference behavior.